Good morning,
I have been trying to get our DNS servers changed from Bind to tinydns
for some time now. I've already installed dnscache on all web and email
servers with great success. We are now faced with a complete IP
changeover in the next thirty days (we are an ISP and hosting provider).
I have convinced the powers that be that this would be an excellent time
to change our DNS servers.
My plan so far is to install a new tinydns server in our local NOC, and
three additional tinydns servers in our remote NOCs. Make all changes to
the local(master) server and push those changes out to the remote
servers via rsync.
As for supporting the old Bind servers during the roll out I am thinking
of making them slaves to the new local tinydns server. This would
require only a change to the named.conf file and a reload.
All pretty standard I think.
So my question is this,
Currently our Bind servers "act" as primary name servers for a few
clients. In practice they are slaves. This was done so that the clients
could manage their own DNS but allow the public to use our distributed
name servers.
I have found several suggestions for how to make tinydns act as a slave
for a Bind server, but nothing on how to make tinydns act as a slave for
only a few zones. Currently I am thinking the best option, since we will
be maintaining the domain data in a DB, is to parse the logs watching
for a notify, do axfr on the zone we are being notified on, insert the
changes into the DB, and remake the tinydns data file.
Does that sound reasonable or has anyone already tripped on this?
Thanks,
DAve
--
Three years now I've asked Google why they don't have a
logo change for Memorial Day. Why do they choose to do logos
for other non-international holidays, but nothing for
Veterans?
Maybe they forgot who made that choice possible.
|