[Pdns-users] MASTER/SLAVE problems

Martin Kuchar lists at nss.wproduction.cz
Fri May 28 10:00:13 UTC 2004


master say:
May 27 22:42:17 ns pdns[6107]: Queued notification of domain 'supernews.cz'
to 81.0.239.51
May 27 22:42:18 ns pdns[6107]: Removed from notification list:
'supernews.cz' to 81.0.239.51 (was acknowledged)
May 27 22:42:20 ns pdns[6107]: No master domains need notifications

slave say:
May 27 22:42:05 ns pdns[23496]: Received NOTIFY for supernews.cz from master
194.213.231.160, we are up to date: 1085674507<=2003072300

Martin


> Martin Kuchar wrote:
> > I update serial for supernews.cz on server 1, whis is 
> master. Server 1 sends
> > notfication to server 2, which is slave. Server 2 claims, 
> that domain
> > supernews.cz have low (still the old) serial.
> > 
> > Play here a role cache on server 1 ??? In cache is the old serial.
> > 
> > Do i need to "pdns_control purge supernews.cz" and then 
> "pdns_control notify
> > supernews.cz" (because server 1 dont send another 
> notification after cache
> > purge) ??
> 
> Does the slave server claim to have received the NOTIFY? What does it 
> say it did with it? Did it say something like:
> 
> Received valid NOTIFY for domain.tld (id=1) from master 192.168.3.2: 
> NNNNNNNNN > MMMMMMMMM
> 
> Did it then say:
> 
> AXFR started for 'domain.tld', transaction started
> AXFR done for 'domain.tld', transaction complete
> 
> Without log entries or something, it's hard to diagnose. I'm using 
> PowerDNS as a slave for our customers (for our own DNS, I've 
> switched to 
> using DB-native replication), and it handles the NOTIFYs just fine.
> 
> -- 
> Derrik Pates
> dpates at dsdk12.net




More information about the Pdns-users mailing list