ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

new ARM version from Mary

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-06-12 20:42:37 +00:00
parent e6e0dadd30
commit 6b07f707e1
10 changed files with 2616 additions and 2120 deletions
Download Patch File Download Diff File Expand all files Collapse all files

236
doc/arm/Bv9ARM.1.html
View File

@@ -5,69 +5,66 @@
<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>
In this document, <EM CLASS="EquationVariables">
Section 1</EM>
introduces the basic DNS and BIND concepts. <EM CLASS="EquationVariables">
Section 2</EM>
describes resource requirements for running BIND in various environments. Information in <EM CLASS="EquationVariables">
Section 3</EM>
is <EM CLASS="EquationVariables">
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>
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 <EM CLASS="EquationVariables">
Section 4</EM>
, which contains more advanced concepts that the system administrator may need for implementing certain options. The contents of <EM CLASS="EquationVariables">
Section 5</EM>
are organized as in a reference manual to aid in the ongoing maintenance of the software. <EM CLASS="EquationVariables">
Section 6</EM>
addresses security considerations, and <EM CLASS="EquationVariables">
Section 7</EM>
contains troubleshooting help. The main body of the document is followed by several <EM CLASS="EquationVariables">
Appendices</EM>
which contain useful reference information, such as a <EM CLASS="EquationVariables">
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>
which contain useful reference information, such as a <EM CLASS="Emphasis">
Glossary</EM>
and a <EM CLASS="EquationVariables">
and a <EM CLASS="Emphasis">
Bibliography</EM>
, as well as 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>
@@ -78,7 +75,7 @@ In this document, we use the following general typographic conventions:</P>
<P CLASS="CellBody3">
<A NAME="pgfId=997359">
</A>
<EM CLASS="EquationVariables">
<EM CLASS="Emphasis">
To describe:</EM>
</P>
</TD>
@@ -86,8 +83,8 @@ To describe:</EM>
<P CLASS="CellBody3">
<A NAME="pgfId=997361">
</A>
<EM CLASS="EquationVariables">
Style:</EM>
<EM CLASS="Emphasis">
We use the style:</EM>
</P>
</TD>
</TR>
@@ -96,13 +93,14 @@ Style:</EM>
<P CLASS="CellBody">
<A NAME="pgfId=997363">
</A>
a pathname, filename, URL, hostname, mailing list name, or new term or concept</P>
a pathname, filename, URL, hostname,<BR>
mailing list name, or new term or concept</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody5">
<A NAME="pgfId=997365">
</A>
<EM CLASS="EquationVariables">
<EM CLASS="pathname">
Italic</EM>
</P>
</TD>
@@ -166,16 +164,16 @@ The following conventions are used in descriptions of the BIND configuration fil
<P CLASS="CellBody3">
<A NAME="pgfId=997385">
</A>
<EM CLASS="EquationVariables">
When describing:</EM>
<EM CLASS="Emphasis">
To describe:</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody3">
<A NAME="pgfId=997387">
</A>
<EM CLASS="EquationVariables">
Style Used:</EM>
<EM CLASS="Emphasis">
We use the style:</EM>
</P>
</TD>
</TR>
@@ -190,8 +188,8 @@ keywords</P>
<P CLASS="CellBody6">
<A NAME="pgfId=997391">
</A>
<EM CLASS="production_target">
Sans Serif Bold</EM>
<CODE CLASS="production_target">
Sans Serif Bold</CODE>
</P>
</TD>
</TR>
@@ -276,93 +274,93 @@ 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>
The purpose of this document is to explain the installation and basic upkeep of the BIND software package, and we begin by reviewing the fundamentals of the domain naming system as they relate to BIND. BIND consists of a <EM CLASS="EquationVariables">
The purpose of this document is to explain the installation and basic upkeep of the BIND software package, and we begin by reviewing the fundamentals of the domain naming system as they relate to BIND. BIND consists of a <EM CLASS="Emphasis">
nameserver</EM>
(or &quot;daemon&quot;) called <CODE CLASS="Program-Process">
named</CODE>
and a <CODE CLASS="Program-Process">
resolver</CODE>
library. The BIND server runs in the background, servicing queries on a well known network port. The standard port for UDP and TCP, usually port 53, is specified in<CODE CLASS="Program-Process">
/etc/services</CODE>
. The <EM CLASS="EquationVariables">
library. The BIND server runs in the background, servicing queries on a well known network port. The standard port for the User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), usually port 53, is specified in<CODE CLASS="Program-Process">
</CODE>
<EM CLASS="pathname">
/etc/services</EM>
. The <EM CLASS="Emphasis">
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>
A nameserver (NS) is a program that stores information about named resources and responds to queries from programs called <EM CLASS="EquationVariables">
A nameserver (NS) is a program that stores information about named resources and responds to queries from programs called <EM CLASS="Emphasis">
resolvers</EM>
which act as client processes. The basic function of an NS is to provide information about network objects by answering queries.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997417">
</A>
With the nameserver, the network can be broken into a hierarchy of domains. The name space is organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The name of the domain is the concatenation of all the labels of the domains from the root to the current domain. This is represented in written form as a string of labels listed from right to left and separated by dots. A label need only be unique within its domain. The whole name space is partitioned into areas called <EM CLASS="EquationVariables">
With the nameserver, the network can be broken into a hierarchy of domains. The name space is organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The name of the domain is the concatenation of all the labels of the domains from the root to the current domain. This is represented in written form as a string of labels listed from right to left and separated by dots. A label need only be unique within its domain. The whole name space is partitioned into areas called <EM CLASS="Emphasis">
zones</EM>
, each starting at a domain and extending down to the leaf domains or to domains where other zones start. Zones usually represent administrative boundaries. For example, a domain name for a host at the company <EM CLASS="EquationVariables">
, each starting at a domain and extending down to the leaf domains or to domains where other zones start. Zones usually represent administrative boundaries. For example, a domain name for a host at the company <EM CLASS="Emphasis">
Example, Inc.</EM>
would be:</P>
<P CLASS="3LevelContinued1">
<A NAME="pgfId=997418">
</A>
<EM CLASS="EquationVariables">
<EM CLASS="URL">
ourhost.example.com</EM>
</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997419">
</A>
The top level domain for corporate organizations is <EM CLASS="EquationVariables">
where <EM CLASS="URL">
com</EM>
; <EM CLASS="EquationVariables">
is the top level domain to which <EM CLASS="URL">
ourhost.example.com</EM>
belongs, <EM CLASS="URL">
example</EM>
is a subdomain of <EM CLASS="EquationVariables">
.com</EM>
; and <EM CLASS="EquationVariables">
is a subdomain of <EM CLASS="URL">
com</EM>
, and <EM CLASS="URL">
ourhost</EM>
is the name of the host.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997420">
</A>
The specifications for the domain nameserver are defined in RFC1034, RFC1035 and RFC974. These documents can be found in<BR>
The specifications for the domain nameserver are defined in the RFC 1034, RFC 1035 and RFC 974. These documents can be found in<BR>
<EM CLASS="pathname">
/usr/src/etc/named/doc</EM>
in 4.4BSD or are available via <CODE CLASS="Program-Process">
FTP</CODE>
from<BR>
in 4.4BSD or are available via File Transfer Protocol (FTP) from<BR>
<EM CLASS="URL">
ftp://www.isi.edu/in-notes/</EM>
or via the Web at <EM CLASS="URL">
http://www.ietf.org/rfc/</EM>
. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related <CODE CLASS="Program-Process">
man</CODE>
pages: <CODE CLASS="Program-Process">
. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related man pages: <CODE CLASS="Program-Process">
named</CODE>
and <CODE CLASS="Program-Process">
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>
@@ -370,57 +368,59 @@ As we stated previously, a zone is a point of delegation in the DNS tree. A zone
<P CLASS="3LevelContinued">
<A NAME="pgfId=997423">
</A>
To properly operate a nameserver, it is important to understand the difference between a <EM CLASS="EquationVariables">
To properly operate a nameserver, it is important to understand the difference between a <EM CLASS="Emphasis">
zone</EM>
and a <EM CLASS="EquationVariables">
and a <EM CLASS="Emphasis">
domain</EM>
.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997424">
</A>
As an example, consider the <EM CLASS="EquationVariables">
For instance, consider the <EM CLASS="URL">
example.com</EM>
domain, which includes names such as <EM CLASS="EquationVariables">
domain which includes names such as <EM CLASS="URL">
host.aaa.example.com </EM>
and <EM CLASS="EquationVariables">
and <EM CLASS="URL">
host.bbb.example.com</EM>
even though the <EM CLASS="EquationVariables">
even though the <EM CLASS="URL">
example.com</EM>
zone includes only delegations for the <EM CLASS="EquationVariables">
zone includes only delegations for the <EM CLASS="URL">
aaa.example.com</EM>
and <EM CLASS="EquationVariables">
and <EM CLASS="URL">
bbb.example.com</EM>
zones. A zone can map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other nameservers. Every name in the DNS tree is a <EM CLASS="EquationVariables">
zones. A zone can map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other nameservers. Every name in the DNS tree is a <EM CLASS="Emphasis">
domain</EM>
, even if it is <EM CLASS="EquationVariables">
, even if it is <EM CLASS="Emphasis">
terminal</EM>
, that is, has no <EM CLASS="EquationVariables">
, that is, has no <EM CLASS="Emphasis">
subdomains</EM>
. Every subdomain is a domain and every domain except the root is also a subdomain. The terminology is not intuitive and it is suggested that you read RFCs 1033, 1034, and 1035 to gain a complete understanding of this difficult and subtle topic.</P>
. Every subdomain is a domain and every domain except the root is also a subdomain. The terminology is not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to gain a complete understanding of this difficult and subtle topic.</P>
<P 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="EquationVariables">
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">
domain</EM>
, you are actually asking for secondary service for some collection of zones.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997426">
</A>
Each zone will have one <EM CLASS="EquationVariables">
Each zone will have one <EM CLASS="Emphasis">
primary master</EM>
(also called <EM CLASS="EquationVariables">
(also called <EM CLASS="Emphasis">
primary</EM>
) server which loads the zone contents from some local file edited by humans or perhaps generated mechanically from some other local file which is edited by humans. There there will be some number of <EM CLASS="EquationVariables">
secondary master </EM>
servers, which load the zone contents using the DNS protocol (that is, the secondary servers will contact the primary and fetch the zone data using TCP). This set of servers--the primary and all of its secondaries--should be listed in the NS records in the parent zone and will constitute a <EM CLASS="EquationVariables">
) server which loads the zone contents from some local file edited by humans or perhaps generated mechanically from some other local file which is edited by humans. There there will be some number of <EM CLASS="Emphasis">
slave</EM>
(also called <EM CLASS="Emphasis">
secondary) </EM>
servers, which load the zone contents using the DNS protocol (that is, the secondary servers will contact the primary and fetch the zone data using TCP). This set of servers--the primary and all of its secondaries--should be listed in the NS records in the parent zone and will constitute a <EM CLASS="Emphasis">
delegation</EM>
. This set of servers must also be listed in the zone file itself, usually under the <CODE CLASS="Program-Process">
@</CODE>
name which indicates the <EM CLASS="EquationVariables">
name which indicates the <EM CLASS="Emphasis">
top level</EM>
or <EM CLASS="EquationVariables">
or <EM CLASS="Emphasis">
root</EM>
of the current zone. You can list servers in the zone's top-level <CODE CLASS="Program-Process">
@</CODE>
@@ -430,115 +430,117 @@ root</EM>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997428">
</A>
Any servers listed in the NS records must be configured as <A NAME="marker=997427">
</A>
authoritative for the zone. A server is authoritative for a zone when it has been configured to answer questions for that zone with authority, which it does by setting the &quot;authoritative answer&quot; (AA) bit in reply packets. A server may be authoritative for more than one zone. The authoritative data for a zone is composed of all of the Resource Records (RRs)--the data associated with names in a tree-structured name space--attached to all of the nodes from the top node of the zone down to leaf nodes or nodes above <A NAME="marker=997429">
</A>
cuts around the bottom edge of the zone.</P>
Any servers listed in the NS records must be configured as <EM CLASS="Emphasis">
authoritative</EM>
for the zone. A server is authoritative for a zone when it has been configured to answer questions for that zone with authority, which it does by setting the &quot;authoritative answer&quot; (AA) bit in reply packets. A server may be authoritative for more than one zone. The authoritative data for a zone is composed of all of the Resource Records (RRs)--the data associated with names in a tree-structured name space--attached to all of the nodes from the top node of the zone down to leaf nodes or nodes above cuts around the bottom edge of the zone.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997430">
</A>
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>
A DNS server can be master for some zones and slave for others or can be only a master, or only a slave, or can serve no zones and just answer queries via its <EM CLASS="EquationVariables">
A DNS server can be master for some zones and slave for others or can be only a master, or only a slave, or can serve no zones and just answer queries via its <EM CLASS="Emphasis">
cache</EM>
. Master servers are often also called <EM CLASS="EquationVariables">
. Master servers are often also called <EM CLASS="Emphasis">
primaries</EM>
and slave servers are often also called <EM CLASS="EquationVariables">
and slave servers are often also called <EM CLASS="Emphasis">
secondaries</EM>
. Both master/primary and slave/secondary servers are authoritative for a zone.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997433">
</A>
All servers keep data in their cache until the data expires, based on a TTL (Time To Live) field which is maintained for all resource records.</P>
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>
The <EM CLASS="EquationVariables">
primary master</EM>
server 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>
The <EM CLASS="Emphasis">
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>
A <EM CLASS="EquationVariables">
A <EM CLASS="Emphasis">
slave server</EM>
, also called a <EM CLASS="EquationVariables">
, also called a <EM CLASS="Emphasis">
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 resource records (RRs) for the zone.</P>
, 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>
Some servers are <EM CLASS="EquationVariables">
Some servers are <EM CLASS="Emphasis">
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>
Instead of interacting with the nameservers for the root and other domains, a <EM CLASS="EquationVariables">
Instead of interacting with the nameservers for the root and other domains, a <EM CLASS="Emphasis">
forwarding server</EM>
always forwards queries it cannot satisfy from its authoritative data or cache to a fixed list of other servers. The forwarded queries are also known as <EM CLASS="EquationVariables">
recursive queries, </EM>
the same type as a client would send to a server. There may be one or more servers forwarded to, and they are queried in turn until the list is exhausted or an answer is found. A forwarding server is typically used when you do not wish all the servers at a given site to interact with the rest of the Internet servers. A typical scenario would involve a number of internal DNS servers, and an internet firewall. The servers which cannot pass packets through the firewall would forward to the server which can, which would ask the internet DNS servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete cache of information that all the workstations can take advantage of. </P>
always forwards queries it cannot satisfy from its authoritative data or cache to a fixed list of other servers. The forwarded queries are also known as <EM CLASS="Emphasis">
recursive queries</EM>
, the same type as a client would send to a server. There may be one or more servers forwarded to, and they are queried in turn until the list is exhausted or an answer is found. A forwarding server is typically used when you do not wish all the servers at a given site to interact with the rest of the Internet servers. A typical scenario would involve a number of internal DNS servers and an Internet firewall. Servers unable to pass packets through the firewall would forward to the server that can do it, and that server would query the Internet DNS servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete cache of information that all the workstations can take advantage of.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997442">
</A>
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>
A stealth server is a server that answers authoritatively for a zone, but is not listed in that zone's NS records. Stealth servers can be used as a way to centralize distribution of a zone, without having to edit the zone on a remote nameserver. Where the master file for a zone resides on a stealth server in this way, it is often referred to as a &quot;hidden primary&quot; configuration. Stealth servers can also be a way to keep a local copy of a zone for rapid access to the zone's records, even if all &quot;official&quot; nameservers for the zone are inaccessible.</P>
A <EM CLASS="Emphasis">
stealth server</EM>
is a server that answers authoritatively for a zone, but is not listed in that zone's NS records. Stealth servers can be used as a way to centralize distribution of a zone, without having to edit the zone on a remote nameserver. Where the master file for a zone resides on a stealth server in this way, it is often referred to as a &quot;hidden primary&quot; configuration. Stealth servers can also be a way to keep a local copy of a zone for rapid access to the zone's records, even if all &quot;official&quot; nameservers for the zone are inaccessible.</P>
</DIV>
</DIV>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
</BODY>
</HTML>

6
doc/arm/Bv9ARM.2.html
View File

@@ -25,7 +25,7 @@ DNS hardware requirements have traditionally been quite modest. For many install
<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>
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>
</DIV>
<DIV>
<OL>
@@ -49,7 +49,7 @@ CPU requirements for BINDv9 range from i486-class machines for serving of static
<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>
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>
</DIV>
<DIV>
<OL>
@@ -86,6 +86,8 @@ 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>
</BODY>
</HTML>

349
doc/arm/Bv9ARM.3.html
View File

@@ -5,251 +5,260 @@
<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>
</A>
Section 3. Nameserver Configuration</H1>
</OL>
<P CLASS="1LevelContinued">
<A NAME="pgfId=997351">
</A>
</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>
</A>
3.1 <A NAME="30164">
</A>
Sample Configuration and Logging</H3>
</OL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997354"></A>
<CODE>logging {
channel <VAR>named_log</VAR> {
file &quot;<EM>logs/named.log</EM>&quot;;
print-time <VAR>yes</VAR>;
print-category <VAR>yes</VAR>;
print-severity <VAR>yes</VAR>;
severity <VAR>info</VAR>;
<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">;
};
channel <VAR>security_log</VAR> {
file &quot;<EM>logs/security.log</EM> &quot; <VAR>versions 7</VAR> ;
print-time <VAR>yes</VAR> ;
<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 <VAR>default</VAR> { named_log; default_debug; };
category security { security_log };
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 corpnet { 192.168.4.0/24; 192.168.7.0/24; };
// The options statement.
options {
directory &quot;<EM>/etc/namedb</EM>&quot;; // Directory
pid-file &quot;<EM>named.pid</EM>&quot;; // Put .pid file in named directory.
check-names master <VAR>fail</VAR>; // Fail on db errors in master zones.
check-names slave <VAR>warn</VAR>; // Warn about db errors
// in slave zones.
check-names response <VAR>warn</VAR>; // Warn about invalid responses
use-id-pool <VAR>yes</VAR>; // Help prevent spoofing
host-statistics <VAR>yes</VAR>; // Keep track of hosts/servers
// we've talked to.
listen-on { 192.168.7.20; }; // Listen on this address.
// 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 { <VAR>none</VAR>; }; // 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.
// 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.
};
include &quot;<EM>keys.conf</EM>&quot;; // Include a keys.conf with
// TSIG/DNSSEC keys.
// Shouldn't be readable to anyone
// except BIND user.
zone &quot;<EM>.</EM>&quot;{ type <VAR>hint</VAR>; file &quot;<EM>local/named.root</EM>&quot;;
}; // root hints
zone &quot;<EM>0.0.127.IN-ADDR.ARPA</EM>&quot; {
type <VAR>master</VAR>; file &quot;<EM>local/localhost.db</EM>&quot;; notify <VAR>no</VAR>;
// localhost
};
zone &quot;example.com&quot; { // Example zone for &quot;<EM>example.com</EM>&quot;.
type <VAR>master</VAR>; // It's a master zone.
file &quot;<EM>m/example.com.db</EM>&quot;; // The file is here.
allow-query { <VAR>any</VAR>; }; // Allow anyone to query.
allow-transfer { corpnet; }; // Only allow corp nets to transfer zone.
};
zone &quot;<EM>offsite.example.com</EM>&quot; { // Example zone for an off-site corp zone.
type <VAR>slave</VAR>; // It's a slave zone.
masters { 192.168.4.12; }; // The master is at this address.
file &quot;<EM>s/offsite.example.com.db</EM>&quot;; // The file is here.
notify <VAR>no</VAR>; // Don't worry about NOTIFYing.
allow-query { <VAR>any</VAR>; }; // Allow anyone to query.
</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>
<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>
</PRE>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997410">
</A>
</A>
3.2 Load Balancing and Round Robin</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997411">
</A>
</A>
Primitive load balancing can be achieved in DNS using multiple A records for one name.</P>
<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 record like 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>
</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>
<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>
www</P>
<A NAME="pgfId=997425"></A>
<CODE CLASS="grammar_literal">
www</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997427">
</A>
10m</P>
<A NAME="pgfId=997427"></A>
<CODE CLASS="grammar_literal">
600</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997429">
</A>
IN</P>
<A NAME="pgfId=997429"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997431">
</A>
A</P>
<A NAME="pgfId=997431"></A>
<CODE CLASS="grammar_literal">
A</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997433">
</A>
10.0.0.1</P>
<A NAME="pgfId=997433"></A>
<CODE CLASS="grammar_literal">
10.0.0.1</CODE>
</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997435">
</A>
<A NAME="pgfId=997435"></A>
<CODE CLASS="grammar_literal">
</CODE>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997437">
</A>
10m</P>
<A NAME="pgfId=997437"></A>
<CODE CLASS="grammar_literal">
600</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997439">
</A>
IN</P>
<A NAME="pgfId=997439"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997441">
</A>
A</P>
<A NAME="pgfId=997441"></A>
<CODE CLASS="grammar_literal">
A</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997443">
</A>
10.0.0.2</P>
<A NAME="pgfId=997443"></A>
<CODE CLASS="grammar_literal">
10.0.0.2</CODE>
</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997445">
</A>
<A NAME="pgfId=997445"></A>
<CODE CLASS="grammar_literal">
</CODE>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997447">
</A>
10m</P>
<A NAME="pgfId=997447"></A>
<CODE CLASS="grammar_literal">
600</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997449">
</A>
IN</P>
<A NAME="pgfId=997449"></A>
<CODE CLASS="grammar_literal">
IN</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997451">
</A>
A</P>
<A NAME="pgfId=997451"></A>
<CODE CLASS="grammar_literal">
A</CODE>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997453">
</A>
10.0.0.3</P>
<A NAME="pgfId=997453"></A>
<CODE CLASS="grammar_literal">
10.0.0.3</CODE>
</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. 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>
<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">
@@ -259,50 +268,52 @@ RRset Ordering</A>
.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997460">
</A>
3.3 Notify</H3>
</OL>
<A NAME="pgfId=997460"></A>
3.3 <A NAME="35205"></A>
Notify</H3>
<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. DNS Notify is turned on by default.</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 and that a query should be initiated to discover the new data.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1016466">
<A NAME="pgfId=1078896">
</A>
DNS Notify is fully documented in RFC 1996. See also the description of the zone option <CODE CLASS="Program-Process">
also-notify</CODE>
on <A HREF="Bv9ARM.5.html#32057" CLASS="XRef">
in <A HREF="Bv9ARM.5.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>
.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=1016467">
<A NAME="pgfId=1078903">
</A>
3.4 Nameserver Operations</H3>
</OL>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997464">
</A>
3.4.1 Tools for Use With the Nameserver Daemon</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997465">
</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>
3.4.1.1 Diagnostic Tools</H5>
</OL>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
@@ -406,12 +417,12 @@ nslookup</CODE>
man page.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997487">
</A>
3.4.1.2 Administrative Tools</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997488">
</A>
@@ -427,7 +438,9 @@ rndc</H5>
</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 rndc without any options it will display a usage message.</P>
) program is a program that allows the system administrator to control the operation of a nameserver. If you run <CODE CLASS="Program-Process">
rndc</CODE>
without any options it will display a usage message.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1012780">
</A>
@@ -438,30 +451,14 @@ Usage:</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997493">
</A>
For more information and a list of available commands and options, see the rndc man page.</P>
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>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997494">
</A>
3.4.1.3 Monitoring Tools</H5>
</OL>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997495">
</A>
MRTG</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997496">
</A>
<CODE CLASS="Program-Process">
MRTG</CODE>
is primarily a router traffic grapher, but can be used to monitor BIND DNS servers, as well. The `stat' script, supplied with MRTG in the MRTG `contrib/stat' directory, can be used to monitor numbers of queries, and counts of various sorts of responses.</P>
</DIV>
</DIV>
</DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
</BODY>
</HTML>

696
doc/arm/Bv9ARM.4.html
View File

File diff suppressed because it is too large Load Diff

2598
doc/arm/Bv9ARM.5.html
View File

File diff suppressed because it is too large Load Diff

104
doc/arm/Bv9ARM.6.html
View File

@@ -5,21 +5,21 @@
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 6. Security Considerations</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
Section 6. Security Considerations</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997352">
</A>
6.1 <A NAME="32222">
</A>
Access Control Lists</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
@@ -51,51 +51,54 @@ Here is an example of how to properly apply ACLs:</P>
</A>
// Set up an ACL named &quot;bogusnets&quot; that will block RFC1918 space,<BR>
// which is commonly used in spoofing attacks.</P>
<PRE>
<CODE>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; };
</CODE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997358"></A>
<CODE CLASS="grammar_literal">acl</CODE> <KBD CLASS="Literal-user-input">bogusnets</KBD> <CODE CLASS="grammar_literal">{</CODE> 0.0.0.0/8<CODE CLASS="grammar_literal">;</CODE> 1.0.0.0/8<CODE CLASS="grammar_literal">;</CODE> 2.0.0.0/8<CODE CLASS="grammar_literal">;</CODE> 192.0.2.0/24<CODE CLASS="grammar_literal">;</CODE>
224.0.0.0/3<CODE CLASS="grammar_literal">;</CODE> 10.0.0.0/8<CODE CLASS="grammar_literal">;</CODE> 172.16.0.0/12<CODE CLASS="grammar_literal">;</CODE> 192.168.0.0/16<CODE CLASS="grammar_literal">; };</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
</A>
// Set up an ACL called our-nets. Replace this with the real IP numbers.</P>
<PRE>
<CODE>acl our-nets { x.x.x.x/24; x.x.x.x/21; };
options {
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997360"></A>
<CODE CLASS="grammar_literal">acl</CODE> <EM CLASS="variable">our-nets</EM> <CODE CLASS="grammar_literal">{ </CODE>x.x.x.x/24<CODE CLASS="grammar_literal">;</CODE> x.x.x.x/21; <CODE CLASS="grammar_literal">};</CODE> </PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997361"></A>
<CODE CLASS="grammar_literal">options {
</CODE>
<EM CLASS="Optional-meta-syntax">...
...
...
allow-query { <VAR>our-nets</VAR>; };
allow-recursion { <VAR>our-nets</VAR>; };
...
blackhole { bogusnets; };
...
};
zone &quot;<EM>example.com</EM>&quot; {
type <VAR>master</VAR>;
file &quot;<EM>m/example.com</EM>&quot;;
allow-query { <VAR>any</VAR>; };
</EM>
<CODE CLASS="grammar_literal">allow-query { </CODE><EM CLASS="variable">our-nets</EM><CODE CLASS="grammar_literal">; };</CODE>
<CODE CLASS="grammar_literal">allow-recursion {</CODE> <EM CLASS="variable">our-nets</EM><CODE CLASS="grammar_literal">; };</CODE>
<EM CLASS="Optional-meta-syntax">...
</EM>
<CODE CLASS="grammar_literal">blackhole {</CODE> <KBD CLASS="Literal-user-input">bogusnets</KBD><CODE CLASS="grammar_literal">; };</CODE>
<EM CLASS="Optional-meta-syntax">...
</EM>
<CODE CLASS="grammar_literal">};</CODE>
</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997362"></A>
<CODE CLASS="grammar_literal">zone</CODE> &quot;<EM CLASS="pathname">example.com</EM>&quot; <CODE CLASS="grammar_literal">{</CODE>
<CODE CLASS="grammar_literal">type</CODE> <EM CLASS="variable">master</EM><CODE CLASS="grammar_literal">;</CODE>
<CODE CLASS="grammar_literal">file</CODE> <KBD CLASS="Literal-user-input">&quot;m/example.com&quot;</KBD><CODE CLASS="grammar_literal">;</CODE>
<CODE CLASS="grammar_literal">allow-query</CODE> <CODE CLASS="grammar_literal">{</CODE> <EM CLASS="variable">any</EM><CODE CLASS="grammar_literal">; };
};</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997363">
</A>
This allows recursive queries of the server from the outside unless recursion has been previously disabled.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997364">
<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>
<EM CLASS="URL">
ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</EM>
<EM CLASS="hypertext">
<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></EM>
</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997365">
</A>
@@ -104,7 +107,7 @@ chroot</CODE>
and <CODE CLASS="Program-Process">
setuid</CODE>
(for UNIX servers)</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997366">
</A>
@@ -112,12 +115,12 @@ 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">
) by specifying the '<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>
' 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>
</A>
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>
&lt;<EM CLASS="variable">
@@ -126,8 +129,7 @@ user</EM>
chroot</CODE>
feature.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997368">
</A>
<A NAME="pgfId=997368"></A>
Here is an example command line to load BIND in a <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox, <BR>
@@ -142,20 +144,20 @@ setuid</CODE>
<KBD CLASS="Literal-user-input">/usr/local/bin/named -u 202 -t /var/named</KBD>
</PRE>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997370">
</A>
</A>
6.2.1 The <CODE CLASS="Program-Process">
chroot</CODE>
Environment</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997371">
</A>
</A>
In order for a <CODE CLASS="Program-Process">
chroot()</CODE>
environment to work properly in a particular directory (e.g., <EM CLASS="pathname">
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>
@@ -166,23 +168,23 @@ chroot()</CODE>
sandbox.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997372">
</A>
</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>
</A>
6.2.2 Using the <CODE CLASS="Program-Process">
setuid</CODE>
Function </H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997374">
</A>
</A>
Prior to running the <CODE CLASS="Program-Process">
named</CODE>
daemon, use the <CODE CLASS="Program-Process">
@@ -193,21 +195,23 @@ chown</CODE>
</DIV>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997375">
</A>
</A>
6.3 Dynamic Updates</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997376">
</A>
</A>
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. BINDv9 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=1006806">
</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>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
</BODY>
</HTML>

96
doc/arm/Bv9ARM.7.html
View File

@@ -25,18 +25,18 @@ Section 7. Troubleshooting</H1>
</A>
lame server</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997353"> </A>
<EM CLASS="grammar_literal">ns named[111]: Lame server on 'www.foo.com' (in 'foo.com'?): [192.168.0.2].53 'ns2.foo.com'</EM>
<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>
<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.foo.com</EM>
ns2.example.com</EM>
) is listed as a nameserver for &quot;<EM CLASS="pathname">
foo.com</EM>
example.com</EM>
&quot;, but it doesn't really know anything about <EM CLASS="pathname">
foo.com</EM>
example.com</EM>
.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
@@ -54,36 +54,36 @@ If it's a zone out on the Internet, it would be nice to notify the owners of the
</A>
bad referral</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997358"> </A>
<EM CLASS="grammar_literal">ns named[111]: bad referral (other.com !&lt; subdomain.other.com)</EM>
<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.foo.com</EM>
ns.example.com</EM>
) queried the nameserver for <EM CLASS="pathname">
foo2.com</EM>
example2.com</EM>
to find out how to get to <EM CLASS="pathname">
subdomain.foo2.com</EM>
. <EM CLASS="pathname">
foo2.com</EM>
subdomain.example2.com</EM>
. The name server <EM CLASS="pathname">
example2.com</EM>
told your nameserver that <EM CLASS="pathname">
subdomain.foo2.com</EM>
subdomain.example2.com</EM>
was delegated to some <EM CLASS="pathname">
other.foo2.com</EM>
other.example2.com</EM>
, so your nameserver queried that.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997360">
</A>
<EM CLASS="pathname">
someother.foo2.com</EM>
someother.example2.com</EM>
didn't think that <EM CLASS="pathname">
subdomain.foo2.com</EM>
subdomain.example2.com</EM>
had been delegated to it, so it referred your server (<EM CLASS="pathname">
ns.foo.com</EM>
ns.example.com</EM>
) back to the <EM CLASS="pathname">
foo2.com</EM>
example2.com</EM>
nameserver.</P>
</DIV>
<DIV>
@@ -93,13 +93,15 @@ foo2.com</EM>
</A>
not authoritative for</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997362"> </A>
<EM CLASS="grammar_literal">ns named-xfer[111]: [192.168.0.1] not authoritative for foo.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0</EM>
<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>
</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 named 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 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>
</DIV>
<DIV>
<UL>
@@ -108,14 +110,14 @@ This error usually shows up on a slave server. It indicates that the master serv
</A>
rejected zone</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997365"> </A>
<EM CLASS="grammar_literal">ns named[111]: master zone &quot;foo.com&quot; (IN) rejected due to errors (serial111)</EM>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997366">
</A>
This indicates that the <EM CLASS="pathname">
foo.com</EM>
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>
@@ -127,14 +129,14 @@ named</CODE>
</A>
no NS RRs found</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997368"> </A>
<EM CLASS="grammar_literal">ns named[111]: Zone &quot;foo.com&quot; (file foo.com.db): no NS RRs found at zonetop</EM>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997369">
</A>
The <EM CLASS="pathname">
foo.com.db</EM>
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>
@@ -144,17 +146,21 @@ foo.com.db</EM>
</A>
no default TTL set</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997371"> </A>
<EM CLASS="grammar_literal">ns named[111]: Zone &quot;foo.com&quot; (file foo.com.db): No default TTL set using SOA minimum instead</EM>
<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 need to add a $TTL to the top of the <EM CLASS="pathname">
foo.com.db</EM>
zone file. See RFC2308, or <A HREF="Bv9ARM.5.html#19693" CLASS="XRef">
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>
in this document, for information on how to use $TTL.</P>
for information on how to use <CODE CLASS="grammar_literal">
$TTL</CODE>
.</P>
</DIV>
<DIV>
<UL>
@@ -163,8 +169,8 @@ Setting TTLs</A>
</A>
no root nameserver for class</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997374"> </A>
<EM CLASS="grammar_literal">findns: No root nameservers for class IN?</EM>
<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">
@@ -182,8 +188,8 @@ If you are running an internal root nameserver, make sure it is configured prope
</A>
address already in use</H6>
</UL>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997378"> </A>
<EM CLASS="grammar_literal">ctl_server: bind: Address already in use</EM>
<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">
@@ -221,7 +227,7 @@ This means that the regular user wouldn't be able to delete it, so it would thin
<A NAME="pgfId=997384">
</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>
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>
</DIV>
</DIV>
@@ -255,23 +261,19 @@ The solution to this is to add 2147483647 (2^31-1) to the number, reload the zon
<P CLASS="2LevelContinued">
<A NAME="pgfId=1001264">
</A>
The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND, DHCP and INN 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, DHCP or INN.</P>
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>
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">
http://www.isc.org/services/support/</EM>
<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>
</DIV>
</DIV>
</DIV>
</DIV>
</BODY>
</HTML>

196
doc/arm/Bv9ARM.8.html
View File

@@ -5,7 +5,6 @@
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Appendices</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<DIV>
<H6 CLASS="Title">
<A NAME="pgfId=997347">
</A>
@@ -15,11 +14,11 @@ Appendices</H6>
<A NAME="pgfId=999043">
</A>
Appendix A. Acknowledgements</H6>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1000953">
</DIV>
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1001089">
</A>
A Brief History of the DNS and BIND</H6>
A.1 A Brief History of the DNS and BIND</H2>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000944">
</A>
@@ -44,25 +43,25 @@ BIND versions from 4.9.3 onward have been developed and maintained by the Intern
<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">
<H1 CLASS="AppendixLevel1">
<A NAME="pgfId=1001064">
</A>
<A NAME="13688">
Appendix B. <A NAME="13688">
</A>
Appendix B. Historical DNS Information</H6>
Historical DNS Information</H1>
<DIV>
<H6 CLASS="AppendixLevel2">
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1001089">
</A>
Classes of resource records</H6>
B.1 <A NAME="38866">
</A>
Classes of Resource Records</H2>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=1029256">
</A>
HS = hesiod</H6>
B.1.1 HS = hesiod</H3>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029267">
</A>
@@ -73,10 +72,10 @@ hs</CODE>
is a synonym for hesiod.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=1029289">
</A>
CH = chaos</H6>
B.1.2 CH = chaos</H3>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029290">
</A>
@@ -85,37 +84,37 @@ 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">
<H1 CLASS="AppendixLevel1">
<A NAME="pgfId=1029291">
</A>
<A NAME="35452">
Appendix C. <A NAME="35452">
</A>
Appendix C. Bibliography (and Suggested Reading)</H6>
Bibliography (and Suggested Reading)</H1>
<DIV>
<H6 CLASS="AppendixLevel2">
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999193">
</A>
<A NAME="42144">
C.1 <A NAME="42144">
</A>
C.1 Request for Comments (RFCs)</H6>
Request for Comments (RFCs)</H2>
<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 themselvers 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>
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>
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>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999212">
</A>
Standards</H6>
C.1.1 Standards</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999776">
</A>
@@ -125,7 +124,7 @@ Mail Routing and the Domain System</EM>
<P CLASS="Biblio">
<A NAME="pgfId=999777">
</A>
RFC1034. Mockapetris, P.V. <EM CLASS="doc-title">
RFC1034. Mockapetris, P.V. <EM CLASS="doc-title">
Domain Names - Concepts and Facilities</EM>
. P.V. November 1987.</P>
<P CLASS="Biblio">
@@ -136,12 +135,12 @@ Domain Names - Implementation and Specification</EM>
. November 1987.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999218">
</A>
<A NAME="17631">
C.1.2 <A NAME="17631">
</A>
Proposed Standards</H6>
Proposed Standards</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999220">
</A>
@@ -172,18 +171,24 @@ A Mechanism for Prompt Notification of Zone Changes</EM>
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">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999227">
</A>
Proposed Standards Still Under Development</H6>
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. (See the Internet Drafts section, below, for current versions).</P>
the following list of RFCs are undergoing major revision by the IETF.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999230">
</A>
@@ -204,10 +209,10 @@ Secure Domain Name System Dynamic Update</EM>
. April 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999235">
</A>
Other Important RFCs About DNS Implementation</H6>
C.1.4 Other Important RFCs About DNS Implementation</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999237">
</A>
@@ -228,10 +233,10 @@ Serial Number Arithmetic</EM>
. August 1996.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999242">
</A>
Resource Record Types</H6>
C.1.5 Resource Record Types</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999244">
</A>
@@ -247,7 +252,7 @@ DNS NSAP Resource Records</EM>
<P CLASS="Biblio">
<A NAME="pgfId=999253">
</A>
RFC2168. Danie1,R., M. Mealling. <EM CLASS="doc-title">
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">
@@ -259,15 +264,15 @@ A Means for Expressing Location Information in the Domain Name System</EM>
<P CLASS="Biblio">
<A NAME="pgfId=999255">
</A>
RFC2052. Gulbrandsen,A., P. Vixie. <EM CLASS="doc-title">
RFC2052. Gulbrandsen, A., P. Vixie. <EM CLASS="doc-title">
A DNS RR for Specifying the Location of Services.</EM>
October 1996.</P>
<P CLASS="Bib31">
<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>
. January 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000251">
</A>
@@ -276,15 +281,15 @@ Key Exchange Delegation Record for the DNS</EM>
. October 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999260">
</A>
DNS and the Internet</H6>
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>
DNS Encoding of Network Names and Other Types</EM>
. April 1989.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999263">
@@ -306,10 +311,10 @@ Classless IN-ADDR.ARPA Delegation</EM>
. March 1998.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999274">
</A>
DNS Operations</H6>
C.1.7 DNS Operations</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999276">
</A>
@@ -336,21 +341,16 @@ Use of DNS Aliases for Network Services.</EM>
October 1997.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999282">
</A>
Other DNS-related RFCs</H6>
</DIV>
</DIV>
</DIV>
</DIV>
<DIV>
<H6 CLASS="3LevelContinued1">
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.</H6>
the following list of RFCs, although DNS-related, are not concerned with implementing software.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999284">
</A>
@@ -387,11 +387,12 @@ Domain Names and Company Name Retrieval</EM>
RFC2352. Vaughan, O. <EM CLASS="doc-title">
A Convention For Using Legal Names as Domain Names</EM>
. May 1998.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<H3 CLASS="AppendixLevel3">
<A NAME="pgfId=999292">
</A>
Obsolete and Unimplemented Experimental RRs</H6>
C.1.9 Obsolete and Unimplemented Experimental RRs</H3>
<P CLASS="Biblio">
<A NAME="pgfId=999294">
</A>
@@ -399,76 +400,31 @@ 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>
<H6 CLASS="AppendixLevel2">
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999195">
</A>
<A NAME="">
C.2 <A NAME="">
</A>
C.2 Internet Drafts</H6>
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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000433">
</A>
IDs can be obtained via FTP from<BR>
<EM CLASS="URL">
ftp://www.isi.edu/internet-drafts/</EM>
or from <EM CLASS="URL">
http://www.ietf.org/1id-abstracts.html</EM>
.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000877">
</A>
<EM CLASS="doc-title">
draft-duerst-dns-i18n-01.txt<BR>
draft-ietf-dhc-dhcp-dns-10.txt<BR>
draft-ietf-dnsind-apl-rr-03.txt<BR>
draft-ietf-dnsind-dddd-01.txt<BR>
draft-ietf-dnsind-dhcp-rr-00.txt<BR>
draft-ietf-dnsind-edns1-03.txt<BR>
draft-ietf-dnsind-iana-dns-04.txt<BR>
draft-ietf-dnsind-indirect-key-00.txt<BR>
draft-ietf-dnsind-keyreferral-00.txt<BR>
draft-ietf-dnsind-kitchen-sink-02.txt<BR>
draft-ietf-dnsind-local-compression-05.txt<BR>
draft-ietf-dnsind-local-names-07.txt<BR>
draft-ietf-dnsind-rfc2052bis-05.txt<BR>
draft-ietf-dnsind-rollover-00.txt<BR>
draft-ietf-dnsind-sec-rr-00.txt<BR>
draft-ietf-dnsind-sigalgopt-00.txt<BR>
draft-ietf-dnsind-simple-secure-update-02.txt<BR>
draft-ietf-dnsind-test-tlds-13.txt<BR>
draft-ietf-dnsind-tkey-01.txt<BR>
draft-ietf-dnsind-tsig-13.txt<BR>
draft-ietf-dnsind-verify-00.txt<BR>
draft-ietf-dnssec-ar-00.txt<BR>
draft-ietf-dnssec-as-map-05.txt<BR>
draft-ietf-dnssec-key-handling-00.txt<BR>
draft-ietf-dnssec-secfail-00.txt<BR>
draft-ietf-dnssec-update2-00.txt<BR>
draft-ietf-ipngwg-2292bis-00.txt<BR>
draft-ietf-ipngwg-dns-lookups-05.txt<BR>
draft-dunlap-dns-duxfr-00.txt<BR>
draft-schroeppel-dnsind-ecc-00.txt<BR>
draft-skwan-gss-tsig-04.txt<BR>
draft-skwan-utf8-dns-02.txt</EM>
</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel2">
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=999464">
</A>
C.3 Electronic Mail Communication</H6>
<P CLASS="Bib2">
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="Bib2">
<P CLASS="2Biblio">
<A NAME="pgfId=1001025">
</A>
Wellington, Brian (bwellington@tislabs.com). <EM CLASS="doc-title">
@@ -476,20 +432,20 @@ TSIG guide for BIND 8.2+</EM>
. E-mail to private mailing list (private communication). 22 April 1999.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel2">
<H2 CLASS="AppendixLevel2">
<A NAME="pgfId=1000764">
</A>
C.4 Other BIND Documents</H6>
<P CLASS="Bib2">
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>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
<DIV>
<p>Return to <A href="Bv9ARM.html">BINDv9 Administrator Reference Manual</A>
</DIV>
</BODY>
</HTML>

397
doc/arm/Bv9ARM.css
View File

@@ -42,6 +42,22 @@ P.1LevelContinued {
text-transform: none;
font-family: Times;
}
P.2Biblio {
text-align: left;
text-indent: -18.000000pt;
margin-top: 5.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 90.000000pt;
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.2Level, H2.2Level, H3.2Level, H4.2Level, H5.2Level, H6.2Level {
text-align: left;
text-indent: -27.000000pt;
@@ -90,7 +106,7 @@ LI.2Level-bullet2 {
text-transform: none;
font-family: Times;
}
P.2Level-fixed {
PRE.2Level-fixed {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
@@ -106,6 +122,22 @@ P.2Level-fixed {
text-transform: none;
font-family: Courier New;
}
PRE.2Level-fixed1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 63.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
LI.2Level-numList1 {
text-align: left;
text-indent: -18.000000pt;
@@ -170,7 +202,7 @@ H1.3Level, H2.3Level, H3.3Level, H4.3Level, H5.3Level, H6.3Level {
text-transform: none;
font-family: Arial;
}
P.3Level-fixed {
PRE.3Level-fixed {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
@@ -202,6 +234,38 @@ P.3Level-fixed-special {
text-transform: none;
font-family: Courier New;
}
P.3Level-fixed1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.3Level-fixed2 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.3LevelContinued {
text-align: left;
text-indent: 0.000000pt;
@@ -218,11 +282,11 @@ P.3LevelContinued {
text-transform: none;
font-family: Times;
}
H1.3LevelContinued1, H2.3LevelContinued1, H3.3LevelContinued1, H4.3LevelContinued1, H5.3LevelContinued1, H6.3LevelContinued1 {
P.3LevelContinued1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 13.000000pt;
margin-bottom: 0.000000pt;
margin-bottom: 1.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 11.000000pt;
@@ -232,7 +296,23 @@ H1.3LevelContinued1, H2.3LevelContinued1, H3.3LevelContinued1, H4.3LevelContinue
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times New Roman;
font-family: Times;
}
P.3LevelContinued21 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 11.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 99.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
H1.4Level, H2.4Level, H3.4Level, H4.4Level, H5.4Level, H6.4Level {
text-align: left;
@@ -250,7 +330,7 @@ H1.4Level, H2.4Level, H3.4Level, H4.4Level, H5.4Level, H6.4Level {
text-transform: none;
font-family: Arial;
}
H1.4Level-bullet1, H2.4Level-bullet1, H3.4Level-bullet1, H4.4Level-bullet1, H5.4Level-bullet1, H6.4Level-bullet1 {
LI.4Level-bullet1 {
text-align: left;
text-indent: 72.000000pt;
margin-top: 13.000000pt;
@@ -282,7 +362,23 @@ LI.4Level-bullet2 {
text-transform: none;
font-family: Times;
}
P.4Level-fixed {
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;
margin-top: 2.000000pt;
@@ -298,7 +394,39 @@ P.4Level-fixed {
text-transform: none;
font-family: Courier New;
}
P.4Level-fixedSmall {
PRE.4Level-fixed1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 3.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.4Level-fixed2 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 2.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
PRE.4Level-fixedSmall {
text-align: left;
text-indent: 0.000000pt;
margin-top: 2.000000pt;
@@ -330,7 +458,39 @@ P.4LevelContinued {
text-transform: none;
font-family: Times;
}
P.ActiveTOC {
H1.4LevelContinued1, H2.4LevelContinued1, H3.4LevelContinued1, H4.4LevelContinued1, H5.4LevelContinued1, H6.4LevelContinued1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 11.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
H1.4LevelContinued2, H2.4LevelContinued2, H3.4LevelContinued2, H4.4LevelContinued2, H5.4LevelContinued2, H6.4LevelContinued2 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 13.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 11.000000pt;
font-weight: medium;
font-style: Italic;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
THROW AWAY.ActiveTOC {
text-align: justify;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -362,7 +522,7 @@ H1.AppendixLevel1, H2.AppendixLevel1, H3.AppendixLevel1, H4.AppendixLevel1, H5.A
text-transform: none;
font-family: Arial;
}
P.AppendixLevel1TOC {
THROW AWAY.AppendixLevel1TOC {
text-align: left;
text-indent: 0.000000pt;
margin-top: 14.000000pt;
@@ -394,7 +554,7 @@ H1.AppendixLevel2, H2.AppendixLevel2, H3.AppendixLevel2, H4.AppendixLevel2, H5.A
text-transform: none;
font-family: Arial;
}
P.AppendixLevel2TOC {
THROW AWAY.AppendixLevel2TOC {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -426,7 +586,7 @@ H1.AppendixLevel3, H2.AppendixLevel3, H3.AppendixLevel3, H4.AppendixLevel3, H5.A
text-transform: none;
font-family: Arial;
}
P.AppendixLevel3TOC {
THROW AWAY.AppendixLevel3TOC {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -442,38 +602,6 @@ P.AppendixLevel3TOC {
text-transform: none;
font-family: Times;
}
P.Bib2 {
text-align: left;
text-indent: -18.000000pt;
margin-top: 6.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 90.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 New Roman;
}
P.Bib31 {
text-align: left;
text-indent: -9.000000pt;
margin-top: 4.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 108.000000pt;
font-size: 10.000000pt;
font-weight: medium;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times New Roman;
}
P.Biblio {
text-align: left;
text-indent: -9.000000pt;
@@ -554,7 +682,7 @@ P.CellBody {
text-transform: none;
font-family: Times;
}
P.CellBody-fixedfont {
CODE.CellBody-fixedfont {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -570,7 +698,7 @@ P.CellBody-fixedfont {
text-transform: none;
font-family: Courier New;
}
P.CellBody-fixedfontLG {
CODE.CellBody-fixedfontLG {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -586,7 +714,39 @@ P.CellBody-fixedfontLG {
text-transform: none;
font-family: Courier New;
}
H1.CellBody1, H2.CellBody1, H3.CellBody1, H4.CellBody1, H5.CellBody1, H6.CellBody1 {
P.CellBody-fixedFontMed {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 7.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.CellBody-fixedFontSmall {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 6.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.CellBody1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -602,7 +762,7 @@ H1.CellBody1, H2.CellBody1, H3.CellBody1, H4.CellBody1, H5.CellBody1, H6.CellBod
text-transform: none;
font-family: Courier New;
}
H1.CellBody2, H2.CellBody2, H3.CellBody2, H4.CellBody2, H5.CellBody2, H6.CellBody2 {
P.CellBody2 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -618,7 +778,7 @@ H1.CellBody2, H2.CellBody2, H3.CellBody2, H4.CellBody2, H5.CellBody2, H6.CellBod
text-transform: none;
font-family: Times;
}
H1.CellBody3, H2.CellBody3, H3.CellBody3, H4.CellBody3, H5.CellBody3, H6.CellBody3 {
P.CellBody3 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -634,7 +794,7 @@ H1.CellBody3, H2.CellBody3, H3.CellBody3, H4.CellBody3, H5.CellBody3, H6.CellBod
text-transform: none;
font-family: Times;
}
H1.CellBody4, H2.CellBody4, H3.CellBody4, H4.CellBody4, H5.CellBody4, H6.CellBody4 {
P.CellBody4 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -650,7 +810,7 @@ H1.CellBody4, H2.CellBody4, H3.CellBody4, H4.CellBody4, H5.CellBody4, H6.CellBod
text-transform: none;
font-family: Courier New;
}
H1.CellBody5, H2.CellBody5, H3.CellBody5, H4.CellBody5, H5.CellBody5, H6.CellBody5 {
P.CellBody5 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -666,7 +826,7 @@ H1.CellBody5, H2.CellBody5, H3.CellBody5, H4.CellBody5, H5.CellBody5, H6.CellBod
text-transform: none;
font-family: Courier New;
}
H1.CellBody6, H2.CellBody6, H3.CellBody6, H4.CellBody6, H5.CellBody6, H6.CellBody6 {
P.CellBody6 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -682,7 +842,7 @@ H1.CellBody6, H2.CellBody6, H3.CellBody6, H4.CellBody6, H5.CellBody6, H6.CellBod
text-transform: none;
font-family: Arial;
}
P.CellBody7 {
H1.CellBody7, H2.CellBody7, H3.CellBody7, H4.CellBody7, H5.CellBody7, H6.CellBody7 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -730,7 +890,7 @@ THROW AWAY.Footer {
text-transform: none;
font-family: Arial;
}
P.Footer1 {
THROW AWAY.Footer1 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -746,7 +906,7 @@ P.Footer1 {
text-transform: none;
font-family: Helvetica;
}
P.Header {
THROW AWAY.Header {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
@@ -986,6 +1146,22 @@ P.Mapping-Table-Cell32 {
text-transform: none;
font-family: Helvetica;
}
P.Mapping-Table-Cell321 {
text-align: left;
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: #ffffff;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Arial;
}
P.Mapping-Table-Cell33 {
text-align: left;
text-indent: 0.000000pt;
@@ -1002,6 +1178,22 @@ P.Mapping-Table-Cell33 {
text-transform: none;
font-family: Times;
}
P.Mapping-Table-Cell331 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-style: Regular;
color: #ffffff;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.Mapping-Table-Cell34 {
text-align: left;
text-indent: 0.000000pt;
@@ -1018,6 +1210,22 @@ P.Mapping-Table-Cell34 {
text-transform: none;
font-family: Helvetica;
}
P.Mapping-Table-Cell341 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #ffffff;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Arial;
}
P.Mapping-Table-Cell35 {
text-align: left;
text-indent: 0.000000pt;
@@ -1082,6 +1290,22 @@ P.Mapping-Table-Cell38 {
text-transform: none;
font-family: Helvetica;
}
P.Mapping-Table-Cell381 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-weight: medium;
font-style: Italic;
color: #ffffff;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Courier New;
}
P.Mapping-Table-Cell39 {
text-align: left;
text-indent: 0.000000pt;
@@ -1098,6 +1322,22 @@ P.Mapping-Table-Cell39 {
text-transform: none;
font-family: Helvetica;
}
P.Mapping-Table-Cell391 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 0.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 0.000000pt;
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
color: #ffffff;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Arial;
}
P.Mapping-Table-Cell4 {
text-align: left;
text-indent: 0.000000pt;
@@ -1130,7 +1370,7 @@ P.Mapping-Table-Title {
text-transform: none;
font-family: Times;
}
LI.Subhead2 {
H1.Subhead2, H2.Subhead2, H3.Subhead2, H4.Subhead2, H5.Subhead2, H6.Subhead2 {
text-align: left;
text-indent: 63.000000pt;
margin-top: 12.000000pt;
@@ -1146,6 +1386,22 @@ LI.Subhead2 {
text-transform: none;
font-family: Arial;
}
H1.Subhead4, H2.Subhead4, H3.Subhead4, H4.Subhead4, H5.Subhead4, H6.Subhead4 {
text-align: left;
text-indent: 0.000000pt;
margin-top: 12.000000pt;
margin-bottom: 0.000000pt;
margin-right: 0.000000pt;
margin-left: 144.000000pt;
font-size: 10.000000pt;
font-weight: Bold;
font-style: Regular;
color: #000000;
text-decoration: none;
vertical-align: baseline;
text-transform: none;
font-family: Times New Roman;
}
H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title {
text-align: center;
text-indent: 0.000000pt;
@@ -1162,6 +1418,9 @@ H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title {
text-transform: none;
font-family: Arial;
}
EM.CharFmt {
font-size: 12.000000pt;
}
EM.CharFmt1 {
}
EM.Command {
@@ -1210,7 +1469,7 @@ EM.Emphasis-underline {
EM.EquationVariables {
font-style: Italic;
}
EM.grammar_literal {
CODE.grammar_literal {
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
@@ -1220,7 +1479,17 @@ EM.grammar_literal {
text-transform: none;
font-family: Courier New;
}
TT.Literal-user-input {
EM.hypertext {
font-size: 11.000000pt;
font-weight: medium;
font-style: Italic;
color: #0000ff;
text-decoration: underline ;
vertical-align: baseline;
text-transform: none;
font-family: Times;
}
KBD.Literal-user-input {
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;
@@ -1244,7 +1513,17 @@ EM.pathname {
font-size: 10.000000pt;
font-style: Italic;
}
EM.production_target {
EM.pathname1 {
font-size: 10.000000pt;
font-style: Italic;
font-family: Times;
}
EM.pathname2 {
font-size: 10.000000pt;
font-style: Italic;
font-family: Times;
}
CODE.production_target {
font-size: 9.000000pt;
font-weight: Bold;
font-style: Regular;

58
doc/arm/Bv9ARM.html
View File

@@ -14,12 +14,13 @@
<H2>BIND version 9<BR>Administrator Reference Manual</H2>
<H2>DRAFT
<br>
May, 2000</H2>
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">
@@ -28,40 +29,43 @@ May, 2000</H2>
</A>
Table of Contents</H6>
</DIV>
<OL>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.1.html#pgfId=1007883" CLASS="Hypertext">
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.1.html" CLASS="Hypertext">
Section 1. Introduction </A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.2.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.2.html" CLASS="Hypertext">
Section 2. BIND Resource Requirements</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.3.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.3.html" CLASS="Hypertext">
Section 3. Nameserver Configuration</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.4.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.4.html" CLASS="Hypertext">
Section 4. Advanced Concepts</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.5.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.5.html" CLASS="Hypertext">
Section 5. BINDv9 Configuration Reference</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.6.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.6.html" CLASS="Hypertext">
Section 6. Security Considerations</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.7.html#pgfId=997350" CLASS="Hypertext">
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.7.html" CLASS="Hypertext">
Section 7. Troubleshooting</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="Bv9ARM.8.html#pgfId=997350" CLASS="Hypertext">
Appendices</A>
</H1></OL>
</H2>
<H2 CLASS="1LevelTOC">
<A HREF="Bv9ARM.8.html" CLASS="Hypertext">Appendices</A>
</H2>
<HR ALIGN="center">
<DIV ALIGN="center">
Copyright &copy;2000 Internet Software Consortium
</DIV>
</BODY>
</HTML>