upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-06-11 12:30:00 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

imported new ARM; fixed broken link at the end of each section

Browse source
This commit is contained in:
Andreas Gustafsson 2000-06-28 23:04:13 +00:00
parent 089b7bf0a5
commit 717cea5293
12 changed files with 11239 additions and 11681 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

127
doc/arm/Bv9ARM.1.html
View file

@ -1,89 +1,71 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.1.html,v 1.5 2000/06/22 21:53:38 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 1. Introduction </TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=1007883">
</A>
Section 1. Introduction </H1>
</OL>
<P CLASS="1LevelContinued">
<A NAME="pgfId=1007884">
</A>
The Internet Domain Name System (DNS) 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. DNS data is maintained in a group of distributed hierarchical databases.</P>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997352">
</A>
1.1 Scope of Document</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
The Berkeley Internet Name Domain (BIND) implements an Internet nameserver for a number of operating systems. This document provides basic information about the installation and care of the Internet Software Consortium (ISC) BIND version 9 software package for system administrators.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997354">
</A>
1.2 Organization of This Document</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
<A NAME="pgfId=1155516">
</A>
In this document, <A HREF="Bv9ARM.2.html"><EM CLASS="Emphasis">
Section 1</EM></A>
introduces the basic DNS and BIND concepts. <A HREF="Bv9ARM.2.html"><EM CLASS="Emphasis">
Section 2</EM></A>
describes resource requirements for running BIND in various environments. Information in <A HREF="Bv9ARM.3.html"><EM CLASS="Emphasis">
Section 3</EM></A>
In this document, <EM CLASS="Emphasis">
Section 1</EM>
introduces the basic DNS and BIND concepts. <EM CLASS="Emphasis">
Section 2</EM>
describes resource requirements for running BIND in various environments. Information in <EM CLASS="Emphasis">
Section 3</EM>
is <EM CLASS="Emphasis">
task-oriented</EM>
in its presentation and is organized functionally, to aid in the process of installing the BINDv9 software. The task-oriented section is followed by <A HREF="Bv9ARM.4.html"><EM CLASS="Emphasis">
Section 4</EM></A>
, which contains more advanced concepts that the system administrator may need for implementing certain options. The contents of <A HREF="Bv9ARM.5.html"><EM CLASS="Emphasis">
Section 5</EM></A>
are organized as in a reference manual to aid in the ongoing maintenance of the software. <A HREF="Bv9ARM.6.html"><EM CLASS="Emphasis">
Section 6</EM></A>
addresses security considerations, and <A HREF="Bv9ARM.7.html"><EM CLASS="Emphasis">
Section 7</EM></A>
contains troubleshooting help. The main body of the document is followed by several <A HREF="Bv9ARM.8.html"><EM CLASS="Emphasis">
Appendices</EM></A>
in its presentation and is organized functionally, to aid in the process of installing the BIND&nbsp;9 software. The task-oriented section is followed by <EM CLASS="Emphasis">
Section 4</EM>
, which contains more advanced concepts that the system administrator may need for implementing certain options. Section 5 describes the BIND&nbsp;9 lightweight resolver. The contents of <EM CLASS="Emphasis">
Section 6</EM>
are organized as in a reference manual to aid in the ongoing maintenance of the software. <EM CLASS="Emphasis">
Section 7 </EM>
addresses security considerations, and <EM CLASS="Emphasis">
Section 8</EM>
contains troubleshooting help. The main body of the document is followed by several <EM CLASS="Emphasis">
Appendices</EM>
which contain useful reference information, such as a <EM CLASS="Emphasis">
Glossary</EM>
and a <EM CLASS="Emphasis">
Bibliography</EM>
, as well as historic information related to BIND and the Domain Name System.</P>
and historic information related to BIND and the Domain Name System.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997356">
</A>
1.3 Conventions Used in This Document</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997382">
</A>
@ -207,8 +189,8 @@ keywords</P>
<P CLASS="CellBody6">
<A NAME="pgfId=997391">
</A>
<CODE CLASS="production_target">
Sans Serif Bold</CODE>
<EM CLASS="production_target">
Sans Serif Bold</EM>
</P>
</TD>
</TR>
@ -293,12 +275,12 @@ Text is enclosed in square brackets</P>
</TABLE>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997413">
</A>
1.4 Discussion of Domain Name System (DNS) Basics and BIND</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997414">
</A>
@ -316,12 +298,12 @@ resolver</CODE>
resolver</EM>
is a set of routines residing in a system library that provides the interface that programs can use to access the domain name services.</P>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997415">
</A>
1.4.1 Nameservers</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997416">
</A>
@ -374,16 +356,16 @@ resolver</CODE>
.</P>
</DIV>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997421">
</A>
1.4.2 Types of Zones</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997422">
</A>
As we stated previously, a zone is a point of delegation in the DNS tree. A zone consists of those contiguous parts of the domain tree for which a domain 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 has one or more NS records in the parent zone, which should be matched by equivalent NS records at the root of the delegated zone (i.e., the &quot;@&quot; name in the zone file).</P>
As we stated previously, a zone is a point of delegation in the DNS tree. A zone consists of those contiguous parts of the domain tree for which a domain 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 has one or more NS records in the parent zone, which should be matched by equivalent NS records at the root of the delegated zone.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997423">
</A>
@ -417,11 +399,11 @@ subdomains</EM>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1007878">
</A>
Though BIND is a Domain Nameserver, it deals primarily in terms of zones. The primary and secondary declarations in the <CODE CLASS="Program-Process">
named.conf</CODE>
file specify zones, not domains. When you ask some other site if it is willing to be a secondary server for your <EM CLASS="Emphasis">
Though BIND is a Domain Nameserver, it deals primarily in terms of zones. The master and slave declarations in the <EM CLASS="pathname">
named.conf</EM>
file specify zones, not domains. When you ask some other site if it is willing to be a slave server for your <EM CLASS="Emphasis">
domain</EM>
, you are actually asking for secondary service for some collection of zones.</P>
, you are actually asking for slave service for some collection of zones.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997426">
</A>
@ -458,12 +440,12 @@ authoritative</EM>
Adding a zone as a type master or type slave will tell the server to answer questions for the zone authoritatively. If the server is able to load the zone into memory without any errors it will set the AA bit when it replies to queries for the zone. See RFCs 1034 and 1035 for more information about the AA bit.</P>
</DIV>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997431">
</A>
1.4.3 Servers</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997432">
</A>
@ -479,12 +461,12 @@ secondaries</EM>
</A>
All servers keep data in their cache until the data expires, based on a Time To Live (TTL) field which is maintained for all resource records.</P>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997434">
</A>
1.4.3.1 Master Server</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997435">
</A>
@ -493,12 +475,12 @@ primary master server</EM>
is the ultimate source of information about a domain. The primary master is an authoritative server configured to be the source of zone transfer for one or more secondary servers. The primary master server obtains data for the zone from a file on disk.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997436">
</A>
1.4.3.2 Slave Server </H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997437">
</A>
@ -509,12 +491,12 @@ secondary server</EM>
, is an authoritative server that uses zone transfers from the primary master server to retrieve the zone data. Optionally, the slave server obtains zone data from a cache on disk. Slave servers provide necessary redundancy. All secondary/slave servers are named in the NS RRs for the zone.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997438">
</A>
1.4.3.3 Caching Only Server</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997439">
</A>
@ -523,12 +505,12 @@ caching only servers</EM>
. This means that the server caches the information that it receives and uses it until the data expires. A caching only server is a server that is not authoritative for any zone. This server services queries and asks other servers, who have the authority, for the information it needs.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997440">
</A>
1.4.3.4 Forwarding Server</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997441">
</A>
@ -543,12 +525,12 @@ recursive queries</EM>
There is no prohibition against declaring a server to be a forwarder even though it has master and/or slave zones as well; the effect will still be that anything in the local server's cache or zones will be answered, and anything else will be forwarded using the forwarders list.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997443">
</A>
1.4.3.5 Stealth Server</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1014846">
</A>
@ -558,8 +540,9 @@ stealth server</EM>
</DIV>
</DIV>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</BODY>
</HTML>

62
doc/arm/Bv9ARM.2.html
View file

@ -1,23 +1,4 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.2.html,v 1.5 2000/06/22 21:53:39 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
@ -27,75 +8,75 @@
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
</A>
Section 2. BIND Resource Requirements</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997351">
</A>
</A>
2.1 Hardware requirements</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997352">
</A>
</A>
DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
The DNSSEC and IPv6 features of BINDv9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BINDv9 is now fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.</P>
</A>
The DNSSEC and IPv6 features of BIND&nbsp;9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BIND&nbsp;9 is now fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997354">
</A>
</A>
2.2 CPU Requirements</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
CPU requirements for BINDv9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.</P>
</A>
CPU requirements for BIND&nbsp;9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997356">
</A>
</A>
2.3 Memory Requirements </H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997357">
</A>
The memory of the server has to be large enough to fit the cache and zones loaded off disk. Future releases of BINDv9 will provide methods to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. It is still good practice to have enough memory to load all zone and cache data into memory--unfortunately, the best way to determine this for a given installation is to watch the nameserver in operation. After a few weeks the server process should reach a relatively stable size where entries are expiring from the cache as fast as they are being inserted. Ideally, the resource limits should be set higher than this stable size.</P>
</A>
The memory of the server has to be large enough to fit the cache and zones loaded off disk. Future releases of BIND&nbsp;9 will provide methods to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. It is still good practice to have enough memory to load all zone and cache data into memory--unfortunately, the best way to determine this for a given installation is to watch the nameserver in operation. After a few weeks the server process should reach a relatively stable size where entries are expiring from the cache as fast as they are being inserted. Ideally, the resource limits should be set higher than this stable size.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997358">
</A>
</A>
2.4 Nameserver Intensive Environment Issues</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
</A>
For nameserver intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal nameservers query a main nameserver, which has enough memory to build a large cache. This approach minimizes the bandwidth used by external name lookups. The second alternative is to set up second-level internal nameservers to make queries independently. In this configuration, none of the individual machines needs to have as much memory or CPU power as in the first alternative, but this has the disadvantage of making many more external queries, as none of the nameservers share their cached data.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997360">
</A>
2.5 Operating Systems Supported by the Internet Software Consortium</H3>
</A>
2.5 Supported Operating Systems</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997361">
</A>
ISC BINDv9 compiles and runs on the following operating systems:</P>
</A>
ISC BIND&nbsp;9 compiles and runs on the following operating systems:</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997362">
</A>
</A>
IBM AIX 4.3<BR>
Compaq Digital/Tru64 UNIX 4.0D<BR>
HP HP-UX 11<BR>
@ -105,8 +86,9 @@ Sun Solaris 2.6, 7, 8 (beta)<BR>
FreeBSD 3.4-STABLE<BR>
NetBSD-current with &quot;unproven&quot; pthreads</P>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</BODY>
</HTML>

468
doc/arm/Bv9ARM.3.html
View file

@ -1,128 +1,122 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.3.html,v 1.5 2000/06/22 21:53:40 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 3. Nameserver Configuration</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
Section 3. Nameserver Configuration</H1>
</OL>
<P CLASS="1LevelContinued">
<A NAME="pgfId=997351">
</A>
In this section we provide some suggested configurations along with guidelines for their use. We also address the topic of reasonable option setting.</P>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997353">
</A>
3.1 <A NAME="30164">
</A>
Sample Configuration and Logging</H3>
</A>
Sample Configurations</H3>
</OL>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=1079232">
</A>
3.1.1 A Caching-only Nameserver</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1079238">
</A>
The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All queries from outside clients are refused.</P>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997354"></A>
<CODE CLASS="grammar_literal">logging {
channel </CODE><EM CLASS="variable">named_log</EM><CODE CLASS="grammar_literal"> {
file </CODE><CODE CLASS="Program-Process">&quot;</CODE><KBD CLASS="Literal-user-input">logs/named.log</KBD><CODE CLASS="Program-Process">&quot;</CODE><CODE CLASS="grammar_literal">;
print-time </CODE><EM CLASS="variable">yes</EM><CODE CLASS="grammar_literal">;
print-category </CODE><EM CLASS="variable">yes</EM><CODE CLASS="grammar_literal">;
print-severity </CODE><EM CLASS="variable">yes</EM<CODE CLASS="grammar_literal">;
severity </CODE><EM CLASS="variable">info</EM><CODE CLASS="grammar_literal">;
<PRE>
<CODE><STRONG>
// Two corporate subnets we wish to allow queries from.
acl &quot;corpnets&quot; { 192.168.4.0/24; 192.168.7.0/24; };
options {
directory &quot;/etc/namedb&quot;; // Working directory
pid-file &quot;named.pid&quot;; // Put pid file in working dir
allow-query { &quot;corpnets &quot;; };
};
<CODE CLASS="grammar_literal">channel</CODE> <EMCLASS="variable">security_log</EM><CODE CLASS="grammar_literal"> {
file </CODE><CODE CLASS="Program-Process">&quot;</CODE><KBD CLASS="Literal-user-input">logs/security.log</KBD><CODE CLASS="Program-Process">&quot;</CODE><CODE CLASS="grammar_literal"> versions</CODE> <EM CLASS="variable">7</EM><CODE CLASS="grammar_literal"> ;
print-time </CODE><EM CLASS="variable">yes</EM><CODE CLASS="grammar_literal">;
};
category </CODE><EM CLASS="variable">default</EM><CODE CLASS="grammar_literal"> { named_log; default_debug; };
category </CODE><EM CLASS="variable">security</EM><CODE CLASS="grammar_literal"> { security_log };
};
// The two corporate subnets.
// Use real IP numbers
// here in the real world.
acl </CODE><EM CLASS="variable">corpnet</EM><CODE CLASS="grammar_literal"> { 192.168.4.0/24; 192.168.7.0/24; };
// The options statement.
options {
directory &quot;</CODE><KBD CLASS="Literal-user-input">/etc/namedb</KBD><CODE CLASS="grammar_literal">&quot;; // Directory
pid-file &quot;</CODE><KBD CLASS="Literal-user-input">named.pid</KBD><CODE CLASS="grammar_literal">&quot;; // Put .pid file in named directory.
check-names master </CODE><EM CLASS="variable">fail</EM><CODE CLASS="grammar_literal">; // Fail on db errors in master zones.
check-names slave </CODE><EM CLASS="variable">warn</EM><CODE CLASS="grammar_literal">; // Warn about db errors
// in slave zones.
check-names response </CODE><EM CLASS="variable">warn</EM><CODE CLASS="grammar_literal">; // Warn about invalid responses
use-id-pool </CODE><EM CLASS="variable">yes</EM><CODE CLASS="grammar_literal">; // Help prevent spoofing
host-statistics </CODE><EM CLASS="variable">yes</EM><CODE CLASS="grammar_literal">; // Keep track of hosts/servers
// we've talked to.
listen-on { 192.168.7.20; }; // Listen on this address.
query-source address 192.168.7.20 port 53 ;
// Source queries from port 53
// to get past firewall.
allow-transfer { </CODEz<EM CLASS="variable">none</EM><CODE CLASS="grammar_literal">; }; // Don't allow anyone to
// transfer zones.
allow-query { corpnet; }; // Allow only corpnets to query server.
// Helps prevent DoS, spoofing.
allow-recursion { corpnet; }; // Same, except this is for recursion.
};
</CODE>
</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=1007322"></A>
<CODE CLASS="grammar_literal">include &quot;</CODE><KBD CLASS="Literal-user-input">keys.conf</KBD><CODE CLASS="grammar_literal">&quot;; // Include a keys.conf with
// TSIG/DNSSEC keys.
// Shouldn't be readable to anyone
// except BIND user.
zone &quot;.&quot;{ type </CODE><EM CLASS="variable">hint</EM><CODE CLASS="grammar_literal">; file &quot;</CODE><KBD CLASS="Literal-user-input">local/named.root</KBD><CODE CLASS="grammar_literal">&quot;; };
// root hints</CODE></PRE<PRE CLASS="2Level-fixed"><A NAME="pgfId=997391"></A>
<CODE CLASS="grammar_literal">zone &quot;0.0.127.IN-ADDR.ARPA&quot; {</CODE>
</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=1079048"></A>
<CODE CLASS="grammar_literal"> type </CODE><EM CLASS="variable">master</EM><CODE CLASS="grammar_literal">; file &quot;</CODE><KBD CLASS="Literal-user-input">local/localhost.db</KBD><CODE CLASS="grammar_literal">&quot;; notify </CODE><EM CLASS="variable">no</EM><CODE CLASS="grammar_literal">;
// localhost
};</CODE>
</PRE><PRE CLASS="2Level-fixed"><A NAME="pgfId=1078744"></A><CODE CLASS="grammar_literal">zone &quot;</CODE><KBD CLASS="Literal-user-input">example.com</KBD><CODE CLASS="grammar_literal">&quot; { // Example zone for &quot;example.com&quot;.
type </CODE><EM CLASS="variable">master</EM><CODE CLASS="grammar_literal">; // It's a master zone.
file &quot;</CODE><KBD CLASS="Literal-user-input">m/example.com.db</KBD><CODE CLASS="grammar_literal">&quot;; // The file is here.
allow-query { </CODE><EM CLASS="variable">any</EM><CODE CLASS="grammar_literal">; }; // Allow anyone to query.
allow-transfer { corpnet; }; // Only allow corp nets to transfer zone.
};</CODE>
// Root server hints
zone &quot;.&quot; { type hint; file &quot;root.hint&quot;; };
// Provide a reverse mapping for the loopback address 127.0.0.1
zone &quot;0.0.127.in-addr.arpa&quot; {
type master;
file &quot;localhost.rev&quot;;
notify no;
<PRE CLASS="2Level-fixed"><A NAME="pgfId=1079157"></A>
<CODE CLASS="grammar_literal">zone &quot;</CODE><KBD CLASS="Literal-user-input">offsite.example.com</KBD><CODE CLASS="grammar_literal">&quot; { // Example zone for an off-site corp zone.
type </CODE><EM CLASS="variable">slave</EM><CODE CLASS="grammar_literal">; // It's a slave zone.
masters { 192.168.4.12; }; // The master is at this address.
file &quot;</CODE><KBD CLASS="Literal-user-input">s/offsite.example.com.db</KBD><CODE CLASS="grammar_literal">&quot;; // The file is here.
notify </CODE><EM CLASS="variable">no</EM><CODE CLASS="grammar_literal">; // Don't worry about NOTIFYing.
allow-query { </CODE><EM CLASS="variable">any</EM><CODE CLASS="grammar_literal">; }; // Allow anyone to query.
};</CODE>
};</STRONG></CODE>
</PRE>
</DIV>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=1079323">
</A>
3.1.2 An Authoritative-only Nameserver</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1079327">
</A>
This sample configuration is for an authoritative-only server that is the master server for &quot;<EM CLASS="pathname">
example.com</EM>
&quot; and a slave for the subdomain &quot;<EM CLASS="pathname">
eng.example.com</EM>
&quot;.</P>
<PRE>
<CODE><STRONG>options {
directory &quot;/etc/namedb&quot;; // Working directory
pid-file &quot;named.pid&quot;; // Put pid file in working dir
allow-query { any; }; // This is the default
recursion no; // Do not provide recursive service
};
// Root server hints
zone &quot;.&quot; { type hint; file &quot;root.hint&quot;; };&nbsp;
// Provide a reverse mapping for the loopback address 127.0.0.1
zone &quot;0.0.127.in-addr.arpa&quot; {
type master;
file &quot;localhost.rev&quot;;
notify no;
};
// We are the master server for example.com
zone &quot;example.com&quot; {
type master;
file &quot;example.com.db&quot;;
// IP addresses of slave servers allowed to transfer example.com
allow-transfer {
192.168.4.14;
192.168.5.53;
};
};
// We are a slave server for eng.example.com
zone &quot;eng.example.com&quot; {
type slave;
file &quot;eng.example.com.bk&quot;;
// IP address of eng.example.com master server
masters { 192.168.4.12; };
};
</STRONG></CODE></PRE>
</DIV>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997410">
</A>
3.2 Load Balancing and Round Robin</H3>
3.2 Load Balancing</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997411">
</A>
@ -130,218 +124,242 @@ Primitive load balancing can be achieved in DNS using multiple A records for one
<P CLASS="2LevelContinued">
<A NAME="pgfId=997412">
</A>
For example, if you have three WWW servers with network addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records like the following means that clients will connect to each machine one third of the time:</P>
For example, if you have three WWW servers with network addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the following means that clients will connect to each machine one third of the time:</P>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997454"></A>
&nbsp;</PRE>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997415"></A>
<A NAME="pgfId=997415">
</A>
Name</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997417"></A>
<A NAME="pgfId=997417">
</A>
TTL</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997419"></A>
<A NAME="pgfId=997419">
</A>
CLASS</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997421"></A>
<A NAME="pgfId=997421">
</A>
TYPE</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997423"></A>
<A NAME="pgfId=997423">
</A>
Resource Record (RR) Data</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997425"></A>
<CODE CLASS="grammar_literal">
www</CODE>
<A NAME="pgfId=997425">
</A>
<EM CLASS="grammar_literal">
www</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997427"></A>
<CODE CLASS="grammar_literal">
600</CODE>
<A NAME="pgfId=997427">
</A>
<EM CLASS="grammar_literal">
600</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997429"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
<A NAME="pgfId=997429">
</A>
<EM CLASS="grammar_literal">
IN</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997431"></A>
<CODE CLASS="grammar_literal">
A</CODE>
<A NAME="pgfId=997431">
</A>
<EM CLASS="grammar_literal">
A</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997433"></A>
<CODE CLASS="grammar_literal">
10.0.0.1</CODE>
<A NAME="pgfId=997433">
</A>
<EM CLASS="grammar_literal">
10.0.0.1</EM>
</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997435"></A>
<CODE CLASS="grammar_literal">
</CODE>
<A NAME="pgfId=997435">
</A>
<EM CLASS="grammar_literal">
</EM>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997437"></A>
<CODE CLASS="grammar_literal">
600</CODE>
<A NAME="pgfId=997437">
</A>
<EM CLASS="grammar_literal">
600</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997439"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
<A NAME="pgfId=997439">
</A>
<EM CLASS="grammar_literal">
IN</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997441"></A>
<CODE CLASS="grammar_literal">
A</CODE>
<A NAME="pgfId=997441">
</A>
<EM CLASS="grammar_literal">
A</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997443"></A>
<CODE CLASS="grammar_literal">
10.0.0.2</CODE>
<A NAME="pgfId=997443">
</A>
<EM CLASS="grammar_literal">
10.0.0.2</EM>
</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997445"></A>
<CODE CLASS="grammar_literal">
</CODE>
<A NAME="pgfId=997445">
</A>
<EM CLASS="grammar_literal">
</EM>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997447"></A>
<CODE CLASS="grammar_literal">
600</CODE>
<A NAME="pgfId=997447">
</A>
<EM CLASS="grammar_literal">
600</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997449"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
<A NAME="pgfId=997449">
</A>
<EM CLASS="grammar_literal">
IN</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997451"></A>
<CODE CLASS="grammar_literal">
A</CODE>
<A NAME="pgfId=997451">
</A>
<EM CLASS="grammar_literal">
A</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997453"></A>
<CODE CLASS="grammar_literal">
10.0.0.3</CODE>
<A NAME="pgfId=997453">
</A>
<EM CLASS="grammar_literal">
10.0.0.3</EM>
</P>
</TD>
</TR>
</TABLE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997455"></A>
When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. This is known as cyclic or round-robin ordering. In the example above, the first client will receive the records in the order 1, 2, 3; the second client will receive them in the order 2, 3, 1; and the third 3, 1, 2. Most clients will use the first record returned and discard the rest.</P>
<A NAME="pgfId=997455">
</A>
When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. In the example above, clients will randomly receive records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients will use the first record returned and discard the rest.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997456"></A>
<A NAME="pgfId=997456">
</A>
For more detail on ordering responses, check the <CODE CLASS="Program-Process">
rrset-order</CODE>
substatement in the <CODE CLASS="Program-Process">
options</CODE>
statement in <A HREF="Bv9ARM.5.html#22766" CLASS="XRef">
RRset Ordering</A>
.</P>
statement under <A HREF="Bv9ARM.6.html#22766" CLASS="XRef">RRset Ordering</A>. This substatement is not supported in BIND&nbsp;9, and only the ordering scheme described above is available.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997460"></A>
3.3 <A NAME="35205"></A>
<A NAME="pgfId=997460">
</A>
3.3 <A NAME="35205">
</A>
Notify</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997461"></A>
DNS Notify is a mechanism that allows master nameservers to notify their slave servers of changes to a zone's data and that a query should be initiated to discover the new data.</P>
<A NAME="pgfId=997461">
</A>
DNS Notify is a mechanism that allows master nameservers to notify their slave servers of changes to a zone's data. In response to a <CODE CLASS="Program-Process">
NOTIFY</CODE>
from a master server, the slave will check to see that its version of the zone is the current version and, if not, initiate a transfer.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1078896">
</A>
</A>
DNS Notify is fully documented in RFC 1996. See also the description of the zone option <CODE CLASS="Program-Process">
also-notify</CODE>
in <A HREF="Bv9ARM.5.html#32057" CLASS="XRef">
Zone Transfers</A>
under <A HREF="Bv9ARM.6.html#32057" CLASS="XRef">Zone Transfers</A>
. More information about <CODE CLASS="Program-Process">
notify</CODE>
can be found in <A HREF="Bv9ARM.5.html#12205" CLASS="XRef">Boolean Options</A>
can be found under <A HREF="Bv9ARM.6.html#12205" CLASS="XRef">Boolean Options</A>
.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=1078903">
</A>
</A>
3.4 Nameserver Operations</H3>
</OL>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997464">
</A>
</A>
3.4.1 Tools for Use With the Nameserver Daemon</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997465">
</A>
</A>
There are several indispensable diagnostic, administrative and monitoring tools available to the system administrator for controlling and debugging the nameserver daemon. We describe several in this section </P>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997466">
</A>
</A>
3.4.1.1 Diagnostic Tools</H5>
</OL>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997467">
</A>
</A>
dig</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997468">
</A>
</A>
The domain information groper (<CODE CLASS="Program-Process">
dig</CODE>
) is a command line tool that can be used to gather information from the Domain Name System servers. Dig has two modes: simple interactive mode for a single query, and batch mode which executes a query for each in a list of several query lines. All query options are accessible from the command line.</P>
@ -349,30 +367,34 @@ dig</CODE>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997469">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997470"> </A>
<PRE>
<CODE><STRONG>
dig [@server] domain [&lt;query-type&gt;] [&lt;query-class&gt;]
[+&lt;query-option&gt;] [-&lt;dig-option&gt;] [%comment]</PRE>
[+&lt;query-option&gt;] [-&lt;dig-option&gt;] [%comment]</STRONG></CODE>
</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997471">
</A>
</A>
The usual simple use of dig will take the form</P>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997472"> </A>
dig @server domain query-type query-class</PRE>
<PRE>
<CODE><STRONG>
dig @server domain query-type query-class</STRONG></CODE>
</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997473">
</A>
</A>
For more information and a list of available commands and options, see the dig man page.</P>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997474">
</A>
</A>
host</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997475">
</A>
</A>
The<EM CLASS="pathname">
</EM>
<CODE CLASS="Program-Process">
@ -384,19 +406,21 @@ utility provides a simple DNS lookup using a command-line interface for looking
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997476">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997477"> </A>
host [-l] [-v] [-w] [-r] [-d] [-t querytype] [-a] host [server]</PRE>
</DIV>
<PRE>
<CODE><STRONG>
host [-aCdlrTwv] [-c class] [-N ndots] [-t type]
[-W timeout] [-R retries] hostname [server]
</STRONG></CODE></PRE>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997478">
</A>
</A>
nslookup</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997479">
</A>
</A>
<CODE CLASS="Program-Process">
nslookup</CODE>
is a program used to query Internet domain nameservers. <CODE CLASS="Program-Process">
@ -406,55 +430,67 @@ nslookup</CODE>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997480">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997481"> </A>
nslookup [-option ...] [host-to-find | -[server]]</PRE>
<PRE>
<CODE><STRONG>
nslookup [-option ...] [host-to-find | -[server]]</STRONG></CODE>
</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997482">
</A>
Interactive mode is entered when no arguments are given (the default nameserver will be used) or when the first argument is a hyphen (-) and the second argument is the host name or Internet address of a nameserver.</P>
</A>
Interactive mode is entered when no arguments are given (the default nameserver will be used) or when the first argument is a hyphen (`-') and the second argument is the host name or Internet address of a nameserver.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997483">
</A>
</A>
Non-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument. The optional second argument specifies the host name or address of a nameserver.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997484">
</A>
</A>
The options listed under the &quot;set&quot; command (see the <CODE CLASS="Program-Process">
nslookup</CODE>
man page for details) can be specified in the <EM CLASS="pathname">
.nslookuprc</EM>
file in the user's home directory if they are listed one per line. Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial time-out to 10 seconds, type:</P>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997485"> </A>
nslookup -query=hinfo -timeout=10</PRE>
<PRE>
<CODE><STRONG>
nslookup -query=hinfo -timeout=10</STRONG></CODE>
</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997486">
</A>
<A NAME="pgfId=1079183">
</A>
For more information and a list of available commands and options, see the <CODE CLASS="Program-Process">
nslookup</CODE>
man page.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1079184">
</A>
Due to its arcane user interface and frequently inconsistent behavior, we do not recommend the use of <CODE CLASS="Program-Process">
nslookup</CODE>
, and it is not installed by default when installing BIND&nbsp;9. Use <CODE CLASS="Program-Process">
dig</CODE>
instead.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997487">
</A>
<A NAME="pgfId=1079185">
</A>
3.4.1.2 Administrative Tools</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997488">
</A>
</A>
Administrative tools play an integral part in the management of a server.</P>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997489">
</A>
</A>
rndc</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997490">
</A>
</A>
The remote name daemon control (<CODE CLASS="Program-Process">
rndc</CODE>
) program is a program that allows the system administrator to control the operation of a nameserver. If you run <CODE CLASS="Program-Process">
@ -462,22 +498,24 @@ rndc</CODE>
without any options it will display a usage message.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1012780">
</A>
</A>
Usage:</P>
<PRE CLASS="4Level-fixed"><A NAME="pgfId=1012777"> </A>
<CODE CLASS="Program-Process">rndc [-p port] [-m] server command [command ...]</CODE>
</PRE>
<PRE>
<CODE><STRONG>
rndc [-p port] [-m] server command [command ...]
</STRONG></CODE></PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997493">
</A>
</A>
For more information and a list of available commands and options, see the <CODE CLASS="Program-Process">
rndc</CODE>
man page.</P>
</DIV>
</DIV>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</BODY>
</HTML>

1576
doc/arm/Bv9ARM.4.html
View file

File diff suppressed because it is too large Load diff

6368
doc/arm/Bv9ARM.5.html
View file

File diff suppressed because it is too large Load diff

6507
doc/arm/Bv9ARM.6.html
View file

File diff suppressed because it is too large Load diff

390
doc/arm/Bv9ARM.7.html
View file

@ -1,298 +1,208 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.7.html,v 1.5 2000/06/22 21:53:45 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 7. Troubleshooting</TITLE></HEAD>
<TITLE> Section 7. BIND&nbsp;9 Security Considerations</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
Section 7. Troubleshooting</H1>
Section 7. BIND&nbsp;9 Security Considerations</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997351">
</A>
7.1 Common Log Messages and What They Mean</H3>
</OL>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997352">
</A>
lame server</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997353"></A>
<CODE CLASS="grammar_literal">ns named[111]: Lame server on 'www.example.com' (in 'example.com'?): [192.168.0.2].53 'ns2.example.com'</CODE>
</PRE>
7.1 <A NAME="32222">
</A>
Access Control Lists</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
Access Control Lists (ACLs), are address match lists that you can set up and nickname for future use in <CODE CLASS="Program-Process">
allow-query</CODE>
, <CODE CLASS="Program-Process">
allow-recursion</CODE>
, <CODE CLASS="Program-Process">
blackhole</CODE>
, <CODE CLASS="Program-Process">
allow-transfer</CODE>
, etc.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997354">
</A>
This is a harmless error message. It means that the server at 192.168.0.2 (<EM CLASS="pathname">
ns2.example.com</EM>
) is listed as a nameserver for &quot;<EM CLASS="pathname">
example.com</EM>
&quot;, but it doesn't really know anything about <EM CLASS="pathname">
example.com</EM>
.</P>
Using ACLs allows you to have finer control over who can access your nameserver, without cluttering up your config files with huge lists of IP addresses.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
If this is a zone under your control, check each of the nameservers to ensure that they are configured to answer questions properly.</P>
It is a <EM CLASS="Emphasis">
good idea</EM>
to use ACLs, and to control access to your server. Limiting access to your server by outside parties can help prevent spoofing and DoS attacks against your server.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997356">
</A>
If it's a zone out on the Internet, it would be nice to notify the owners of the domain in question so that they can take a look at it. In practice, though, not many people have time to do this.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997357">
</A>
bad referral</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997358"></A>
<CODE CLASS="grammar_literal">ns named[111]: bad referral (other.com !&lt; subdomain.other.com)</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
This indicates that your nameserver (<EM CLASS="pathname">
ns.example.com</EM>
) queried the nameserver for <EM CLASS="pathname">
example2.com</EM>
to find out how to get to <EM CLASS="pathname">
subdomain.example2.com</EM>
. The name server <EM CLASS="pathname">
example2.com</EM>
told your nameserver that <EM CLASS="pathname">
subdomain.example2.com</EM>
was delegated to some <EM CLASS="pathname">
other.example2.com</EM>
, so your nameserver queried that.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997360">
</A>
<EM CLASS="pathname">
someother.example2.com</EM>
didn't think that <EM CLASS="pathname">
subdomain.example2.com</EM>
had been delegated to it, so it referred your server (<EM CLASS="pathname">
ns.example.com</EM>
) back to the <EM CLASS="pathname">
example2.com</EM>
nameserver.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997361">
</A>
not authoritative for</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997362"></A>
<CODE CLASS="grammar_literal">ns named-xfer[111]: [192.168.0.1] not authoritative for example.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0</CODE>
Here is an example of how to properly apply ACLs:</P>
<PRE>
<CODE><STRONG>// Set up an ACL named &quot;bogusnets&quot; that will block RFC1918 space,
// which is commonly used in spoofing attacks.
acl bogusnets { 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3;
10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; };
// Set up an ACL called our-nets. Replace this with the real IP numbers.
acl our-nets { x.x.x.x/24; x.x.x.x/21; };
options {
...
...
allow-query { our-nets; };
allow-recursion { our-nets; };
...
blackhole { bogusnets; };
...
};
zone &quot;example.com&quot; {
type master;
file &quot;m/example.com&quot;;
allow-query { any; };
};
</STRONG></CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997363">
</A>
This error usually shows up on a slave server. It indicates that the master server is not answering authoritatively for the zone. This usually happens when the zone is rejected (while <CODE CLASS="Program-Process">
named</CODE>
is loading) on the master server. Check the logs on the master server. If ancount -- 0, you may be pointing at the wrong master server for the zone.</P>
This allows recursive queries of the server from the outside unless recursion has been previously disabled.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1028031">
</A>
For more information on how to use ACLs to protect your server, see the <EM CLASS="Emphasis">
AUSCERT</EM>
advisory at<BR>
<a href="ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos">
ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</a>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997364">
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997365">
</A>
rejected zone</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997365"></A>
<CODE CLASS="grammar_literal">ns named[111]: master zone &quot;example.com&quot; (IN) rejected due to errors (serial111)</CODE>
</PRE>
7.2 <CODE CLASS="Program-Process">
chroot</CODE>
and <CODE CLASS="Program-Process">
setuid</CODE>
(for UNIX servers)</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997366">
</A>
This indicates that the <EM CLASS="pathname">
example.com</EM>
zone was rejected because of an error in the zone file. Check the lines above this error. <CODE CLASS="Program-Process">
named</CODE>
will usually tell you what it didn't like and where to find it in the zone file.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
On UNIX servers, it is possible to run BIND in a <EM CLASS="Emphasis">
chrooted</EM>
environment (<CODE CLASS="Program-Process">
chroot()</CODE>
) by specifying the &quot;<CODE CLASS="Program-Process">
-t</CODE>
&quot; option. This can help improve system security by placing BIND in a &quot;sandbox,&quot; which will limit the damage done if a server is compromised.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997367">
</A>
no NS RRs found</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997368"></A>
<CODE CLASS="grammar_literal">ns named[111]: Zone &quot;example.com&quot; (file example.com.db): no NS RRs found at zonetop</CODE>
</PRE>
Another useful feature in the UNIX version of BIND is the ability to run the daemon as a nonprivileged user ( <CODE CLASS="Program-Process">
-u</CODE>
<EM CLASS="variable">
user</EM>
). We suggest running as a nonprivileged user when using the <CODE CLASS="Program-Process">
chroot</CODE>
feature.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997369">
</A>
The <EM CLASS="pathname">
example.com.db</EM>
file is missing NS records at the top of the zone (in the SOA section). Check to make sure they exist and that there is white space (spaces or tabs) in front of them. White spaces matter here.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997370">
</A>
no default TTL set</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997371"></A>
<CODE CLASS="grammar_literal">ns named[111]: Zone &quot;example.com&quot; (file example.com.db): No default TTL set using SOA minimum instead</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997372">
</A>
You will need to add a <KBD CLASS="Literal-user-input">
$TTL</KBD>
to the top of the <EM CLASS="pathname">
example.com.db</EM>
zone file. See RFC 2308, or <A HREF="Bv9ARM.5.html#19693" CLASS="XRef">
Setting TTLs</A>
for information on how to use <CODE CLASS="grammar_literal">
$TTL</CODE>
.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997373">
</A>
no root nameserver for class</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997374"></A>
<CODE CLASS="grammar_literal">findns: No root nameservers for class IN?</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997375">
</A>
Your nameserver is having problems finding the root nameservers. Check your root hints file to make sure it is not corrupted. Also, make sure that your nameserver can reach the Internet.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997376">
</A>
If you are running an internal root nameserver, make sure it is configured properly and is answering queries.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997377">
</A>
address already in use</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997378"></A>
<CODE CLASS="grammar_literal">ctl_server: bind: Address already in use</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997379">
</A>
This usually indicates that another copy of BIND is already running. Verify that you have killed old copies of the daemon.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997380">
</A>
This can also pop up if you originally ran named as &quot;root&quot; and now run it as a regular user. named may have left behind an ndc control socket that is owned by root if it crashed, or was not killed gracefully.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997381">
</A>
This means that the regular user wouldn't be able to delete it, so it would think named is still running. The solution is to remove any ndc sockets in <EM CLASS="pathname">
/usr/local/etc</EM>
, or <EM CLASS="pathname">
/var/run</EM>
, etc.</P>
</DIV>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997382">
</A>
7.2 Common Problems</H3>
</OL>
<A NAME="pgfId=997368">
</A>
Here is an example command line to load BIND in a <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox, <BR>
<CODE CLASS="Program-Process">
<STRONG>/var/named</STRONG></CODE>
, and to run <CODE CLASS="Program-Process">
<STRONG>named setuid</STRONG></CODE>
to user 202:</P>
<PRE>
<CODE><STRONG>/usr/local/bin/named -u 202 -t /var/named
</STRONG></CODE></PRE>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997383">
</A>
7.2.1 It's not working; how can I figure out what's wrong?</H4>
<A NAME="pgfId=997370">
</A>
7.2.1 The <CODE CLASS="Program-Process">
chroot</CODE>
Environment</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997384">
<A NAME="pgfId=997371">
</A>
The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand (see the sample configurations in <A HREF="Bv9ARM.3.html#30164" CLASS="XRef">
Sample Configuration and Logging.</A>
). The log files provide a source of hints and information that can be used to figure out what went wrong and how to fix the problem.</P>
In order for a <CODE CLASS="Program-Process">
chroot()</CODE>
environment to work properly in a particular directory (for example, <EM CLASS="pathname">
/var/named</EM>
), you will need to set up an environment that includes everything BIND needs to run. From BIND's point of view, <EM CLASS="pathname">
/var/named</EM>
is the root of the filesystem. You will need <EM CLASS="pathname">
/dev/null</EM>
, and any library directories and files that BIND needs to run on your system. Please consult your operating system's instructions if you need help figuring out which library files you need to copy over to the <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997372">
</A>
If you are running an operating system that supports static binaries, you can also compile BIND statically and avoid the need to copy system libraries over to your <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox.</P>
</DIV>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997373">
</A>
7.2.2 Using the <CODE CLASS="Program-Process">
setuid</CODE>
Function </H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997374">
</A>
Prior to running the <CODE CLASS="Program-Process">
named</CODE>
daemon, use the <CODE CLASS="Program-Process">
touch</CODE>
utility (to change file access and modification times) or the <CODE CLASS="Program-Process">
chown</CODE>
utility (to set the user id and/or group id) on files to which you want BIND to write.</P>
</DIV>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997388">
<A NAME="pgfId=997375">
</A>
7.3 Incrementing and Changing the Serial Number</H3>
7.3 Dynamic Updates</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1001230">
<A NAME="pgfId=997376">
</A>
Zone serial numbers are just numbers--they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. A number of people have been testing these numbers for Y2K compliance and have set the number to the year 2000 to see if it will work. They then try to restore the old serial number. This will cause problems, because serial numbers are used to indicate that a zone has been updated. If the serial number on the secondary server is lower than the serial number on the primary, the secondary server will attempt to update its copy of the zone.</P>
Access to the dynamic update facility should be strictly limited. In earlier versions of BIND the only way to do this was based on the IP address of the host requesting the update. BIND&nbsp;9BIND&nbsp;9 also supports authenticating updates cryptographically by means of transaction signatures (TSIG). The use of TSIG is strongly recommended.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997390">
<A NAME="pgfId=1006806">
</A>
Setting the serial number to a lower number on the primary server than the secondary server means that the secondary will not perform updates to its copy of the zone.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997391">
</A>
The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all secondaries have updated to the new zone serial number, then reset the number to what you want it to be, and reload the zone again.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997392">
</A>
7.4 Where Can I Get Help?</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1001264">
</A>
The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND and DHCP servers. Four levels of premium support are available and each level includes support for all ISC programs, significant discounts on products and training, and a recognized priority on bug fixes and non-funded feature requests. In addition, ISC offers a standard support agreement package which includes services ranging from bug fix announcements to remote support. It also includes training in BIND and DHCP.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997394">
</A>
To discuss arrangements for support, contact
<A HREF="mailto:info@isc.org">info@isc.org</A>
or visit the ISC web page at<BR>
<EM CLASS="URL">
<A HREF="http://www.isc.org/services/support/">http://www.isc.org/services/support/</A></EM>
to read more.</P>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
Some sites choose to keep all dynamically updated DNS data in a subdomain and delegate that subdomain to a separate zone. This way, the top-level zone containing critical data such as the IP addresses of public web and mail servers need not allow dynamic update at all.</P>
</DIV>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</BODY>
</HTML>

507
doc/arm/Bv9ARM.8.html
View file

@ -1,470 +1,83 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.8.html,v 1.5 2000/06/22 21:53:46 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Appendices</TITLE></HEAD>
<TITLE> Section 8. Troubleshooting</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<H6 CLASS="Title">
<A NAME="pgfId=997347">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
Appendices</H6>
Section 8. Troubleshooting</H1>
</OL>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=999043">
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997382">
</A>
Appendix A. Acknowledgements</H6>
</DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1001089">
</A>
A.1 A Brief History of the DNS and BIND</H2>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000944">
</A>
Although the &quot;official&quot; beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and 883. From 1984 to 1987, the ARPAnet (the precursor to today's Internet) became a testbed of experimentation for developing the new naming/addressing scheme in an rapidly expanding, operational network environment. New RFCs were written and published in 1987 that modified the original documents to incorporate improvements based on the working model. RFC 1034, &quot;Domain Names-Concepts and Facilities,&quot; and RFC 1035, &quot;Domain Names-Implementation and Specification&quot; were published and became the standards upon which all DNS implementations are built.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000945">
</A>
The first working domain name server, called &quot;Jeeves,&quot; was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 machines located at the University of Southern California's Information Sciences Institute (USC-ISI) and SRI International's Network Information Center (SRI-NIC). A DNS server for Unix machines, the Berkeley Internet Name Domain (BIND) package, was written soon after by a group of graduate students at the University of California at Berkeley under a grant from the US Defense Advanced Research Projects Administration (DARPA). Versions of BIND through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark Painter, David Riggle and Songnian Zhou made up the initial BIND project team. After that, additional work on the software package was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation employee on loan to the CSRG, worked on BIND for 2 years, from 1985 to 1987. Many other people also contributed to BIND development during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently handled by Mike Karels and O. Kure.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000946">
</A>
BIND versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then a DEC employee, became BIND's primary caretaker. Paul was assisted by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000947">
</A>
BIND Version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became BIND's principal architect/programmer.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000948">
</A>
BIND versions from 4.9.3 onward have been developed and maintained by the Internet Software Consortium with support being provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of BIND version 8 in May 1997.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000986">
</A>
BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.</P>
<H1 CLASS="AppendixLevel1">
<A NAME="pgfId=1001064">
</A>
Appendix B. <A NAME="13688">
</A>
Historical DNS Information</H1>
8.1 Common Problems</H3>
</OL>
<DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1001089">
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997383">
</A>
B.1 <A NAME="38866">
</A>
Classes of Resource Records</H2>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=1029256">
</A>
B.1.1 HS = hesiod</H3>
8.1.1 It's not working; how can I figure out what's wrong?</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029267">
<A NAME="pgfId=997384">
</A>
The <EM CLASS="Optional-meta-syntax">
hesiod </EM>
class is an information service developed by MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword <CODE CLASS="Program-Process">
hs</CODE>
is a synonym for hesiod.</P>
The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand. (See the <A HREF="Bv9ARM.3.html#30164" CLASS="XRef">sample configurations</A>) in Section 3. The log files provide a source of hints and information that can be used to figure out what went wrong and how to fix the problem.</P>
</DIV>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=1029289">
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997388">
</A>
B.1.2 CH = chaos</H3>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029290">
</A>
The <CODE CLASS="Program-Process">
chaos</CODE>
class is used to specify zone data for the MIT-developed CHAOSnet, a LAN protocol created in the mid-1970s.</P>
</DIV>
</DIV>
<H1 CLASS="AppendixLevel1">
<A NAME="pgfId=1029291">
</A>
Appendix C. <A NAME="35452">
</A>
Bibliography (and Suggested Reading)</H1>
<DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999193">
</A>
C.1 <A NAME="42144">
</A>
Request for Comments (RFCs)</H2>
8.2 Incrementing and Changing the Serial Number</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=999780">
<A NAME="pgfId=1001230">
</A>
Specification documents for the Internet protocol suite, including the DNS, are published as part of the Request for Comments (RFCs) series of technical notes. The standards themselves are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at <BR>
Zone serial numbers are just numbers--they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. A number of people have been testing these numbers for Y2K compliance and have set the number to the year 2000 to see if it will work. They then try to restore the old serial number. This will cause problems because serial numbers are used to indicate that a zone has been updated. If the serial number on the slave server is lower than the serial number on the master, the slave server will attempt to update its copy of the zone.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997390">
</A>
Setting the serial number to a lower number on the master server than the slave server means that the slave will not perform updates to its copy of the zone.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997391">
</A>
The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all slaves have updated to the new zone serial number, then reset the number to what you want it to be, and reload the zone again.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997392">
</A>
8.3 Where Can I Get Help?</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1001264">
</A>
The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND and DHCP servers. Four levels of premium support are available and each level includes support for all ISC programs, significant discounts on products and training, and a recognized priority on bug fixes and non-funded feature requests. In addition, ISC offers a standard support agreement package which includes services ranging from bug fix announcements to remote support. It also includes training in BIND and DHCP.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997394">
</A>
To discuss arrangements for support, contact <EM CLASS="pathname">
info@isc.org</EM>
<CODE CLASS="Program-Process">
</CODE>
or visit the ISC web page at<BR>
<EM CLASS="URL">
ftp://www.isi.edu/in-notes/RFCxxx.txt</EM>
(where <EM CLASS="URL">
xxx</EM>
is the number of the RFC). RFCs are also available via the Web at
<br><EM CLASS="URL">
<A HREF="http://www.ietf.org/rfc/">http://www.ietf.org/rfc/</A></EM>
.</P>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999212">
</A>
C.1.1 Standards</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999776">
</A>
RFC974. Partridge, C. <EM CLASS="doc-title">
Mail Routing and the Domain System</EM>
. January 1986.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999777">
</A>
RFC1034. Mockapetris, P.V. <EM CLASS="doc-title">
Domain Names - Concepts and Facilities</EM>
. P.V. November 1987.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000013">
</A>
RFC1035. Mockapetris, P. V. <EM CLASS="doc-title">
Domain Names - Implementation and Specification</EM>
. November 1987.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999218">
</A>
C.1.2 <A NAME="17631">
</A>
Proposed Standards</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999220">
</A>
RFC2181. Elz, R., R. Bush. <EM CLASS="doc-title">
Clarifications to the DNS Specification</EM>
. July 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999221">
</A>
RFC2308. Andrews, M. <EM CLASS="doc-title">
Negative Caching of DNS Queries</EM>
. March 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999222">
</A>
RFC1995. Ohta, M. <EM CLASS="doc-title">
Incremental Zone Transfer in DNS</EM>
. August 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999223">
</A>
RFC1996. Vixie, P. <EM CLASS="doc-title">
A Mechanism for Prompt Notification of Zone Changes</EM>
. August 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999747">
</A>
RFC2136. Vixie, P., S. Thomson, Y. Rekhter, J. Bound. <EM CLASS="doc-title">
Dynamic Updates in the Domain Name System</EM>
. April 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1045908">
</A>
RFC2845. Vixie, P., O. Gudmundsson, D. Eastlake 3rd, B. Wellington. <EM CLASS="doc-title">
Secret Key Transaction Authentication for DNS (TSIG)</EM>
. May 2000.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999227">
</A>
C.1.3 Proposed Standards Still Under Development</H3>
<P CLASS="3LevelContinued">
<A NAME="pgfId=999436">
</A>
<EM CLASS="Emphasis">
Note:</EM>
the following list of RFCs are undergoing major revision by the IETF.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999230">
</A>
RFC1886. Thomson, S., C. Huitema. <EM CLASS="doc-title">
DNS Extensions to support IP version 6</EM>
. S. December 1995.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999231">
</A>
RFC2065. Eastlake, 3rd, D., C. Kaufman. <EM CLASS="doc-title">
Domain Name System Security Extensions</EM>
. January 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999232">
</A>
RFC2137. Eastlake, 3rd, D. <EM CLASS="doc-title">
Secure Domain Name System Dynamic Update</EM>
. April 1997.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999235">
</A>
C.1.4 Other Important RFCs About DNS Implementation</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999237">
</A>
RFC1535. Gavron, E. <EM CLASS="doc-title">
A Security Problem and Proposed Correction With Widely Deployed DNS Software.</EM>
October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000173">
</A>
RFC1536. Kumar, A., J. Postel, C. Neuman, P. Danzig, S. Miller. <EM CLASS="doc-title">
Common DNS Implementation Errors and Suggested Fixes</EM>
. October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999239">
</A>
RFC1982. Elz, R., R. Bush. <EM CLASS="doc-title">
Serial Number Arithmetic</EM>
. August 1996.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999242">
</A>
C.1.5 Resource Record Types</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999244">
</A>
RFC1183. Everhart, C.F., L. A. Mamakos, R. Ullmann, P. Mockapetris. <EM CLASS="doc-title">
New DNS RR Definitions</EM>
. October 1990.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999249">
</A>
RFC1706. Manning, B., R. Colella. <EM CLASS="doc-title">
DNS NSAP Resource Records</EM>
. October 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999253">
</A>
RFC2168. Daniel, R., M. Mealling. <EM CLASS="doc-title">
Resolution of Uniform Resource Identifiers using the Domain Name System. June 1997.</EM>
</P>
<P CLASS="Biblio">
<A NAME="pgfId=999254">
</A>
RFC1876. Davis, C., P. Vixie, T. Goodwin, I. Dickinson. <EM CLASS="doc-title">
A Means for Expressing Location Information in the Domain Name System</EM>
. January 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999255">
</A>
RFC2052. Gulbrandsen, A., P. Vixie. <EM CLASS="doc-title">
A DNS RR for Specifying the Location of Services.</EM>
October 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000261">
</A>
RFC2163. Allocchio, A. U<EM CLASS="doc-title">
sing the Internet DNS to Distribute MIXER Conformant Global Address Mapping</EM>
. January 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000251">
</A>
RFC2230. Atkinson, R. <EM CLASS="doc-title">
Key Exchange Delegation Record for the DNS</EM>
. October 1997.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999260">
</A>
C.1.6 DNS and the Internet</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999262">
</A>
RFC1101. Mockapetris, P. V. <EM CLASS="doc-title">
DNS Encoding of Network Names and Other Types</EM>
. April 1989.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999263">
</A>
RFC1123. Braden, R. <EM CLASS="doc-title">
Requirements for Internet Hosts - Application and Support</EM>
. October 1989.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999264">
</A>
RFC1591. Postel, J. D<EM CLASS="doc-title">
omain Name System Structure and Delegation</EM>
. March 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999265">
</A>
RFC2317. Eidnes, H., G. de Groot, P. Vixie. <EM CLASS="doc-title">
Classless IN-ADDR.ARPA Delegation</EM>
. March 1998.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999274">
</A>
C.1.7 DNS Operations</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999276">
</A>
RFC1537. Beertema, P. <EM CLASS="doc-title">
Common DNS Data File Configuration Errors</EM>
. October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999277">
</A>
RFC1912. Barr, D. <EM CLASS="doc-title">
Common DNS Operational and Configuration Errors</EM>
. February 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000360">
</A>
RFC2182. Elz, R. R. Bush, S. Bradner, M. Patton. <EM CLASS="doc-title">
Selection and Operation of Secondary DNS Servers</EM>
. July 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000361">
</A>
RFC2219. Hamilton, M., R. Wright. <EM CLASS="doc-title">
Use of DNS Aliases for Network Services.</EM>
October 1997.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999282">
</A>
C.1.8 Other DNS-related RFCs</H3>
<P CLASS="3LevelContinued1">
<A NAME="pgfId=999409">
</A>
<EM CLASS="doc-title">
Note:</EM>
the following list of RFCs, although DNS-related, are not concerned with implementing software.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999284">
</A>
RFC1464. Rosenbaum, R. <EM CLASS="doc-title">
Using the Domain Name System To Store Arbitrary String Attributes</EM>
. May 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999285">
</A>
RFC1713. Romao, A. <EM CLASS="doc-title">
Tools for DNS Debugging</EM>
. November 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999286">
</A>
RFC1794. Brisco, T. <EM CLASS="doc-title">
DNS Support for Load Balancing</EM>
. April 1995.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999287">
</A>
RFC2240. Vaughan, O. <EM CLASS="doc-title">
A Legal Basis for Domain Name Allocation</EM>
. November1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999288">
</A>
RFC2345. Klensin, J., T. Wolf, G. Oglesby. <EM CLASS="doc-title">
Domain Names and Company Name Retrieval</EM>
. May 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999289">
</A>
RFC2352. Vaughan, O. <EM CLASS="doc-title">
A Convention For Using Legal Names as Domain Names</EM>
. May 1998.</P>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999292">
</A>
C.1.9 Obsolete and Unimplemented Experimental RRs</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999294">
</A>
RFC1712. Farrell, C., M. Schulze, S. Pleitner, D. Baldoni. <EM CLASS="doc-title">
DNS Encoding of Geographical Location</EM>
. November 1994.</P>
</DIV>
</DIV>
<DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999195">
</A>
C.2 <A NAME="">
</A>
Internet Drafts</H2>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000609">
</A>
Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs in the preliminary stages of development. Implementors are cautioned not to regard IDs as archival, and they should not be quoted or cited in any formal documents unless accompanied by the disclaimer that they are &quot;works in progress.&quot; IDs have a lifespan of six months after which they are deleted unless updated by their authors.</P>
</DIV>
<DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999464">
</A>
C.3 Electronic Mail Communication</H2>
<P CLASS="2Biblio">
<A NAME="pgfId=1001024">
</A>
Wellington, Brian (bwellington@tislabs.com). <EM CLASS="doc-title">
DNSSEC usage document</EM>
. E-mail to David Conrad (David_Conrad@isc.org). 15 March 1999.</P>
<P CLASS="2Biblio">
<A NAME="pgfId=1001025">
</A>
Wellington, Brian (bwellington@tislabs.com). <EM CLASS="doc-title">
TSIG guide for BIND 8.2+</EM>
. E-mail to private mailing list (private communication). 22 April 1999.</P>
</DIV>
<DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1000764">
</A>
C.4 Other BIND Documents</H2>
<P CLASS="2Biblio">
<A NAME="pgfId=1039827">
</A>
Albitz, Paul and Cricket Liu. 1998. <EM CLASS="doc-title">
DNS and BIND</EM>
. Sebastopol, CA: O'Reilly and Associates.</P>
</DIV>
http://www.isc.org/services/support/</EM>
to read more.</P>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
</DIV>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</BODY>
</HTML>

886
doc/arm/Bv9ARM.9.html Normal file
View file

@ -0,0 +1,886 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="9APPENDICES.css">
<TITLE>Appendices</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<DIV>
<H6 CLASS="Title">
<A NAME="pgfId=997347">
</A>
Appendices</H6>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=999043">
</A>
Acknowledgements</H6>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1000953">
</A>
A Brief History of the DNS and BIND</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000944">
</A>
Although the &quot;official&quot; beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and 883. From 1984 to 1987, the ARPAnet (the precursor to today's Internet) became a testbed of experimentation for developing the new naming/addressing scheme in an rapidly expanding, operational network environment. New RFCs were written and published in 1987 that modified the original documents to incorporate improvements based on the working model. RFC 1034, &quot;Domain Names-Concepts and Facilities,&quot; and RFC 1035, &quot;Domain Names-Implementation and Specification&quot; were published and became the standards upon which all DNS implementations are built.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000945">
</A>
The first working domain name server, called &quot;Jeeves,&quot; was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 machines located at the University of Southern California's Information Sciences Institute (USC-ISI) and SRI International's Network Information Center (SRI-NIC). A DNS server for Unix machines, the Berkeley Internet Name Domain (BIND) package, was written soon after by a group of graduate students at the University of California at Berkeley under a grant from the US Defense Advanced Research Projects Administration (DARPA). Versions of BIND through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark Painter, David Riggle and Songnian Zhou made up the initial BIND project team. After that, additional work on the software package was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation employee on loan to the CSRG, worked on BIND for 2 years, from 1985 to 1987. Many other people also contributed to BIND development during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently handled by Mike Karels and O. Kure.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000946">
</A>
BIND versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then a DEC employee, became BIND's primary caretaker. Paul was assisted by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000947">
</A>
BIND Version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became BIND's principal architect/programmer.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000948">
</A>
BIND versions from 4.9.3 onward have been developed and maintained by the Internet Software Consortium with support being provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of BIND version 8 in May 1997.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000986">
</A>
BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.</P>
</DIV>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=1001064">
</A>
<A NAME="13688">
</A>
Historical DNS Information</H6>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1046008">
</A>
<A NAME="38866">
</A>
Classes of Resource Records</H6>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=1046031">
</A>
HS = hesiod</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1046032">
</A>
The <EM CLASS="Optional-meta-syntax">
hesiod </EM>
class is an information service developed by MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword <CODE CLASS="Program-Process">
hs</CODE>
is a synonym for hesiod.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=1046033">
</A>
CH = chaos</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1046034">
</A>
The <CODE CLASS="Program-Process">
chaos</CODE>
class is used to specify zone data for the MIT-developed CHAOSnet, a LAN protocol created in the mid-1970s.</P>
</DIV>
</DIV>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=1046214">
</A>
General DNS Reference Information</H6>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1046040">
</A>
IPv6 addresses (A6)</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046041">
</A>
IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the DNS to facilitate scalable Internet routing. There are three types of addresses: <EM CLASS="Emphasis">
Unicast</EM>
, an identifier for a single interface; <EM CLASS="Emphasis">
Anycast</EM>
, an identifier for a set of interfaces; and <EM CLASS="Emphasis">
Multicast</EM>
, an identifier for a set of interfaces. Here we describe the global Unicast address scheme. For more information, see RFC 2374.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046042">
</A>
The aggregatable global Unicast address format is as follows:</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046104">
</A>
&nbsp;</P>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046045">
</A>
3</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046047">
</A>
13</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046049">
</A>
8</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046051">
</A>
24</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046053">
</A>
16</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046055">
</A>
64 bits</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046057">
</A>
FP</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046059">
</A>
TLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046061">
</A>
RES</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046063">
</A>
NLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046065">
</A>
SLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046067">
</A>
Interface ID</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="4">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046069">
</A>
&lt;------ Public Topology ------&gt;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046077">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046079">
</A>
&nbsp;</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046081">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046083">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046085">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046087">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046089">
</A>
&lt;-Site Topology-&gt;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046091">
</A>
&nbsp;</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046093">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046095">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046097">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046099">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046101">
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<A NAME="pgfId=1046103">
</A>
&lt;------ Interface Identifier ------&gt;</P>
</TD>
</TR>
</TABLE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046142">
</A>
Where</P>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046107">
</A>
FP</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046109">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046111">
</A>
Format Prefix (001)</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046113">
</A>
TLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046115">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046117">
</A>
Top-Level Aggregation Identifier</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046119">
</A>
RES</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046121">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046123">
</A>
Reserved for future use</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046125">
</A>
NLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046127">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046129">
</A>
Next-Level Aggregation Identifier</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046131">
</A>
SLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046133">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046135">
</A>
Site-Level Aggregation Identifier</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046137">
</A>
INTERFACE ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046139">
</A>
=</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046141">
</A>
Interface Identifier</P>
</TD>
</TR>
</TABLE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046143">
</A>
The <EM CLASS="Emphasis">
Public Topology</EM>
is provided by the upstream provider or ISP, and (roughly) corresponds to the IPv4 <EM CLASS="Emphasis">
network</EM>
section of the address range. The <EM CLASS="Emphasis">
Site Topology</EM>
is where you can subnet this space, much the same as subnetting an IPv4 class A or B network into class Cs. The <EM CLASS="Emphasis">
Interface Identifier</EM>
is the address of an individual interface on a given network. (With IPv6, addresses belong to interfaces rather than machines.)</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046144">
</A>
The subnetting capability of IPv6 is much more flexible than that of IPv4: subnetting can now be carried out on bit boundaries, in much the same way as Classless InterDomain Routing (CIDR).</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046145">
</A>
The internal structure of the Public Topology for an A6 global unicast address consists of:</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046163">
</A>
&nbsp;</P>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046148">
</A>
3</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046150">
</A>
13</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046152">
</A>
8</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046154">
</A>
24</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046156">
</A>
FP</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046158">
</A>
TLA ID</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046160">
</A>
RES</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=1046162">
</A>
NLA ID</P>
</TD>
</TR>
</TABLE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046164">
</A>
A 3 bit FP (Format Prefix) of 001 indicates this is a global Unicast address. FP lengths for other types of addresses may vary.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046165">
</A>
13 TLA (Top Level Aggregator) bits give the prefix of your top-level IP backbone carrier.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046166">
</A>
8 Reserved bits</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046167">
</A>
24 bits for Next Level Aggregators. This allows organizations with a TLA to hand out portions of their IP space to client organizations, so that the client can then split up the network further by filling in more NLA bits, and hand out IPv6 prefixes to their clients, and so forth.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046168">
</A>
There is no particular structure for the Site topology section. Organizations can allocate these bits in any way they desire, in the same way as they would subnet an IPv4 class A (8-bit prefix) network.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046169">
</A>
The Interface Identifier must be unique on that network. On ethernet networks, one way to ensure this is to set the address to the first three bytes of the hardware address, &quot;FFFE&quot;, then the last three bytes of the hardware address. The lowest significant bit of the first byte should then be complemented. Addresses are written as 32-bit blocks separated with a colon, and leading zeros of a block may be omitted, for example:</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046170">
</A>
<CODE CLASS="Program-Process">
3ffe:8050:201:9:a00:20ff:fe81:2b32</CODE>
</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1046171">
</A>
IPv6 address specifications are likely to contain long strings of zeros, so the architects have included a shorthand for specifying them. The double colon (`::') indicates the longest possible string of zeros that can fit, and can be used only once in an address.</P>
</DIV>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=1029291">
</A>
<A NAME="35452">
</A>
Bibliography (and Suggested Reading)</H6>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=999193">
</A>
<A NAME="42144">
</A>
Request for Comments (RFCs)</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=999780">
</A>
Specification documents for the Internet protocol suite, including the DNS, are published as part of the Request for Comments (RFCs) series of technical notes. The standards themselves are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at <BR>
<EM CLASS="URL">
ftp://www.isi.edu/in-notes/RFCxxx.txt</EM>
(where <EM CLASS="URL">
xxx</EM>
is the number of the RFC). RFCs are also available via the Web at <EM CLASS="URL">
http://www.ietf.org/rfc/</EM>
.</P>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999212">
</A>
Standards</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999776">
</A>
RFC974. Partridge, C. <EM CLASS="doc-title">
Mail Routing and the Domain System</EM>
. January 1986.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999777">
</A>
RFC1034. Mockapetris, P.V. <EM CLASS="doc-title">
Domain Names - Concepts and Facilities</EM>
. P.V. November 1987.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000013">
</A>
RFC1035. Mockapetris, P. V. <EM CLASS="doc-title">
Domain Names - Implementation and Specification</EM>
. November 1987.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999218">
</A>
<A NAME="17631">
</A>
Proposed Standards</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999220">
</A>
RFC2181. Elz, R., R. Bush. <EM CLASS="doc-title">
Clarifications to the DNS Specification</EM>
. July 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999221">
</A>
RFC2308. Andrews, M. <EM CLASS="doc-title">
Negative Caching of DNS Queries</EM>
. March 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999222">
</A>
RFC1995. Ohta, M. <EM CLASS="doc-title">
Incremental Zone Transfer in DNS</EM>
. August 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999223">
</A>
RFC1996. Vixie, P. <EM CLASS="doc-title">
A Mechanism for Prompt Notification of Zone Changes</EM>
. August 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999747">
</A>
RFC2136. Vixie, P., S. Thomson, Y. Rekhter, J. Bound. <EM CLASS="doc-title">
Dynamic Updates in the Domain Name System</EM>
. April 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1045908">
</A>
RFC2845. Vixie, P., O. Gudmundsson, D. Eastlake 3rd, B. Wellington. <EM CLASS="doc-title">
Secret Key Transaction Authentication for DNS (TSIG)</EM>
. May 2000.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999227">
</A>
Proposed Standards Still Under Development</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=999436">
</A>
<EM CLASS="Emphasis">
Note:</EM> the following list of RFCs are undergoing major revision by the IETF.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999230">
</A>
RFC1886. Thomson, S., C. Huitema. <EM CLASS="doc-title">
DNS Extensions to support IP version 6</EM>
. S. December 1995.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999231">
</A>
RFC2065. Eastlake, 3rd, D., C. Kaufman. <EM CLASS="doc-title">
Domain Name System Security Extensions</EM>
. January 1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999232">
</A>
RFC2137. Eastlake, 3rd, D. <EM CLASS="doc-title">
Secure Domain Name System Dynamic Update</EM>
. April 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999235">
</A>
Other Important RFCs About DNS Implementation</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999237">
</A>
RFC1535. Gavron, E. <EM CLASS="doc-title">
A Security Problem and Proposed Correction With Widely Deployed DNS Software.</EM>
October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000173">
</A>
RFC1536. Kumar, A., J. Postel, C. Neuman, P. Danzig, S. Miller. <EM CLASS="doc-title">
Common DNS Implementation Errors and Suggested Fixes</EM>
. October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999239">
</A>
RFC1982. Elz, R., R. Bush. <EM CLASS="doc-title">
Serial Number Arithmetic</EM>
. August 1996.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999242">
</A>
Resource Record Types</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999244">
</A>
RFC1183. Everhart, C.F., L. A. Mamakos, R. Ullmann, P. Mockapetris. <EM CLASS="doc-title">
New DNS RR Definitions</EM>
. October 1990.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999249">
</A>
RFC1706. Manning, B., R. Colella. <EM CLASS="doc-title">
DNS NSAP Resource Records</EM>
. October 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999253">
</A>
RFC2168. Daniel, R., M. Mealling. <EM CLASS="doc-title">
Resolution of Uniform Resource Identifiers using the Domain Name System. June 1997.</EM>
</P>
<P CLASS="Biblio">
<A NAME="pgfId=999254">
</A>
RFC1876. Davis, C., P. Vixie, T. Goodwin, I. Dickinson. <EM CLASS="doc-title">
A Means for Expressing Location Information in the Domain Name System</EM>
. January 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999255">
</A>
RFC2052. Gulbrandsen, A., P. Vixie. <EM CLASS="doc-title">
A DNS RR for Specifying the Location of Services.</EM>
October 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000261">
</A>
RFC2163. Allocchio, A. U<EM CLASS="doc-title">
sing the Internet DNS to Distribute MIXER Conformant Global Address Mapping</EM>
. January 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000251">
</A>
RFC2230. Atkinson, R. <EM CLASS="doc-title">
Key Exchange Delegation Record for the DNS</EM>
. October 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999260">
</A>
DNS and the Internet</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999262">
</A>
RFC1101. Mockapetris, P. V. <EM CLASS="doc-title">
DNS Encoding of Network Names and Other Types</EM>
. April 1989.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999263">
</A>
RFC1123. Braden, R. <EM CLASS="doc-title">
Requirements for Internet Hosts - Application and Support</EM>
. October 1989.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999264">
</A>
RFC1591. Postel, J. D<EM CLASS="doc-title">
omain Name System Structure and Delegation</EM>
. March 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999265">
</A>
RFC2317. Eidnes, H., G. de Groot, P. Vixie. <EM CLASS="doc-title">
Classless IN-ADDR.ARPA Delegation</EM>
. March 1998.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999274">
</A>
DNS Operations</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999276">
</A>
RFC1537. Beertema, P. <EM CLASS="doc-title">
Common DNS Data File Configuration Errors</EM>
. October 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999277">
</A>
RFC1912. Barr, D. <EM CLASS="doc-title">
Common DNS Operational and Configuration Errors</EM>
. February 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1054098">
</A>
RFC1912. Barr, D. <EM CLASS="doc-title">
Common DNS Operational and Configuration Errors</EM>
. February 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1054096">
</A>
RFC2010. Manning, B., P. Vixie. <EM CLASS="doc-title">
Operational Criteria for Root Name Servers.</EM>
October 1996.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000361">
</A>
RFC2219. Hamilton, M., R. Wright. <EM CLASS="doc-title">
Use of DNS Aliases for Network Services.</EM>
October 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999282">
</A>
Other DNS-related RFCs</H6>
</DIV>
</DIV>
</DIV>
</DIV>
<DIV>
<P CLASS="3LevelContinued">
<A NAME="pgfId=999409">
</A>
<EM CLASS="Emphasis">
Note:</EM> the following list of RFCs, although DNS-related, are not concerned with implementing software.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999284">
</A>
RFC1464. Rosenbaum, R. <EM CLASS="doc-title">
Using the Domain Name System To Store Arbitrary String Attributes</EM>
. May 1993.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999285">
</A>
RFC1713. Romao, A. <EM CLASS="doc-title">
Tools for DNS Debugging</EM>
. November 1994.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999286">
</A>
RFC1794. Brisco, T. <EM CLASS="doc-title">
DNS Support for Load Balancing</EM>
. April 1995.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999287">
</A>
RFC2240. Vaughan, O. <EM CLASS="doc-title">
A Legal Basis for Domain Name Allocation</EM>
. November1997.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999288">
</A>
RFC2345. Klensin, J., T. Wolf, G. Oglesby. <EM CLASS="doc-title">
Domain Names and Company Name Retrieval</EM>
. May 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999289">
</A>
RFC2352. Vaughan, O. <EM CLASS="doc-title">
A Convention For Using Legal Names as Domain Names</EM>
. May 1998.</P>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999292">
</A>
Obsolete and Unimplemented Experimental RRs</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999294">
</A>
RFC1712. Farrell, C., M. Schulze, S. Pleitner, D. Baldoni. <EM CLASS="doc-title">
DNS Encoding of Geographical Location</EM>
. November 1994.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=999195">
</A>
<A NAME="">
</A>
Internet Drafts</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000609">
</A>
Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs in the preliminary stages of development. Implementors are cautioned not to regard IDs as archival, and they should not be quoted or cited in any formal documents unless accompanied by the disclaimer that they are &quot;works in progress.&quot; IDs have a lifespan of six months after which they are deleted unless updated by their authors.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1000764">
</A>
Other BIND Documents</H6>
<DIV>
Albitz, Paul and Cricket Liu. 1998. <EM CLASS="doc-title">
DNS and BIND</EM>
. Sebastopol, CA: O'Reilly and Associates.</P>
<HR ALIGN="center">
<p>Return to <A href="Bv9ARM.html">BIND 9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
</DIV>
</DIV>
</BODY>
</HTML>

287
doc/arm/Bv9ARM.css
View file

@ -1,22 +1,3 @@
/*
* Copyright (C) 2000 Internet Software Consortium.
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
* ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
* OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
* CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
* DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
* PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
* ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
* SOFTWARE.
*/
/* $Id: Bv9ARM.css,v 1.4 2000/06/22 21:53:47 tale Exp $ */
A:link {
color: blue;
text-decoration: underline;
@ -148,7 +129,7 @@ PRE.2Level-fixed1 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 63.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -228,7 +209,7 @@ PRE.3Level-fixed {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -244,7 +225,7 @@ P.3Level-fixed-special {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -260,7 +241,7 @@ P.3Level-fixed1 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -276,7 +257,7 @@ P.3Level-fixed2 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -324,7 +305,7 @@ P.3LevelContinued21 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -381,22 +362,6 @@ LI.4Level-bullet2 {
text-transform: none;
font-family: Times;
}
H1.4Level-bullet21, H2.4Level-bullet21, H3.4Level-bullet21, H4.4Level-bullet21, H5.4Level-bullet21, H6.4Level-bullet21 {
text-align: left;
text-indent: -9.000000pt;
margin-top: 6.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 162.000000pt;
font-size: 11.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
PRE.4Level-fixed {
text-align: left;
text-indent: 0.000000pt;
@ -404,8 +369,8 @@ PRE.4Level-fixed {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
@ -420,7 +385,7 @@ PRE.4Level-fixed1 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -436,7 +401,7 @@ P.4Level-fixed2 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -452,7 +417,7 @@ PRE.4Level-fixedSmall {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 126.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -484,7 +449,7 @@ H1.4LevelContinued1, H2.4LevelContinued1, H3.4LevelContinued1, H4.4LevelContinue
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -635,7 +600,7 @@ P.Biblio {
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times New Roman;
font-family: Times;
}
P.Body {
text-align: left;
@ -685,6 +650,22 @@ P.Body11 {
text-transform: none;
font-family: Courier;
}
LI.Bulleted {
text-align: left;
text-indent: -18.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 18.000000pt;
font-size: 12.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
P.CellBody {
text-align: left;
text-indent: 0.000000pt;
@ -701,7 +682,7 @@ P.CellBody {
text-transform: none;
font-family: Times;
}
CODE.CellBody-fixedfont {
P.CellBody-fixedfont {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@ -717,7 +698,7 @@ CODE.CellBody-fixedfont {
text-transform: none;
font-family: Courier New;
}
CODE.CellBody-fixedfontLG {
P.CellBody-fixedfontLG {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@ -772,7 +753,7 @@ P.CellBody1 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -820,7 +801,7 @@ P.CellBody4 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -836,7 +817,7 @@ P.CellBody5 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
@ -852,7 +833,7 @@ P.CellBody6 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -868,7 +849,7 @@ H1.CellBody7, H2.CellBody7, H3.CellBody7, H4.CellBody7, H5.CellBody7, H6.CellBod
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
@ -893,6 +874,22 @@ P.CellBody8 {
text-transform: none;
font-family: Times;
}
P.CellHeading {
text-align: center;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 12.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
THROW AWAY.Footer {
text-align: left;
text-indent: 0.000000pt;
@ -900,7 +897,7 @@ THROW AWAY.Footer {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -916,7 +913,7 @@ THROW AWAY.Footer1 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -925,6 +922,22 @@ THROW AWAY.Footer1 {
text-transform: none;
font-family: Helvetica;
}
P.Footnote {
text-align: left;
text-indent: -12.000229pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 18.000000pt;
margin-left: 30.000229pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
THROW AWAY.Header {
text-align: left;
text-indent: 0.000000pt;
@ -941,6 +954,70 @@ THROW AWAY.Header {
text-transform: none;
font-family: Arial;
}
H1.Heading1, H2.Heading1, H3.Heading1, H4.Heading1, H5.Heading1, H6.Heading1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 14.000000pt;
margin-bottom: 6.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 14.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
H1.Heading2, H2.Heading2, H3.Heading2, H4.Heading2, H5.Heading2, H6.Heading2 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 12.000000pt;
margin-bottom: 3.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 12.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
H1.HeadingRunIn, H2.HeadingRunIn, H3.HeadingRunIn, H4.HeadingRunIn, H5.HeadingRunIn, H6.HeadingRunIn {
text-align: left;
text-indent: 0.000000pt;
margin-top: 6.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 12.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
P.Indented {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 18.000000pt;
font-size: 12.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
P.Mapping-Table-Cell {
text-align: left;
text-indent: 0.000000pt;
@ -1044,7 +1121,7 @@ P.Mapping-Table-Cell310 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #ffffff;
@ -1140,7 +1217,7 @@ P.Mapping-Table-Cell316 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -1204,7 +1281,7 @@ P.Mapping-Table-Cell331 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #ffffff;
@ -1316,7 +1393,7 @@ P.Mapping-Table-Cell381 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Italic;
color: #ffffff;
@ -1332,7 +1409,7 @@ P.Mapping-Table-Cell39 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Oblique;
color: #ffffff;
@ -1348,7 +1425,7 @@ P.Mapping-Table-Cell391 {
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #ffffff;
@ -1389,6 +1466,38 @@ P.Mapping-Table-Title {
text-transform: none;
font-family: Times;
}
LI.Numbered {
text-align: left;
text-indent: -18.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 18.000000pt;
font-size: 12.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
LI.Numbered1 {
text-align: left;
text-indent: -18.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 18.000000pt;
font-size: 12.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
H1.Subhead2, H2.Subhead2, H3.Subhead2, H4.Subhead2, H5.Subhead2, H6.Subhead2 {
text-align: left;
text-indent: 63.000000pt;
@ -1419,7 +1528,39 @@ H1.Subhead4, H2.Subhead4, H3.Subhead4, H4.Subhead4, H5.Subhead4, H6.Subhead4 {
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times New Roman;
font-family: Times;
}
P.TableFootnote {
text-align: left;
text-indent: -12.000229pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 18.000000pt;
margin-left: 30.000229pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
H1.TableTitle, H2.TableTitle, H3.TableTitle, H4.TableTitle, H5.TableTitle, H6.TableTitle {
text-align: center;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 12.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title {
text-align: center;
@ -1443,7 +1584,7 @@ EM.CharFmt {
EM.CharFmt1 {
}
EM.Command {
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
@ -1488,8 +1629,8 @@ EM.Emphasis-underline {
EM.EquationVariables {
font-style: Italic;
}
CODE.grammar_literal {
font-size: 9.000000pt;
EM.grammar_literal {
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -1509,7 +1650,7 @@ EM.hypertext {
font-family: Times;
}
KBD.Literal-user-input {
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -1519,7 +1660,7 @@ KBD.Literal-user-input {
font-family: Courier New;
}
EM.Optional-meta-syntax {
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
@ -1542,8 +1683,8 @@ EM.pathname2 {
font-style: Italic;
font-family: Times;
}
CODE.production_target {
font-size: 9.000000pt;
EM.production_target {
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -1553,7 +1694,7 @@ CODE.production_target {
font-family: Arial;
}
CODE.Program-Process {
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
@ -1573,7 +1714,7 @@ EM.URL {
font-family: Times;
}
EM.variable {
font-size: 9.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;

62
doc/arm/Bv9ARM.html
View file

@ -1,46 +1,20 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<!--
- Copyright (C) 2000 Internet Software Consortium.
-
- Permission to use, copy, modify, and distribute this software for any
- purpose with or without fee is hereby granted, provided that the above
- copyright notice and this permission notice appear in all copies.
-
- THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM DISCLAIMS
- ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES
- OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL INTERNET SOFTWARE
- CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
- DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
- PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
- ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
- SOFTWARE.
-->
<!-- $Id: Bv9ARM.html,v 1.4 2000/06/22 21:53:48 tale Exp $ -->
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE>BINDv9 Administrator Reference Manual</TITLE></HEAD>
<TITLE>BIND 9 Administrator Reference Manual</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<DIV>
<DIV ALIGN="left">
<A HREF="http://www.isc.org/"><IMG SRC="isc.color.gif" ALT="ISC logo" WIDTH="144" HEIGHT="90" ALIGN="left" HSPACE="30" BORDER="0"></A>
</DIV>
<DIV ALIGN="left">
<H2>BIND version 9<BR>Administrator Reference Manual</H2>
<H2>DRAFT
<H2>BIND 9<BR>Administrator Reference Manual</H2>
<br>
June, 2000</H2>
</DIV>
<HR ALIGN="center">
<DIV ALIGN="left">
<H4>Warning! This DRAFT document is the property of the Internet Software Consortium (ISC) and contains proprietary ISC information. The information in this document is subject to change.</H4>
</DIV>
<HR ALIGN="center">
<H6 CLASS="Title">
@ -49,38 +23,44 @@ June, 2000</H2>
Table of Contents</H6>
</DIV>
<OL>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.1.html" CLASS="Hypertext">
<A HREF="Bv9ARM.1.html#pgfId=1007883" CLASS="Hypertext">
Section 1. Introduction </A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.2.html" CLASS="Hypertext">
<A HREF="Bv9ARM.2.html#pgfId=997350" CLASS="Hypertext">
Section 2. BIND Resource Requirements</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.3.html" CLASS="Hypertext">
<A HREF="Bv9ARM.3.html#pgfId=997350" CLASS="Hypertext">
Section 3. Nameserver Configuration</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.4.html" CLASS="Hypertext">
<A HREF="Bv9ARM.4.html#pgfId=997350" CLASS="Hypertext">
Section 4. Advanced Concepts</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.5.html" CLASS="Hypertext">
Section 5. BINDv9 Configuration Reference</A>
<A HREF="Bv9ARM.5.html#pgfId=1001240" CLASS="Hypertext">
Section 5. The BIND&nbsp;9 Lightweight Resolver</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.6.html" CLASS="Hypertext">
Section 6. Security Considerations</A>
<A HREF="Bv9ARM.6.html#pgfId=997350" CLASS="Hypertext">
Section 6. BIND&nbsp;9 Configuration Reference</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.7.html" CLASS="Hypertext">
Section 7. Troubleshooting</A>
<A HREF="Bv9ARM.7.html#pgfId=997350" CLASS="Hypertext">
Section 7. BIND&nbsp;9 Security Considerations</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.8.html" CLASS="Hypertext">Appendices</A>
<A HREF="Bv9ARM.8.html#pgfId=997350" CLASS="Hypertext">
Section 8. Troubleshooting</A>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.9.html#pgfId=997350" CLASS="Hypertext">
Section 9. Appendices</A>
</H2>
</OL>
<HR ALIGN="center">
<DIV ALIGN="center">
Copyright &copy;2000 Internet Software Consortium

5680
doc/arm/Bv9ARM.txt
View file

File diff suppressed because it is too large Load diff