[Pdns-users] Problems with NSD as slave to PowerDNS

[bert hubert]

> Jul 16 13:52:36 atpcz2pc pdns[29554]: 1 domain for which we are master needs notifications
> Jul 16 13:52:36 atpcz2pc pdns[29554]: Queued notification of domain '7.0.3.e164.arpa' to 158.226.218.54
> Jul 16 13:52:37 atpcz2pc pdns[29554]: No question section in packet from 158.226.218.54, rcode=3
> Jul 16 13:52:37 atpcz2pc pdns[29554]: Unable to parse SOA notification answer from 158.226.218.54

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.

Good luck!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://netherlabs.nl              Open and Closed source services