Ok, my last version of the dns sync setup...
Note that this version has NO protection against double zones, so Bind will crash and burn if it should detect double zones.
This version does have logging by default to a /var/log/namedsync file.
As this is a 'service' ran by the root user, this should not pose a problem (root is needed to reload Bind if changes are detected).
Actually, each nameserver will act as a master server so the .db zone files are needed. Unless there is a way those can be autogenerated that I don't know about.
As you can see in my example below, there is no need to let the 'master' nameserver actually be the master server when looking at the DNS.
I usually build a setup in which the master server is the server where the clients are on, and the slave server is the actual primary nameserver (or master) for the domains.
Only problem is, this version of the dns syncer isn't an version I'm proud of, there are a lot of things that can be different (and should be different).
DO NOT USE THESE IN PRODUCTION ENVIRONMENT
The file that's ran on the DA server that has the customers on it is:
http://montu.sebsoft.nl/Jeff/named.sh
The actual synchronisation works with the following file:
http://montu.sebsoft.nl/Jeff/fetch.montu.sh
Both files are ran in a cronjob syncing every 30 minutes. DNS changes are transferred by Bind from master to slave whenever slave checks if there are differences (which happens every x minutes (thought this was 30 min or something)).
Note that I do not support this version, nor should it be used in a production environment by someone who doesn't know exactly how DNS works.
As I've stated in other threads, if Jeff doesn't finish his version within a month or 2, I'll ask him to send me everything he has, so I might be able to finish it.
The license on my version is subject to change, so I would recommend you just look at it for reference purposes, don't use it and wait until Jeff or me release a version that actually does have the ability to live if there are multiple zones the same...
Note that my version is also a quick set of scripts I wrote after reading up a book on how Bind can work in production environments. It was in no way meant to be published

.