[Pdns-users] PowerDNS does not contain changeset 2217

Peter van Dijk peter.van.dijk at netherlabs.nl
Thu Dec 13 08:23:40 UTC 2012

Hello Chuyen,

On Dec 13, 2012, at 9:21 , Vo Dai Chuyen wrote:

> Very clear ! Thank Peter so much !
> Actually, I'm considering upgrade to 3.1 and doing some testing. Actually, we had run one authoritative name server version 3.1 with the old database schema from 2.9.22 and it just works fine but we need to be sure it does not encounter any troubles and we don't need DNSSEC and maybe it's OK for us to upgrade directly. 

It usually is, but make sure to run 'pdnssec check-all-zones'. 3.1 is stricter in some areas, especially when some domains are missing their SOA.

> One concern is that do I need to change the SQL shema while upgrade the authoritative from 2.9.22 to 3.1 as in the document describe from http://doc.powerdns.com/from3.0to3.1.html
> mysql> ALTER TABLE records MODIFY content VARCHAR(64000);
> mysql> ALTER TABLE tsigkeys MODIFY algorithm VARCHAR(50);

The records change is recommended for all versions, including 2.9, really.

The tsigkeys change only applies if you have upgraded your schema to support DNSSEC (and if you do that now, you will already, probably, get the right size for tsigkeys).

Kind regards,
Peter van Dijk
Netherlabs Computer Consulting BV - http://www.netherlabs.nl/

More information about the Pdns-users mailing list