[Pdns-users] Missing SQL upgrade line for 3.3.x => 3.4.x and allow-axfr-ips change?

Nicky Gerritsen nickygerritsen at me.com
Sat Dec 26 11:18:41 UTC 2015

Hi all!

I was updating my PowerDNS 3.3 to 3.4 (what better to do during Christmas right?).
All worked fine, until I wanted to AXFR a zone to my secondary DNS. At first I didn’t know what went wrong, but then I saw that syslog told me the “account” field was missing in a query.

Comparing a 3.3->3.4 upgrade database to a 3.4 database, I say my domain table did not have a “account” field. So it seems the following line is missing from the 3.3->3.4 SQL upgrade snippet:
ALTER TABLE domains add account VARCHAR(40) DEFAULT NULL;

Furthermore: shouldn't “account” be NON NULL and default to the empty string? This is the case for account-fields in other tables?

A second thing: when I fixed this, I still got AXFR errors. It told me my secondary DNS did not have AXFR permissions.
On my master I did not configure “allow-axfr-ips” and the docs then say every server is allowed AXFR. However, as soon as I added the IP addresses (ipv4 and ipv6) of my secondary DNS to this config option, it did work.
So is the meaning of this value changed? If so, maybe the docs should be updated :).

Have a nice christmas!



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20151226/9b9c2974/attachment.sig>

More information about the Pdns-users mailing list