[deployment-guide/comm-rel: 285/727] Removed redundant information.

[Jaromir Hradilek]

commit cc1be2969faa2c2272f9f36ab54b0422c3a34b57
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Mon Aug 9 14:33:36 2010 +0200

    Removed redundant information.

 en-US/The_BIND_DNS_Server.xml |    8 +-------
 1 files changed, 1 insertions(+), 7 deletions(-)
---
diff --git a/en-US/The_BIND_DNS_Server.xml b/en-US/The_BIND_DNS_Server.xml
index 04773bd..af98730 100644
--- a/en-US/The_BIND_DNS_Server.xml
+++ b/en-US/The_BIND_DNS_Server.xml
@@ -53,13 +53,7 @@
   <section id="s1-bind-introduction">
     <title>Introduction to DNS</title>
     <para>
-      <!-- RHEL5:        When hosts on a network connect to one another via a hostname, also called a <firstterm>fully qualified domain name (FQDN)</firstterm>, DNS is used to associate the names of machines to the IP address for the host. --> DNS associates hostnames with their respective IP addresses, so that when users want to connect to other machines on the network, they can refer to them by name, without having to remember IP addresses.
-    </para>
-    <para>
-      Use of DNS also has advantages for system administrators, allowing the flexibility to change the IP address for a host without affecting name-based queries to the machine. Conversely, administrators can shuffle which machines handle a name-based query.
-    </para>
-    <para>
-      DNS is normally implemented using centralized servers that are authoritative for some domains and refer to other DNS servers for other domains.
+      DNS is usually implemented using one or more cenralized servers that are authoritative for certain domains. When a different domain is requested, they refer to other nameserver instead.
     </para>
     <para>
       When a client host requests information from a nameserver, it usually connects to port 53. The nameserver then attempts to resolve the name requested. If the nameserver does not have an authoritative answer about the name the which host requested, or does not already have the answer cached from an earlier query, it queries other nameservers, called <firstterm>root nameservers</firstterm>, to determine which nameservers are authoritative for the name in question. Then, with that information, it queries the authoritative nameservers to get the requested name.