From e28050e7a40ddd6d27834f44dae0573beb02e25f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Petr=20=C5=A0pa=C4=8Dek?= Date: Thu, 16 Jun 2022 16:45:09 +0200 Subject: [PATCH] Deduplicate allow-update definition in the ARM (cherry picked from commit 420a7331a8ea10ab25b8d96f0c5ff10f92942884) --- doc/arm/reference.rst | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index 023330cb48..2a407edbb9 100644 --- a/doc/arm/reference.rst +++ b/doc/arm/reference.rst @@ -2743,6 +2743,7 @@ for details on how to specify IP address lists. .. namedconf:statement:: allow-update + A simple access control list. When set in the ``zone`` statement for a primary zone, this specifies which hosts are allowed to submit Dynamic DNS updates to that zone. The default is to deny updates from all hosts. @@ -6733,16 +6734,14 @@ Dynamic Update Policies ^^^^^^^^^^^^^^^^^^^^^^^ BIND 9 supports two methods of granting clients the right to -perform dynamic updates to a zone, configured by the ``allow-update`` -or ``update-policy`` options. In both cases, BIND 9 writes the updates +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``. -.. namedconf:statement:: allow-update - - The ``allow-update`` clause is a simple access control list. Any client - that matches the ACL is granted permission to update any record in the - zone. - .. namedconf:statement:: update-policy The ``update-policy`` clause allows more fine-grained control over which