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

[Ton van Rosmalen]

Hi Frank,

Frank van den Diepstraten schreef:
> Sorry I didn't gave all the syslog output. Hereby the log information:
>
> Mar 15 12:10:32 ns1 pdns[16236]: AXFR of domain 'test-cict-1.nl' initiated by x.x.x.x
> Mar 15 12:10:32 ns1 pdns[16236]: gmysql Connection succesful
> Mar 15 12:10:32 ns1 pdns[16236]: Exception: Unknown record was stored incorrectly, need 3 fields, got 1: http://www.bla.nl
> Mar 15 12:10:32 ns1 pdns[16236]: TCP Connection Thread died because of STL error: Unknown record was stored incorrectly, need 3 fields, got 1: http://www.bla.nl
>
> I found something on the internet about it:
>
> http://wiki.powerdns.com/trac/ticket/156
>
> unfortunately I use the package manager and do not prefere to compile the given patch (above) manually. Is there another option to get this working? I can't find any newer powerdns versions where this problem is solved (CS 1464).
>
>   
I justed test my 2.9.22 install with a URL-record and have confirmed the
AXFR-problem. The URL-redirector does work on my master but changes
aren't propagated to the slaves.
I created a ticket (#285) in the bugtracker and will try to get more
information if time allows.

For now I don't see any other options other than either keep on using
your current release of pdns of find some other means of propagating the
changes from the master to the slave (e.g. mysql replication).

Regards,

Ton van Rosmalen

> Hope to hear from you.
>
> Regards,
>
> Frank van den Diepstraten. 
>
> -----Oorspronkelijk bericht-----
> Van: Frank van den Diepstraten 
> Verzonden: maandag 15 maart 2010 12:00
> Aan: 'Ton van Rosmalen'
> CC: pdns-users at mailman.powerdns.com
> Onderwerp: RE: [Pdns-users] AXFR tranfers from master to slave with URL forward gives error
>
> Hi Ton,
>
> Thank you for responding. I've turned the loglevel to 9 (highest) and get the following output on the master:
>
> ns1 pdns[16091]: 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 213.197.27.201#53: end of file
>
> It doesn't really tell me more.....
>
>
> -----Oorspronkelijk bericht-----
> 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
>
> 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
>