doc: remove auth-can-lower-ttl

This wasn't around as of 4.0 - it landed in this file in 223bb49ef87feee34af9d1076b55bee81a38b8bc
but the removal notice was already included at that time.

diff --git a/pdns/recursordist/docs/settings.rst b/pdns/recursordist/docs/settings.rst
index 0bf2c781a4c28f654af82e92dcd7589f9c80d0b9..78c34fcae176e67a1561d0d8d6e9052d930318f3 100644 (file)
--- a/pdns/recursordist/docs/settings.rst
+++ b/pdns/recursordist/docs/settings.rst
@@ -192,19 +192,6 @@ Disallow data modification through the REST API when set.
 
 Location of the server logfile (used by the REST API).
 
-.. _setting-auth-can-lower-ttl:
-
-``auth-can-lower-ttl``
-----------------------
--  Boolean
--  Default: no
-
-Authoritative zones can transmit a TTL value that is lower than that specified in the parent zone.
-This is called a 'delegation inconsistency'.
-To follow :rfc:`RFC 2181 section 5.2<2181#section-5.2>` and :rfc:`5.4 <2181#section-5.4>` to the letter, enable this feature.
-This will mean a slight deterioration of performance, and it will not solve any problems, but does make the recursor more standards compliant.
-Not recommended unless you have to tick an 'RFC 2181 compliant' box.
-
 .. _setting-auth-zones:
 
 ``auth-zones``