mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-09-02 23:55:27 +00:00
Code Issues Releases Wiki Activity

Merge branch 'matthijs-fix-arm-typos' into 'main'

Browse Source 
The s stands for security

See merge request isc-projects/bind9!5428
This commit is contained in:
Matthijs Mekking
2021-09-23 07:52:09 +00:00
parent db00265dec 4e3ba81696
commit c5c6a76e8c
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/arm/reference.rst
View File

@@ -5079,7 +5079,7 @@ The following options can be specified in a ``dnssec-policy`` statement:
An optional second token determines where the key is stored. An optional second token determines where the key is stored.
Currently, keys can only be stored in the configured Currently, keys can only be stored in the configured
``key-directory``. This token may be used in the future to store ``key-directory``. This token may be used in the future to store
keys in hardware service modules or separate directories. keys in hardware security modules or separate directories.
The ``lifetime`` parameter specifies how long a key may be used The ``lifetime`` parameter specifies how long a key may be used
before rolling over. In the example above, the first key has an before rolling over. In the example above, the first key has an
@@ -5138,10 +5138,7 @@ The following options can be specified in a ``dnssec-policy`` statement:
``max-zone-ttl`` ``max-zone-ttl``
Like the ``max-zone-ttl`` zone option, this specifies the maximum Like the ``max-zone-ttl`` zone option, this specifies the maximum
permissible TTL value, in seconds, for the zone. When loading a permissible TTL value, in seconds, for the zone.
zone file using a ``masterfile-format`` of ``text`` or ``raw``, any
record encountered with a TTL higher than ``max-zone-ttl`` is capped
at the maximum permissible TTL value.
This is needed in DNSSEC-maintained zones because when rolling to a This is needed in DNSSEC-maintained zones because when rolling to a
new DNSKEY, the old key needs to remain available until RRSIG new DNSKEY, the old key needs to remain available until RRSIG
@@ -5163,7 +5160,9 @@ The following options can be specified in a ``dnssec-policy`` statement:
The default is to use NSEC. The ``iterations``, ``optout`` and The default is to use NSEC. The ``iterations``, ``optout`` and
``salt-length`` parts are optional, but if not set, the values in ``salt-length`` parts are optional, but if not set, the values in
the example above are the default NSEC3 parameters. the example above are the default NSEC3 parameters. Note that you don't
specify a specific salt string, ``named`` will create a salt for you
of the provided salt length.
``zone-propagation-delay`` ``zone-propagation-delay``
This is the expected propagation delay from the time when a zone is This is the expected propagation delay from the time when a zone is