[Pdns-users] AXFR tranfers from master to slave with URL forward gives error
Frank van den Diepstraten
frank.van.den.diepstraten at concepts-ict.nl
Mon Mar 15 10:59:54 UTC 2010
Thank you for responding. I've turned the loglevel to 9 (highest) and get the following output on the master:
ns1 pdns: AXFR of domain 'test-cict-1.nl' initiated by x.x.x.x
The output of the dig says:
dig @x.x.x.x test-cict-1.nl AXFR
; <<>> DiG 9.5.1-P3 <<>> @x.x.x.x test-cict-1.nl AXFR
; (1 server found)
;; global options: printcmd
test-cict-1.nl. 3600 IN SOA ns1. postmaster.concepts.nl. 2010031511 28800 7200 604800 86400
;; communications error to 188.8.131.52#53: end of file
It doesn't really tell me more.....
Van: Ton van Rosmalen [mailto:ton at netbase.nl]
Verzonden: maandag 15 maart 2010 10:58
Aan: Frank van den Diepstraten
CC: pdns-users at mailman.powerdns.com
Onderwerp: Re: [Pdns-users] AXFR tranfers from master to slave with URL forward gives error
Frank van den Diepstraten schreef:
> I recently posted the question underneath. While I kept searching I
> found that I had to upgrade to the 2.9.22 version to get the fancy
> records (URL in my case) AXFR’ed to my secondary name server again.
> I just upgraded both my nameservers from version 2.9.21-2 to version
> 2.9.22 which is a debian lenny-backports package. But still I get the
> Mar 15 09:56:57 ns2 pdns: Received valid NOTIFY for
> test-cict-1.nl (id=5420) from master x.x.x.x: 2010031505 > 2010031504
> Mar 15 09:56:58 ns2 pdns: Initiating transfer of
> 'test-cict-1.nl' from remote 'x.x.x.x'
> Mar 15 09:56:58 ns2 pdns: AXFR started for 'test-cict-1.nl',
> transaction started
> Mar 15 09:56:58 ns2 pdns: Unable to AXFR zone 'test-cict-1.nl'
> from remote 'x.x.x.x': EOF trying to read axfr chunk from remote TCP
> Mar 15 09:56:58 ns2 pdns: Aborting possible open transaction
> for domain 'test-cict-1.nl' AXFR
> Mar 15 09:57:00 ns2 pdns: Received NOTIFY for test-cict-1.nl
> from x.x.x.x, we are up to date: 2010031505<=2010031505
> Is there someone who can help me with this issue? Please respond….
I don't use the fancy-records myself but my first step would be to turn
on debugging on the master and execute a manual dig @<master> <zone> AXFR
Digging in the source code for possible changes with regard to fancy
records and axfr might give you a clue whether anything has changed in pdns.
More information about the Pdns-users