[Pdns-users] Problems with NSD as slave to PowerDNS
bert.hubert at netherlabs.nl
Mon Jul 16 14:05:50 UTC 2007
> Jul 16 13:52:36 atpcz2pc pdns: 1 domain for which we are master needs notifications
> Jul 16 13:52:36 atpcz2pc pdns: Queued notification of domain '7.0.3.e164.arpa' to 188.8.131.52
> Jul 16 13:52:37 atpcz2pc pdns: No question section in packet from 184.108.40.206, rcode=3
> Jul 16 13:52:37 atpcz2pc pdns: Unable to parse SOA notification answer from 220.127.116.11
This is NSD that answers 'NXDOMAIN' for the SOA notification (which is rcode
3). Additionally, PowerDNS can't parse the answer from NSD.
Can you double check NSD knows it should slave 7.0.3.e164.arpa from you?
Perhaps NSD logs something?
Please let us know, interoperability with NSD is important for us.
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
More information about the Pdns-users