From: Matthijs Mekking Date: Fri, 24 Jun 2022 14:36:23 +0000 (+0200) Subject: Add some clarifications wrt dynamic zones X-Git-Tag: v9.19.3~24^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fb517eb52a64a784cafd29ed1e046f60c34935b7;p=thirdparty%2Fbind9.git Add some clarifications wrt dynamic zones These were suggested by GitLab user @elmaimbo. --- diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index 00ee0914787..abd39be914d 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -6659,8 +6659,16 @@ perform dynamic updates to a zone: - :namedconf:ref:`allow-update` - a simple access control list - :namedconf:ref:`update-policy` - fine-grained access control -In both cases, BIND 9 writes the updates -to the zone's filename set in ``file``. +In both cases, BIND 9 writes the updates to the zone's filename +set in ``file``. + +In the case of a DNSSEC zone, DNSSEC records are also written to +the zone's filename, unless ``inline-signing`` is enabled. + + .. note:: The zone file can no longer be manually updated while ``named`` + is running; it is now necessary to perform :option:`rndc freeze`, edit, + and then perform :option:`rndc thaw`. Comments and formatting + in the zone file are lost when dynamic updates occur. .. namedconf:statement:: update-policy