Add some clarifications wrt dynamic zones

These were suggested by GitLab user @elmaimbo.

(cherry picked from commit fb517eb52a64a784cafd29ed1e046f60c34935b7)

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index 0caa8a374ef48dc5022f8b35895119ff12c297f3..7f8cdc65b732e4713d03be6cb24c039c1e0ca84e 100644 (file)
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -6667,8 +6667,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