From: Peter van Dijk Date: Fri, 23 Mar 2012 09:29:35 +0000 (+0000) Subject: doc updates, including very minor extra notes about upgrading to 3.1 X-Git-Tag: auth-3.1-rc1 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8f37a49de1017166b1001637174959afe04a7cc9;p=pdns doc updates, including very minor extra notes about upgrading to 3.1 git-svn-id: svn://svn.powerdns.com/pdns/trunk/pdns@2526 d19b8d6e-7fed-0310-83ef-9ca221ded41b --- diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml index add41f5b8..80a1489c7 100644 --- a/pdns/docs/pdns.xml +++ b/pdns/docs/pdns.xml @@ -10345,14 +10345,6 @@ local0.err /var/log/pdns.err - - --startid - - - Supply a value for the first domain_id generated. Defaults at 0. - - - --transactions @@ -10498,6 +10490,11 @@ local0.err /var/log/pdns.err From PowerDNS Authoritative Server 3.0 to 3.1 + + + If you are coming from 2.9.x, please also read . + + PowerDNS 3.1 introduces native SQLite3 support for storing key material for DNSSEC in the bindbackend. With this change, support for bind+gsql-setups ('hybrid mode') has been dropped. If you were using this mode, you will need to switch to @@ -10506,6 +10503,13 @@ local0.err /var/log/pdns.err There have been changes to the SQL schemas for the generic backends. + + For MySQL: + + mysql> ALTER TABLE records MODIFY content VARCHAR(64000); + mysql> ALTER TABLE tsigkeys MODIFY algorithm VARCHAR(50); + + @@ -11135,7 +11139,7 @@ $ pdnssec rectify-zone powerdnssec.org This mode is only supported in 3.0 and 3.0.1! In 3.1 and up, the bindbackend - always does its own key storage. See FIXME for more details. + always does its own key storage.