On Tuesday 31 March 2009 05:19 pm, Greg Nolan wrote: > This is the ideal setup. The primary will notify it's slaves (yeah, > bind uses poor terminology) when zones are updated and pull the new > zone file. Much easier then messing w/ crontab (which will delay > updates), rsync, ssh, keys.... > > LMK and I can help with configs.
As I responded previously, this was my first choice. I tried to talk the client into it for a week. He finally agreed. I honestly don't need help; We host slave DNS for many thousands of zones already; slave DNS is somthing I _do_ know how to do. One question, though... what system do you use for telling the slaving server that it needs to be authoritative for the domain (for adding the zone to the named.conf file)? My understanding is that it won't slave the zone just because the master tells it to ... it must be listed in the zone file. I have code I've written to do it but I'm curious if anyone has something better. Thanks! Jeff -- Jeff Lasman, Nobaloney Internet Services P.O. Box 52200, Riverside, CA 92517 Our jplists address used on lists is for list email only voice: +1 951 643-5345, or see: "http://www.nobaloney.net/contactus.html";
