On Aug 6, 2010, at 17:00 , LikeFiction wrote: > Ok, I think I found the problem. It's quite simple too. > > My zones are not changing very often. So, after my re-setup of NS2, and > restart master-powerdns, the "notified-serial" and the first digit serial of > "SOA" where the same. If notified-serial is smaller than SOA, only then > PowerDNS will do an AXFR. > > So, indeed, after setting up a new/extra nameserver, to start the transfer, > one should just run SQL: > > UPDATE domains set notified_serial=0 > > and make sure that every SOA record is NOT 0. Then, PowerDNS will start > notifying slaves.
I got put off by thinking you were provisioning a new zone and thus assuming that notified-seriel would be set to 0 or NULL by default. Alright then. Case solved. ;) > I think it might be a good idea for future versions of PowerDNS, to "force" > updating all slaves when PowerDNS is started. At first i thought this were a good feature request, but on second though this might not be what people with huge numbers of zones would want. upon restart the would have to deal with increased load in both master and slaves due to them checking their database for out-of-date zones, hence i'm doubtful if Bert would implement it this way. Also iirc there is a slow-start mechanism in place to prevent exactly this behaviour. Stefan _______________________________________________ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
