Before proceeding, it is advised to check the release notes for your PowerDNS version, as specified in the name of the distribution file.
Please upgrade to the PowerDNS Authoritative Server 4.0.0 from 3.4.2+. See the 3.X upgrade notes if your version is older than 3.4.2.
4.0.X to 4.1.0
configure options have been deprecated.
configure now attempts to find the Postgresql client libraries via
pkg-config, falling back to detecting
--with-pg-config to specify a path to a non-default
pg_config if you have Postgresql installed in a non-default location.
4.0.X to 4.0.2
3.4.X to 4.0.0
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-order-queryhave been replaced by one query named
insert-record-order-queryhas been dropped,
insert-record-querynow sets the ordername (or NULL)
insert-slave-queryhas been dropped,
insert-zone-querynow sets the type of zone
Several options have been removed or renamed, for the full overview of all options, see settings.
The following options have been renamed:
default-ksk-algorithmschanged from rsasha256 to ecdsa256
default-zsk-algorithmschanged from rsasha256 to empty
The following options are removed:
pipebackend-abi-version, it now a setting per-pipe backend.
The API path has changed to
SOA-EDIT-API now follows
SOA-EDIT-DNSUPDATE instead of
SOA-EDIT (incl. the fact that it now has a default value of
You must update your existing
SOA-EDIT-API metadata (set
SOA-EDIT to your previous
SOA-EDIT-API value, and
SOA-EDIT to keep the old behaviour).
Resource Record Changes
Since PowerDNS 4.0.0 the CAA resource record (type 257) is supported. Before PowerDNS 4.0.0 type 257 was used for a proprietary MBOXFW resource 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 fine) 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.