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

replaced ARM with latest edition

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-05-19 17:28:31 +00:00
parent 93d2839b39
commit 77071cec20
12 changed files with 3789 additions and 3466 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/arm/BV9ARM.PDF
View File

Binary file not shown.

242
doc/arm/BV9ARM.1.html → doc/arm/Bv9ARM.1.html
View File

@@ -2,7 +2,7 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 1. Introduction </TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
@@ -34,30 +34,30 @@ The Berkeley Internet Name Domain (BIND) implements an Internet nameserver for a
</A>
1.2 Organization of This Document</H3>
</OL>
<P CLASS="2LevelContinued1">
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
In this document, <EM CLASS="Emphasis">
In this document, <EM CLASS="EquationVariables">
Section 1</EM>
introduces the basic DNS and BIND concepts. <EM CLASS="Emphasis">
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="Emphasis">
describes resource requirements for running BIND in various environments. Information in <EM CLASS="EquationVariables">
Section 3</EM>
is <EM CLASS="Emphasis">
is <EM CLASS="EquationVariables">
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="Emphasis">
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="Emphasis">
, 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="Emphasis">
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="Emphasis">
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="Emphasis">
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="Emphasis">
which contain useful reference information, such as a <EM CLASS="EquationVariables">
Glossary</EM>
and a <EM CLASS="Emphasis">
and a <EM CLASS="EquationVariables">
Bibliography</EM>
, as well as historic information related to BIND and the Domain Name System.</P>
</DIV>
@@ -71,20 +71,24 @@ Bibliography</EM>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997382">
</A>
In this document, the following general typographic conventions are used:</P>
In this document, we use the following general typographic conventions:</P>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<P CLASS="CellBody3">
<A NAME="pgfId=997359">
</A>
When describing:</P>
<EM CLASS="EquationVariables">
To describe:</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<P CLASS="CellBody3">
<A NAME="pgfId=997361">
</A>
Style Used:</P>
<EM CLASS="EquationVariables">
Style:</EM>
</P>
</TD>
</TR>
<TR>
@@ -92,30 +96,14 @@ Style Used:</P>
<P CLASS="CellBody">
<A NAME="pgfId=997363">
</A>
A pathname, filename, URL, hostname, or mailing list name</P>
a pathname, filename, URL, hostname, mailing list name, or new term or concept</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody1">
<P CLASS="CellBody5">
<A NAME="pgfId=997365">
</A>
<EM CLASS="Emphasis">
Times Italic</EM>
</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<A NAME="pgfId=997367">
</A>
A new term or concept</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody1">
<A NAME="pgfId=997369">
</A>
<EM CLASS="Emphasis">
Times Italic</EM>
<EM CLASS="EquationVariables">
Italic</EM>
</P>
</TD>
</TR>
@@ -124,13 +112,14 @@ Times Italic</EM>
<P CLASS="CellBody">
<A NAME="pgfId=997371">
</A>
Literal user input</P>
literal user input</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody2">
<P CLASS="CellBody4">
<A NAME="pgfId=997373">
</A>
Courier Bold
<KBD CLASS="Literal-user-input">
Fixed Width Bold</KBD>
</P>
</TD>
</TR>
@@ -139,14 +128,14 @@ Courier Bold
<P CLASS="CellBody">
<A NAME="pgfId=997375">
</A>
Variable user input</P>
variable user input</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody3">
<A NAME="pgfId=997377">
<P CLASS="CellBody5">
<A NAME="pgfId=1034911">
</A>
<EM CLASS="Emphasis">
Courier Italic</EM>
<EM CLASS="Optional-meta-syntax">
Fixed Width Italic</EM>
</P>
</TD>
</TR>
@@ -155,14 +144,14 @@ Courier Italic</EM>
<P CLASS="CellBody">
<A NAME="pgfId=997379">
</A>
Program output</P>
program output</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody4">
<A NAME="pgfId=997381">
</A>
<KBD CLASS="Literal-user-input">
Courier Plain</KBD>
<CODE CLASS="Program-Process">
Fixed Width</CODE>
</P>
</TD>
</TR>
@@ -174,16 +163,20 @@ The following conventions are used in descriptions of the BIND configuration fil
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<P CLASS="CellBody3">
<A NAME="pgfId=997385">
</A>
When describing:</P>
<EM CLASS="EquationVariables">
When describing:</EM>
</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody">
<P CLASS="CellBody3">
<A NAME="pgfId=997387">
</A>
Style Used:</P>
<EM CLASS="EquationVariables">
Style Used:</EM>
</P>
</TD>
</TR>
<TR>
@@ -194,11 +187,11 @@ Style Used:</P>
keywords</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody5">
<P CLASS="CellBody6">
<A NAME="pgfId=997391">
</A>
<KBD CLASS="Literal-user-input">
Arial Bold</KBD>
<EM CLASS="production_target">
Sans Serif Bold</EM>
</P>
</TD>
</TR>
@@ -210,12 +203,12 @@ Arial Bold</KBD>
variables</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody6">
<H6 CLASS="CellBody7">
<A NAME="pgfId=997395">
</A>
<EM CLASS="Emphasis">
Arial Italic</EM>
</P>
<EM CLASS="variable">
Sans Serif Italic</EM>
</H6>
</TD>
</TR>
<TR>
@@ -226,11 +219,11 @@ Arial Italic</EM>
&quot;meta-syntactic&quot; information (within brackets when optional)</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody3">
<P CLASS="CellBody5">
<A NAME="pgfId=997399">
</A>
<EM CLASS="Emphasis">
Courier Italic</EM>
<EM CLASS="Optional-meta-syntax">
Fixed Width Italic</EM>
</P>
</TD>
</TR>
@@ -242,11 +235,11 @@ Courier Italic</EM>
Command line input</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody2">
<P CLASS="CellBody4">
<A NAME="pgfId=997403">
</A>
<KBD CLASS="Literal-user-input">
Courier Bold</KBD>
Fixed Width Bold</KBD>
</P>
</TD>
</TR>
@@ -261,8 +254,8 @@ Program output</P>
<P CLASS="CellBody4">
<A NAME="pgfId=997407">
</A>
<KBD CLASS="Literal-user-input">
Courier Plain</KBD>
<CODE CLASS="Program-Process">
Fixed Width</CODE>
</P>
</TD>
</TR>
@@ -277,7 +270,7 @@ Optional input</P>
<P CLASS="CellBody">
<A NAME="pgfId=997411">
</A>
Text is enclosed in square brackets </P>
Text is enclosed in square brackets</P>
</TD>
</TR>
</TABLE>
@@ -292,15 +285,15 @@ Text is enclosed in square brackets </P>
<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="Emphasis">
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">
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">
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="Emphasis">
. The <EM CLASS="EquationVariables">
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>
@@ -313,49 +306,49 @@ resolver</EM>
<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="Emphasis">
A nameserver (NS) is a program that stores information about named resources and responds to queries from programs called <EM CLASS="EquationVariables">
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="Emphasis">
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">
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="Emphasis">
, 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">
Example, Inc.</EM>
would be:</P>
<P CLASS="3LevelContinued1">
<A NAME="pgfId=997418">
</A>
<EM CLASS="Emphasis">
<EM CLASS="EquationVariables">
ourhost.example.com</EM>
</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997419">
</A>
The top level domain for corporate organizations is <EM CLASS="Emphasis">
The top level domain for corporate organizations is <EM CLASS="EquationVariables">
com</EM>
; <EM CLASS="Emphasis">
; <EM CLASS="EquationVariables">
example</EM>
is a subdomain of <EM CLASS="Emphasis">
is a subdomain of <EM CLASS="EquationVariables">
.com</EM>
; and <EM CLASS="Emphasis">
; and <EM CLASS="EquationVariables">
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>
<EM CLASS="Emphasis">
<EM CLASS="pathname">
/usr/src/etc/named/doc</EM>
in 4.4BSD or are available via <CODE CLASS="Program-Process">
FTP</CODE>
from<BR>
<EM CLASS="Emphasis">
<EM CLASS="URL">
ftp://www.isi.edu/in-notes/</EM>
or via the Web at <EM CLASS="Emphasis">
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">
. (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">
named</CODE>
@@ -377,31 +370,31 @@ 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="Emphasis">
To properly operate a nameserver, it is important to understand the difference between a <EM CLASS="EquationVariables">
zone</EM>
and a <EM CLASS="Emphasis">
and a <EM CLASS="EquationVariables">
domain</EM>
.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997424">
</A>
As an example, consider the <EM CLASS="Emphasis">
As an example, consider the <EM CLASS="EquationVariables">
example.com</EM>
domain, which includes names such as <EM CLASS="Emphasis">
domain, which includes names such as <EM CLASS="EquationVariables">
host.aaa.example.com </EM>
and <EM CLASS="Emphasis">
and <EM CLASS="EquationVariables">
host.bbb.example.com</EM>
even though the <EM CLASS="Emphasis">
even though the <EM CLASS="EquationVariables">
example.com</EM>
zone includes only delegations for the <EM CLASS="Emphasis">
zone includes only delegations for the <EM CLASS="EquationVariables">
aaa.example.com</EM>
and <EM CLASS="Emphasis">
and <EM CLASS="EquationVariables">
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="Emphasis">
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">
domain</EM>
, even if it is <EM CLASS="Emphasis">
, even if it is <EM CLASS="EquationVariables">
terminal</EM>
, that is, has no <EM CLASS="Emphasis">
, that is, has no <EM CLASS="EquationVariables">
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>
<P CLASS="3LevelContinued">
@@ -409,25 +402,25 @@ subdomains</EM>
</A>
Though BIND is a Domain Nameserver, it deals primarily in terms of zones. The primary and secondary declarations in the <CODE CLASS="Program-Process">
named.conf</CODE>
file specify zones, not domains. When you ask some other site if it is willing to be a secondary server for your <EM CLASS="Emphasis">
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">
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="Emphasis">
Each zone will have one <EM CLASS="EquationVariables">
primary master</EM>
(also called <EM CLASS="Emphasis">
(also called <EM CLASS="EquationVariables">
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="Emphasis">
) 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="Emphasis">
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">
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="Emphasis">
name which indicates the <EM CLASS="EquationVariables">
top level</EM>
or <EM CLASS="Emphasis">
or <EM CLASS="EquationVariables">
root</EM>
of the current zone. You can list servers in the zone's top-level <CODE CLASS="Program-Process">
@</CODE>
@@ -445,7 +438,7 @@ 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>
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>
@@ -457,11 +450,11 @@ Adding a zone as a type master or type slave will tell the server to answer ques
<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="Emphasis">
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">
cache</EM>
. Master servers are often also called <EM CLASS="Emphasis">
. Master servers are often also called <EM CLASS="EquationVariables">
primaries</EM>
and slave servers are often also called <EM CLASS="Emphasis">
and slave servers are often also called <EM CLASS="EquationVariables">
secondaries</EM>
. Both master/primary and slave/secondary servers are authoritative for a zone.</P>
<P CLASS="3LevelContinued">
@@ -478,9 +471,9 @@ All servers keep data in their cache until the data expires, based on a TTL (Tim
<P CLASS="4LevelContinued">
<A NAME="pgfId=997435">
</A>
The <EM CLASS="Emphasis">
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>
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>
</DIV>
<DIV>
<OL>
@@ -492,9 +485,9 @@ primary master</EM>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997437">
</A>
A <EM CLASS="Emphasis">
A <EM CLASS="EquationVariables">
slave server</EM>
, also called a <EM CLASS="Emphasis">
, also called a <EM CLASS="EquationVariables">
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>
</DIV>
@@ -508,7 +501,7 @@ secondary server</EM>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997439">
</A>
Some servers are <EM CLASS="Emphasis">
Some servers are <EM CLASS="EquationVariables">
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>
@@ -522,11 +515,11 @@ caching only servers</EM>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997441">
</A>
Instead of interacting with the nameservers for the root and other domains, a <EM CLASS="Emphasis">
Instead of interacting with the nameservers for the root and other domains, a <EM CLASS="EquationVariables">
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="Emphasis">
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>
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>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997442">
</A>
@@ -539,30 +532,13 @@ There is no prohibition against declaring a server to be a forwarder even though
</A>
1.4.3.5 Stealth Server</H5>
</OL>
<!--
[[P CLASS="comment"]]
[[A NAME="pgfId=997445"]]
[[/A]]
A [[A NAME="marker=997444"]]
[[/A]]
stealth server is a primary master server that is neither listed in any root zone files nor advertised as being a server. It is set up to hide the true master server for a zone in order to provide some measure of security, or protect the zone from [[A NAME="marker=997446"]]
[[/A]]
Denial of Service ([[A NAME="marker=997447"]]
[[/A]]
DoS) attacks, or reduce the load on the main server, or any number of other reasons. It is also used to provide some measure of network redundancy. Slave servers load zone data from it.[[/P]]
[[P CLASS="4LevelContinued"]]
[[A NAME="pgfId=997347"]]
[[/A]]
-->
<P CLASS="4LevelContinued">
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 centralise 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 often referred to as a 'hidden primary' 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 'official' nameservers for the zone are inaccessable.</P>
<P CLASS="Body">
<A NAME="pgfId=1007863">
<A NAME="pgfId=1014846">
</A>
&nbsp;</P>
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>
</DIV>
</DIV>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A>
</BODY>
</HTML>

59
doc/arm/BV9ARM.2.html → doc/arm/Bv9ARM.2.html
View File

@@ -2,99 +2,90 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 2. BIND Resource Requirements</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
</A>
Section 2. BIND Resource Requirements</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997351">
</A>
</A>
2.1 Hardware requirements</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997352">
</A>
</A>
DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
</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>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997354">
</A>
</A>
2.2 CPU Requirements</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
</A>
CPU requirements for BINDv9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997356">
</A>
</A>
2.3 Memory Requirements </H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997357">
</A>
</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>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997358">
</A>
</A>
2.4 Nameserver Intensive Environment Issues</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
</A>
For nameserver intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal nameservers query a main nameserver, which has enough memory to build a large cache. This approach minimizes the bandwidth used by external name lookups. The second alternative is to set up second-level internal nameservers to make queries independently. In this configuration, none of the individual machines needs to have as much memory or CPU power as in the first alternative, but this has the disadvantage of making many more external queries, as none of the nameservers share their cached data.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997360">
</A>
</A>
2.5 Operating Systems Supported by the Internet Software Consortium</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997361">
</A>
</A>
ISC BINDv9 compiles and runs on the following operating systems:</P>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997362"></A>
IBM AIX 4.3
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997363"></A>
Compaq Digital/Tru64 UNIX 4.0D
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997364"></A>
HP HP-UX 11
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997365"></A>
IRIX64 6.5
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997366"></A>
Red Hat Linux 6.0, 6.1
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997367"></A>
Sun Solaris 2.6, 7, 8 (beta)
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997368"></A>
FreeBSD 3.4-STABLE
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997369"></A>
NetBSD-current with &quot;unproven&quot; pthreads</PRE>
<P CLASS="Body">
<A NAME="pgfId=997347">
</A>
&nbsp;</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997362">
</A>
IBM AIX 4.3<BR>
Compaq Digital/Tru64 UNIX 4.0D<BR>
HP HP-UX 11<BR>
IRIX64 6.5<BR>
Red Hat Linux 6.0, 6.1<BR>
Sun Solaris 2.6, 7, 8 (beta)<BR>
FreeBSD 3.4-STABLE<BR>
NetBSD-current with &quot;unproven&quot; pthreads</P>
</DIV>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A>
</BODY>
</HTML>

359
doc/arm/BV9ARM.3.html → doc/arm/Bv9ARM.3.html
View File

@@ -2,271 +2,259 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<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>
</A>
Sample Configuration and Logging</H3>
</OL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997354"></A>
logging {
channel named_log {
file &quot;logs/named.log&quot;;
print-time yes;
print-category yes;
print-severity yes;
severity info;
<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>;
};
channel security_log {
file &quot;logs/security.log&quot; versions 7 ;
print-time yes;
channel <VAR>security_log</VAR> {
file &quot;<EM>logs/security.log</EM> &quot; <VAR>versions 7</VAR> ;
print-time <VAR>yes</VAR> ;
};
category default { named_log; default_debug; };
category security { security_log };
category <VAR>default</VAR> { named_log; default_debug; };
category security { security_log };
};
// The two corporate subnets. Use real IP numbers here in the real world.
// 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.
// The options statement.
options {
directory &quot;/etc/namedb&quot;; // Directory
pid-file &quot;named.pid&quot;; // Put .pid file in named directory.
named-xfer &quot;/path/to/named-xfer&quot;; // Where is our named-xfer ?
check-names master fail; // Fail on db errors in master zones.
check-names slave warn; // Warn about db errors
// in slave zones.
check-names response warn; // Warn about invalid responses
use-id-pool yes; // Help prevent spoofing
host-statistics yes; // Keep track of hosts/servers
// we've talked to.
listen-on { 192.168.7.20; }; // Listen on this address.
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.
query-source address 192.168.7.20 port 53 ;
// Source queries from port 53
// to get past firewall.
allow-transfer { none; }; // 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 { <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.
};
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-fixed1"><A NAME="pgfId=1007322"></A>
include &quot;keys.conf&quot;; // Include a keys.conf with
// TSIG/DNSSEC keys.
// Shouldn't be readable to anyone
// except BIND user.
zone &quot;.&quot;{ type hint; file &quot;local/named.root&quot;; };
// root hints
</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997391"></A>
zone &quot;0.0.127.IN-ADDR.ARPA&quot; {</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997392"></A>
type master; file &quot;local/localhost.db&quot;; notify no;
// localhost
};</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997395"></A>
&nbsp;</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997396"></A>
zone &quot;example.com&quot; { // Example zone for &quot;example.com&quot;.
type master; // It's a master zone.
file &quot;m/example.com.db&quot;; // The file is here.
allow-query { any; }; // Allow anyone to query.
allow-transfer { corpnet; }; // Only allow corp nets to transfer zone.
};</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997402"></A>
&nbsp;</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997403"></A>
zone &quot;offsite.example.com&quot; { // Example zone for an off-site corp zone.
type slave; // It's a slave zone.
masters { 192.168.4.12; }; // The master is at this address.
file &quot;s/offsite.example.com.db&quot;; // The file is here.
notify no; // Don't worry about <CODE CLASS="Program-Process">NOTIFY</CODE>
ing.
allow-query { any; }; // Allow anyone to query.
;</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>
</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>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997454"> </A>
&nbsp;</PRE>
<TABLE>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997415">
</A>
</A>
Name</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997417">
</A>
</A>
TTL</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997419">
</A>
</A>
CLASS</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997421">
</A>
</A>
TYPE</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997423">
</A>
</A>
Resource Record (RR) Data</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997425">
</A>
<CODE CLASS="Program-Process">
www</CODE>
</P>
</A>
www</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997427">
</A>
</A>
10m</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997429">
</A>
<CODE CLASS="Program-Process">
IN</CODE>
</P>
</A>
IN</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997431">
</A>
</A>
A</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997433">
</A>
</A>
10.0.0.1</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<P CLASS="CellBody">
<A NAME="pgfId=997435">
</A>
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997437">
</A>
</A>
10m</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997439">
</A>
<CODE CLASS="Program-Process">
IN</CODE>
</P>
</A>
IN</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997441">
</A>
</A>
A</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997443">
</A>
</A>
10.0.0.2</P>
</TD>
</TR>
<TR>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG">
<P CLASS="CellBody">
<A NAME="pgfId=997445">
</A>
</A>
&nbsp;</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997447">
</A>
</A>
10m</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997449">
</A>
<CODE CLASS="Program-Process">
IN</CODE>
</P>
</A>
IN</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997451">
</A>
</A>
A</P>
</TD>
<TD ROWSPAN="1" COLSPAN="1">
<P CLASS="CellBody-fixedfontLG1">
<P CLASS="CellBody">
<A NAME="pgfId=997453">
</A>
</A>
10.0.0.3</P>
</TD>
</TR>
</TABLE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997455">
</A>
</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>
For more detail on ordering responses, check the <CODE CLASS="Program-Process">
rrset-order</CODE>
substatement in the <CODE CLASS="Program-Process">
options</CODE>
statement in <A HREF="BV9ARM.5.html#22766" CLASS="XRef">
statement in <A HREF="Bv9ARM.5.html#22766" CLASS="XRef">
RRset Ordering</A>
.</P>
</DIV>
@@ -274,54 +262,56 @@ RRset Ordering</A>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997460">
</A>
</A>
3.3 Notify</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997461">
</A>
</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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997462">
</A>
<A NAME="pgfId=1016466">
</A>
DNS Notify is fully documented in RFC 1996. See also the description of the zone option <CODE CLASS="Program-Process">
also-notify</CODE>
in section 3.1.3.7, &quot;Zone transfers.&quot;</P>
on <A HREF="Bv9ARM.5.html#32057" CLASS="XRef">
Zone Transfers</A>
.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997463">
</A>
<A NAME="pgfId=1016467">
</A>
3.4 Nameserver Operations</H3>
</OL>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997464">
</A>
</A>
3.4.1 Tools for Use With the Nameserver Daemon</H4>
</OL>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997465">
</A>
</A>
There are several indispensable diagnostic, administrative and monitoring tools available to the system administrator for controlling and debugging the nameserver daemon. We describe several in this section </P>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997466">
</A>
</A>
3.4.1.1 Diagnostic Tools</H5>
</OL>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997467">
</A>
</A>
dig</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997468">
</A>
</A>
The domain information groper (<CODE CLASS="Program-Process">
dig</CODE>
) is a command line tool that can be used to gather information from the Domain Name System servers. Dig has two modes: simple interactive mode for a single query, and batch mode which executes a query for each in a list of several query lines. All query options are accessible from the command line.</P>
@@ -329,30 +319,30 @@ dig</CODE>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997469">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997470"></A>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997470"> </A>
dig [@server] domain [&lt;query-type&gt;] [&lt;query-class&gt;]
[+&lt;query-option&gt;] [-&lt;dig-option&gt;] [%comment]</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997471">
</A>
</A>
The usual simple use of dig will take the form</P>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997472"></A>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997472"> </A>
dig @server domain query-type query-class</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997473">
</A>
</A>
For more information and a list of available commands and options, see the dig man page.</P>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997474">
</A>
</A>
host</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997475">
</A>
</A>
The<EM CLASS="pathname">
</EM>
<CODE CLASS="Program-Process">
@@ -364,113 +354,114 @@ utility provides a simple DNS lookup using a command-line interface for looking
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997476">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997477"></A>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997477"> </A>
host [-l] [-v] [-w] [-r] [-d] [-t querytype] [-a] host [server]</PRE>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997478">
</A>
</A>
nslookup</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997479">
</A>
</A>
<CODE CLASS="Program-Process">
nslookup</CODE>
is a program used to query Internet domain nameservers. nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query nameservers for information about various hosts and domains or to print a list of hosts in a domain. Non-interactive mode is used to print just the name and requested information for a host or domain.</P>
is a program used to query Internet domain nameservers. <CODE CLASS="Program-Process">
nslookup</CODE>
has two modes: interactive and non-interactive. Interactive mode allows the user to query nameservers for information about various hosts and domains or to print a list of hosts in a domain. Non-interactive mode is used to print just the name and requested information for a host or domain.</P>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997480">
</A>
</A>
Usage</H5>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997481"></A>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997481"> </A>
nslookup [-option ...] [host-to-find | -[server]]</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997482">
</A>
</A>
Interactive mode is entered when no arguments are given (the default nameserver will be used) or when the first argument is a hyphen (-) and the second argument is the host name or Internet address of a nameserver.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997483">
</A>
</A>
Non-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument. The optional second argument specifies the host name or address of a nameserver.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997484">
</A>
The options listed under the &quot;set&quot; command (see the nslookup man page for details) can be specified in the .nslookuprc file in the user's home directory if they are listed one per line. Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial time-out to 10 seconds, type:</P>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997485"></A>
</A>
The options listed under the &quot;set&quot; command (see the <CODE CLASS="Program-Process">
nslookup</CODE>
man page for details) can be specified in the <EM CLASS="pathname">
.nslookuprc</EM>
file in the user's home directory if they are listed one per line. Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial time-out to 10 seconds, type:</P>
<PRE CLASS="4Level-fixed1"><A NAME="pgfId=997485"> </A>
nslookup -query=hinfo -timeout=10</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997486">
</A>
For more information and a list of available commands and options, see the nslookup man page.</P>
</A>
For more information and a list of available commands and options, see the <CODE CLASS="Program-Process">
nslookup</CODE>
man page.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997487">
</A>
</A>
3.4.1.2 Administrative Tools</H5>
</OL>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997488">
</A>
</A>
Administrative tools play an integral part in the management of a server.</P>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997489">
</A>
</A>
rndc</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997490">
</A>
</A>
The remote name daemon control (<CODE CLASS="Program-Process">
rndc</CODE>
) program is a program that allows the system administrator to control the operation of a nameserver. If you run rndc without any options it will display a usage message.</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1012780">
</A>
</A>
Usage:</P>
<P CLASS="4LevelContinued">
<A NAME="pgfId=1012777">
</A>
<CODE CLASS="Program-Process">
rndc [-p port] [-m] server command [command ...]</CODE>
</P>
<PRE CLASS="4Level-fixed"><A NAME="pgfId=1012777"> </A>
<CODE CLASS="Program-Process">rndc [-p port] [-m] server command [command ...]</CODE>
</PRE>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997493">
</A>
</A>
For more information and a list of available commands and options, see the rndc man page.</P>
</DIV>
<DIV>
<OL>
<H5 CLASS="4Level">
<A NAME="pgfId=997494">
</A>
</A>
3.4.1.3 Monitoring Tools</H5>
</OL>
</DIV>
<DIV>
<H5 CLASS="Subhead4">
<A NAME="pgfId=997495">
</A>
</A>
MRTG</H5>
<P CLASS="4LevelContinued">
<A NAME="pgfId=997496">
</A>
</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>
<P CLASS="Body">
<A NAME="pgfId=997347">
</A>
&nbsp;</P>
</DIV>
</DIV>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A>
</BODY>
</HTML>

1410
doc/arm/BV9ARM.4.html → doc/arm/Bv9ARM.4.html
View File

File diff suppressed because it is too large Load Diff

3619
doc/arm/BV9ARM.5.html → doc/arm/Bv9ARM.5.html
View File

File diff suppressed because it is too large Load Diff

110
doc/arm/BV9ARM.6.html → doc/arm/Bv9ARM.6.html
View File

@@ -2,27 +2,27 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<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>
</A>
Section 6. Security Considerations</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997352">
</A>
</A>
6.1 <A NAME="32222">
</A>
</A>
Access Control Lists</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997353">
</A>
</A>
Access Control Lists (ACLs), are address match lists that you can set up and nickname for future use in <CODE CLASS="Program-Process">
allow-query</CODE>
, <CODE CLASS="Program-Process">
@@ -34,58 +34,63 @@ allow-transfer</CODE>
, etc.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997354">
</A>
</A>
Using ACLs allows you to have finer control over who can access your nameserver, without cluttering up your config files with huge lists of IP addresses.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
</A>
It is a <EM CLASS="Emphasis">
good idea</EM>
to use ACLs, and to control access to your server. Limiting access to your server by outside parties can help prevent spoofing and DoS attacks against your server.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997356">
</A>
</A>
Here is an example of how to properly apply ACLs:</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997357">
</A>
</A>
// Set up an ACL named &quot;bogusnets&quot; that will block RFC1918 space,<BR>
// which is commonly used in spoofing attacks.</P>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997358"></A>
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; };</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
// Set up an ACL called our-nets. Replace this with the real IP numbers.</P>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997360"></A>
acl our-nets { x.x.x.x/24; x.x.x.x/21; }; </PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997361"></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 {
...
...
allow-query { our-nets; };
allow-recursion { our-nets; };
allow-query { <VAR>our-nets</VAR>; };
allow-recursion { <VAR>our-nets</VAR>; };
...
blackhole { bogusnets; };
...
};</PRE>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997362"></A>
zone &quot;example.com&quot; {
type master;
file &quot;m/example.com&quot;;
allow-query { any; };
};</PRE>
};
zone &quot;<EM>example.com</EM>&quot; {
type <VAR>master</VAR>;
file &quot;<EM>m/example.com</EM>&quot;;
allow-query { <VAR>any</VAR>; };
};</CODE>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997363">
</A>
</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>
</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="Emphasis">
<EM CLASS="URL">
ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</EM>
</P>
</DIV>
@@ -93,7 +98,7 @@ ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</EM>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997365">
</A>
</A>
6.2 <CODE CLASS="Program-Process">
chroot</CODE>
and <CODE CLASS="Program-Process">
@@ -102,7 +107,7 @@ setuid</CODE>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997366">
</A>
</A>
On UNIX servers, it is possible to run BIND in a <EM CLASS="Emphasis">
chrooted</EM>
environment (<CODE CLASS="Program-Process">
@@ -112,15 +117,17 @@ chroot()</CODE>
&quot; option. This can help improve system security by placing BIND in a &quot;sandbox,&quot; which will limit the damage done if a server is compromised.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997367">
</A>
</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;user&gt; ). We suggest running as a nonprivileged user when using the <CODE CLASS="Program-Process">
&lt;<EM CLASS="variable">
user</EM>
&gt; ). We suggest running as a nonprivileged user when using the <CODE CLASS="Program-Process">
chroot</CODE>
feature.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997368">
</A>
</A>
Here is an example command line to load BIND in a <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox, <BR>
@@ -131,35 +138,36 @@ named</CODE>
<CODE CLASS="Program-Process">
setuid</CODE>
to user 202:</P>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997369"></A>
/usr/local/bin/named -u 202 -t /var/named</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997369"></A>
<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>
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 (e.g., <EM CLASS="pathname">
/var/named</EM>
), you will need to set up an environment that includes everything BIND needs to run. From BIND's point of view, <EM CLASS="pathname">
/var/named</EM>
is the root of the filesystem. You will need <EM CLASS="pathname">
/dev/null</EM>
, and any library directories and files that BIND needs to run on your system. Please consult your operating system's instructions if you need help figuring out which library files you need to copy over to the <CODE CLASS="Program-Process">
, and any library directories and files that BIND needs to run on your system. Please consult your operating system's instructions if you need help figuring out which library files you need to copy over to the <CODE CLASS="Program-Process">
chroot()</CODE>
sandbox.</P>
<P CLASS="3LevelContinued">
<A NAME="pgfId=997372">
</A>
If you are running an operating system that supports static binaries, you can also compile BIND staticly and avoid the need to copy system libraries over to your <CODE CLASS="Program-Process">
</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>
@@ -167,14 +175,14 @@ chroot()</CODE>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997373">
</A>
6.2.2 Using <CODE CLASS="Program-Process">
</A>
6.2.2 Using the <CODE CLASS="Program-Process">
setuid</CODE>
</H4>
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">
@@ -188,18 +196,18 @@ chown</CODE>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997375">
</A>
6.3 Dynamic updates</H3>
</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>
</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>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A>
</BODY>
</HTML>

190
doc/arm/BV9ARM.7.html → doc/arm/Bv9ARM.7.html
View File

@@ -2,177 +2,225 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Section 7. Troubleshooting</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
</A>
Section 7. Troubleshooting</H1>
</OL>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997351">
</A>
</A>
7.1 Common Log Messages and What They Mean</H3>
</OL>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997352">
</A>
</A>
lame server</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997353"></A>
ns named[111]: Lame server on 'www.foo.com' (in 'foo.com'?): [192.168.0.2].53 'ns2.foo.com'</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997354">
</A>
This is a harmless error message. It means that the server at 192.168.0.2 (ns2.foo.com) is listed as a nameserver for &quot;foo.com&quot;, but it doesn't really know anything about foo.com.</P>
</A>
This is a harmless error message. It means that the server at 192.168.0.2 (<EM CLASS="pathname">
ns2.foo.com</EM>
) is listed as a nameserver for &quot;<EM CLASS="pathname">
foo.com</EM>
&quot;, but it doesn't really know anything about <EM CLASS="pathname">
foo.com</EM>
.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997355">
</A>
</A>
If this is a zone under your control, check each of the nameservers to ensure that they are configured to answer questions properly.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997356">
</A>
</A>
If it's a zone out on the Internet, it would be nice to notify the owners of the domain in question so that they can take a look at it. In practice, though, not many people have time to do this.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997357">
</A>
</A>
bad referral</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997358"></A>
ns named[111]: bad referral (other.com !&lt; subdomain.other.com)</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997359">
</A>
This indicates that your nameserver (ns.foo.com) queried the nameserver for foo2.com to find out how to get to subdomain.foo2.com. foo2.com told your nameserver that subdomain.foo2.com was delegated to some other.foo2.com, so your nameserver queried that.</P>
</A>
This indicates that your nameserver (<EM CLASS="pathname">
ns.foo.com</EM>
) queried the nameserver for <EM CLASS="pathname">
foo2.com</EM>
to find out how to get to <EM CLASS="pathname">
subdomain.foo2.com</EM>
. <EM CLASS="pathname">
foo2.com</EM>
told your nameserver that <EM CLASS="pathname">
subdomain.foo2.com</EM>
was delegated to some <EM CLASS="pathname">
other.foo2.com</EM>
, so your nameserver queried that.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997360">
</A>
someother.foo2.com didn't think that subdomain.foo2.com had been delegated to it, so it referred your server (ns.foo.com) back to the foo2.com nameserver.</P>
</A>
<EM CLASS="pathname">
someother.foo2.com</EM>
didn't think that <EM CLASS="pathname">
subdomain.foo2.com</EM>
had been delegated to it, so it referred your server (<EM CLASS="pathname">
ns.foo.com</EM>
) back to the <EM CLASS="pathname">
foo2.com</EM>
nameserver.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997361">
</A>
</A>
not authoritative for</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997362"></A>
ns named-xfer[111]: [192.168.0.1] not authoritative for foo.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997363">
</A>
</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>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997364">
</A>
</A>
rejected zone</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997365"></A>
ns named[111]: master zone &quot;foo.com&quot; (IN) rejected due to errors (serial111)</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997366">
</A>
This indicates that the foo.com zone was rejected because of an error in the zone file. Check the lines above this error -- named will usually tell you what it didn't like and where to find it in the zone file.</P>
</A>
This indicates that the <EM CLASS="pathname">
foo.com</EM>
zone was rejected because of an error in the zone file. Check the lines above this error. <CODE CLASS="Program-Process">
named</CODE>
will usually tell you what it didn't like and where to find it in the zone file.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997367">
</A>
</A>
no NS RRs found</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997368"></A>
ns named[111]: Zone &quot;foo.com&quot; (file foo.com.db): no NS RRs found at zonetop</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997369">
</A>
The foo.com.db 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>
</A>
The <EM CLASS="pathname">
foo.com.db</EM>
file is missing NS records at the top of the zone (in the SOA section). Check to make sure they exist and that there is white space (spaces or tabs) in front of them. White spaces matter here.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997370">
</A>
</A>
no default TTL set</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997371"></A>
ns named[111]: Zone &quot;foo.com&quot; (file foo.com.db): No default TTL set using SOA minimum instead</PRE>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997372">
</A>
You need to add a $TTL to the top of the foo.com.db zone file. See RFC2308, or section 3.2.3, &quot;Setting TTLs&quot; in this document, for information on how to use $TTL.</P>
</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">
Setting TTLs</A>
in this document, for information on how to use $TTL.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997373">
</A>
</A>
no root nameserver for class</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997374"></A>
findns: No root nameservers for class IN?</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997374"> </A>
<EM CLASS="grammar_literal">findns: No root nameservers for class IN?</EM>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997375">
</A>
</A>
Your nameserver is having problems finding the root nameservers. Check your root hints file to make sure it is not corrupted. Also, make sure that your nameserver can reach the Internet.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997376">
</A>
If you are running an internal root nameserver, make sure it's configured properly and is answering queries.</P>
</A>
If you are running an internal root nameserver, make sure it is configured properly and is answering queries.</P>
</DIV>
<DIV>
<UL>
<H6 CLASS="Subhead2">
<A NAME="pgfId=997377">
</A>
</A>
address already in use</H6>
</UL>
<PRE CLASS="2Level-fixed1"><A NAME="pgfId=997378"></A>
ctl_server: bind: Address already in use</PRE>
<PRE CLASS="2Level-fixed"><A NAME="pgfId=997378"> </A>
<EM CLASS="grammar_literal">ctl_server: bind: Address already in use</EM>
</PRE>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997379">
</A>
</A>
This usually indicates that another copy of BIND is already running. Verify that you have killed old copies of the daemon.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997380">
</A>
</A>
This can also pop up if you originally ran named as &quot;root&quot; and now run it as a regular user. named may have left behind an ndc control socket that is owned by root if it crashed, or was not killed gracefully.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997381">
</A>
This means that the regular user wouldn't be able to delete it, so it would think named is still running. The solution is to remove any ndc sockets in /usr/local/etc, or /var/run, etc.</P>
</A>
This means that the regular user wouldn't be able to delete it, so it would think named is still running. The solution is to remove any ndc sockets in <EM CLASS="pathname">
/usr/local/etc</EM>
, or <EM CLASS="pathname">
/var/run</EM>
, etc.</P>
</DIV>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997382">
</A>
</A>
7.2 Common Problems</H3>
</OL>
<DIV>
<OL>
<H4 CLASS="3Level">
<A NAME="pgfId=997383">
</A>
</A>
7.2.1 It's not working; how can I figure out what's wrong?</H4>
</OL>
<P CLASS="3LevelContinued">
<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="BvARM.3.html#30164" CLASS="XRef">
</A>
The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand (see the sample configurations in <A HREF="Bv9ARM.3.html#30164" CLASS="XRef">
Sample Configuration and Logging</A>
). The log files provide a source of hints and information that can be used to figure out what went wrong and how to fix the problem.</P>
</DIV>
@@ -181,49 +229,49 @@ Sample Configuration and Logging</A>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997388">
</A>
</A>
7.3 Incrementing and Changing the Serial Number</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1001230">
</A>
</A>
Zone serial numbers are just numbers--they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. A number of people have been testing these numbers for Y2K compliance and have set the number to the year 2000 to see if it will work. They then try to restore the old serial number. This will cause problems, because serial numbers are used to indicate that a zone has been updated. If the serial number on the secondary server is lower than the serial number on the primary, the secondary server will attempt to update its copy of the zone.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997390">
</A>
</A>
Setting the serial number to a lower number on the primary server than the secondary server means that the secondary will not perform updates to its copy of the zone.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997391">
</A>
</A>
The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all secondaries have updated to the new zone serial number, then reset the number to what you want it to be, and reload the zone again.</P>
</DIV>
<DIV>
<OL>
<H3 CLASS="2Level">
<A NAME="pgfId=997392">
</A>
</A>
7.4 Where Can I Get Help?</H3>
</OL>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997393">
</A>
<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>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997394">
</A>
To discuss arrangements for support, contact
<a href="mailto: info@isc.org">info@isc.org</A></CODE>
or visit the ISC web page at
<a href="http://www.isc.org/services/support/">the ISC web site</A></EM>
</A>
To discuss arrangements for support, contact <EM CLASS="pathname">
info@isc.org</EM>
<CODE CLASS="Program-Process">
</CODE>
or visit the ISC web page at<BR>
<EM CLASS="URL">
http://www.isc.org/services/support/</EM>
to read more.</P>
<P CLASS="Body">
<A NAME="pgfId=997347">
</A>
&nbsp;</P>
<DIV>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A>
</DIV>
</DIV>
</DIV>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
</BODY>
</HTML>

343
doc/arm/BV9ARM.8.html → doc/arm/Bv9ARM.8.html
View File

@@ -2,121 +2,135 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE> Appendices</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<OL>
<H1 CLASS="1Level">
<A NAME="pgfId=997350">
</A>
Appendices</H1>
</OL>
<DIV>
<H3 CLASS="AppendixLevel1">
<H6 CLASS="Title">
<A NAME="pgfId=997347">
</A>
Appendices</H6>
<DIV>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=999043">
</A>
Appendix A. Acknowledgements</H3>
</A>
Appendix A. Acknowledgements</H6>
<DIV>
<H4 CLASS="AppendixLevel2">
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1000953">
</A>
A Brief History of the DNS and BIND</H4>
</A>
A Brief History of the DNS and BIND</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000944">
</A>
</A>
Although the &quot;official&quot; beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and 883. From 1984 to 1987, the ARPAnet (the precursor to today's Internet) became a testbed of experimentation for developing the new naming/addressing scheme in an rapidly expanding, operational network environment. New RFCs were written and published in 1987 that modified the original documents to incorporate improvements based on the working model. RFC 1034, &quot;Domain Names-Concepts and Facilities,&quot; and RFC 1035, &quot;Domain Names-Implementation and Specification&quot; were published and became the standards upon which all DNS implementations are built.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000945">
</A>
</A>
The first working domain name server, called &quot;Jeeves,&quot; was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 machines located at the University of Southern California's Information Sciences Institute (USC-ISI) and SRI International's Network Information Center (SRI-NIC). A DNS server for Unix machines, the Berkeley Internet Name Domain (BIND) package, was written soon after by a group of graduate students at the University of California at Berkeley under a grant from the US Defense Advanced Research Projects Administration (DARPA). Versions of BIND through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark Painter, David Riggle and Songnian Zhou made up the initial BIND project team. After that, additional work on the software package was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation employee on loan to the CSRG, worked on BIND for 2 years, from 1985 to 1987. Many other people also contributed to BIND development during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently handled by Mike Karels and O. Kure.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000946">
</A>
</A>
BIND versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then a DEC employee, became BIND's primary caretaker. Paul was assisted by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000947">
</A>
</A>
BIND Version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became BIND's principal architect/programmer.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000948">
</A>
</A>
BIND versions from 4.9.3 onward have been developed and maintained by the Internet Software Consortium with support being provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of BIND version 8 in May 1997.</P>
<P CLASS="2LevelContinued1">
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000986">
</A>
BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.
</P>
</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>
<H3 CLASS="AppendixLevel1">
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=1001064">
</A>
</A>
<A NAME="13688">
</A>
Appendix B. Historical DNS Information</H3>
</A>
Appendix B. Historical DNS Information</H6>
<DIV>
<H4 CLASS="AppendixLevel2">
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1001089">
</A>
Classes of resource records</H4>
</A>
Classes of resource records</H6>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=1001093">
</A>
<A NAME="pgfId=1029256">
</A>
HS = hesiod</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029267">
</A>
The <EM CLASS="Optional-meta-syntax">
hesiod </EM>
class is an information service developed by MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword <CODE CLASS="Program-Process">
hs</CODE>
is a synonym for hesiod.</P>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=1001097">
</A>
<A NAME="pgfId=1029289">
</A>
CH = chaos</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=1029290">
</A>
The <CODE CLASS="Program-Process">
chaos</CODE>
class is used to specify zone data for the MIT-developed CHAOSnet, a LAN protocol created in the mid-1970s.</P>
</DIV>
</DIV>
<p>Return to <A href="BV9ARM.html">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
<DIV>
<H3 CLASS="AppendixLevel1">
<A NAME="pgfId=1000908">
</A>
Appendix C. Bibliography (and Suggested Reading)</H3>
<H6 CLASS="AppendixLevel1">
<A NAME="pgfId=1029291">
</A>
<A NAME="35452">
</A>
Appendix C. Bibliography (and Suggested Reading)</H6>
<DIV>
<H4 CLASS="AppendixLevel2">
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=999193">
</A>
Request for Comments (RFCs)</H4>
</A>
<A NAME="42144">
</A>
C.1 Request for Comments (RFCs)</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=999780">
</A>
</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>
<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">
<a href="http://www.ietf.org/rfc/"> http://www.ietf.org/rfc/</A></EM>
http://www.ietf.org/rfc/</EM>
.</P>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999212">
</A>
</A>
Standards</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999776">
</A>
</A>
RFC974. Partridge, C. <EM CLASS="doc-title">
Mail Routing and the Domain System</EM>
. January 1986. (Standard </P>
<P CLASS="Bib3">
. January 1986.</P>
<P CLASS="Biblio">
<A NAME="pgfId=999777">
</A>
</A>
RFC1034. Mockapetris, P.V. <EM CLASS="doc-title">
Domain Names - Concepts and Facilities</EM>
. P.V. November 1987.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=1000013">
</A>
</A>
RFC1035. Mockapetris, P. V. <EM CLASS="doc-title">
Domain Names - Implementation and Specification</EM>
. November 1987.</P>
@@ -124,35 +138,37 @@ Domain Names - Implementation and Specification</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999218">
</A>
</A>
<A NAME="17631">
</A>
Proposed Standards</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999220">
</A>
</A>
RFC2181. Elz, R., R. Bush. <EM CLASS="doc-title">
Clarifications to the DNS Specification</EM>
. July 1997.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999221">
</A>
</A>
RFC2308. Andrews, M. <EM CLASS="doc-title">
Negative Caching of DNS Queries</EM>
. March 1998.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999222">
</A>
</A>
RFC1995. Ohta, M. <EM CLASS="doc-title">
Incremental Zone Transfer in DNS</EM>
. August 1996.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999223">
</A>
</A>
RFC1996. Vixie, P. <EM CLASS="doc-title">
A Mechanism for Prompt Notification of Zone Changes</EM>
. August 1996.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999747">
</A>
</A>
RFC2136. Vixie, P., S. Thomson, Y. Rekhter, J. Bound. <EM CLASS="doc-title">
Dynamic Updates in the Domain Name System</EM>
. April 1997.</P>
@@ -160,31 +176,29 @@ Dynamic Updates in the Domain Name System</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999227">
</A>
</A>
Proposed Standards Still Under Development</H6>
<P CLASS="3LevelContinued">
<A NAME="pgfId=999436">
</A>
<EM CLASS="doc-title1">
</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>
<P CLASS="Bib3">
the following list of RFCs are undergoing major revision by the IETF. (See the Internet Drafts section, below, for current versions).</P>
<P CLASS="Biblio">
<A NAME="pgfId=999230">
</A>
</A>
RFC1886. Thomson, S., C. Huitema. <EM CLASS="doc-title">
DNS Extensions to support IP version 6</EM>
. S. December 1995.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999231">
</A>
</A>
RFC2065. Eastlake, 3rd, D., C. Kaufman. <EM CLASS="doc-title">
Domain Name System Security Extensions</EM>
. January 1997.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999232">
</A>
</A>
RFC2137. Eastlake, 3rd, D. <EM CLASS="doc-title">
Secure Domain Name System Dynamic Update</EM>
. April 1997.</P>
@@ -192,23 +206,23 @@ Secure Domain Name System Dynamic Update</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999235">
</A>
</A>
Other Important RFCs About DNS Implementation</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999237">
</A>
</A>
RFC1535. Gavron, E. <EM CLASS="doc-title">
A Security Problem and Proposed Correction With Widely Deployed DNS Software.</EM>
October 1993.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=1000173">
</A>
</A>
RFC1536. Kumar, A., J. Postel, C. Neuman, P. Danzig, S. Miller. <EM CLASS="doc-title">
Common DNS Implementation Errors and Suggested Fixes</EM>
. October 1993.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999239">
</A>
</A>
RFC1982. Elz, R., R. Bush. <EM CLASS="doc-title">
Serial Number Arithmetic</EM>
. August 1996.</P>
@@ -216,53 +230,47 @@ Serial Number Arithmetic</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999242">
</A>
</A>
Resource Record Types</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999244">
</A>
</A>
RFC1183. Everhart, C.F., L. A. Mamakos, R. Ullmann, P. Mockapetris. <EM CLASS="doc-title">
New DNS RR Definitions</EM>
. October 1990.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999249">
</A>
</A>
RFC1706. Manning, B., R. Colella. <EM CLASS="doc-title">
DNS NSAP Resource Records</EM>
. October 1994.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999253">
</A>
</A>
RFC2168. Danie1,R., M. Mealling. <EM CLASS="doc-title">
Resolution of Uniform Resource Identifiers using the Domain Name System. June 1997.</EM>
</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999254">
</A>
</A>
RFC1876. Davis, C., P. Vixie, T. Goodwin, I. Dickinson. <EM CLASS="doc-title">
A Means for Expressing Location Information in the Domain Name System</EM>
. January 1996.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999255">
</A>
</A>
RFC2052. Gulbrandsen,A., P. Vixie. <EM CLASS="doc-title">
A DNS RR for Specifying the Location of Services.</EM>
October 1996.</P>
<P CLASS="Bib31">
<A NAME="pgfId=1000261">
</A>
<EM CLASS="CharFmt">
RFC2163. Allocchio, A. U</EM>
<EM CLASS="doc-title">
</A>
RFC2163. Allocchio, A. U<EM CLASS="doc-title">
sing the Internet DNS to Distribute MIXER Conformant Global Address Mapping</EM>
<EM CLASS="CharFmt1">
.</EM>
<EM CLASS="CharFmt">
January 1998.</EM>
</P>
<P CLASS="Bib3">
.January 1998.</P>
<P CLASS="Biblio">
<A NAME="pgfId=1000251">
</A>
</A>
RFC2230. Atkinson, R. <EM CLASS="doc-title">
Key Exchange Delegation Record for the DNS</EM>
. October 1997.</P>
@@ -270,29 +278,29 @@ Key Exchange Delegation Record for the DNS</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999260">
</A>
</A>
DNS and the Internet</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999262">
</A>
</A>
RFC1101. Mockapetris, P. V. <EM CLASS="doc-title">
Dns Encoding of Network Names and Other Types</EM>
. April 1989.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999263">
</A>
</A>
RFC1123. Braden, R. <EM CLASS="doc-title">
Requirements for Internet Hosts - Application and Support</EM>
. October 1989.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999264">
</A>
</A>
RFC1591. Postel, J. D<EM CLASS="doc-title">
omain Name System Structure and Delegation</EM>
. March 1994.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999265">
</A>
</A>
RFC2317. Eidnes, H., G. de Groot, P. Vixie. <EM CLASS="doc-title">
Classless IN-ADDR.ARPA Delegation</EM>
. March 1998.</P>
@@ -300,29 +308,29 @@ Classless IN-ADDR.ARPA Delegation</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999274">
</A>
</A>
DNS Operations</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999276">
</A>
</A>
RFC1537. Beertema, P. <EM CLASS="doc-title">
Common DNS Data File Configuration Errors</EM>
. October 1993.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999277">
</A>
</A>
RFC1912. Barr, D. <EM CLASS="doc-title">
Common DNS Operational and Configuration Errors</EM>
. February 1996.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=1000360">
</A>
</A>
RFC2182. Elz, R. R. Bush, S. Bradner, M. Patton. <EM CLASS="doc-title">
Selection and Operation of Secondary DNS Servers</EM>
. July 1997.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=1000361">
</A>
</A>
RFC2219. Hamilton, M., R. Wright. <EM CLASS="doc-title">
Use of DNS Aliases for Network Services.</EM>
October 1997.</P>
@@ -330,86 +338,90 @@ Use of DNS Aliases for Network Services.</EM>
<DIV>
<H6 CLASS="AppendixLevel3">
<A NAME="pgfId=999282">
</A>
</A>
Other DNS-related RFCs</H6>
<P CLASS="3LevelContinued1">
</DIV>
</DIV>
</DIV>
</DIV>
<DIV>
<H6 CLASS="3LevelContinued1">
<A NAME="pgfId=999409">
</A>
</A>
<EM CLASS="doc-title">
Note:</EM>
the following list of RFCs, although DNS-related, are not concerned with implementing software.</P>
<P CLASS="Bib3">
the following list of RFCs, although DNS-related, are not concerned with implementing software.</H6>
<P CLASS="Biblio">
<A NAME="pgfId=999284">
</A>
</A>
RFC1464. Rosenbaum, R. <EM CLASS="doc-title">
Using the Domain Name System To Store Arbitrary String Attributes</EM>
. May 1993.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999285">
</A>
</A>
RFC1713. Romao, A. <EM CLASS="doc-title">
Tools for DNS Debugging</EM>
. November 1994.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999286">
</A>
</A>
RFC1794. Brisco, T. <EM CLASS="doc-title">
DNS Support for Load Balancing</EM>
. April 1995.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999287">
</A>
</A>
RFC2240. Vaughan, O. <EM CLASS="doc-title">
A Legal Basis for Domain Name Allocation</EM>
. November1997.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999288">
</A>
</A>
RFC2345. Klensin, J., T. Wolf, G. Oglesby. <EM CLASS="doc-title">
Domain Names and Company Name Retrieval</EM>
. May 1998.</P>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999289">
</A>
</A>
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">
<A NAME="pgfId=999292">
</A>
</A>
Obsolete and Unimplemented Experimental RRs</H6>
<P CLASS="Bib3">
<P CLASS="Biblio">
<A NAME="pgfId=999294">
</A>
</A>
RFC1712. Farrell, C., M. Schulze, S. Pleitner, D. Baldoni. <EM CLASS="doc-title">
DNS Encoding of Geographical Location</EM>
. November 1994.</P>
</DIV>
</DIV>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=999195">
</A>
</A>
<A NAME="">
</A>
Internet Drafts</H6>
</A>
C.2 Internet Drafts</H6>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000609">
</A>
</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="2LevelContinued1">
<P CLASS="2LevelContinued">
<A NAME="pgfId=1000433">
</A>
IDs can be obtained via FTP from
<a href="ftp://www.isi.edu/internet-drafts/">ftp://www.isi.edu/internet-drafts/</A>
or from
<a href="http://www.ietf.org/1id-abstracts.html">http://www.ietf.org/1id-abstracts.html</A>.
</P>
<P CLASS="2LevelContinued2">
</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>
</A>
<EM CLASS="doc-title">
draft-duerst-dns-i18n-01.txt<BR>
draft-ietf-dhc-dhcp-dns-10.txt<BR>
@@ -448,17 +460,17 @@ draft-skwan-utf8-dns-02.txt</EM>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=999464">
</A>
Electronic Mail Communication</H6>
</A>
C.3 Electronic Mail Communication</H6>
<P CLASS="Bib2">
<A NAME="pgfId=1001024">
</A>
</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">
<A NAME="pgfId=1001025">
</A>
</A>
Wellington, Brian (bwellington@tislabs.com). <EM CLASS="doc-title">
TSIG guide for BIND 8.2+</EM>
. E-mail to private mailing list (private communication). 22 April 1999.</P>
@@ -466,16 +478,17 @@ TSIG guide for BIND 8.2+</EM>
<DIV>
<H6 CLASS="AppendixLevel2">
<A NAME="pgfId=1000764">
</A>
Other BIND Documents</H6>
</A>
C.4 Other BIND Documents</H6>
<P CLASS="Bib2">
<A NAME="pgfId=999522">
</A>
<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>
<p>Return to <A href="Bv9ARM.HTML">BINDv9 Administrator Reference Manual</A> table of contents.</p>
</DIV>
</DIV>
</BODY>

886
doc/arm/BV9ARM.css → doc/arm/Bv9ARM.css
View File

File diff suppressed because it is too large Load Diff

37
doc/arm/BV9ARM.html → doc/arm/Bv9ARM.html
View File

@@ -2,19 +2,19 @@
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe FrameMaker 5.5/HTML Export Filter">
<LINK REL="STYLESHEET" HREF="BV9ARM.css">
<TITLE> </TITLE></HEAD>
<LINK REL="STYLESHEET" HREF="Bv9ARM.css">
<TITLE>BINDv9 Administrator Reference Manual</TITLE></HEAD>
<BODY BGCOLOR="#ffffff">
<DIV>
<DIV ALIGN="left">
<IMG SRC="isc.color.gif" ALT="ISC logo" WIDTH="144" HEIGHT="90" ALIGN="left" HSPACE=30>
<A HREF="http://www.isc.org/"><IMG SRC="isc.color.gif" ALT="ISC logo" WIDTH="144" HEIGHT="90" ALIGN="left" HSPACE="30" BORDER="0"></A>
</DIV>
<DIV ALIGN="left">
<H2>BIND version 9<BR>Administrator Reference Manual</H2>
<H2>DRAFT
<br>
March 19, 2000</H2>
May, 2000</H2>
</DIV>
<HR ALIGN="center">
@@ -22,39 +22,46 @@ March 19, 2000</H2>
<H4>Warning! This DRAFT document is the property of the Internet Software Consortium (ISC) and contains proprietary ISC information. The information in this document is subject to change.</H4>
</DIV>
<HR ALIGN="center">
<H6 CLASS="Title">
<A NAME="pgfId=21862">
</A>
Table of Contents</H6>
</DIV>
<OL>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.1.html#pgfId=1007883" CLASS="Hypertext">
<A HREF="Bv9ARM.1.html#pgfId=1007883" CLASS="Hypertext">
Section 1. Introduction </A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.2.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.2.html#pgfId=997350" CLASS="Hypertext">
Section 2. BIND Resource Requirements</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.3.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.3.html#pgfId=997350" CLASS="Hypertext">
Section 3. Nameserver Configuration</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.4.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.4.html#pgfId=997350" CLASS="Hypertext">
Section 4. Advanced Concepts</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.5.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.5.html#pgfId=997350" CLASS="Hypertext">
Section 5. BINDv9 Configuration Reference</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.6.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.6.html#pgfId=997350" CLASS="Hypertext">
Section 6. Security Considerations</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.7.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.7.html#pgfId=997350" CLASS="Hypertext">
Section 7. Troubleshooting</A>
</H1>
<H1 CLASS="1LevelTOC">
<A HREF="BV9ARM.8.html#pgfId=997350" CLASS="Hypertext">
<A HREF="Bv9ARM.8.html#pgfId=997350" CLASS="Hypertext">
Appendices</A>
</H1>
</OL>
</H1></OL>
<HR ALIGN="center">
</BODY>
</HTML>

BIN
doc/arm/Bv9ARM.pdf Executable file
View File

Binary file not shown.