From: David VaĊĦek Date: Mon, 20 Jun 2022 21:39:05 +0000 (+0200) Subject: doc/configuration: mention that nested catalog zones aren't supported X-Git-Tag: v3.3.dev~91^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c97c0a5300a4ad9c4fc61ef2e88d98b246ab14af;p=thirdparty%2Fknot-dns.git doc/configuration: mention that nested catalog zones aren't supported --- diff --git a/doc/configuration.rst b/doc/configuration.rst index 19f233ce9d..5cd4cd698b 100644 --- a/doc/configuration.rst +++ b/doc/configuration.rst @@ -656,7 +656,8 @@ configured. The configuration for any defined member zone is taken from its *group* property value, which should match some catalog-template name. If the *group* property is not defined for a member, is empty, or doesn't match any of defined catalog-template names, the first catalog-template -(in the order from configuration) is used. +(in the order from configuration) is used. Nesting of catalog zones isn't +supported. Any de-cataloged member zone is purged immediately, including its zone file, journal, timers, and DNSSEC keys. The zone file is not