Define topmost configuration blocks

diff --git a/doc/arm/reference.rst b/doc/arm/reference.rst
index 875640894b8908b01f8584da3e2d63b6bded4506..e6bfe7f4db08c2ff63fef3d1a9945dfbe720683b 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
@@ -7011,7 +7029,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