[deployment-guide/comm-rel: 377/727] Removed the outdated comment.

[Jaromir Hradilek]

commit 5d1df4ebe278f3f016640960d908f9e7d7851e06
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 16 13:49:45 2010 +0200

    Removed the outdated comment.

 en-US/The_BIND_DNS_Server.xml |   26 --------------------------
 1 files changed, 0 insertions(+), 26 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 939141a..5b70fb6 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -1082,32 +1082,6 @@ options {
           </listitem>
         </varlistentry>
       </variablelist>
-      <!-- RHEL5:   ddomingo at redhat.com: above <variablelist> replaces following <itemizedlist>:
-      <itemizedlist>
-        <listitem>
-          <para><command>$INCLUDE</command> &mdash; Configures <command>named</command> to include another zone file in this zone file at the place where the directive appears. This allows additional zone settings to be stored apart
-            from the main zone file.</para>
-        </listitem>
-        <listitem>
-          <para><command>$ORIGIN</command> &mdash; Appends the domain name to unqualified records, such as those with the hostname and nothing more.</para>
-          <para>For example, a zone file may contain the following line:</para>
-<screen>
-<command>$ORIGIN example.com.</command>
-</screen>
-          <para>Any names used in resource records that do not end in a trailing period (<command>.</command>) are appended with <command>example.com</command>.</para>
-          <note>
-            <title>Note</title>
-            <para>The use of the <command>$ORIGIN</command> directive is unnecessary if the zone is specified in <filename>/etc/named.conf</filename> because the zone name is used as the value for the
-              <command>$ORIGIN</command> directive by default.</para>
-          </note>
-        </listitem>
-        <listitem>
-          <para><command>$TTL</command> &mdash; Sets the default <firstterm>Time to Live (TTL)</firstterm> value for the zone. This is the length of time, in seconds, a zone resource record is valid. Each resource record can contain its own TTL
-            value, which overrides this directive.</para>
-          <para>Increasing this value allows remote nameservers to cache the zone information for a longer period of time, reducing the number of queries for the zone and lengthening the amount of time required to proliferate resource record changes.</para>
-        </listitem>
-      </itemizedlist>
- -->
     </section>
     <section id="s3-bind-zone-rr">
       <title>Common Resource Records</title>