Commit 727f5b88 authored by Andreas Gustafsson's avatar Andreas Gustafsson
Browse files

regenerated

parent 7ff4660f
......@@ -139,7 +139,7 @@ CLASS="acronym"
> version 9 software package for system
administrators.</P
><P
>This version of the manual corresponds to BIND version 9.2.</P
>This version of the manual corresponds to BIND version 9.3.</P
></DIV
><DIV
CLASS="sect1"
......@@ -490,16 +490,27 @@ CLASS="emphasis"
> and interprets the responses.
The <SPAN
CLASS="acronym"
>BIND 9</SPAN
> software distribution contains both a
name server and a resolver library.</P
>BIND</SPAN
> 9 software distribution contains a
name server, <B
CLASS="command"
>named</B
>, and two resolver
libraries, <B
CLASS="command"
>liblwres</B
> and <B
CLASS="command"
>libbind</B
>.
</P
></DIV
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN119"
NAME="AEN122"
>1.4.2. Domains and Domain Names</A
></H2
><P
......@@ -529,9 +540,9 @@ CLASS="emphasis"
> could be
<TT
CLASS="literal"
>mail.example.net</TT
>mail.example.com</TT
>,
were <TT
where <TT
CLASS="literal"
>com</TT
> is the
......@@ -597,7 +608,7 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN143"
NAME="AEN146"
>1.4.3. Zones</A
></H2
><P
......@@ -617,7 +628,7 @@ CLASS="acronym"
>DNS</SPAN
> tree. A zone consists of
those contiguous parts of the domain
tree for which a a name server has complete information and over which
tree for which a name server has complete information and over which
it has authority. It contains all domain names from a certain point
downward in the domain tree except those which are delegated to
other zones. A delegation point is marked by one or more
......@@ -697,7 +708,7 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN166"
NAME="AEN169"
>1.4.4. Authoritative Name Servers</A
></H2
><P
......@@ -719,14 +730,14 @@ CLASS="command"
>dig</B
> (<A
HREF="Bv9ARM.ch03.html#diagnostic_tools"
>Section 3.4.1.1</A
>Section 3.3.1.1</A
>).</P
><DIV
CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="AEN173"
NAME="AEN176"
>1.4.4.1. The Primary Master</A
></H3
><P
......@@ -754,7 +765,7 @@ CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="AEN180"
NAME="AEN183"
>1.4.4.2. Slave Servers</A
></H3
><P
......@@ -780,7 +791,7 @@ CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="AEN186"
NAME="AEN189"
>1.4.4.3. Stealth Servers</A
></H3
><P
......@@ -825,7 +836,7 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN195"
NAME="AEN198"
>1.4.5. Caching Name Servers</A
></H2
><P
......@@ -867,7 +878,7 @@ CLASS="sect3"
><H3
CLASS="sect3"
><A
NAME="AEN205"
NAME="AEN208"
>1.4.5.1. Forwarding</A
></H3
><P
......@@ -909,7 +920,7 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN213"
NAME="AEN216"
>1.4.6. Name Servers in Multiple Roles</A
></H2
><P
......
......@@ -13,7 +13,7 @@ REL="PREVIOUS"
TITLE="Introduction "
HREF="Bv9ARM.ch01.html"><LINK
REL="NEXT"
TITLE="Nameserver Configuration"
TITLE="Name Server Configuration"
HREF="Bv9ARM.ch03.html"></HEAD
><BODY
CLASS="chapter"
......@@ -81,27 +81,27 @@ CLASS="TOC"
></DT
><DT
>2.1. <A
HREF="Bv9ARM.ch02.html#AEN223"
HREF="Bv9ARM.ch02.html#AEN226"
>Hardware requirements</A
></DT
><DT
>2.2. <A
HREF="Bv9ARM.ch02.html#AEN231"
HREF="Bv9ARM.ch02.html#AEN234"
>CPU Requirements</A
></DT
><DT
>2.3. <A
HREF="Bv9ARM.ch02.html#AEN235"
HREF="Bv9ARM.ch02.html#AEN238"
>Memory Requirements</A
></DT
><DT
>2.4. <A
HREF="Bv9ARM.ch02.html#AEN240"
>Nameserver Intensive Environment Issues</A
HREF="Bv9ARM.ch02.html#AEN243"
>Name Server Intensive Environment Issues</A
></DT
><DT
>2.5. <A
HREF="Bv9ARM.ch02.html#AEN243"
HREF="Bv9ARM.ch02.html#AEN246"
>Supported Operating Systems</A
></DT
></DL
......@@ -111,7 +111,7 @@ CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN223"
NAME="AEN226"
>2.1. Hardware requirements</A
></H1
><P
......@@ -134,7 +134,7 @@ features may wish to consider larger systems for these applications.
<SPAN
CLASS="acronym"
>BIND</SPAN
> 9 is now fully multithreaded, allowing full utilization of
> 9 is fully multithreaded, allowing full utilization of
multiprocessor systems for installations that need it.</P
></DIV
><DIV
......@@ -142,7 +142,7 @@ CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN231"
NAME="AEN234"
>2.2. CPU Requirements</A
></H1
><P
......@@ -159,7 +159,7 @@ CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN235"
NAME="AEN238"
>2.3. Memory Requirements</A
></H1
><P
......@@ -175,86 +175,47 @@ CLASS="acronym"
>
traffic. It is still good practice to have enough memory to load
all zone and cache data into memory &#8212; unfortunately, the best way
to determine this for a given installation is to watch the nameserver
to determine this for a given installation is to watch the name server
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
fast as they are being inserted.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN240"
>2.4. Nameserver Intensive Environment Issues</A
NAME="AEN243"
>2.4. Name Server Intensive Environment Issues</A
></H1
><P
>For nameserver intensive environments, there are two alternative
>For name server 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
any second-level internal name servers query a main name server, 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.
is to set up second-level internal name servers 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
as none of the name servers share their cached data.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN243"
NAME="AEN246"
>2.5. Supported Operating Systems</A
></H1
><P
>ISC <SPAN
CLASS="acronym"
>BIND</SPAN
> 9 compiles and runs on the following operating
systems:</P
><P
></P
><UL
><LI
><P
>IBM AIX 4.3</P
></LI
><LI
><P
>Compaq Digital/Tru64 UNIX 4.0D</P
></LI
><LI
><P
>Compaq Digital/Tru64 UNIX 5 (with IPv6 EAK)</P
></LI
><LI
><P
>HP HP-UX 11</P
></LI
><LI
><P
>IRIX64 6.5</P
></LI
><LI
><P
>Sun Solaris 2.6, 7, 8</P
></LI
><LI
><P
>NetBSD 1.5 (with unproven-pthreads 0.17)</P
></LI
><LI
><P
>FreeBSD 3.4-STABLE, 3.5, 4.0, 4.1</P
></LI
><LI
><P
>Red Hat Linux 6.0, 6.1, 6.2, 7.0</P
></LI
></UL
> 9 compiles and runs on a large number
of Unix-like operating system and on Windows NT / 2000. For an up-to-date
list of supported systems, see the README file in the top level directory
of the BIND 9 source distribution.</P
></DIV
></DIV
><DIV
......@@ -307,7 +268,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Nameserver Configuration</TD
>Name Server Configuration</TD
></TR
></TABLE
></DIV
......
<HTML
><HEAD
><TITLE
>Nameserver Configuration</TITLE
>Name Server Configuration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61
......@@ -13,7 +13,7 @@ REL="PREVIOUS"
TITLE="BIND Resource Requirements"
HREF="Bv9ARM.ch02.html"><LINK
REL="NEXT"
TITLE="Advanced Concepts"
TITLE="Advanced DNS Features"
HREF="Bv9ARM.ch04.html"></HEAD
><BODY
CLASS="chapter"
......@@ -67,7 +67,7 @@ CLASS="chapter"
><H1
><A
NAME="ch03"
>Chapter 3. Nameserver Configuration</A
>Chapter 3. Name Server Configuration</A
></H1
><DIV
CLASS="TOC"
......@@ -83,18 +83,13 @@ HREF="Bv9ARM.ch03.html#sample_configuration"
></DT
><DT
>3.2. <A
HREF="Bv9ARM.ch03.html#AEN281"
HREF="Bv9ARM.ch03.html#AEN266"
>Load Balancing</A
></DT
><DT
>3.3. <A
HREF="Bv9ARM.ch03.html#notify"
>Notify</A
></DT
><DT
>3.4. <A
HREF="Bv9ARM.ch03.html#AEN369"
>Nameserver Operations</A
HREF="Bv9ARM.ch03.html#AEN343"
>Name Server Operations</A
></DT
></DL
></DIV
......@@ -115,21 +110,25 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN271"
>3.1.1. A Caching-only Nameserver</A
NAME="AEN255"
>3.1.1. A Caching-only Name Server</A
></H2
><P
>The following sample configuration is appropriate for a caching-only
name server for use by clients internal to a corporation. All queries
from outside clients are refused.</P
from outside clients are refused using the <B
CLASS="command"
>allow-query</B
>
option. Alternatively, the same effect could be achieved using suitable
firewall rules.</P
><PRE
CLASS="programlisting"
>&#13;// Two corporate subnets we wish to allow queries from.
acl "corpnets" { 192.168.4.0/24; 192.168.7.0/24; };
acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
options {
directory "/etc/namedb"; // Working directory
pid-file "named.pid"; // Put pid file in working dir
allow-query { "corpnets"; };
allow-query { corpnets; };
};
// Provide a reverse mapping for the loopback address 127.0.0.1
zone "0.0.127.in-addr.arpa" {
......@@ -144,8 +143,8 @@ CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN275"
>3.1.2. An Authoritative-only Nameserver</A
NAME="AEN260"
>3.1.2. An Authoritative-only Name Server</A
></H2
><P
>This sample configuration is for an authoritative-only server
......@@ -161,7 +160,6 @@ CLASS="filename"
CLASS="programlisting"
>&#13;options {
directory "/etc/namedb"; // Working directory
pid-file "named.pid"; // Put pid file in working dir
allow-query { any; }; // This is the default
recursion no; // Do not provide recursive service
};
......@@ -197,15 +195,15 @@ CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN281"
NAME="AEN266"
>3.2. Load Balancing</A
></H1
><P
>Primitive load balancing can be achieved in <SPAN
>A primitive form of load balancing can be achieved in
the <SPAN
CLASS="acronym"
>DNS</SPAN
> using multiple
A records for one name.</P
> by using multiple A records for one name.</P
><P
>For example, if you have three WWW servers with network addresses
of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the
......@@ -214,7 +212,7 @@ of the time:</P
><DIV
CLASS="informaltable"
><A
NAME="AEN286"
NAME="AEN271"
></A
><P
></P
......@@ -452,63 +450,21 @@ CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="notify"
>3.3. Notify</A
></H1
><P
><SPAN
CLASS="acronym"
>DNS</SPAN
> Notify is a mechanism that allows master nameservers to
notify their slave servers of changes to a zone's data. In
response to a <B
CLASS="command"
>NOTIFY</B
> from a master server, the
slave will check to see that its version of the zone is the
current version and, if not, initiate a transfer.</P
><P
><SPAN
CLASS="acronym"
>DNS</SPAN
>
Notify is fully documented in RFC 1996. See also the description
of the zone option <B
CLASS="command"
>also-notify</B
>, see
<A
HREF="Bv9ARM.ch06.html#zone_transfers"
>Section 6.2.14.6</A
>. For more information about
<B
CLASS="command"
>notify</B
>, see <A
HREF="Bv9ARM.ch06.html#boolean_options"
>Section 6.2.14.1</A
>.</P
></DIV
><DIV
CLASS="sect1"
><H1
CLASS="sect1"
><A
NAME="AEN369"
>3.4. Nameserver Operations</A
NAME="AEN343"
>3.3. Name Server Operations</A
></H1
><DIV
CLASS="sect2"
><H2
CLASS="sect2"
><A
NAME="AEN371"
>3.4.1. Tools for Use With the Nameserver Daemon</A
NAME="AEN345"
>3.3.1. Tools for Use With the Name Server Daemon</A
></H2
><P
>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
and debugging the name server daemon. We describe several in this
section </P
><DIV
CLASS="sect3"
......@@ -516,9 +472,24 @@ CLASS="sect3"
CLASS="sect3"
><A
NAME="diagnostic_tools"
>3.4.1.1. Diagnostic Tools</A
>3.3.1.1. Diagnostic Tools</A
></H3
><P
>The <B
CLASS="command"
>dig</B
>, <B
CLASS="command"
>host</B
>, and
<B
CLASS="command"
>nslookup</B
> programs are all command line tools
for manually querying name servers. They differ in style and
output format.
</P
><P
></P
><DIV
CLASS="variablelist"
......@@ -533,9 +504,9 @@ CLASS="command"
>The domain information groper (<B
CLASS="command"
>dig</B
>) is
a command line tool that can be used to gather information from
the Domain Name System servers. Dig has two modes: simple interactive
>)
is the most versatile and complete of these lookup tools.
It 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
......@@ -603,12 +574,8 @@ CLASS="command"
>The <B
CLASS="command"
>host</B
> utility
provides a simple <SPAN
CLASS="acronym"
>DNS</SPAN
> lookup using a command-line interface for
looking up Internet hostnames. By default, the utility converts
> utility emphasizes simplicity
and ease of use. By default, it converts
between host names and Internet addresses, but its functionality
can be extended with the use of options.</P
><P
......@@ -668,12 +635,8 @@ CLASS="command"
><B
CLASS="command"
>nslookup</B
> is a program used to query Internet
domain nameservers. <B
CLASS="command"
>nslookup</B
> has two modes: interactive
and non-interactive. Interactive mode allows the user to query nameservers
and non-interactive. Interactive mode allows the user to query name servers
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
......@@ -689,13 +652,13 @@ CLASS="replaceable"
> | - [server]]</P
><P
>Interactive mode is entered when no arguments are given (the
default nameserver will be used) or when the first argument is a
default name server 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
of a name server.</P
><P
>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
optional second argument specifies the host name or address of a name server.</P
><P
>Due to its arcane user interface and frequently inconsistent
behavior, we do not recommend the use of <B
......@@ -716,7 +679,7 @@ CLASS="sect3"
CLASS="sect3"
><A
NAME="admin_tools"
>3.4.1.2. Administrative Tools</A
>3.3.1.2. Administrative Tools</A
></H3
><P
>Administrative tools play an integral part in the management
......@@ -811,7 +774,7 @@ CLASS="command"
CLASS="command"
>rndc</B
>) program allows the system
administrator to control the operation of a nameserver.
administrator to control the operation of a name server.
If you run <B
CLASS="command"
>rndc</B
......@@ -1152,7 +1115,11 @@ CLASS="command"
utility except <B
CLASS="command"
>ndc start</B
>, which was also
> and
<B
CLASS="command"
>ndc restart</B
>, which were also
not supported in <B
CLASS="command"
>ndc</B
......@@ -1259,7 +1226,7 @@ option is provided on the command line.
CLASS="command"
>default-key</B
> takes
the name of key as its argument, as defined by a <B
the name of a key as its argument, as defined by a <B
CLASS="command"
>key</B
> statement.
......@@ -1280,8 +1247,26 @@ CLASS="command"
>The <B
CLASS="command"
>key</B
> statement names a key with its
string argument. The string is required by the server to be a valid
> statement defines an key to be used
by <B
CLASS="command"
>rndc</B
> when authenticating with
<B
CLASS="command"
>named</B
>. Its syntax is identical to the
<B
CLASS="command"
>key</B
> statement in named.conf.
The keyword <TT
CLASS="userinput"
><B
>key</B