From: Matthijs Mekking <matthijs@isc.org>
Date: Tue, 21 Sep 2021 13:22:49 +0000 (+0200)
Subject: Remove copy paste error on zone-max-ttl
X-Git-Tag: v9.17.19~28^2
X-Git-Url: http://git.ipfire.org/gitweb/?a=commitdiff_plain;h=4e3ba8169652e3e0423d176aa59d8686e95e014a;p=thirdparty%2Fbind9.git

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.
---

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index 725800dfcf9..0a4627bf408 100644
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -5138,10 +5138,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