RE: [Pdns-users] Problems with NSD as slave to PowerDNS
Hi Bert, Thanks for quick reply :) An error in NSD configuration was causing this problem. I was missing "AXFR" in nsd.conf for the zone. request-xfr: 158.226.218.55 NOKEY -> request-xfr: AXFR 158.226.218.55 NOKEY Jul 16 16:23:47 atpcz2pc pdns[31690]: AXFR of domain '7.0.3.e164.arpa' initiated by 158.226.218.54 Jul 16 16:23:47 atpcz2pc pdns[31690]: gpgsql Connection succesful Jul 16 16:23:47 atpcz2pc pdns[31690]: AXFR of domain '7.0.3.e164.arpa' to 158.226.218.54 finished Best Regards / Mit freundlichen Grüßen / Pozdrav, .. Tomislav Crljen Siemens d.d. Program and System Engineering PSE CSS MPS1 Zupanijska 21/5 HR-31000 Osijek Croatia Phone: + 385 (31) 23 49 59 Fax: + 385 (31) 23 49 03 Mobile: + 385 (98) 44 32 34 mailto:[EMAIL PROTECTED] http://www.siemens.hr -Original Message- From: bert hubert [mailto:[EMAIL PROTECTED] Sent: Monday, July 16, 2007 4:06 PM To: Crljen, Tomislav Cc: pdns-users@mailman.powerdns.com Subject: Re: [Pdns-users] Problems with NSD as slave to PowerDNS > 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 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Problems with NSD as slave to PowerDNS
> 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 ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
[Pdns-users] Problems with NSD as slave to PowerDNS
Hi, I am having problems with AXFR from PowerDNS to a NSD slave. Following errors are logged: 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 Jul 16 13:52:39 atpcz2pc pdns[29554]: No master domains need notifications Jul 16 13:52:39 atpcz2pc pdns[29554]: No question section in packet from 158.226.218.54, rcode=3 Jul 16 13:52:39 atpcz2pc pdns[29554]: Unable to parse SOA notification answer from 158.226.218.54 Jul 16 13:52:44 atpcz2pc pdns[29554]: No question section in packet from 158.226.218.54, rcode=3 Jul 16 13:52:44 atpcz2pc pdns[29554]: Unable to parse SOA notification answer from 158.226.218.54 Jul 16 13:52:53 atpcz2pc pdns[29554]: No question section in packet from 158.226.218.54, rcode=3 Jul 16 13:52:53 atpcz2pc pdns[29554]: Unable to parse SOA notification answer from 158.226.218.54 The AXFR of the same zone works fine when the slave is BIND9: Jul 16 15:42:42 atpcz2pc pdns[29917]: AXFR of domain '7.0.3.e164.arpa' initiated by 158.226.197.179 Jul 16 15:42:42 atpcz2pc pdns[29917]: gpgsql Connection succesful Jul 16 15:42:42 atpcz2pc pdns[29917]: AXFR of domain '7.0.3.e164.arpa' to 158.226.197.179 finished Did anybody have similar problems, and how did you solve it? Thanks in advance. Best Regards / Mit freundlichen Grüßen / Pozdrav, .. Tomislav Crljen Siemens d.d. Program and System Engineering SIS PSE CSS MPS Zupanijska 21/5 HR-31000 Osijek Croatia Phone: + 385 (31) 23 49 59 Fax: + 385 (31) 23 49 03 Mobile: + 385 (98) 44 32 34 mailto:[EMAIL PROTECTED] http://www.siemens.hr ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
