diff options
Diffstat (limited to 'doc/arm/Bv9ARM.ch01.html')
| -rw-r--r-- | doc/arm/Bv9ARM.ch01.html | 98 |
1 files changed, 49 insertions, 49 deletions
diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index b2e28c05..c844c229 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $Id: Bv9ARM.ch01.html,v 1.16.18.12 2006/05/08 15:46:13 marka Exp $ --> +<!-- $Id: Bv9ARM.ch01.html,v 1.16.18.15 2006/07/20 02:33:47 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 1. Introduction</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.69.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> @@ -45,40 +45,40 @@ <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2544701">Scope of Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2544132">Organization of This Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2544545">Conventions Used in This Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2545545">The Domain Name System (<span class="acronym">DNS</span>)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569838">Scope of Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2568778">Organization of This Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569737">Conventions Used in This Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2570192">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2545566">DNS Fundamentals</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2545669">Domains and Domain Names</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2548211">Zones</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2548288">Authoritative Name Servers</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2548392">Caching Name Servers</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2548454">Name Servers in Multiple Roles</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570213">DNS Fundamentals</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570247">Domains and Domain Names</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570331">Zones</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2572661">Authoritative Name Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2572970">Caching Name Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2573032">Name Servers in Multiple Roles</a></span></dt> </dl></dd> </dl> </div> <p> - The Internet Domain Name System (<span class="acronym">DNS</span>) + The Internet Domain Name System (<acronym class="acronym">DNS</acronym>) consists of the syntax to specify the names of entities in the Internet in a hierarchical manner, the rules used for delegating authority over names, and the system implementation that actually maps names to Internet - addresses. <span class="acronym">DNS</span> data is maintained in a + addresses. <acronym class="acronym">DNS</acronym> data is maintained in a group of distributed hierarchical databases. </p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2544701"></a>Scope of Document</h2></div></div></div> +<a name="id2569838"></a>Scope of Document</h2></div></div></div> <p> The Berkeley Internet Name Domain - (<span class="acronym">BIND</span>) implements an + (<acronym class="acronym">BIND</acronym>) implements a domain name server for a number of operating systems. This document provides basic information about the installation and - care of the Internet Systems Consortium (<span class="acronym">ISC</span>) - <span class="acronym">BIND</span> version 9 software package for + care of the Internet Systems Consortium (<acronym class="acronym">ISC</acronym>) + <acronym class="acronym">BIND</acronym> version 9 software package for system administrators. </p> <p> @@ -87,20 +87,20 @@ </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2544132"></a>Organization of This Document</h2></div></div></div> +<a name="id2568778"></a>Organization of This Document</h2></div></div></div> <p> In this document, <span class="emphasis"><em>Section 1</em></span> introduces - the basic <span class="acronym">DNS</span> and <span class="acronym">BIND</span> concepts. <span class="emphasis"><em>Section 2</em></span> - describes resource requirements for running <span class="acronym">BIND</span> in various + the basic <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym> concepts. <span class="emphasis"><em>Section 2</em></span> + describes resource requirements for running <acronym class="acronym">BIND</acronym> in various environments. Information in <span class="emphasis"><em>Section 3</em></span> is <span class="emphasis"><em>task-oriented</em></span> in its presentation and is organized functionally, to aid in the process of installing the - <span class="acronym">BIND</span> 9 software. The task-oriented + <acronym class="acronym">BIND</acronym> 9 software. The task-oriented section is followed by <span class="emphasis"><em>Section 4</em></span>, which contains more advanced concepts that the system administrator may need for implementing certain options. <span class="emphasis"><em>Section 5</em></span> - describes the <span class="acronym">BIND</span> 9 lightweight + describes the <acronym class="acronym">BIND</acronym> 9 lightweight resolver. The contents of <span class="emphasis"><em>Section 6</em></span> are organized as in a reference manual to aid in the ongoing maintenance of the software. <span class="emphasis"><em>Section 7</em></span> addresses @@ -109,14 +109,14 @@ main body of the document is followed by several <span class="emphasis"><em>Appendices</em></span> which contain useful reference information, such as a <span class="emphasis"><em>Bibliography</em></span> and - historic information related to <span class="acronym">BIND</span> + historic information related to <acronym class="acronym">BIND</acronym> and the Domain Name System. </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2544545"></a>Conventions Used in This Document</h2></div></div></div> +<a name="id2569737"></a>Conventions Used in This Document</h2></div></div></div> <p> In this document, we use the following general typographic conventions: @@ -181,7 +181,7 @@ </table></div> <p> The following conventions are used in descriptions of the - <span class="acronym">BIND</span> configuration file:</p> + <acronym class="acronym">BIND</acronym> configuration file:</p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -243,17 +243,17 @@ </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2545545"></a>The Domain Name System (<span class="acronym">DNS</span>)</h2></div></div></div> +<a name="id2570192"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div> <p> The purpose of this document is to explain the installation - and upkeep of the <span class="acronym">BIND</span> software + and upkeep of the <acronym class="acronym">BIND</acronym> software package, and we begin by reviewing the fundamentals of the Domain Name System - (<span class="acronym">DNS</span>) as they relate to <span class="acronym">BIND</span>. + (<acronym class="acronym">DNS</acronym>) as they relate to <acronym class="acronym">BIND</acronym>. </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2545566"></a>DNS Fundamentals</h3></div></div></div> +<a name="id2570213"></a>DNS Fundamentals</h3></div></div></div> <p> The Domain Name System (DNS) is a hierarchical, distributed database. It stores information for mapping Internet host names to @@ -265,7 +265,7 @@ Clients look up information in the DNS by calling a <span class="emphasis"><em>resolver</em></span> library, which sends queries to one or more <span class="emphasis"><em>name servers</em></span> and interprets the responses. - The <span class="acronym">BIND</span> 9 software distribution + The <acronym class="acronym">BIND</acronym> 9 software distribution contains a name server, <span><strong class="command">named</strong></span>, and two resolver libraries, <span><strong class="command">liblwres</strong></span> and <span><strong class="command">libbind</strong></span>. @@ -273,7 +273,7 @@ </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2545669"></a>Domains and Domain Names</h3></div></div></div> +<a name="id2570247"></a>Domains and Domain Names</h3></div></div></div> <p> The data stored in the DNS is identified by <span class="emphasis"><em>domain names</em></span> that are organized as a tree according to organizational or administrative boundaries. Each node of the tree, @@ -307,7 +307,7 @@ </p> <p> The data associated with each domain name is stored in the - form of <span class="emphasis"><em>resource records</em></span> (<span class="acronym">RR</span>s). + form of <span class="emphasis"><em>resource records</em></span> (<acronym class="acronym">RR</acronym>s). Some of the supported resource record types are described in <a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" title="Types of Resource Records and When to Use Them">the section called “Types of Resource Records and When to Use Them”</a>. </p> @@ -319,7 +319,7 @@ </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2548211"></a>Zones</h3></div></div></div> +<a name="id2570331"></a>Zones</h3></div></div></div> <p> To properly operate a name server, it is important to understand the difference between a <span class="emphasis"><em>zone</em></span> @@ -327,7 +327,7 @@ </p> <p> As stated previously, a zone is a point of delegation in - the <span class="acronym">DNS</span> tree. A zone consists of + the <acronym class="acronym">DNS</acronym> tree. A zone consists of those contiguous parts of the domain tree for which a name server has complete information and over which it has authority. It contains all domain names from a certain point @@ -348,7 +348,7 @@ map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other - name servers. Every name in the <span class="acronym">DNS</span> + name servers. Every name in the <acronym class="acronym">DNS</acronym> tree is a <span class="emphasis"><em>domain</em></span>, even if it is <span class="emphasis"><em>terminal</em></span>, that is, has no @@ -360,7 +360,7 @@ topic. </p> <p> - Though <span class="acronym">BIND</span> is called a "domain name + Though <acronym class="acronym">BIND</acronym> is called a "domain name server", it deals primarily in terms of zones. The master and slave declarations in the <code class="filename">named.conf</code> file @@ -372,7 +372,7 @@ </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2548288"></a>Authoritative Name Servers</h3></div></div></div> +<a name="id2572661"></a>Authoritative Name Servers</h3></div></div></div> <p> Each zone is served by at least one <span class="emphasis"><em>authoritative name server</em></span>, @@ -389,7 +389,7 @@ </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2548311"></a>The Primary Master</h4></div></div></div> +<a name="id2572684"></a>The Primary Master</h4></div></div></div> <p> The authoritative server where the master copy of the zone data is maintained is called the @@ -409,7 +409,7 @@ </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2548341"></a>Slave Servers</h4></div></div></div> +<a name="id2572714"></a>Slave Servers</h4></div></div></div> <p> The other authoritative servers, the <span class="emphasis"><em>slave</em></span> servers (also known as <span class="emphasis"><em>secondary</em></span> servers) @@ -425,7 +425,7 @@ </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2548362"></a>Stealth Servers</h4></div></div></div> +<a name="id2572736"></a>Stealth Servers</h4></div></div></div> <p> Usually all of the zone's authoritative servers are listed in NS records in the parent zone. These NS records constitute @@ -460,7 +460,7 @@ </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2548392"></a>Caching Name Servers</h3></div></div></div> +<a name="id2572970"></a>Caching Name Servers</h3></div></div></div> <p> The resolver libraries provided by most operating systems are <span class="emphasis"><em>stub resolvers</em></span>, meaning that they are not @@ -482,12 +482,12 @@ </p> <p> The length of time for which a record may be retained in - in the cache of a caching name server is controlled by the + the cache of a caching name server is controlled by the Time To Live (TTL) field associated with each resource record. </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2548427"></a>Forwarding</h4></div></div></div> +<a name="id2573005"></a>Forwarding</h4></div></div></div> <p> Even a caching name server does not necessarily perform the complete recursive lookup itself. Instead, it can @@ -504,19 +504,19 @@ wish all the servers at a given site to interact directly with the rest of the Internet servers. A typical scenario would involve a number - of internal <span class="acronym">DNS</span> servers and an + of internal <acronym class="acronym">DNS</acronym> servers and an Internet firewall. Servers unable to pass packets through the firewall would forward to the server - that can do it, and that server would query the Internet <span class="acronym">DNS</span> servers + that can do it, and that server would query the Internet <acronym class="acronym">DNS</acronym> servers on the internal server's behalf. </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2548454"></a>Name Servers in Multiple Roles</h3></div></div></div> +<a name="id2573032"></a>Name Servers in Multiple Roles</h3></div></div></div> <p> - The <span class="acronym">BIND</span> name server can + The <acronym class="acronym">BIND</acronym> name server can simultaneously act as a master for some zones, a slave for other zones, and as a caching (recursive) server for a set of local clients. @@ -552,7 +552,7 @@ <tr> <td width="40%" align="left" valign="top">BIND 9 Administrator Reference Manual </td> <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td> -<td width="40%" align="right" valign="top"> Chapter 2. <span class="acronym">BIND</span> Resource Requirements</td> +<td width="40%" align="right" valign="top"> Chapter 2. <acronym class="acronym">BIND</acronym> Resource Requirements</td> </tr> </table> </div> |