Hi, I just started trying out Vegadns and one of the first things I noticed was that, unless clocks are synced, CPU and network load on the nameservers equal, then the SOA serial generated by tinydns-data can hardly be guaranteed to be the same. Although tinydns won't care about this it doesn't look particularly good to the outside world since it leads people to believe that there might be some discrepances between the servers if serials differ.
I guess you could just as well add a column in the domains-table with the timestamp, but I can't/don't want to modify the database structure at this time, so instead, attatched to this mail is a patch that sort-of fixes the problem by generating a stable serial each time a "?state=get_data" request is recieved within a certain time interval.
My approach to this has been for one server to build the cdb file, and then replicate that to the other dns servers via rsync. This way, the data is identical. Also, rsync only transfers changes, and saves on bandwidth (albeit not much in this case). I believe I originally had serial number support, but removed it to just rely on tinydns' built in serial number generation.
Regards,
Bill Shupp
