Bind slave not updating

posted by | Leave a comment

Thanks Well one thing you are clearly missing in [b]named.conf[/b] of your slave DNS servers, are slave zone declarations along with location where to commit this data (and retrieve it from afterward).

Your slaves' [b]named.conf[/b] need to contain zone declaration like: [b] zone "" IN ; [/b] This way your slaves will create zone data-files in [b]/var/named/chroot/var/named/slaves/[/b] folder with appropriate SE Linux context.

bind slave not updating-63bind slave not updating-53bind slave not updating-11

Also makes things much easier to add more slave servers. If the zone has changed(new serial number), the slave will initiate a zone transfer on its own without the need to run any scripts.

This is it, so I hope this might be able to help someone else: [code] #!

/bin/bash cd /var/named/chroot/etc/ #store number of lines in conf file lines=`cat | wc -l` # bc calculates how many lines to tail - header modifylines=`echo "$lines-27" | bc` #write the header to a file (first 27 lines) head -27 /var/named/chroot/etc/named_slave/named.conf2 rm tail head fwd slave tailnew rev # rsync it over to secondary rsync -e ssh -avzl P /var/named/chroot/etc/named_slave/[email protected]:/var/named/chroot/etc/. 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.

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.

Leave a Reply

Free chat fuck no sighn up