Bind slave not updating dawn richard and qwanell mosley dating
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.
Just another question, If I create a new zone on the master server in "named.conf", as well as the corresponding file in [b]/var/named/chroot/var/named[/b], do I have to manually create it on both the slave servers as well ? If not automatically created in the slave server's "named.conf", is there a way to automate it ? I will have a look into the literature that you have suggested. I carefully went through all my configs and fixed anything and everything that I could find that looked faulty or mistyped or even just left out.
So now the logs show that files are being transferred.
My configs are now as follows: Master server: # vi /var/named/chroot/etc/[code] options ; key "rndc-key" ; controls ; zone "yourdomain.com" IN ; zone "0.168.192.in-addr.arpa" IN ; [/code] Both slave servers have the same config below: # vi /var/named/chroot/etc/[code] options ; key "rndc-key" ; controls ; zone "yourdomain.com" IN ; zone "0.168.192.in-addr.arpa" ; [/code] So, I tried to run a test.
So on my Master server, I added the following entry: # vi /var/named/chroot/etc/[code] zone "test1.com" IN ; [/code] I also added the zone file under: # ll /var/named/chroot/var/named/test1zone [quote] -rw-r--r-- 1 root root 325 Feb 4 /var/named/chroot/var/named/test1zone [/quote] I update the serial of the above zone file. But the new "test1" entry is not transfered to either of the slave servers.
Hi all, Thanks for all the replies and help, but I managed to find a script and make it work so that it works 100% for my needs.Here is the SOA record for my zone: $TTL 86400 ; 1 day IN SOA ns1. ( 2010013001 ; serial, I use date and a 2 digit number 10800 ; refresh (3 hours) 900 ; retry (15 minutes) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) On the /etc/on the master server you have all the relevant options I have: notify yes; allow transfer; etc. I'm happy to post full conf files, minus private info. took a bit to tweak the script to change the master entries in the "named.conf" file to slave for the slave servers, but so far it is working fine.On the /etc/on the slave servers you specify the master server for the zone. It will be great if all this can happen on the fly and we never have to really touch any of the slave server's configuration(named.conf) files.ssh ns2.server "service named reload" rsync -e ssh -avzl P /var/named/chroot/etc/named_slave/named.conf2 [email protected]:/var/named/chroot/etc/ssh ns3.server "service named reload" service named reload [/code] All changes are made to all the [b]"master"[/b] entries and replaced by [b]"slave"[/b] And as you can see the [b]named.conf[/b] file, is then rsync'd over to the initial 2 slave servers. When the TTL for the zone expires, the slave server(s), provided that they have been specified on the master's /etc/as slaves and allowed to transfer, will contact the master server to check the serial number for the zone.
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.So if you telling me that your file replicates to the slave server 100%, as well as any changed or new zone files, that is great.