svn commit: r44393 - head/en_US.ISO8859-1/books/handbook/network-servers

[Brad Davis]

Author: brd
Date: Mon Mar 31 00:32:09 2014
New Revision: 44393
URL: http://svnweb.freebsd.org/changeset/doc/44393

Log:
  - First pass at making the DNS section less BIND specific and mentioning Unbound.

Modified:
  head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml	Sun Mar 30 20:44:41 2014	(r44392)
+++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml	Mon Mar 31 00:32:09 2014	(r44393)
@@ -2945,33 +2945,41 @@ dhcpd_ifaces="dc0"</programlisting>
     -->
     <title>Domain Name System (<acronym>DNS</acronym>)</title>
 
-    <indexterm><primary>BIND</primary></indexterm>
+    <indexterm><primary>DNS</primary></indexterm>
 
     <para>Domain Name System (<acronym>DNS</acronym>) is the protocol
       through which domain names are mapped to <acronym>IP</acronym>
-      addresses, and vice versa.  By default, &os; installs the
-      Berkeley Internet Name Domain (<acronym>BIND</acronym>), which
-      is the most common implementation of the <acronym>DNS</acronym>
-      protocol.  The &os; version provides enhanced security features,
-      a new file system layout, and automated &man.chroot.8;
-      configuration.  BIND is maintained by the <link
-	xlink:href="https://www.isc.org/">isc.org</link>.  It is not
-      necessary to run a name server to perform <acronym>DNS</acronym>
-      lookups on a system.</para>
+      addresses, and vice versa.  <acronym>DNS</acronym> is coordinated
+      across the Internet through a somewhat complex system of
+      authoritative root, Top Level Domain (<acronym>TLD</acronym>),
+      and other smaller-scale name servers, which host and cache
+      individual domain information.  It is not necessary to run a name
+      server to perform <acronym>DNS</acronym> lookups on a system.</para>
 
-    <indexterm><primary>DNS</primary></indexterm>
-    <para><acronym>DNS</acronym> is coordinated across the Internet
-      through a somewhat complex system of authoritative root, Top
-      Level Domain (<acronym>TLD</acronym>), and other smaller-scale
-      name servers, which host and cache individual domain
-      information.  Table 28.4 describes some of the terms associated
-      with <acronym>DNS</acronym>:</para>
+    <indexterm><primary>BIND</primary></indexterm>
+
+    <para>In &os; 10, the Berkeley Internet Name Domain
+      (<acronym>BIND</acronym>) has been removed from the base system
+      and replaced with Unbound.  Unbound as configured in the &os;
+      Base is a local caching resolver.  <acronym>BIND</acronym> is
+      still available from The Ports Collection as <package
+      role="port">dns/bind99</package> or <package
+      role="port">dns/bind98</package>.  In &os; 9 and lower,
+      <acronym>BIND</acronym> is included in &os; Base.  The &os;
+      version provides enhanced security features, a new file system
+      layout, and automated &man.chroot.8; configuration.
+      <acronym>BIND</acronym> is maintained by the <link
+      xlink:href="https://www.isc.org/">Internet Systems
+      Consortium</link>.</para>
 
     <indexterm><primary>resolver</primary></indexterm>
     <indexterm><primary>reverse
       <acronym>DNS</acronym></primary></indexterm>
     <indexterm><primary>root zone</primary></indexterm>
 
+    <para>The following table describes some of the terms associated
+      with <acronym>DNS</acronym>:</para>
+
     <table frame="none" pgwide="1">
       <title><acronym>DNS</acronym> Terminology</title>