[Pdns-users] PowerDNS 220.127.116.11 does not contain changeset 2217
Vo Dai Chuyen
vdchuyen at gmail.com
Thu Dec 13 08:21:00 UTC 2012
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.
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
mysql> ALTER TABLE records MODIFY content VARCHAR(64000);
mysql> ALTER TABLE tsigkeys MODIFY algorithm VARCHAR(50);
We had run powerdns for several years and found it very stable.
Thanks again Powerdns team.
On Thu, Dec 13, 2012 at 2:56 PM, Peter van Dijk <
peter.van.dijk at netherlabs.nl> wrote:
> Hello Chuyen,
> On Dec 13, 2012, at 2:40 , Vo Dai Chuyen wrote:
> > I've just upgraded our authoritative from 2.9.22 to 18.104.22.168 to get
> latest security updates but I can not find change set 2217 included.
> > http://wiki.powerdns.com/projects/trac/changeset/2217
> > Our setup uses DB sync and the authoritative had this problem once so I
> may need this change. So I wonder why we don't merge this change in
> 2.9.22.x. Do I have to patch manually this change to get
> overload-queue-length set ?
> The patches for 22.214.171.124/126.96.36.199 were selected very carefully, and
> limited to those we found most important. We recommend upgrading to 3.1 or
> Of course, you are indeed free to backport patches for yourself!
> Kind regards,
> Peter van Dijk
> Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pdns-users