Upgrade 2.4.x to 2.5.x¶
This chapter describes some steps necessary after upgrading Knot DNS from version 2.4.x to 2.5.x.
--enable-dnstap configure option now enables the dnstap support in kdig only! To build the dnstap query module,
--with-module-dnstap have to be used.
Since Knot DNS version 2.5.0 each query module can be configured to be:
--with-timer-mapsize configure option was replaced with the runtime
template.max-timer-db-size configuration option.
KASP DB migration¶
Knot DNS version 2.4.x and earlier uses JSON files to store DNSSEC keys metadata, one for each zone. 2.5.x versions store those in binary format in a LMDB, all zones together. The migration is possible with the pykeymgr script:
$ pykeymgr -i path/to/keydir
The path to KASP DB directory is configuration-dependent, usually it is the
keys subdirectory in the zone storage.
In rare installations, the JSON files might be spread across more directories. In such case, it is necessary to put them together into one directory and migrate at once.
It is no longer possible to configure KASP DB per zone or in a non-default template. Ensure just one common KASP DB configuration in the default template.
As Knot DNS version 2.5.0 brings dynamically loaded modules, some modules were renamed for technical reasons. So it is necessary to rename all occurrences (module section names and references from zones or templates) of the following module names in the configuration:
mod-online-sign -> mod-onlinesign mod-synth-record -> mod-synthrecord
Upgrade 2.5.x to 2.6.x¶
Upgrading from Knot DNS version 2.5.x to 2.6.x is almost seamless.
Upgrade 2.6.x to 2.7.x¶
Upgrading from Knot DNS version 2.6.x to 2.7.x is seamless if no obsolete configuration or module rosedb is used.
Upgrade 2.7.x to 2.8.x¶
Upgrading from Knot DNS version 2.7.x to 2.8.x is seamless.
However, if the previous version was migrated (possibly indirectly) from version 2.5.x, the format of the keys stored in Keys And Signature Policy Database is no longer compatible and needs to be updated.
The easiest ways to update how keys are stored in KASP DB is to modify with Keymgr version 2.7.x some of each key's parameters in an undamaging way, e.g.:
$ keymgr example.com. list $ keymgr example.com. set <keyTag> created=1 $ keymgr example.com. set <keyTag2> created=1 ...
Upgrade 2.8.x to 2.9.x¶
Upgrading from Knot DNS version 2.8.x to 2.9.x is almost seamless but check the following changes first.
Replaced options (with backward compatibility):
Old item name
New item name
Removed options (no backward compatibility):
New default values for:
New DNSSEC policy option rrsig-pre-refresh may affect configuration validity, which is
rrsig-refresh + rrsig-pre-refresh < rrsig-lifetime
Memory use estimation via
knotc zone-memstatswas removed
Based on https://tools.ietf.org/html/draft-ietf-dnsop-server-cookies the module DNS Cookies was updated to be interoperable
Number of open files limit is set to 1048576 in upstream packages
Upgrade 2.9.x to 3.0.x¶
Knot DNS version 3.0.x is functionally compatible with 2.9.x with the following exceptions.
Configuration option update-owner-name is newly FQDN-sensitive. It means that values
a.example.com. are not equivalent.
Reverse IPv6 address shortening is enabled by default. For example, the module generates:
dynamic-2620-0-b61-100--1.test. 400 IN AAAA 2620:0:b61:100::1
dynamic-2620-0000-0b61-0100-0000-0000-0000-0001.test. 400 IN AAAA 2620:0:b61:100::1
Query module API change¶
The following functions require additional parameter (thread id –
qdata->params->thread_id) on the second position:
knotd_mod_stats_incr() knotd_mod_stats_decr() knotd_mod_stats_store()
The embedded library LMDB is no longer part of the source code. Almost every modern operating system has a sufficient version of this library.
DoH support in kdig requires optional library libnghttp2.
XDP support on Linux requires optional library libbpf >= 0.0.6. If not available, an embedded library can be used via
Upgrade 3.0.x to 3.1.x¶
Knot DNS version 3.1.x is functionally compatible with 3.0.x with the following exceptions.
Automatic SOA serial incrementation (
zonefile-load: difference-no-serial) requires having full zone stored in the journal (
journal-content: all). This change is necessary for reliable operation.
Replaced options (with backward compatibility):
Ignored obsolete options (with a notice log):
Silently ignored obsolete options:
Zone backup and restore¶
The online backup format has changed slightly since 3.0 version. For zone-restore from backups in the previous format, it's necessary to set the -f option. Offline restore procedure of zone files from online backups is different than what it was before. The details are described in Data and metadata backup.
The configure option
--enable-xdp=yeshas slightly changed its semantics. It first tries to find an external library libbpf. If it's not detected, the embedded one is used instead.
The kxdpgun tool also depends on library libmnl.
Knot DNS for BIND users¶
Automatic DNSSEC signing¶
Migrating automatically signed zones from BIND to Knot DNS requires copying up-to-date zone files from BIND, importing existing private keys, and updating server configuration:
To obtain current content of the zone which is being migrated, request BIND to flush the zone into the zone file:
rndc sync example.com.
If dynamic updates (DDNS) are enabled for the given zone, you might need to freeze the zone before flushing it. That can be done similarly:
$ rndc freeze example.com
Copy the fresh zone file into the zones storage directory of Knot DNS.
Import all existing zone keys into the KASP database. Make sure that all the keys were imported correctly:
$ keymgr example.com. import-bind path/to/Kexample.com.+013+11111 $ keymgr example.com. import-bind path/to/Kexample.com.+013+22222 $ ... $ keymgr example.com. list
If the server configuration file or database is not at the default location, add a configuration parameter (-c or -C). See keymgr for more info about required access rights to the key files.
Follow Automatic DNSSEC signing steps to configure DNSSEC signing.