From e60d0d069e455d28b0cc7e7b39733609bb0c5fc4 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 12 Jan 2022 15:51:07 -0500
Subject: [PATCH] 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.
---
 pdns/recursordist/docs/settings.rst | 13 -------------
 1 file changed, 13 deletions(-)

diff --git a/pdns/recursordist/docs/settings.rst b/pdns/recursordist/docs/settings.rst
index 0bf2c781a4..78c34fcae1 100644
--- 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``
-- 
2.47.2