.. highlight:: none .. _Migration: ********* Migration ********* .. _Upgrade 2.4.x to 2.5.x: 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. .. _Building changes: Building changes ---------------- The ``--enable-dnstap`` configure option now enables the dnstap support in :doc:`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: - disabled: ``--with-module-``\ MODULE_NAME\ ``=no`` - embedded: ``--with-module-``\ MODULE_NAME\ ``=yes`` - external: ``--with-module-``\ MODULE_NAME\ ``=shared`` (excluding ``dnsproxy`` and ``onlinesign``) The ``--with-timer-mapsize`` configure option was replaced with the runtime ``template.max-timer-db-size`` configuration option. .. _KASP DB migration: 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. .. _Configuration changes 2.5: Configuration changes --------------------- 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: Upgrade 2.5.x to 2.6.x ====================== Upgrading from Knot DNS version 2.5.x to 2.6.x is almost seamless. .. _Configuration changes 2.6: Configuration changes --------------------- The ``dsa`` and ``dsa-nsec3-sha1`` algorithm values are no longer supported by the :ref:`policy_algorithm` option. The ``ixfr-from-differences`` zone/template option was deprecated in favor of the :ref:`zone_zonefile-load` option. .. _Upgrade 2.6.x to 2.7.x: 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: 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 created=1 $ keymgr example.com. set created=1 ... .. _Upgrade 2.8.x to 2.9.x: 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. Configuration changes --------------------- - Imperfect runtime reconfiguration of :ref:`server_udp-workers`, :ref:`server_tcp-workers`, and :ref:`server_listen` is no longer supported. - Replaced options (with backward compatibility): .. csv-table:: :header: Old section, Old item name, New section, New item name :widths: 35, 60, 35, 60 :ref:`server` , ``tcp-reply-timeout`` [s] , :ref:`server` , :ref:`server_tcp-remote-io-timeout` [ms] :ref:`server` , ``max-tcp-clients`` , :ref:`server` , :ref:`server_tcp-max-clients` :ref:`server` , ``max-udp-payload`` , :ref:`server` , :ref:`server_udp-max-payload` :ref:`server` , ``max-ipv4-udp-payload`` , :ref:`server` , :ref:`server_udp-max-payload-ipv4` :ref:`server` , ``max-ipv6-udp-payload`` , :ref:`server` , :ref:`server_udp-max-payload-ipv6` :ref:`template