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

regenerated

parent 7ff4660f
...@@ -139,7 +139,7 @@ CLASS="acronym" ...@@ -139,7 +139,7 @@ CLASS="acronym"
> version 9 software package for system > version 9 software package for system
administrators.</P administrators.</P
><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
><DIV ><DIV
CLASS="sect1" CLASS="sect1"
...@@ -490,16 +490,27 @@ CLASS="emphasis" ...@@ -490,16 +490,27 @@ CLASS="emphasis"
> and interprets the responses. > and interprets the responses.
The <SPAN The <SPAN
CLASS="acronym" CLASS="acronym"
>BIND 9</SPAN >BIND</SPAN
> software distribution contains both a > 9 software distribution contains a
name server and a resolver library.</P 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
><DIV ><DIV
CLASS="sect2" CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN119" NAME="AEN122"
>1.4.2. Domains and Domain Names</A >1.4.2. Domains and Domain Names</A
></H2 ></H2
><P ><P
...@@ -529,9 +540,9 @@ CLASS="emphasis" ...@@ -529,9 +540,9 @@ CLASS="emphasis"
> could be > could be
<TT <TT
CLASS="literal" CLASS="literal"
>mail.example.net</TT >mail.example.com</TT
>, >,
were <TT where <TT
CLASS="literal" CLASS="literal"
>com</TT >com</TT
> is the > is the
...@@ -597,7 +608,7 @@ CLASS="sect2" ...@@ -597,7 +608,7 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN143" NAME="AEN146"
>1.4.3. Zones</A >1.4.3. Zones</A
></H2 ></H2
><P ><P
...@@ -617,7 +628,7 @@ CLASS="acronym" ...@@ -617,7 +628,7 @@ CLASS="acronym"
>DNS</SPAN >DNS</SPAN
> tree. A zone consists of > tree. A zone consists of
those contiguous parts of the domain 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 it has authority. It contains all domain names from a certain point
downward in the domain tree except those which are delegated to downward in the domain tree except those which are delegated to
other zones. A delegation point is marked by one or more other zones. A delegation point is marked by one or more
...@@ -697,7 +708,7 @@ CLASS="sect2" ...@@ -697,7 +708,7 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN166" NAME="AEN169"
>1.4.4. Authoritative Name Servers</A >1.4.4. Authoritative Name Servers</A
></H2 ></H2
><P ><P
...@@ -719,14 +730,14 @@ CLASS="command" ...@@ -719,14 +730,14 @@ CLASS="command"
>dig</B >dig</B
> (<A > (<A
HREF="Bv9ARM.ch03.html#diagnostic_tools" HREF="Bv9ARM.ch03.html#diagnostic_tools"
>Section 3.4.1.1</A >Section 3.3.1.1</A
>).</P >).</P
><DIV ><DIV
CLASS="sect3" CLASS="sect3"
><H3 ><H3
CLASS="sect3" CLASS="sect3"
><A ><A
NAME="AEN173" NAME="AEN176"
>1.4.4.1. The Primary Master</A >1.4.4.1. The Primary Master</A
></H3 ></H3
><P ><P
...@@ -754,7 +765,7 @@ CLASS="sect3" ...@@ -754,7 +765,7 @@ CLASS="sect3"
><H3 ><H3
CLASS="sect3" CLASS="sect3"
><A ><A
NAME="AEN180" NAME="AEN183"
>1.4.4.2. Slave Servers</A >1.4.4.2. Slave Servers</A
></H3 ></H3
><P ><P
...@@ -780,7 +791,7 @@ CLASS="sect3" ...@@ -780,7 +791,7 @@ CLASS="sect3"
><H3 ><H3
CLASS="sect3" CLASS="sect3"
><A ><A
NAME="AEN186" NAME="AEN189"
>1.4.4.3. Stealth Servers</A >1.4.4.3. Stealth Servers</A
></H3 ></H3
><P ><P
...@@ -825,7 +836,7 @@ CLASS="sect2" ...@@ -825,7 +836,7 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN195" NAME="AEN198"
>1.4.5. Caching Name Servers</A >1.4.5. Caching Name Servers</A
></H2 ></H2
><P ><P
...@@ -867,7 +878,7 @@ CLASS="sect3" ...@@ -867,7 +878,7 @@ CLASS="sect3"
><H3 ><H3
CLASS="sect3" CLASS="sect3"
><A ><A
NAME="AEN205" NAME="AEN208"
>1.4.5.1. Forwarding</A >1.4.5.1. Forwarding</A
></H3 ></H3
><P ><P
...@@ -909,7 +920,7 @@ CLASS="sect2" ...@@ -909,7 +920,7 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN213" NAME="AEN216"
>1.4.6. Name Servers in Multiple Roles</A >1.4.6. Name Servers in Multiple Roles</A
></H2 ></H2
><P ><P
......
...@@ -13,7 +13,7 @@ REL="PREVIOUS" ...@@ -13,7 +13,7 @@ REL="PREVIOUS"
TITLE="Introduction " TITLE="Introduction "
HREF="Bv9ARM.ch01.html"><LINK HREF="Bv9ARM.ch01.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Nameserver Configuration" TITLE="Name Server Configuration"
HREF="Bv9ARM.ch03.html"></HEAD HREF="Bv9ARM.ch03.html"></HEAD
><BODY ><BODY
CLASS="chapter" CLASS="chapter"
...@@ -81,27 +81,27 @@ CLASS="TOC" ...@@ -81,27 +81,27 @@ CLASS="TOC"
></DT ></DT
><DT ><DT
>2.1. <A >2.1. <A
HREF="Bv9ARM.ch02.html#AEN223" HREF="Bv9ARM.ch02.html#AEN226"
>Hardware requirements</A >Hardware requirements</A
></DT ></DT
><DT ><DT
>2.2. <A >2.2. <A
HREF="Bv9ARM.ch02.html#AEN231" HREF="Bv9ARM.ch02.html#AEN234"
>CPU Requirements</A >CPU Requirements</A
></DT ></DT
><DT ><DT
>2.3. <A >2.3. <A
HREF="Bv9ARM.ch02.html#AEN235" HREF="Bv9ARM.ch02.html#AEN238"
>Memory Requirements</A >Memory Requirements</A
></DT ></DT
><DT ><DT
>2.4. <A >2.4. <A
HREF="Bv9ARM.ch02.html#AEN240" HREF="Bv9ARM.ch02.html#AEN243"
>Nameserver Intensive Environment Issues</A >Name Server Intensive Environment Issues</A
></DT ></DT
><DT ><DT
>2.5. <A >2.5. <A
HREF="Bv9ARM.ch02.html#AEN243" HREF="Bv9ARM.ch02.html#AEN246"
>Supported Operating Systems</A >Supported Operating Systems</A
></DT ></DT
></DL ></DL
...@@ -111,7 +111,7 @@ CLASS="sect1" ...@@ -111,7 +111,7 @@ CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN223" NAME="AEN226"
>2.1. Hardware requirements</A >2.1. Hardware requirements</A
></H1 ></H1
><P ><P
...@@ -134,7 +134,7 @@ features may wish to consider larger systems for these applications. ...@@ -134,7 +134,7 @@ features may wish to consider larger systems for these applications.
<SPAN <SPAN
CLASS="acronym" CLASS="acronym"
>BIND</SPAN >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 multiprocessor systems for installations that need it.</P
></DIV ></DIV
><DIV ><DIV
...@@ -142,7 +142,7 @@ CLASS="sect1" ...@@ -142,7 +142,7 @@ CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN231" NAME="AEN234"
>2.2. CPU Requirements</A >2.2. CPU Requirements</A
></H1 ></H1
><P ><P
...@@ -159,7 +159,7 @@ CLASS="sect1" ...@@ -159,7 +159,7 @@ CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN235" NAME="AEN238"
>2.3. Memory Requirements</A >2.3. Memory Requirements</A
></H1 ></H1
><P ><P
...@@ -175,86 +175,47 @@ CLASS="acronym" ...@@ -175,86 +175,47 @@ CLASS="acronym"
> >
traffic. It is still good practice to have enough memory to load traffic. It is still good practice to have enough memory to load
all zone and cache data into memory &#8212; unfortunately, the best way 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 in operation. After a few weeks the server process should reach
a relatively stable size where entries are expiring from the cache as a relatively stable size where entries are expiring from the cache as
fast as they are being inserted. Ideally, the resource limits should fast as they are being inserted.</P
be set higher than this stable size.</P
></DIV ></DIV
><DIV ><DIV
CLASS="sect1" CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN240" NAME="AEN243"
>2.4. Nameserver Intensive Environment Issues</A >2.4. Name Server Intensive Environment Issues</A
></H1 ></H1
><P ><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 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 has enough memory to build a large cache. This approach minimizes
the bandwidth used by external name lookups. The second alternative 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 In this configuration, none of the individual machines needs to
have as much memory or CPU power as in the first alternative, but have as much memory or CPU power as in the first alternative, but
this has the disadvantage of making many more external queries, 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
><DIV ><DIV
CLASS="sect1" CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN243" NAME="AEN246"
>2.5. Supported Operating Systems</A >2.5. Supported Operating Systems</A
></H1 ></H1
><P ><P
>ISC <SPAN >ISC <SPAN
CLASS="acronym" CLASS="acronym"
>BIND</SPAN >BIND</SPAN
> 9 compiles and runs on the following operating > 9 compiles and runs on a large number
systems:</P of Unix-like operating system and on Windows NT / 2000. For an up-to-date
><P list of supported systems, see the README file in the top level directory
></P of the BIND 9 source distribution.</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
></DIV ></DIV
></DIV ></DIV
><DIV ><DIV
...@@ -307,7 +268,7 @@ VALIGN="top" ...@@ -307,7 +268,7 @@ VALIGN="top"
WIDTH="33%" WIDTH="33%"
ALIGN="right" ALIGN="right"
VALIGN="top" VALIGN="top"
>Nameserver Configuration</TD >Name Server Configuration</TD
></TR ></TR
></TABLE ></TABLE
></DIV ></DIV
......
<HTML <HTML
><HEAD ><HEAD
><TITLE ><TITLE
>Nameserver Configuration</TITLE >Name Server Configuration</TITLE
><META ><META
NAME="GENERATOR" NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.61 CONTENT="Modular DocBook HTML Stylesheet Version 1.61
...@@ -13,7 +13,7 @@ REL="PREVIOUS" ...@@ -13,7 +13,7 @@ REL="PREVIOUS"
TITLE="BIND Resource Requirements" TITLE="BIND Resource Requirements"
HREF="Bv9ARM.ch02.html"><LINK HREF="Bv9ARM.ch02.html"><LINK
REL="NEXT" REL="NEXT"
TITLE="Advanced Concepts" TITLE="Advanced DNS Features"
HREF="Bv9ARM.ch04.html"></HEAD HREF="Bv9ARM.ch04.html"></HEAD
><BODY ><BODY
CLASS="chapter" CLASS="chapter"
...@@ -67,7 +67,7 @@ CLASS="chapter" ...@@ -67,7 +67,7 @@ CLASS="chapter"
><H1 ><H1
><A ><A
NAME="ch03" NAME="ch03"
>Chapter 3. Nameserver Configuration</A >Chapter 3. Name Server Configuration</A
></H1 ></H1
><DIV ><DIV
CLASS="TOC" CLASS="TOC"
...@@ -83,18 +83,13 @@ HREF="Bv9ARM.ch03.html#sample_configuration" ...@@ -83,18 +83,13 @@ HREF="Bv9ARM.ch03.html#sample_configuration"
></DT ></DT
><DT ><DT
>3.2. <A >3.2. <A
HREF="Bv9ARM.ch03.html#AEN281" HREF="Bv9ARM.ch03.html#AEN266"
>Load Balancing</A >Load Balancing</A
></DT ></DT
><DT ><DT
>3.3. <A >3.3. <A
HREF="Bv9ARM.ch03.html#notify" HREF="Bv9ARM.ch03.html#AEN343"
>Notify</A >Name Server Operations</A
></DT
><DT
>3.4. <A
HREF="Bv9ARM.ch03.html#AEN369"
>Nameserver Operations</A
></DT ></DT
></DL ></DL
></DIV ></DIV
...@@ -115,21 +110,25 @@ CLASS="sect2" ...@@ -115,21 +110,25 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN271" NAME="AEN255"
>3.1.1. A Caching-only Nameserver</A >3.1.1. A Caching-only Name Server</A
></H2 ></H2
><P ><P
>The following sample configuration is appropriate for a caching-only >The following sample configuration is appropriate for a caching-only
name server for use by clients internal to a corporation. All queries 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 ><PRE
CLASS="programlisting" CLASS="programlisting"
>&#13;// Two corporate subnets we wish to allow queries from. >&#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 { options {
directory "/etc/namedb"; // Working directory 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 // Provide a reverse mapping for the loopback address 127.0.0.1
zone "0.0.127.in-addr.arpa" { zone "0.0.127.in-addr.arpa" {
...@@ -144,8 +143,8 @@ CLASS="sect2" ...@@ -144,8 +143,8 @@ CLASS="sect2"
><H2 ><H2
CLASS="sect2" CLASS="sect2"
><A ><A
NAME="AEN275" NAME="AEN260"
>3.1.2. An Authoritative-only Nameserver</A >3.1.2. An Authoritative-only Name Server</A
></H2 ></H2
><P ><P
>This sample configuration is for an authoritative-only server >This sample configuration is for an authoritative-only server
...@@ -161,7 +160,6 @@ CLASS="filename" ...@@ -161,7 +160,6 @@ CLASS="filename"
CLASS="programlisting" CLASS="programlisting"
>&#13;options { >&#13;options {
directory "/etc/namedb"; // Working directory directory "/etc/namedb"; // Working directory
pid-file "named.pid"; // Put pid file in working dir
allow-query { any; }; // This is the default allow-query { any; }; // This is the default
recursion no; // Do not provide recursive service recursion no; // Do not provide recursive service
}; };
...@@ -197,15 +195,15 @@ CLASS="sect1" ...@@ -197,15 +195,15 @@ CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="AEN281" NAME="AEN266"
>3.2. Load Balancing</A >3.2. Load Balancing</A
></H1 ></H1
><P ><P
>Primitive load balancing can be achieved in <SPAN >A primitive form of load balancing can be achieved in
the <SPAN
CLASS="acronym" CLASS="acronym"
>DNS</SPAN >DNS</SPAN
> using multiple > by using multiple A records for one name.</P
A records for one name.</P
><P ><P
>For example, if you have three WWW servers with network addresses >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 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 ...@@ -214,7 +212,7 @@ of the time:</P
><DIV ><DIV
CLASS="informaltable" CLASS="informaltable"
><A ><A
NAME="AEN286" NAME="AEN271"
></A ></A
><P ><P
></P ></P
...@@ -452,63 +450,21 @@ CLASS="sect1" ...@@ -452,63 +450,21 @@ CLASS="sect1"
><H1 ><H1
CLASS="sect1" CLASS="sect1"
><A ><A
NAME="notify" NAME="AEN343"
>3.3. Notify</A >3.3. Name Server Operations</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