migration.rst 1.74 KB
Newer Older
1
.. highlight:: yaml
2 3
.. _Migration from other DNS servers:

4 5 6 7
********************************
Migration from other DNS servers
********************************

8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
.. _Knot DNS for BIND users:

Knot DNS for BIND users
=======================

.. _Automatic DNSSEC signing:

Automatic DNSSEC signing
------------------------

Migrating automatically signed zones from Bind to Knot DNS is very
easy due to the fact that Knot DNS is able to use DNSSEC keys
generated by Bind.

1. To obtain current content of the zone which is being migrated,
   request Bind to flush the zone into the zone file: ``rndc flush
   example.com``.
25

26
   Note: If dynamic updates (DDNS) are enabled for the given zone, you
27
   might need to freeze the zone before flushing it. That can be done
28 29 30
   similarly: ``rndc freeze example.com``

2. Copy the fresh zone file into the zones storage directory of Knot
31
   DNS. It's default location is ``/var/lib/knot``.
32 33

3. We recommend to store DNSSEC keys for each zone in a separate
34 35
   directory. For this purpose, create a directory
   ``example.com.keys`` in zones storage directory. Then copy all
36 37 38
   DNSSEC keys (``*.key`` and ``*.private``) from Bind key directory
   (configured as ``key-directory``) into the newly created one.

39
4. Add the zone into the Knot DNS configuration file. Zone
40
   configuration should contain at least specification of the zone
41
   file (option ``file``), key directory (option ``kasp-db``),
42 43 44 45
   and enable automatic DNSSEC signing (option ``dnssec-enable``).

   You can follow this example::

46 47 48 49 50
    zone:
      - domain: "example.com."
        file: "example.com.db"
        storage: "/var/lib/knot"
        dnssec-enable: on
51
        kasp-db: "example.com.keys"
52 53

5. Start Knot DNS and check the log files to make sure that everything went right.