From dff495a0d01ef726b8ce045c56c528ea680496e0 Mon Sep 17 00:00:00 2001 From: Matthijs Mekking Date: Tue, 21 Sep 2021 15:22:49 +0200 Subject: [PATCH] Remove copy paste error on zone-max-ttl The "zone-max-ttl" option inside a "dnssec-policy" is not used to cap the TTLs in a zone, only yo calculate key rollover timings. (cherry picked from commit 4e3ba8169652e3e0423d176aa59d8686e95e014a) --- doc/arm/reference.rst | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index a7030ee32e..a455609b10 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -5019,10 +5019,7 @@ The following options can be specified in a ``dnssec-policy`` statement: ``max-zone-ttl`` Like the ``max-zone-ttl`` zone option, this specifies the maximum - permissible TTL value, in seconds, for the zone. When loading a - 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. + permissible TTL value, in seconds, for the zone. This is needed in DNSSEC-maintained zones because when rolling to a new DNSKEY, the old key needs to remain available until RRSIG