[deployment-guide/comm-rel: 343/727] Moved the Running BIND in a Chroot Environment admonition.

[Jaromir Hradilek]

commit 51ae02abe5667d028637deb0f4ed65c408ed9d16
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Wed Aug 11 17:39:36 2010 +0200

    Moved the Running BIND in a Chroot Environment admonition.

 en-US/The_BIND_DNS_Server.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index aaf1403..b555201 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -280,12 +280,6 @@
         </tbody>
       </tgroup>
     </table>
-    <note>
-      <title>Note: Running BIND in a Chroot Environment</title>
-      <para>
-        If you have installed the <package>bind-chroot</package> package, the BIND service will run in the <command>/var/named/chroot</command> environment. In that case, the initialization script will mount the above configuration files using the <command>mount --bind</command> command, so that you can manage the configuration outside this environment.
-      </para>
-    </note>
     <para>
       The <filename>/etc/named.conf</filename> file consists of a collection of statements with nested options surrounded by opening and closing curly brackets (that is, <literal>{</literal> and <literal>}</literal>). Note that when editing the file, you have to be careful not to make any syntax error, otherwise the <systemitem class="service">named</systemitem> service will not start. A typical configuration is organized as follows:
     </para>
@@ -304,6 +298,12 @@
   <replaceable>&lt;option-2&gt;</replaceable>;
   <replaceable>&lt;option-N&gt;</replaceable>;
 };</screen>
+    <note>
+      <title>Note: Running BIND in a Chroot Environment</title>
+      <para>
+        If you have installed the <package>bind-chroot</package> package, the BIND service will run in the <command>/var/named/chroot</command> environment. In that case, the initialization script will mount the above configuration files using the <command>mount --bind</command> command, so that you can manage the configuration outside this environment.
+      </para>
+    </note>
     <section id="s2-bind-namedconf-state">
       <title>Common Statement Types</title>
       <para>