Bind slave server not updating

I do not think that this will handle setting up zones but it will propagate changes made in the zones that are defined on both master and slave servers.

We use a mixture of nsupdate and dhcp to update our internal zones and those updates do get sent to the slaves.#!

Once I edit the slave server file manually and add the zone entry for the newly registered/created domain and reload named then db files are getting created without any issue. Again I am mentioning it here why zone record are not getting appended to at slave server when I add a new domain name at master server.

bind slave server not updating-20bind slave server not updating-36

The 3 servers are tentatively installed on a Xen virtual server for testing purposes.

All 3 servers are 64bit and installed with:-Stopping named: [ OK ]Starting named: [ OK ]Jan 27 ns1 named[6103]: using default UDP/IPv6 port range: [1024, 65535]Jan 27 ns1 named[6103]: listening on IPv4 interface lo, 127.0.0.1#53Jan 27 ns1 named[6103]: listening on IPv4 interface eth0, 10.2.37.202#53Jan 27 ns1 named[6103]: command channel listening on 127.0.0.1#953Jan 27 ns1 named[6103]: command channel listening on ::1#953Jan 27 ns1 named[6103]: zone 0.168.192.in-addr.arpa/IN: loaded serial 100Jan 27 ns1 named[6103]: zone yourdomain.com/IN: loaded serial 100Jan 27 ns1 named[6103]: running Jan 27 ns1 named[6103]: zone yourdomain.com/IN: sending notifies (serial 100)Jan 27 ns1 named[6103]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 100)Stopping named: [ OK ]Starting named: [ OK ]Jan 27 ns2 named[5965]: found 2 CPUs, using 2 worker threads Jan 27 ns2 named[5965]: using up to 4096 sockets Jan 27 ns2 named[5965]: loading configuration from '/etc/named.conf'Jan 27 ns2 named[5965]: using default UDP/IPv4 port range: [1024, 65535]Jan 27 ns2 named[5965]: using default UDP/IPv6 port range: [1024, 65535]Jan 27 ns2 named[5965]: listening on IPv4 interface lo, 127.0.0.1#53Jan 27 ns2 named[5965]: listening on IPv4 interface eth0, 10.2.37.214#53Jan 27 ns2 named[5965]: command channel listening on 127.0.0.1#953Jan 27 ns2 named[5965]: command channel listening on ::1#953Jan 27 ns2 named[5965]: running Stopping named: [ OK ]Starting named: [ OK ]Jan 27 ns3 named[5874]: found 2 CPUs, using 2 worker threads Jan 27 ns3 named[5874]: using up to 4096 sockets Jan 27 ns3 named[5874]: loading configuration from '/etc/named.conf'Jan 27 ns3 named[5874]: using default UDP/IPv4 port range: [1024, 65535]Jan 27 ns3 named[5874]: using default UDP/IPv6 port range: [1024, 65535]Jan 27 ns3 named[5874]: listening on IPv4 interface lo, 127.0.0.1#53Jan 27 ns3 named[5874]: listening on IPv4 interface eth0, 10.2.37.225#53Jan 27 ns3 named[5874]: command channel listening on 127.0.0.1#953Jan 27 ns3 named[5874]: command channel listening on ::1#953Jan 27 ns3 named[5874]: running Jan 28 ns1 named[1465]: client 10.2.37.214#50135: transfer of 'yourdomain.com/IN': AXFR started Jan 28 ns1 named[1465]: client 10.2.37.214#50135: transfer of 'yourdomain.com/IN': AXFR ended Jan 28 ns1 named[1465]: client 10.2.37.225#52508: transfer of 'yourdomain.com/IN': AXFR started Jan 28 ns1 named[1465]: client 10.2.37.225#52508: transfer of 'yourdomain.com/IN': AXFR ended Jan 28 ns2 named[1445]: zone yourdomain.com/IN: Transfer started.

Hi all, I have set up a master BIND DNS server with 2 slaves.

All the services start up fine on all 3 servers, but zones and info is not being replicated.

Right now it just waits for TTL expiration on the slaves.

Any way to easily fix this, or is it a bug/feature request?It is a relatively simple task to write a script that reads the master config and turns it into a config suitable for the slaves.Once you have this config you can then scp it to the slaves and then reload bind. Hi there, I am also just glad that it seems my configuration is good. I must admit though that my scripting/programming skills are not all that good.My configs are now as follows: Master server:# vi /var/named/chroot/etc/Feb 4 ns1 named[10157]: command channel listening on 127.0.0.1#953Feb 4 ns1 named[10157]: zone 0.168.192.in-addr.arpa/IN: loaded serial 101Feb 4 ns1 named[10157]: zone test1.com/IN: loaded serial 101Feb 4 ns1 named[10157]: zone yourdomain.com/IN: loaded serial 101Feb 4 ns1 named[10157]: running Feb 4 ns1 named[10157]: zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 101)Feb 4 ns1 named[10157]: zone yourdomain.com/IN: sending notifies (serial 101)Feb 4 ns1 named[10157]: zone test1.com/IN: sending notifies (serial 101) entry. As currently I am testing on only 3 BIND DNS servers, but we will end up having close to 8 servers at all our branches.And to do such a task manually is really not viable. Please help Thanks As far as I am aware you need to write scripts to automate the configuration transfer between the master and the slaves./bin/bashcd /var/named/chroot/etc/#store number of lines in conf filelines=`cat | wc -l`# bc calculates how many lines to tail - headermodifylines=`echo "$lines-27" | bc`#write the header to a file (first 27 lines)head -27 /var/named/chroot/etc/named_slave/named.conf2rm tail head fwd slave tailnew rev# rsync it over to secondaryrsync -e ssh -avzl P /var/named/chroot/etc/named_slave/[email protected]:/var/named/chroot/etc/ns2.server "service named reload"rsync -e ssh -avzl P /var/named/chroot/etc/named_slave/named.conf2 [email protected]:/var/named/chroot/etc/named.confssh ns3.server "service named reload"service named reload WOW! I think there is an easier way and please correct me if I'm wrong: According to the theory of DNS, authoritative DNS servers, that is master DNS servers, have TTL(time-to-live) and serial number values specified in the SOA record for each zone.

Tags: , ,