Define topmost configuration blocks

(cherry picked from commit f91cbcf996d66ddb87e7c66cbc8ec6fc588a6a02)

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index a153b4963bebcc42031c04159f98d4937f7a9d35..20d0b556d6bf3b5626772328faaed53058d8e7ec 100644 (file)
--- a/doc/arm/reference.rst
+++ b/doc/arm/reference.rst
@@ -40,6 +40,24 @@ The file :file:`named.conf` may contain three types of entities:
       define the scope of the statement - for example, a statement which appears
       in a :namedconf:ref:`zone` block has scope only for that zone.
 
+      Blocks are organized hierarchically within named.conf and may have a
+      number of different properties:
+
+      - Certain blocks cannot be nested in other blocks and thus may be
+        regarded as the *topmost* level blocks. For example, the
+        :namedconf:ref:`options` block and the :namedconf:ref:`logging` block.
+
+      - Certain blocks can appear multiple times in which case they will have
+        an associated name to disambiguate them. For example, the
+        :namedconf:ref:`zone` block (``zone example.com { ... };``) or the
+        :namedconf:ref:`key` block (``key mykey { ... };``).
+
+      - Certain blocks may be nested within other blocks. For example, the
+        :namedconf:ref:`zone` block may be nested (appear within) a
+        :namedconf:ref:`view` block.
+
+      Description of each block in this manual lists its permissible locations.
+
    Statement
       - Statements define and control specific BIND behaviors.
       - Statements may have a single parameter (a **Value**) or multiple parameters
@@ -7033,7 +7051,6 @@ An :any:`in-view` zone cannot be used as a response policy zone.
 
 An :any:`in-view` zone is not intended to reference a :any:`forward` zone.
 
-
 .. _statistics:
 
 BIND 9 Statistics