From: Petr Špaček Date: Thu, 16 Jun 2022 14:45:09 +0000 (+0200) Subject: Deduplicate allow-update definition in the ARM X-Git-Tag: v9.19.3~25^2~21 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=420a7331a8ea10ab25b8d96f0c5ff10f92942884;p=thirdparty%2Fbind9.git Deduplicate allow-update definition in the ARM --- diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst index f4929c621c5..407a9e3dfcc 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. @@ -6725,15 +6726,13 @@ 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 -to the zone's filename set in ``file``. +perform dynamic updates to a zone: -.. namedconf:statement:: allow-update +- :namedconf:ref:`allow-update` - a simple access control list +- :namedconf:ref:`update-policy` - fine-grained access control - 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. +In both cases, BIND 9 writes the updates +to the zone's filename set in ``file``. .. namedconf:statement:: update-policy