[Pdns-users] IPV6 ARPA AXFR problem

[Peter van Dijk]

Hello Dennis,

On Oct 12, 2012, at 11:55 , dennis w wrote:

> We have a master-slave setup with PowerDNS version 3.1 (both servers).
> Domains and IPv4 arpa records be transferred properly to the second server.
> 
> Our ip6.arpa zone will not transfer to the second server.
> The SOA serial from that zone will be updated on both nodes.
> 
> The second server log file:
> 
> Oct 12 10:44:07 ns2 pdns[1299]: Domain xxxxx.ip6.arpa is stale, master serial 2012101203, our serial 2012101202
> Oct 12 10:44:07 ns2 pdns[1299]: Initiating transfer of 'xxxxx.ip6.arpa' from remote 'xx.xx.xx.xxx'
> Oct 12 10:44:07 ns2 pdns[1299]: AXFR started for 'xxxxx.ip6.arpa', transaction started
> Oct 12 10:44:07 ns2 pdns[1299]: Unable to parse record during incoming AXFR of 'xxxxx.ip6.arpa' (MOADNSException): Loop
> Oct 12 10:44:07 ns2 pdns[1299]: Aborting possible open transaction for domain 'xxxxx.ip6.arpa' AXFR
> Oct 12 10:44:09 ns2 pdns[1299]: Received NOTIFY for xxxxx.ip6.arpa from 2a00:xxx:x::5 which is not a master
> Oct 12 10:44:16 ns2 pdns[1299]: Received NOTIFY for xxxxx.ip6.arpa from 2a00:xxx:x::5 which is not a master
> Oct 12 10:44:25 ns2 pdns[1299]: Received NOTIFY for xxxxx.ip6.arpa from 2a00:xxx:x::5 which is not a master
> 
> 
> A XFR transfer with DIG from the second server displays all the correct records.
> 
> dig -t axfr xxxxx.ip6.arpa @xx.xx.xx.xxx
> 
> 
> Possible bug?

Possible bug, or possible wrong data in your zone. Please run 'pdnssec check-zone xxxx.ip6.arpa' on your master. If that does not help, then please provide the xxxxx.ip6.arpa zone from the master in whatever format is native for you (BIND zone file, MySQL dump, etc.). Thanks.

Kind regards,
-- 
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/