summaryrefslogtreecommitdiffstats
path: root/doc/migration.rst
diff options
context:
space:
mode:
authorLibor Peltan <libor.peltan@nic.cz>2017-06-15 13:06:22 +0200
committerDaniel Salzman <daniel.salzman@nic.cz>2017-06-15 14:51:31 +0200
commit198a4b891a70578b9d473e1f99c1cdeb5130d904 (patch)
treec72972dd2138969bf610cb3f25f0f8de9a53182d /doc/migration.rst
parentdoc: exterminated 't+123unit' (diff)
downloadknot-198a4b891a70578b9d473e1f99c1cdeb5130d904.tar.xz
knot-198a4b891a70578b9d473e1f99c1cdeb5130d904.zip
doc: migration 2.4 to 2.5
Diffstat (limited to 'doc/migration.rst')
-rw-r--r--doc/migration.rst51
1 files changed, 47 insertions, 4 deletions
diff --git a/doc/migration.rst b/doc/migration.rst
index 5b0ffac55..bb6de59e6 100644
--- a/doc/migration.rst
+++ b/doc/migration.rst
@@ -1,9 +1,52 @@
.. highlight:: none
-.. _Migration from other DNS servers:
+.. _Migration:
-********************************
-Migration from other DNS servers
-********************************
+*********
+Migration
+*********
+
+.. _Upgrade comments 2.4 to 2.5:
+
+Upgrade comments 2.4 to 2.5
+===========================
+
+This chapter describes some steps necessary after upgrading Knot DNS from
+version 2.4.x to 2.5.x.
+
+.. _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 ``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:
+
+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
.. _Knot DNS for BIND users: