replicating dynamicly updated servers..

John Hascall john at
Wed Sep 6 14:19:42 UTC 2006

[multiple masters]

One other option may be appropriate if you, like us,
do not use bind as your authoratative data source,
but rather have something else (e.g., a DB) which
is your master repository.

We configure all the servers to think they are masters
and that there are no slaves.  Then when the DB has an
update to push out, it "nsupdates" each server.  Of course,
the ISC nsupdate can't do this, but it's not that complicated
to roll your own (our "dnsupd" library is only ~400 lines).


More information about the bind-users mailing list