upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-02-25 19:04:57 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update DNSSEC documentation

Browse source 
This was originally done in commit
da0ae5299f but was lost when the
documentation was converted to RST files.

(cherry picked from commit 0b0320360f)
This commit is contained in:
Matthijs Mekking 2020-09-10 13:48:04 +02:00
parent a93a6844a9
commit b4d8db40d4
1 changed files with 27 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
doc/arm/dnssec.rst
View file

@ -26,13 +26,15 @@ DNSSEC, Dynamic Zones, and Automatic Signing
Converting From Insecure to Secure
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Changing a zone from insecure to secure can be done in two ways: using a
dynamic DNS update, or via the ``auto-dnssec`` zone option.
Changing a zone from insecure to secure can be done in three ways: using a
dynamic DNS update, or via the ``auto-dnssec`` zone option, or set a
DNSSEC policy for the zone with ``dnssec-policy``.
For either method, ``named`` must be configured so that it can see
the ``K*`` files which contain the public and private parts of the keys
that are used to sign the zone. These files are generated
by ``dnssec-keygen``, and they should be placed in the
by ``dnssec-keygen`` (or created when needed by ``named`` if
``dnssec-policy`` is used). Keys should be placed in the
key-directory, as specified in ``named.conf``:
::
@ -49,6 +51,18 @@ configuration causes all records in the zone to be signed with the
ZSK, and the DNSKEY RRset to be signed with the KSK. An NSEC
chain is generated as part of the initial signing process.
With ``dnssec-policy you specify what keys should be KSK and/or ZSK.
If you want a key to sign all records with a key you will need to
specify a CSK. For example:
::
dnssec-policy csk {
keys {
csk lifetime unlimited algorithm 13;
};
};
Dynamic DNS Update Method
~~~~~~~~~~~~~~~~~~~~~~~~~
@ -93,9 +107,9 @@ other updates are possible as well.
Fully Automatic Zone Signing
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To enable automatic signing, add the ``auto-dnssec`` option to the zone
statement in ``named.conf``. ``auto-dnssec`` has two possible arguments:
``allow`` or ``maintain``.
To enable automatic signing, you can set a ``dnssec-policy``, or add the
``auto-dnssec`` option to the zone statement in ``named.conf``.
``auto-dnssec`` has two possible arguments: ``allow`` or ``maintain``.
With ``auto-dnssec allow``, ``named`` can search the key directory for
keys matching the zone, insert them into the zone, and use them to sign
@ -107,6 +121,11 @@ automatically adjusts the zone's DNSKEY records on a schedule according to
the keys' timing metadata. (See :ref:`man_dnssec-keygen` and
:ref:`man_dnssec-settime` for more information.)
``dnssec-policy`` is like ``auto-dnssec maintain``, but will also automatically
create new keys when necessary. Also any configuration related to DNSSEC
signing is retrieved from the policy (ignoring existing DNSSEC ``named.conf``
options).
``named`` periodically searches the key directory for keys matching
the zone; if the keys' metadata indicates that any change should be
made to the zone, such as adding, removing, or revoking a key, then that
@ -234,6 +253,8 @@ conversion is complete, the NSEC chain is removed and the
NSEC3PARAM record has a zero flag field. The NSEC3 chain is
generated before the NSEC chain is destroyed.
NSEC3 is not supported yet with ``dnssec-policy``.
Converting From NSEC3 to NSEC
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~