[Pdns-users] AXFR tranfers from master to slave with URL forward gives error

[Ton van Rosmalen]

Hi Frank,

Frank van den Diepstraten schreef:
>
> Hi,
>
>  
>
> 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
> errors:
>
>  
>
> Mar 15 09:56:57 ns2 pdns[13082]: 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[13082]: Initiating transfer of
> 'test-cict-1.nl' from remote 'x.x.x.x'
>
> Mar 15 09:56:58 ns2 pdns[13082]: AXFR started for 'test-cict-1.nl',
> transaction started
>
> Mar 15 09:56:58 ns2 pdns[13082]: Unable to AXFR zone 'test-cict-1.nl'
> from remote 'x.x.x.x': EOF trying to read axfr chunk from remote TCP
> client
>
> Mar 15 09:56:58 ns2 pdns[13082]: Aborting possible open transaction
> for domain 'test-cict-1.nl' AXFR
>
> Mar 15 09:57:00 ns2 pdns[13082]: 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.

Good luck.

Regards,

Ton