[deployment-guide/comm-rel: 339/727] Modified the BIND as a Nameserver subsection.
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:53:10 UTC 2010
commit 4878195d31f29481bcf20bc1307857f7f77a8cb7
Author: Jaromir Hradilek <jhradile at redhat.com>
Date: Wed Aug 11 15:03:17 2010 +0200
Modified the BIND as a Nameserver subsection.
Note that this is only a temporary state, and the subsection will be
extended once the relevant parts of the chapter are finished.
en-US/The_BIND_DNS_Server.xml | 16 ++++------------
1 files changed, 4 insertions(+), 12 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 3e53559..efb9d9f 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -148,9 +148,10 @@
<tertiary>BIND as a Nameserver</tertiary>
</indexterm>
<para>
- BIND is set of DNS related programs. It contains a monolithic nameserver called <command>/usr/sbin/named</command>, an administration utility called <command>/usr/sbin/rndc</command> and DNS debugging utility called <command>/usr/bin/dig</command>. More information about <command>rndc</command> can be found in <xref linkend="s1-bind-rndc" />.
+ BIND consists of a set of DNS-related programs. It contains a monolithic nameserver called <command>named</command>, an administration utility called <command>rndc</command>, and a debugging tool called <command>dig</command>.
</para>
<!-- TODO: Add "dig" utility decription -->
+ <!-- TODO: Move these information to different sections.
<para>
BIND stores its configuration files in the following locations:
</para>
@@ -204,25 +205,16 @@
</listitem>
</varlistentry>
</variablelist>
- <!-- RHEL5: ddomingo at redhat.com: above <variablelist> replaces following <itemizedlist>:
- <itemizedlist>
- <listitem>
- <para><filename>/etc/named.conf</filename> — The configuration file for the <command>named</command> daemon.</para>
- </listitem>
- <listitem>
- <para><filename>/var/named/</filename> directory — The <command>named</command> working directory which stores zone, statistic, and cache files.</para>
- </listitem>
- </itemizedlist>
- -->
<note>
<title>Note</title>
<para>
- If you have installed the <filename>bind-chroot</filename> package, the BIND service will run in the <command>/var/named/chroot</command> environment. All configuration files will be automatically mounted (via <command>mount --bind</command>) there by initscript so you can manage your configuration in non-chroot environment. All files and directories written above are mounted.
+ If you have installed the <filename>bind-chroot</filename> package, the BIND service will run in the <command>/var/named/chroot</command> environment. All configuration files will be automatically mounted (via <command>mount ‐‐bind</command>) there by initscript so you can manage your configuration in non-chroot environment. All files and directories written above are mounted.
</para>
</note>
<para>
The next few sections review the BIND configuration in more detail.
</para>
+ -->
</section>
</section>
<section id="s1-bind-namedconf">
More information about the docs-commits
mailing list