diff options
| author | Jakob Schlyter <jakob@cvs.openbsd.org> | 2004-09-28 16:36:11 +0000 |
|---|---|---|
| committer | Jakob Schlyter <jakob@cvs.openbsd.org> | 2004-09-28 16:36:11 +0000 |
| commit | e89047d826b7f97551768d5ac32cbda8cb5b72b8 (patch) | |
| tree | 5ef67c015854f54a701d53b0fed0662a85e9f0d1 /usr.sbin/bind/doc/arm/Bv9ARM.ch01.html | |
| parent | 759ea572586be172c3e200dcfae39c1fc0ca1f5a (diff) | |
ISC BIND version 9.3.0. ok deraadt@
Diffstat (limited to 'usr.sbin/bind/doc/arm/Bv9ARM.ch01.html')
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch01.html | 297 |
1 files changed, 129 insertions, 168 deletions
diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html index ab899fa0919..5b3659e6101 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html @@ -1,11 +1,11 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >Introduction </TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.73 -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="BIND 9 Administrator Reference Manual" HREF="Bv9ARM.html"><LINK @@ -70,8 +70,8 @@ CLASS="chapter" ><H1 ><A NAME="ch01" ->Chapter 1. Introduction </A -></H1 +></A +>Chapter 1. Introduction </H1 ><DIV CLASS="TOC" ><DL @@ -81,40 +81,40 @@ CLASS="TOC" ></DT ><DT >1.1. <A -HREF="Bv9ARM.ch01.html#AEN13" +HREF="Bv9ARM.ch01.html#AEN15" >Scope of Document</A ></DT ><DT >1.2. <A -HREF="Bv9ARM.ch01.html#AEN20" +HREF="Bv9ARM.ch01.html#AEN22" >Organization of This Document</A ></DT ><DT >1.3. <A -HREF="Bv9ARM.ch01.html#AEN40" +HREF="Bv9ARM.ch01.html#AEN42" >Conventions Used in This Document</A ></DT ><DT >1.4. <A -HREF="Bv9ARM.ch01.html#AEN105" ->The Domain Name System (<SPAN +HREF="Bv9ARM.ch01.html#AEN107" +>The Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM >)</A ></DT ></DL ></DIV ><P ->The Internet Domain Name System (<SPAN +>The Internet Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>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 + addresses. <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > data is maintained in a group of distributed hierarchical databases.</P ><DIV @@ -122,34 +122,34 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN13" +NAME="AEN15" >1.1. Scope of Document</A ></H1 ><P ->The Berkeley Internet Name Domain (<SPAN +>The Berkeley Internet Name Domain (<ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM >) implements an domain name server for a number of operating systems. This document provides basic information about the installation and - care of the Internet Software Consortium (<SPAN + care of the Internet Software Consortium (<ACRONYM CLASS="acronym" ->ISC</SPAN +>ISC</ACRONYM >) - <SPAN + <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > version 9 software package for system administrators.</P ><P ->This version of the manual corresponds to BIND version 9.2.</P +>This version of the manual corresponds to BIND version 9.3.</P ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN20" +NAME="AEN22" >1.2. Organization of This Document</A ></H1 ><P @@ -160,12 +160,12 @@ CLASS="emphasis" >Section 1</I ></SPAN > introduces - the basic <SPAN + the basic <ACRONYM CLASS="acronym" ->DNS</SPAN -> and <SPAN +>DNS</ACRONYM +> and <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > concepts. <SPAN CLASS="emphasis" ><I @@ -173,9 +173,9 @@ CLASS="emphasis" >Section 2</I ></SPAN > - describes resource requirements for running <SPAN + describes resource requirements for running <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > in various environments. Information in <SPAN CLASS="emphasis" @@ -192,9 +192,9 @@ CLASS="emphasis" ></SPAN > in its presentation and is organized functionally, to aid in the process of installing the - <SPAN + <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 software. The task-oriented section is followed by <SPAN CLASS="emphasis" @@ -211,9 +211,9 @@ CLASS="emphasis" >Section 5</I ></SPAN > - describes the <SPAN + describes the <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 lightweight resolver. The contents of <SPAN CLASS="emphasis" @@ -253,9 +253,9 @@ CLASS="emphasis" >Bibliography</I ></SPAN > and - historic information related to <SPAN + historic information related to <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > and the Domain Name System.</P ></DIV @@ -264,7 +264,7 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN40" +NAME="AEN42" >1.3. Conventions Used in This Document</A ></H1 ><P @@ -272,11 +272,11 @@ NAME="AEN40" conventions:</P ><DIV CLASS="informaltable" -><A -NAME="AEN43" -></A ><P ></P +><A +NAME="AEN45" +></A ><TABLE CELLPADDING="3" BORDER="1" @@ -284,9 +284,6 @@ CLASS="CALSTABLE" ><TBODY ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P ><SPAN CLASS="emphasis" @@ -298,9 +295,6 @@ describe:</I ></P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P ><SPAN CLASS="emphasis" @@ -313,17 +307,11 @@ CLASS="emphasis" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P >a pathname, filename, URL, hostname, mailing list name, or new term or concept</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><TT CLASS="filename" @@ -333,42 +321,28 @@ CLASS="filename" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >literal user input</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><KBD CLASS="userinput" -><B ->Fixed Width Bold</B -></TT +>Fixed Width Bold</KBD ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >program output</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><SAMP CLASS="computeroutput" ->Fixed Width</TT +>Fixed Width</SAMP ></P ></TD ></TR @@ -379,16 +353,16 @@ CLASS="computeroutput" ></DIV ><P >The following conventions are used in descriptions of the -<SPAN +<ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > configuration file:<DIV CLASS="informaltable" -><A -NAME="AEN75" -></A ><P ></P +><A +NAME="AEN77" +></A ><TABLE CELLPADDING="3" BORDER="1" @@ -396,9 +370,6 @@ CLASS="CALSTABLE" ><TBODY ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><SPAN CLASS="emphasis" @@ -410,9 +381,6 @@ describe:</I ></P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><SPAN CLASS="emphasis" @@ -425,54 +393,36 @@ CLASS="emphasis" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >keywords</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><VAR CLASS="literal" ->Fixed Width</TT +>Fixed Width</VAR ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >variables</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><VAR CLASS="varname" ->Fixed Width</TT +>Fixed Width</VAR ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >Optional input</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >[<SPAN CLASS="optional" @@ -492,25 +442,25 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN105" ->1.4. The Domain Name System (<SPAN +NAME="AEN107" +>1.4. The Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM >)</A ></H1 ><P >The purpose of this document is to explain the installation -and upkeep of the <SPAN +and upkeep of the <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > software package, and we begin by reviewing the fundamentals of the Domain Name System -(<SPAN +(<ACRONYM CLASS="acronym" ->DNS</SPAN ->) as they relate to <SPAN +>DNS</ACRONYM +>) as they relate to <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM >. </P ><DIV @@ -518,7 +468,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN112" +NAME="AEN114" >1.4.1. DNS Fundamentals</A ></H2 ><P @@ -542,18 +492,29 @@ CLASS="emphasis" >name servers</I ></SPAN > and interprets the responses. -The <SPAN +The <ACRONYM CLASS="acronym" ->BIND 9</SPAN -> software distribution contains both a -name server and a resolver library.</P +>BIND</ACRONYM +> 9 software distribution contains a +name server, <B +CLASS="command" +>named</B +>, and two resolver +libraries, <B +CLASS="command" +>liblwres</B +> and <B +CLASS="command" +>libbind</B +>. +</P ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN119" +NAME="AEN124" >1.4.2. Domains and Domain Names</A ></H2 ><P @@ -593,30 +554,30 @@ CLASS="emphasis" >Example, Inc.</I ></SPAN > could be -<TT +<VAR CLASS="literal" ->mail.example.com</TT +>mail.example.com</VAR >, -where <TT +where <VAR CLASS="literal" ->com</TT +>com</VAR > is the top level domain to which -<TT +<VAR CLASS="literal" ->ourhost.example.com</TT +>ourhost.example.com</VAR > belongs, -<TT +<VAR CLASS="literal" ->example</TT +>example</VAR > is -a subdomain of <TT +a subdomain of <VAR CLASS="literal" ->com</TT +>com</VAR >, and -<TT +<VAR CLASS="literal" ->ourhost</TT +>ourhost</VAR > is the name of the host.</P ><P @@ -653,9 +614,9 @@ CLASS="emphasis" CLASS="emphasis" >resource records</I ></SPAN -> (<SPAN +> (<ACRONYM CLASS="acronym" ->RR</SPAN +>RR</ACRONYM >s). Some of the supported resource record types are described in <A @@ -667,7 +628,7 @@ HREF="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" the DNS protocol, please refer to the standards documents listed in <A HREF="Bv9ARM.ch09.html#rfcs" ->Section A.4.1</A +>Section A.3.1</A >.</P ></DIV ><DIV @@ -675,7 +636,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN143" +NAME="AEN148" >1.4.3. Zones</A ></H2 ><P @@ -696,12 +657,12 @@ CLASS="emphasis" >.</P ><P >As we stated previously, a zone is a point of delegation in -the <SPAN +the <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > tree. A zone consists of those contiguous parts of the domain -tree for which a a name server has complete information and over which +tree for which a name server has complete information and over which it has authority. It contains all domain names from a certain point downward in the domain tree except those which are delegated to other zones. A delegation point is marked by one or more @@ -715,36 +676,36 @@ CLASS="emphasis" parent zone, which should be matched by equivalent NS records at the root of the delegated zone.</P ><P ->For instance, consider the <TT +>For instance, consider the <VAR CLASS="literal" ->example.com</TT +>example.com</VAR > domain which includes names -such as <TT +such as <VAR CLASS="literal" ->host.aaa.example.com</TT +>host.aaa.example.com</VAR > and -<TT +<VAR CLASS="literal" ->host.bbb.example.com</TT +>host.bbb.example.com</VAR > even though -the <TT +the <VAR CLASS="literal" ->example.com</TT +>example.com</VAR > zone includes -only delegations for the <TT +only delegations for the <VAR CLASS="literal" ->aaa.example.com</TT +>aaa.example.com</VAR > and -<TT +<VAR CLASS="literal" ->bbb.example.com</TT +>bbb.example.com</VAR > zones. A zone can 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 +name servers. Every name in the <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > tree is a <SPAN CLASS="emphasis" @@ -772,9 +733,9 @@ not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to gain a complete understanding of this difficult and subtle topic.</P ><P ->Though <SPAN +>Though <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > is called a "domain name server", it deals primarily in terms of zones. The master and slave declarations in the <TT @@ -796,7 +757,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN166" +NAME="AEN171" >1.4.4. Authoritative Name Servers</A ></H2 ><P @@ -821,14 +782,14 @@ CLASS="command" >dig</B > (<A HREF="Bv9ARM.ch03.html#diagnostic_tools" ->Section 3.4.1.1</A +>Section 3.3.1.1</A >).</P ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN173" +NAME="AEN178" >1.4.4.1. The Primary Master</A ></H3 ><P @@ -868,7 +829,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN180" +NAME="AEN185" >1.4.4.2. Slave Servers</A ></H3 ><P @@ -903,7 +864,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN186" +NAME="AEN191" >1.4.4.3. Stealth Servers</A ></H3 ><P @@ -960,7 +921,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN195" +NAME="AEN200" >1.4.5. Caching Name Servers</A ></H2 ><P @@ -1017,7 +978,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN205" +NAME="AEN210" >1.4.5.1. Forwarding</A ></H3 ><P @@ -1045,14 +1006,14 @@ and they are queried in turn until the list is exhausted or an answer is found. Forwarders are typically used when you do not 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 +of internal <ACRONYM CLASS="acronym" ->DNS</SPAN +>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 +that can do it, and that server would query the Internet <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete @@ -1065,13 +1026,13 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN213" +NAME="AEN218" >1.4.6. Name Servers in Multiple Roles</A ></H2 ><P ->The <SPAN +>The <ACRONYM CLASS="acronym" ->BIND</SPAN +>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.</P @@ -1158,9 +1119,9 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" -><SPAN +><ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > Resource Requirements</TD ></TR ></TABLE |