diff --git a/doc/arm/config-auth.inc.rst b/doc/arm/config-auth.inc.rst index 06a1715d42..d60b1b7b8b 100644 --- a/doc/arm/config-auth.inc.rst +++ b/doc/arm/config-auth.inc.rst @@ -167,9 +167,9 @@ the :iscman:`named.conf` file has been modified as shown: }; }; -The added statements and clauses are commented in the above file. +The added statements and blocks are commented in the above file. -The :ref:`zone` clause, and :ref:`allow-query`, +The :ref:`zone` block, and :ref:`allow-query`, :any:`allow-query-cache`, :ref:`allow-transfer`, :ref:`file`, :ref:`notify`, :ref:`recursion`, and :ref:`type` @@ -250,9 +250,9 @@ The :iscman:`named.conf` file has been modified as shown: primaries { 192.168.254.2; }; }; -The statements and clauses added are all commented in the above file. +The statements and blocks added are all commented in the above file. -The :ref:`zone` clause, and :ref:`allow-query`, +The :ref:`zone` block, and :ref:`allow-query`, :any:`allow-query-cache`, :ref:`allow-transfer`, :ref:`file`, :ref:`notify`, :ref:`primaries`, @@ -268,5 +268,5 @@ message. can get more complicated. A secondary zone can also be a primary to other secondaries: :iscman:`named`, by default, sends NOTIFY messages for every zone it loads. Specifying :ref:`notify primary-only;` in the - :ref:`zone` clause for the secondary causes :iscman:`named` to + :ref:`zone` block for the secondary causes :iscman:`named` to only send NOTIFY messages for primary zones that it loads. diff --git a/doc/arm/config-intro.inc.rst b/doc/arm/config-intro.inc.rst index 7598c6571e..4a07ffacb4 100644 --- a/doc/arm/config-intro.inc.rst +++ b/doc/arm/config-intro.inc.rst @@ -79,7 +79,7 @@ as required by the user. }; }; -The :ref:`logging` and :ref:`options` clauses +The :ref:`logging` and :ref:`options` blocks and :ref:`category`, :ref:`channel`, :ref:`directory`, :ref:`file`, and :ref:`severity` statements are all described further in the appropriate sections of this ARM. diff --git a/doc/arm/config-resolve.inc.rst b/doc/arm/config-resolve.inc.rst index ab05742bac..d8563a9ad0 100644 --- a/doc/arm/config-resolve.inc.rst +++ b/doc/arm/config-resolve.inc.rst @@ -93,7 +93,7 @@ Resolver and Forwarding Resolver can be used by rogue actors to cause all kinds of problems including **Denial of Service (DoS)** attacks. Resolvers should always be configured to limit the IP addresses that can use their services. BIND 9 provides a - number of statements and clauses to simplify defining these IP limits and + number of statements and blocks to simplify defining these IP limits and configuring a **closed resolver**. The resolver samples given here all configure closed resolvers using a variety of techniques. @@ -264,7 +264,7 @@ It is therefore a **closed** resolver and cannot be used in wider network attack notify no; }; -The :ref:`zone` and :ref:`acl` clauses, and the +The :ref:`zone` and :ref:`acl` blocks, and the :ref:`allow-query`, :ref:`empty-zones-enable`, :ref:`file`, :ref:`notify`, :ref:`recursion`, and :ref:`type` statements are described in detail in the appropriate @@ -383,7 +383,7 @@ provided`. notify no; }; -The :ref:`zone` and :ref:`acl` clauses, and the +The :ref:`zone` and :ref:`acl` blocks, and the :ref:`allow-query`, :ref:`empty-zones-enable`, :ref:`file`, :ref:`forward`, :ref:`forwarders`, :ref:`notify`, :ref:`recursion`, and :ref:`type` @@ -511,7 +511,7 @@ those IPs from which it will accept recursive queries. }; -The :ref:`zone` and :ref:`acl` clauses, and the +The :ref:`zone` and :ref:`acl` blocks, and the :ref:`allow-query`, :ref:`empty-zones-enable`, :ref:`file`, :ref:`forward`, :ref:`forwarders`, :ref:`notify`, :ref:`recursion`, and :ref:`type` @@ -567,4 +567,4 @@ and discard the rest. For more detail on ordering responses, refer to the :ref:`rrset-order` statement in the -:ref:`options` clause. +:ref:`options` block. diff --git a/doc/arm/introduction.inc.rst b/doc/arm/introduction.inc.rst index 009a702347..ebb7e7acc8 100644 --- a/doc/arm/introduction.inc.rst +++ b/doc/arm/introduction.inc.rst @@ -65,7 +65,7 @@ running BIND 9 in a "jail," and securing file transfers and dynamic updates. :ref:`dnssec` describes the theory and practice of cryptographic authentication of DNS information. The :ref:`dnssec_guide` is a practical guide to implementing DNSSEC. -:ref:`Reference` gives exhaustive descriptions of all supported clauses, statements, +:ref:`Reference` gives exhaustive descriptions of all supported blocks, statements, and grammars used in BIND 9's ``named.conf`` configuration file. :ref:`troubleshooting` provides information on identifying and solving BIND 9 and DNS