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
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
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
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
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
Thank you! I will insert the URL record manually now. It only goes wrong with
the AXFR, so existing URL forwards still work. Only when I edit a zone with a
URL forward in it, it goes wrong.
I will follow the ticket carefully :)
Thanx again!
-Oorspronkelijk bericht-
Van: Ton van
Hi Frank,
I just closed the ticket for now because I misread the dates on commit
1464.
There is a patch available in the current pdns-source which should
solve the problem you're seeing.
The patch outputs the an A-record when a URL-record is encountered on
the master and a MX-record when a
