Derek Atkins writes:
Setting up axfr is simple. I list my secondaries, and they just say
"master <my-ip-adderess>". There. Done. End of configuration. How
could setting up a secondary be any easier than that?
What do you do when you change named.conf---for example, to add a zone?
You have to copy the changes to the secondary. With server replication,
this is handled automatically.
Well, perhaps this is as good a time as any to raise the fact that I've
been working on an "auto-slaving" mechanism. The basic idea is that upon
receipt of a signed NOTIFY from a particular entity, a slave can, if
configured to do so, automatically configure itself as a slave for the
zone being NOTIFY'ed. I've already started implementing this in the BIND
9 codebase, but the general concept is not implementation-specific and
could conceivably be supported by any implementation that handles signed
NOTIFYs.