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

a b tripivceta at hotmail.com
Sat Dec 26 13:35:59 UTC 2015

Yes, the semantics of who is allowed to perfom AXFR's have changed.
I got busted by this as well, several months back, because it didn't occur to me that a sift through the change logs before upgrade is mandatory.

At the time, I had suggested that backward compatibility be made a goal for pdns 4.# series, but as far as I recall, it did not elicit any comments. I let it go at that.
From: pdns-users-bounces at mailman.powerdns.com [pdns-users-bounces at mailman.powerdns.com] on behalf of Nicky Gerritsen [nickygerritsen at me.com]
Sent: Saturday, December 26, 2015 12:18
To: pdns-users at mailman.powerdns.com
Subject: [Pdns-users] Missing SQL upgrade line for 3.3.x => 3.4.x and   allow-axfr-ips change?

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!



More information about the Pdns-users mailing list