From: Klaus Darilion Date: Mon, 30 Jan 2017 20:38:57 +0000 (+0000) Subject: add prepared statements and CAA records to the upgrade info X-Git-Tag: rec-4.1.0-alpha1~96^2~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=50f93410cd885095ee494c25cba0d789e427f1ba;p=thirdparty%2Fpdns.git add prepared statements and CAA records to the upgrade info --- diff --git a/docs/markdown/authoritative/upgrading.md b/docs/markdown/authoritative/upgrading.md index 69a5da4ca3..db63fb6511 100644 --- a/docs/markdown/authoritative/upgrading.md +++ b/docs/markdown/authoritative/upgrading.md @@ -15,6 +15,7 @@ Please upgrade to the PowerDNS Authoritative Server 4.0.0 from 3.4.2+. See the [ ## Database changes No changes have been made to the database schema. However, several superfluous queries have been dropped from the SQL backend. +Furthermore, the generic SQL backends switched to prepared statements. If you use a non-standard SQL schema, please review the new defaults. - `insert-ent-query`, `insert-empty-non-terminal-query`, `insert-ent-order-query` have been replaced by one query named `insert-empty-non-terminal-order-query` @@ -52,3 +53,9 @@ The API path has changed to `/api/v1`. Incompatible change: `SOA-EDIT-API` now follows `SOA-EDIT-DNSUPDATE` instead of `SOA-EDIT` (incl. the fact that it now has a default value of `DEFAULT`). You must update your existing `SOA-EDIT-API` metadata (set `SOA-EDIT` to your previous `SOA-EDIT-API` value, and `SOA-EDIT-API` to `SOA-EDIT` to keep the old behaviour). + +## Ressource Record Changes +Since PowerDNS 4.0.0 the CAA ressource record (type 257) is supported. In PowerDNS 3.4.x type 257 was used for a proprietary MBOXFW ressource record, which +was removed from PowerDNS 4.0. Hence, if you used CAA records with 3.4.x (stored in the DB with wrong type=MBOXFW but worked fined) and upgrade to 4.0, +PowerDNS will fail to parse this records and will throw an exception on all queries for a label with MBOXFW records. Thus, make sure to clean up the +records in the DB.