};
};
-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<zone_clause>` clause, and :ref:`allow-query<allow-query>`,
+The :ref:`zone<zone_clause>` block, and :ref:`allow-query<allow-query>`,
:any:`allow-query-cache`,
:ref:`allow-transfer<allow-transfer>`, :ref:`file<file>`,
:ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and :ref:`type<type>`
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<zone_clause>` clause, and :ref:`allow-query<allow-query>`,
+The :ref:`zone<zone_clause>` block, and :ref:`allow-query<allow-query>`,
:any:`allow-query-cache`,
:ref:`allow-transfer<allow-transfer>`, :ref:`file<file>`,
:ref:`notify<notify_st>`, :ref:`primaries<primaries>`,
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;<notify>` in the
- :ref:`zone<zone_clause>` clause for the secondary causes :iscman:`named` to
+ :ref:`zone<zone_clause>` block for the secondary causes :iscman:`named` to
only send NOTIFY messages for primary zones that it loads.
};
};
-The :ref:`logging<logging_grammar>` and :ref:`options<options_grammar>` clauses
+The :ref:`logging<logging_grammar>` and :ref:`options<options_grammar>` blocks
and :ref:`category<the_category_phrase>`, :ref:`channel<channel>`,
:ref:`directory<directory>`, :ref:`file<file>`, and :ref:`severity<severity>`
statements are all described further in the appropriate sections of this ARM.
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.
notify no;
};
-The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` clauses, and the
+The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` blocks, and the
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
:ref:`file<file>`, :ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and
:ref:`type<type>` statements are described in detail in the appropriate
notify no;
};
-The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` clauses, and the
+The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` blocks, and the
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
:ref:`file<file>`, :ref:`forward<forward>`, :ref:`forwarders<forwarders>`,
:ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and :ref:`type<type>`
};
-The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` clauses, and the
+The :ref:`zone<zone_clause>` and :ref:`acl<acl_grammar>` blocks, and the
:ref:`allow-query<allow-query>`, :ref:`empty-zones-enable<empty-zones-enable>`,
:ref:`file<file>`, :ref:`forward<forward>`, :ref:`forwarders<forwarders>`,
:ref:`notify<notify_st>`, :ref:`recursion<recursion>`, and :ref:`type<type>`
For more detail on ordering responses, refer to the
:ref:`rrset-order<rrset_ordering>` statement in the
-:ref:`options<options_grammar>` clause.
+:ref:`options<options_grammar>` block.
: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