Best method - secondary for lots of domains

[Kevin Darcy]

If you've already gone through the trouble of setting up rsync between your master and its slaves, and it's doing the job, why re-architect it? If you wanted to make the system more responsive to changes, you could probably improve it incrementally by using the receipt of a NOTIFY to trigger an rsync
transaction on the slave. Unfortunately, since BIND doesn't support spawning external programs in response to receipt of a NOTIFY (and there would be serious security concerns in doing so), you'd have to have something watching the slave's logs to know that a NOTIFY was received. You'd also want to
put in some sort of rate-limiting logic to prevent thrashing and/or Denial of Service attacks.

                                                                                                                                                         - Kevin

Bob Puff at NLE wrote:

> Hello,
>
> I've got two Bind 8 servers running.  I've got what seems to be good DNS records for the domains I serve.  I am frequently adding new domains.
>
> My secondary server I currently have simply doing an RSYNC to the primary's /var/named directory, and copy over the named.conf file every night.  So the secondary is really acting like another master.
>
> I'd rather let the notifys do the job, but how do you handle new records?  Do you have to keep editing the config file on the secondary also?  I'd like to only have to mess with the records on one machine, and have the secondary simply be a mirror; but it needs to handle adding / deleting domains.
>
> Bob