mirror of
https://github.com/isc-projects/bind9.git
synced 2026-06-11 03:59:59 -04:00
regen v9_9
This commit is contained in:
parent
1d934788ab
commit
69d2776907
11 changed files with 389 additions and 414 deletions
|
|
@ -44,17 +44,17 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.3">Scope of Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.4">Organization of This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.5">Conventions Used in This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#doc_scope">Scope of Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#organization">Organization of This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#conventions">Conventions Used in This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#dns_overview">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.3">DNS Fundamentals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.4">Domains and Domain Names</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.5">Zones</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.6">Authoritative Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.7">Caching Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.8">Name Servers in Multiple Roles</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#dns_fundamentals">DNS Fundamentals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#domain_names">Domains and Domain Names</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#zones">Zones</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#auth_servers">Authoritative Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#cache_servers">Caching Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#multi_role">Name Servers in Multiple Roles</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
</div>
|
||||
|
|
@ -70,7 +70,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.2.3"></a>Scope of Document</h2></div></div></div>
|
||||
<a name="doc_scope"></a>Scope of Document</h2></div></div></div>
|
||||
<p>
|
||||
The Berkeley Internet Name Domain
|
||||
(<acronym class="acronym">BIND</acronym>) implements a
|
||||
|
|
@ -84,7 +84,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.2.4"></a>Organization of This Document</h2></div></div></div>
|
||||
<a name="organization"></a>Organization of This Document</h2></div></div></div>
|
||||
<p>
|
||||
In this document, <span class="emphasis"><em>Chapter 1</em></span> introduces
|
||||
the basic <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym> concepts. <span class="emphasis"><em>Chapter 2</em></span>
|
||||
|
|
@ -113,7 +113,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.2.5"></a>Conventions Used in This Document</h2></div></div></div>
|
||||
<a name="conventions"></a>Conventions Used in This Document</h2></div></div></div>
|
||||
<p>
|
||||
In this document, we use the following general typographic
|
||||
conventions:
|
||||
|
|
@ -240,7 +240,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.2.6"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div>
|
||||
<a name="dns_overview"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div>
|
||||
<p>
|
||||
The purpose of this document is to explain the installation
|
||||
and upkeep of the <acronym class="acronym">BIND</acronym> (Berkeley Internet
|
||||
|
|
@ -250,7 +250,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.3"></a>DNS Fundamentals</h3></div></div></div>
|
||||
<a name="dns_fundamentals"></a>DNS Fundamentals</h3></div></div></div>
|
||||
<p>
|
||||
The Domain Name System (DNS) is a hierarchical, distributed
|
||||
database. It stores information for mapping Internet host names to
|
||||
|
|
@ -272,7 +272,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.4"></a>Domains and Domain Names</h3></div></div></div>
|
||||
<a name="domain_names"></a>Domains and Domain Names</h3></div></div></div>
|
||||
<p>
|
||||
The data stored in the DNS is identified by <span class="emphasis"><em>domain names</em></span> that are organized as a tree according to
|
||||
organizational or administrative boundaries. Each node of the tree,
|
||||
|
|
@ -318,7 +318,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.5"></a>Zones</h3></div></div></div>
|
||||
<a name="zones"></a>Zones</h3></div></div></div>
|
||||
<p>
|
||||
To properly operate a name server, it is important to understand
|
||||
the difference between a <span class="emphasis"><em>zone</em></span>
|
||||
|
|
@ -371,7 +371,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.6"></a>Authoritative Name Servers</h3></div></div></div>
|
||||
<a name="auth_servers"></a>Authoritative Name Servers</h3></div></div></div>
|
||||
<p>
|
||||
Each zone is served by at least
|
||||
one <span class="emphasis"><em>authoritative name server</em></span>,
|
||||
|
|
@ -388,7 +388,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.2.6.6.4"></a>The Primary Master</h4></div></div></div>
|
||||
<a name="primary_master"></a>The Primary Master</h4></div></div></div>
|
||||
<p>
|
||||
The authoritative server where the master copy of the zone
|
||||
data is maintained is called the
|
||||
|
|
@ -408,7 +408,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.2.6.6.5"></a>Slave Servers</h4></div></div></div>
|
||||
<a name="slave_server"></a>Slave Servers</h4></div></div></div>
|
||||
<p>
|
||||
The other authoritative servers, the <span class="emphasis"><em>slave</em></span>
|
||||
servers (also known as <span class="emphasis"><em>secondary</em></span> servers)
|
||||
|
|
@ -424,7 +424,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.2.6.6.6"></a>Stealth Servers</h4></div></div></div>
|
||||
<a name="stealth_server"></a>Stealth Servers</h4></div></div></div>
|
||||
<p>
|
||||
Usually all of the zone's authoritative servers are listed in
|
||||
NS records in the parent zone. These NS records constitute
|
||||
|
|
@ -459,7 +459,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.7"></a>Caching Name Servers</h3></div></div></div>
|
||||
<a name="cache_servers"></a>Caching Name Servers</h3></div></div></div>
|
||||
<p>
|
||||
The resolver libraries provided by most operating systems are
|
||||
<span class="emphasis"><em>stub resolvers</em></span>, meaning that they are not
|
||||
|
|
@ -486,7 +486,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.2.6.7.5"></a>Forwarding</h4></div></div></div>
|
||||
<a name="forwarder"></a>Forwarding</h4></div></div></div>
|
||||
<p>
|
||||
Even a caching name server does not necessarily perform
|
||||
the complete recursive lookup itself. Instead, it can
|
||||
|
|
@ -513,7 +513,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.2.6.8"></a>Name Servers in Multiple Roles</h3></div></div></div>
|
||||
<a name="multi_role"></a>Name Servers in Multiple Roles</h3></div></div></div>
|
||||
<p>
|
||||
The <acronym class="acronym">BIND</acronym> name server can
|
||||
simultaneously act as
|
||||
|
|
|
|||
|
|
@ -44,16 +44,16 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.2">Hardware requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.3">CPU Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.4">Memory Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.5">Name Server Intensive Environment Issues</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.6">Supported Operating Systems</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#hw_req">Hardware requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#cpu_req">CPU Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#mem_req">Memory Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#intensive_env">Name Server Intensive Environment Issues</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#supported_os">Supported Operating Systems</a></span></dt>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.3.2"></a>Hardware requirements</h2></div></div></div>
|
||||
<a name="hw_req"></a>Hardware requirements</h2></div></div></div>
|
||||
<p>
|
||||
<acronym class="acronym">DNS</acronym> hardware requirements have
|
||||
traditionally been quite modest.
|
||||
|
|
@ -72,7 +72,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.3.3"></a>CPU Requirements</h2></div></div></div>
|
||||
<a name="cpu_req"></a>CPU Requirements</h2></div></div></div>
|
||||
<p>
|
||||
CPU requirements for <acronym class="acronym">BIND</acronym> 9 range from
|
||||
i486-class machines
|
||||
|
|
@ -83,7 +83,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.3.4"></a>Memory Requirements</h2></div></div></div>
|
||||
<a name="mem_req"></a>Memory Requirements</h2></div></div></div>
|
||||
<p>
|
||||
The memory of the server has to be large enough to fit the
|
||||
cache and zones loaded off disk. The <span class="command"><strong>max-cache-size</strong></span>
|
||||
|
|
@ -106,7 +106,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.3.5"></a>Name Server Intensive Environment Issues</h2></div></div></div>
|
||||
<a name="intensive_env"></a>Name Server Intensive Environment Issues</h2></div></div></div>
|
||||
<p>
|
||||
For name server intensive environments, there are two alternative
|
||||
configurations that may be used. The first is where clients and
|
||||
|
|
@ -123,7 +123,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.3.6"></a>Supported Operating Systems</h2></div></div></div>
|
||||
<a name="supported_os"></a>Supported Operating Systems</h2></div></div></div>
|
||||
<p>
|
||||
ISC <acronym class="acronym">BIND</acronym> 9 compiles and runs on a large
|
||||
number
|
||||
|
|
|
|||
|
|
@ -46,14 +46,14 @@
|
|||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.3.2">A Caching-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.3.3">An Authoritative-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#cache_only_sample">A Caching-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#auth_only_sample">An Authoritative-only Name Server</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4">Load Balancing</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5">Name Server Operations</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#load_balancing">Load Balancing</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#ns_operations">Name Server Operations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5.2">Tools for Use With the Name Server Daemon</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5.3">Signals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#tools">Tools for Use With the Name Server Daemon</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#signals">Signals</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
</div>
|
||||
|
|
@ -67,7 +67,7 @@
|
|||
<a name="sample_configuration"></a>Sample Configurations</h2></div></div></div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.4.3.2"></a>A Caching-only Name Server</h3></div></div></div>
|
||||
<a name="cache_only_sample"></a>A Caching-only Name Server</h3></div></div></div>
|
||||
<p>
|
||||
The following sample configuration is appropriate for a caching-only
|
||||
name server for use by clients internal to a corporation. All
|
||||
|
|
@ -97,7 +97,7 @@ zone "0.0.127.in-addr.arpa" {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.4.3.3"></a>An Authoritative-only Name Server</h3></div></div></div>
|
||||
<a name="auth_only_sample"></a>An Authoritative-only Name Server</h3></div></div></div>
|
||||
<p>
|
||||
This sample configuration is for an authoritative-only server
|
||||
that is the master server for "<code class="filename">example.com</code>"
|
||||
|
|
@ -145,7 +145,7 @@ zone "eng.example.com" {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.4.4"></a>Load Balancing</h2></div></div></div>
|
||||
<a name="load_balancing"></a>Load Balancing</h2></div></div></div>
|
||||
<p>
|
||||
A primitive form of load balancing can be achieved in
|
||||
the <acronym class="acronym">DNS</acronym> by using multiple records
|
||||
|
|
@ -288,10 +288,10 @@ zone "eng.example.com" {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.4.5"></a>Name Server Operations</h2></div></div></div>
|
||||
<a name="ns_operations"></a>Name Server Operations</h2></div></div></div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.4.5.2"></a>Tools for Use With the Name Server Daemon</h3></div></div></div>
|
||||
<a name="tools"></a>Tools for Use With the Name Server Daemon</h3></div></div></div>
|
||||
<p>
|
||||
This section describes several indispensable diagnostic,
|
||||
administrative and monitoring tools available to the system
|
||||
|
|
@ -598,7 +598,7 @@ controls {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.4.5.3"></a>Signals</h3></div></div></div>
|
||||
<a name="signals"></a>Signals</h3></div></div></div>
|
||||
<p>
|
||||
Certain UNIX signals cause the name server to take specific
|
||||
actions, as described in the following table. These signals can
|
||||
|
|
|
|||
|
|
@ -48,8 +48,8 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.5">Split DNS</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.5.5">Example split DNS setup</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns">Split DNS</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns_sample">Example split DNS setup</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.5">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
|
||||
|
|
@ -59,13 +59,13 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.9">TSIG Key Based Access Control</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.10">Errors</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7">TKEY</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.8">SIG(0)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#tkey">TKEY</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#sig0">SIG(0)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.6">Generating Keys</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.7">Signing the Zone</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.8">Configuring Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_keys">Generating Keys</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_signing">Signing the Zone</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_config">Configuring Servers</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
|
||||
<dd><dl>
|
||||
|
|
@ -97,7 +97,7 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.8">Specifying the engine on the command line</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.9">Running named with automatic zone re-signing</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#ipv6">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.6">Address Lookups Using AAAA Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.7">Address to Name Lookups Using Nibble Format</a></span></dt>
|
||||
|
|
@ -264,7 +264,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.5.5"></a>Split DNS</h2></div></div></div>
|
||||
<a name="split_dns"></a>Split DNS</h2></div></div></div>
|
||||
<p>
|
||||
Setting up different views, or visibility, of the DNS space to
|
||||
internal and external resolvers is usually referred to as a
|
||||
|
|
@ -294,124 +294,124 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.5.5.5"></a>Example split DNS setup</h3></div></div></div>
|
||||
<a name="split_dns_sample"></a>Example split DNS setup</h3></div></div></div>
|
||||
<p>
|
||||
Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
|
||||
(<code class="literal">example.com</code>)
|
||||
has several corporate sites that have an internal network with
|
||||
reserved
|
||||
Internet Protocol (IP) space and an external demilitarized zone (DMZ),
|
||||
or "outside" section of a network, that is available to the public.
|
||||
</p>
|
||||
Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
|
||||
(<code class="literal">example.com</code>)
|
||||
has several corporate sites that have an internal network with
|
||||
reserved
|
||||
Internet Protocol (IP) space and an external demilitarized zone (DMZ),
|
||||
or "outside" section of a network, that is available to the public.
|
||||
</p>
|
||||
<p>
|
||||
<span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
|
||||
to be able to resolve external hostnames and to exchange mail with
|
||||
people on the outside. The company also wants its internal resolvers
|
||||
to have access to certain internal-only zones that are not available
|
||||
at all outside of the internal network.
|
||||
</p>
|
||||
<span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
|
||||
to be able to resolve external hostnames and to exchange mail with
|
||||
people on the outside. The company also wants its internal resolvers
|
||||
to have access to certain internal-only zones that are not available
|
||||
at all outside of the internal network.
|
||||
</p>
|
||||
<p>
|
||||
In order to accomplish this, the company will set up two sets
|
||||
of name servers. One set will be on the inside network (in the
|
||||
reserved
|
||||
IP space) and the other set will be on bastion hosts, which are
|
||||
"proxy"
|
||||
hosts that can talk to both sides of its network, in the DMZ.
|
||||
</p>
|
||||
In order to accomplish this, the company will set up two sets
|
||||
of name servers. One set will be on the inside network (in the
|
||||
reserved
|
||||
IP space) and the other set will be on bastion hosts, which are
|
||||
"proxy"
|
||||
hosts that can talk to both sides of its network, in the DMZ.
|
||||
</p>
|
||||
<p>
|
||||
The internal servers will be configured to forward all queries,
|
||||
except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
|
||||
and <code class="filename">site2.example.com</code>, to the servers
|
||||
in the
|
||||
DMZ. These internal servers will have complete sets of information
|
||||
for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>, <code class="filename">site1.internal</code>,
|
||||
and <code class="filename">site2.internal</code>.
|
||||
</p>
|
||||
The internal servers will be configured to forward all queries,
|
||||
except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
|
||||
and <code class="filename">site2.example.com</code>, to the servers
|
||||
in the
|
||||
DMZ. These internal servers will have complete sets of information
|
||||
for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>, <code class="filename">site1.internal</code>,
|
||||
and <code class="filename">site2.internal</code>.
|
||||
</p>
|
||||
<p>
|
||||
To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
|
||||
the internal name servers must be configured to disallow all queries
|
||||
to these domains from any external hosts, including the bastion
|
||||
hosts.
|
||||
</p>
|
||||
To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
|
||||
the internal name servers must be configured to disallow all queries
|
||||
to these domains from any external hosts, including the bastion
|
||||
hosts.
|
||||
</p>
|
||||
<p>
|
||||
The external servers, which are on the bastion hosts, will
|
||||
be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
|
||||
This could include things such as the host records for public servers
|
||||
(<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
|
||||
and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
|
||||
</p>
|
||||
The external servers, which are on the bastion hosts, will
|
||||
be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
|
||||
This could include things such as the host records for public servers
|
||||
(<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
|
||||
and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
|
||||
</p>
|
||||
<p>
|
||||
In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
|
||||
should have special MX records that contain wildcard (`*') records
|
||||
pointing to the bastion hosts. This is needed because external mail
|
||||
servers do not have any other way of looking up how to deliver mail
|
||||
to those internal hosts. With the wildcard records, the mail will
|
||||
be delivered to the bastion host, which can then forward it on to
|
||||
internal hosts.
|
||||
</p>
|
||||
In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
|
||||
should have special MX records that contain wildcard (`*') records
|
||||
pointing to the bastion hosts. This is needed because external mail
|
||||
servers do not have any other way of looking up how to deliver mail
|
||||
to those internal hosts. With the wildcard records, the mail will
|
||||
be delivered to the bastion host, which can then forward it on to
|
||||
internal hosts.
|
||||
</p>
|
||||
<p>
|
||||
Here's an example of a wildcard MX record:
|
||||
</p>
|
||||
Here's an example of a wildcard MX record:
|
||||
</p>
|
||||
<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
|
||||
<p>
|
||||
Now that they accept mail on behalf of anything in the internal
|
||||
network, the bastion hosts will need to know how to deliver mail
|
||||
to internal hosts. In order for this to work properly, the resolvers
|
||||
on
|
||||
the bastion hosts will need to be configured to point to the internal
|
||||
name servers for DNS resolution.
|
||||
</p>
|
||||
Now that they accept mail on behalf of anything in the internal
|
||||
network, the bastion hosts will need to know how to deliver mail
|
||||
to internal hosts. In order for this to work properly, the resolvers
|
||||
on
|
||||
the bastion hosts will need to be configured to point to the internal
|
||||
name servers for DNS resolution.
|
||||
</p>
|
||||
<p>
|
||||
Queries for internal hostnames will be answered by the internal
|
||||
servers, and queries for external hostnames will be forwarded back
|
||||
out to the DNS servers on the bastion hosts.
|
||||
</p>
|
||||
Queries for internal hostnames will be answered by the internal
|
||||
servers, and queries for external hostnames will be forwarded back
|
||||
out to the DNS servers on the bastion hosts.
|
||||
</p>
|
||||
<p>
|
||||
In order for all this to work properly, internal clients will
|
||||
need to be configured to query <span class="emphasis"><em>only</em></span> the internal
|
||||
name servers for DNS queries. This could also be enforced via
|
||||
selective
|
||||
filtering on the network.
|
||||
</p>
|
||||
In order for all this to work properly, internal clients will
|
||||
need to be configured to query <span class="emphasis"><em>only</em></span> the internal
|
||||
name servers for DNS queries. This could also be enforced via
|
||||
selective
|
||||
filtering on the network.
|
||||
</p>
|
||||
<p>
|
||||
If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
|
||||
internal clients will now be able to:
|
||||
</p>
|
||||
If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
|
||||
internal clients will now be able to:
|
||||
</p>
|
||||
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
|
||||
<li class="listitem">
|
||||
Look up any hostnames in the <code class="literal">site1</code>
|
||||
and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
Look up any hostnames in the <code class="literal">site1</code>
|
||||
and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
<li class="listitem">
|
||||
Look up any hostnames in the <code class="literal">site1.internal</code> and
|
||||
<code class="literal">site2.internal</code> domains.
|
||||
</li>
|
||||
Look up any hostnames in the <code class="literal">site1.internal</code> and
|
||||
<code class="literal">site2.internal</code> domains.
|
||||
</li>
|
||||
<li class="listitem">Look up any hostnames on the Internet.</li>
|
||||
<li class="listitem">Exchange mail with both internal and external people.</li>
|
||||
</ul></div>
|
||||
<p>
|
||||
Hosts on the Internet will be able to:
|
||||
</p>
|
||||
Hosts on the Internet will be able to:
|
||||
</p>
|
||||
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
|
||||
<li class="listitem">
|
||||
Look up any hostnames in the <code class="literal">site1</code>
|
||||
and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
Look up any hostnames in the <code class="literal">site1</code>
|
||||
and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
<li class="listitem">
|
||||
Exchange mail with anyone in the <code class="literal">site1</code> and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
Exchange mail with anyone in the <code class="literal">site1</code> and
|
||||
<code class="literal">site2.example.com</code> zones.
|
||||
</li>
|
||||
</ul></div>
|
||||
<p>
|
||||
Here is an example configuration for the setup we just
|
||||
described above. Note that this is only configuration information;
|
||||
for information on how to configure your zone files, see <a class="xref" href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
|
||||
</p>
|
||||
Here is an example configuration for the setup we just
|
||||
described above. Note that this is only configuration information;
|
||||
for information on how to configure your zone files, see <a class="xref" href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
|
||||
</p>
|
||||
<p>
|
||||
Internal DNS server config:
|
||||
</p>
|
||||
Internal DNS server config:
|
||||
</p>
|
||||
<pre class="programlisting">
|
||||
|
||||
acl internals { 172.16.72.0/24; 192.168.1.0/24; };
|
||||
|
|
@ -474,8 +474,8 @@ zone "site2.internal" {
|
|||
};
|
||||
</pre>
|
||||
<p>
|
||||
External (bastion host) DNS server config:
|
||||
</p>
|
||||
External (bastion host) DNS server config:
|
||||
</p>
|
||||
<pre class="programlisting">
|
||||
acl internals { 172.16.72.0/24; 192.168.1.0/24; };
|
||||
|
||||
|
|
@ -511,9 +511,9 @@ zone "site2.example.com" {
|
|||
};
|
||||
</pre>
|
||||
<p>
|
||||
In the <code class="filename">resolv.conf</code> (or equivalent) on
|
||||
the bastion host(s):
|
||||
</p>
|
||||
In the <code class="filename">resolv.conf</code> (or equivalent) on
|
||||
the bastion host(s):
|
||||
</p>
|
||||
<pre class="programlisting">
|
||||
search ...
|
||||
nameserver 172.16.72.2
|
||||
|
|
@ -718,7 +718,7 @@ allow-update { key host1-host2. ;};
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.5.7"></a>TKEY</h2></div></div></div>
|
||||
<a name="tkey"></a>TKEY</h2></div></div></div>
|
||||
<p><span class="command"><strong>TKEY</strong></span>
|
||||
is a mechanism for automatically generating a shared secret
|
||||
between two hosts. There are several "modes" of
|
||||
|
|
@ -754,7 +754,7 @@ allow-update { key host1-host2. ;};
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.5.8"></a>SIG(0)</h2></div></div></div>
|
||||
<a name="sig0"></a>SIG(0)</h2></div></div></div>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0)
|
||||
transaction signatures as specified in RFC 2535 and RFC 2931.
|
||||
|
|
@ -815,7 +815,7 @@ allow-update { key host1-host2. ;};
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.5.9.6"></a>Generating Keys</h3></div></div></div>
|
||||
<a name="dnssec_keys"></a>Generating Keys</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>dnssec-keygen</strong></span> program is used to
|
||||
generate keys.
|
||||
|
|
@ -871,7 +871,7 @@ allow-update { key host1-host2. ;};
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.5.9.7"></a>Signing the Zone</h3></div></div></div>
|
||||
<a name="dnssec_signing"></a>Signing the Zone</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>dnssec-signzone</strong></span> program is used
|
||||
to sign a zone.
|
||||
|
|
@ -913,7 +913,7 @@ allow-update { key host1-host2. ;};
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.5.9.8"></a>Configuring Servers</h3></div></div></div>
|
||||
<a name="dnssec_config"></a>Configuring Servers</h3></div></div></div>
|
||||
<p>
|
||||
To enable <span class="command"><strong>named</strong></span> to respond appropriately
|
||||
to DNS requests from DNSSEC aware clients,
|
||||
|
|
@ -1841,7 +1841,7 @@ $ <strong class="userinput"><code>dnssec-signzone -E '' -S example.net</code></s
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.5.13"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
|
||||
<a name="ipv6"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> 9 fully supports all currently
|
||||
defined forms of IPv6 name to address and address to name
|
||||
|
|
|
|||
|
|
@ -44,13 +44,13 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#id-1.6.2">The Lightweight Resolver Library</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#lightweight_resolver">The Lightweight Resolver Library</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.6.2"></a>The Lightweight Resolver Library</h2></div></div></div>
|
||||
<a name="lightweight_resolver"></a>The Lightweight Resolver Library</h2></div></div></div>
|
||||
<p>
|
||||
Traditionally applications have been linked with a stub resolver
|
||||
library that sends recursive DNS queries to a local caching name
|
||||
|
|
|
|||
|
|
@ -47,58 +47,56 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.4.5">Comment Syntax</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#comment_syntax">Comment Syntax</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.6"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#acl_grammar"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#acl"><span class="command"><strong>acl</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.8"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_grammar"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span class="command"><strong>controls</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.10"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.11"><span class="command"><strong>include</strong></span> Statement Definition and
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#include_grammar"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#include_statement"><span class="command"><strong>include</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#key_grammar"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#key_statement"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_grammar"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_statement"><span class="command"><strong>logging</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_grammar"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_statement"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_grammar"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_statement"><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.12"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.13"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.14"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.15"><span class="command"><strong>logging</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.16"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.17"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.18"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.19"><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.20"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#options_grammar"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#options"><span class="command"><strong>options</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span class="command"><strong>server</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span class="command"><strong>server</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statschannels"><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.25"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_channels"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted-keys"><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.27"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted_keys"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.28"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#managed_keys"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#managed-keys"><span class="command"><strong>managed-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span class="command"><strong>view</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.31"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span class="command"><strong>zone</strong></span>
|
||||
Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.33"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6">Zone File</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_file">Zone File</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.3">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#mx_records">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.5">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.6">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.7"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#ipv4_reverse">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_directives">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#generate_directive"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
|
||||
|
|
@ -588,7 +586,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.4.5"></a>Comment Syntax</h3></div></div></div>
|
||||
<a name="comment_syntax"></a>Comment Syntax</h3></div></div></div>
|
||||
<p>
|
||||
The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
|
||||
comments to appear
|
||||
|
|
@ -868,7 +866,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.6"></a><span class="command"><strong>acl</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="acl_grammar"></a><span class="command"><strong>acl</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>acl</strong></span> acl-name {
|
||||
address_match_list
|
||||
};
|
||||
|
|
@ -950,7 +948,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.8"></a><span class="command"><strong>controls</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="controls_grammar"></a><span class="command"><strong>controls</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>controls</strong></span> {
|
||||
[ inet ( ip_addr | * ) [ port ip_port ]
|
||||
allow { <em class="replaceable"><code> address_match_list </code></em> }
|
||||
|
|
@ -1074,13 +1072,12 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.10"></a><span class="command"><strong>include</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="include_grammar"></a><span class="command"><strong>include</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.11"></a><span class="command"><strong>include</strong></span> Statement Definition and
|
||||
Usage</h3></div></div></div>
|
||||
<a name="include_statement"></a><span class="command"><strong>include</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>include</strong></span> statement inserts the
|
||||
specified file at the point where the <span class="command"><strong>include</strong></span>
|
||||
|
|
@ -1094,7 +1091,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.12"></a><span class="command"><strong>key</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="key_grammar"></a><span class="command"><strong>key</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>key</strong></span> <em class="replaceable"><code>key_id</code></em> {
|
||||
algorithm <em class="replaceable"><code>algorithm_id</code></em>;
|
||||
secret <em class="replaceable"><code>secret_string</code></em>;
|
||||
|
|
@ -1103,7 +1100,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.13"></a><span class="command"><strong>key</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="key_statement"></a><span class="command"><strong>key</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>key</strong></span> statement defines a shared
|
||||
secret key for use with TSIG (see <a class="xref" href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>)
|
||||
|
|
@ -1148,7 +1145,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.14"></a><span class="command"><strong>logging</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="logging_grammar"></a><span class="command"><strong>logging</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>logging</strong></span> {
|
||||
[ <span class="command"><strong>channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
|
||||
( <span class="command"><strong>file</strong></span> <em class="replaceable"><code>path_name</code></em>
|
||||
|
|
@ -1172,8 +1169,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.15"></a><span class="command"><strong>logging</strong></span> Statement Definition and
|
||||
Usage</h3></div></div></div>
|
||||
<a name="logging_statement"></a><span class="command"><strong>logging</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>logging</strong></span> statement configures a
|
||||
wide
|
||||
|
|
@ -1206,7 +1202,7 @@
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.15.6"></a>The <span class="command"><strong>channel</strong></span> Phrase</h4></div></div></div>
|
||||
<a name="channel"></a>The <span class="command"><strong>channel</strong></span> Phrase</h4></div></div></div>
|
||||
<p>
|
||||
All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
|
||||
you can make as many of them as you want.
|
||||
|
|
@ -1847,7 +1843,7 @@ category notify { null; };
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.15.8"></a>The <span class="command"><strong>query-errors</strong></span> Category</h4></div></div></div>
|
||||
<a name="query_errors"></a>The <span class="command"><strong>query-errors</strong></span> Category</h4></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>query-errors</strong></span> category is
|
||||
specifically intended for debugging purposes: To identify
|
||||
|
|
@ -2075,7 +2071,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.16"></a><span class="command"><strong>lwres</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="lwres_grammar"></a><span class="command"><strong>lwres</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<p>
|
||||
This is the grammar of the <span class="command"><strong>lwres</strong></span>
|
||||
statement in the <code class="filename">named.conf</code> file:
|
||||
|
|
@ -2091,7 +2087,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.17"></a><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="lwres_statement"></a><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>lwres</strong></span> statement configures the
|
||||
name
|
||||
|
|
@ -2142,7 +2138,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.18"></a><span class="command"><strong>masters</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="masters_grammar"></a><span class="command"><strong>masters</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting">
|
||||
<span class="command"><strong>masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> |
|
||||
<em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] };
|
||||
|
|
@ -2150,7 +2146,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.19"></a><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
<a name="masters_statement"></a><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
Usage</h3></div></div></div>
|
||||
<p><span class="command"><strong>masters</strong></span>
|
||||
lists allow for a common set of masters to be easily used by
|
||||
|
|
@ -2160,7 +2156,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.20"></a><span class="command"><strong>options</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="options_grammar"></a><span class="command"><strong>options</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<p>
|
||||
This is the grammar of the <span class="command"><strong>options</strong></span>
|
||||
statement in the <code class="filename">named.conf</code> file:
|
||||
|
|
@ -3966,7 +3962,7 @@ options {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.5"></a>Forwarding</h4></div></div></div>
|
||||
<a name="forwarding"></a>Forwarding</h4></div></div></div>
|
||||
<p>
|
||||
The forwarding facility can be used to create a large site-wide
|
||||
cache on a few servers, reducing traffic over links to external
|
||||
|
|
@ -4009,7 +4005,7 @@ options {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.6"></a>Dual-stack Servers</h4></div></div></div>
|
||||
<a name="dual_stack"></a>Dual-stack Servers</h4></div></div></div>
|
||||
<p>
|
||||
Dual-stack servers are used as servers of last resort to work
|
||||
around
|
||||
|
|
@ -4277,7 +4273,7 @@ options {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.8"></a>Interfaces</h4></div></div></div>
|
||||
<a name="interfaces"></a>Interfaces</h4></div></div></div>
|
||||
<p>
|
||||
The interfaces and ports that the server will answer queries
|
||||
from may be specified using the <span class="command"><strong>listen-on</strong></span> option. <span class="command"><strong>listen-on</strong></span> takes
|
||||
|
|
@ -4751,7 +4747,7 @@ avoid-v6-udp-ports {};
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.11"></a>UDP Port Lists</h4></div></div></div>
|
||||
<a name="port_lists"></a>UDP Port Lists</h4></div></div></div>
|
||||
<p>
|
||||
<span class="command"><strong>use-v4-udp-ports</strong></span>,
|
||||
<span class="command"><strong>avoid-v4-udp-ports</strong></span>,
|
||||
|
|
@ -4793,7 +4789,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.12"></a>Operating System Resource Limits</h4></div></div></div>
|
||||
<a name="resource_limits"></a>Operating System Resource Limits</h4></div></div></div>
|
||||
<p>
|
||||
The server's usage of many system resources can be limited.
|
||||
Scaled values are allowed when specifying resource limits. For
|
||||
|
|
@ -5150,7 +5146,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.14"></a>Periodic Task Intervals</h4></div></div></div>
|
||||
<a name="intervals"></a>Periodic Task Intervals</h4></div></div></div>
|
||||
<div class="variablelist"><dl class="variablelist">
|
||||
<dt><span class="term"><span class="command"><strong>cleaning-interval</strong></span></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -6082,7 +6078,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.22"></a>Content Filtering</h4></div></div></div>
|
||||
<a name="content_filtering"></a>Content Filtering</h4></div></div></div>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> 9 provides the ability to filter
|
||||
out DNS responses from external DNS servers containing
|
||||
|
|
@ -6205,7 +6201,7 @@ deny-answer-aliases { "example.net"; };
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.23"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
|
||||
<a name="rpz"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> 9 includes a limited
|
||||
mechanism to modify DNS responses for requests
|
||||
|
|
@ -6472,7 +6468,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.21.24"></a>Response Rate Limiting</h4></div></div></div>
|
||||
<a name="rrl"></a>Response Rate Limiting</h4></div></div></div>
|
||||
<p>
|
||||
This feature is only available when <acronym class="acronym">BIND</acronym> 9
|
||||
is compiled with the <strong class="userinput"><code>--enable-rrl</code></strong>
|
||||
|
|
@ -6910,7 +6906,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.25"></a><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
<a name="statistics_channels"></a><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>statistics-channels</strong></span> statement
|
||||
|
|
@ -6994,7 +6990,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.27"></a><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
<a name="trusted_keys"></a><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>trusted-keys</strong></span> statement defines
|
||||
|
|
@ -7034,7 +7030,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.28"></a><span class="command"><strong>managed-keys</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="managed_keys"></a><span class="command"><strong>managed-keys</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span class="command"><strong>managed-keys</strong></span> {
|
||||
<em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ;
|
||||
[<span class="optional"> <em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ; [<span class="optional">...</span>]</span>]
|
||||
|
|
@ -7172,7 +7168,7 @@ ns.domain.com.rpz-nsdname CNAME .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.31"></a><span class="command"><strong>view</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="view_statement"></a><span class="command"><strong>view</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>view</strong></span> statement is a powerful
|
||||
feature
|
||||
|
|
@ -7484,10 +7480,10 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.5.33"></a><span class="command"><strong>zone</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="zone_statement"></a><span class="command"><strong>zone</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.33.2"></a>Zone Types</h4></div></div></div>
|
||||
<a name="zone_types"></a>Zone Types</h4></div></div></div>
|
||||
<p>
|
||||
The <span class="command"><strong>type</strong></span> keyword is required
|
||||
for the <span class="command"><strong>zone</strong></span> configuration. Its
|
||||
|
|
@ -7814,7 +7810,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.33.3"></a>Class</h4></div></div></div>
|
||||
<a name="class"></a>Class</h4></div></div></div>
|
||||
<p>
|
||||
The zone's name may optionally be followed by a class. If
|
||||
a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>),
|
||||
|
|
@ -7836,7 +7832,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.5.33.4"></a>Zone Options</h4></div></div></div>
|
||||
<a name="zone_options"></a>Zone Options</h4></div></div></div>
|
||||
<div class="variablelist"><dl class="variablelist">
|
||||
<dt><span class="term"><span class="command"><strong>allow-notify</strong></span></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -8708,7 +8704,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.7.6"></a>Zone File</h2></div></div></div>
|
||||
<a name="zone_file"></a>Zone File</h2></div></div></div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="types_of_resource_records_and_when_to_use_them"></a>Types of Resource Records and When to Use Them</h3></div></div></div>
|
||||
|
|
@ -9894,7 +9890,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.6.2.4"></a>Textual expression of RRs</h4></div></div></div>
|
||||
<a name="rr_text"></a>Textual expression of RRs</h4></div></div></div>
|
||||
<p>
|
||||
RRs are represented in binary form in the packets of the DNS
|
||||
protocol, and are usually represented in highly encoded form
|
||||
|
|
@ -10097,7 +10093,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.6.3"></a>Discussion of MX Records</h3></div></div></div>
|
||||
<a name="mx_records"></a>Discussion of MX Records</h3></div></div></div>
|
||||
<p>
|
||||
As described above, domain servers store information as a
|
||||
series of resource records, each of which contains a particular
|
||||
|
|
@ -10352,7 +10348,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.6.5"></a>Inverse Mapping in IPv4</h3></div></div></div>
|
||||
<a name="ipv4_reverse"></a>Inverse Mapping in IPv4</h3></div></div></div>
|
||||
<p>
|
||||
Reverse name resolution (that is, translation from IP address
|
||||
to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain
|
||||
|
|
@ -10413,7 +10409,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.6.6"></a>Other Zone File Directives</h3></div></div></div>
|
||||
<a name="zone_directives"></a>Other Zone File Directives</h3></div></div></div>
|
||||
<p>
|
||||
The Master File Format was initially defined in RFC 1035 and
|
||||
has subsequently been extended. While the Master File Format
|
||||
|
|
@ -10428,7 +10424,7 @@ example.com. NS ns2.example.net.
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.6.6.4"></a>The <span class="command"><strong>@</strong></span> (at-sign)</h4></div></div></div>
|
||||
<a name="atsign"></a>The <span class="command"><strong>@</strong></span> (at-sign)</h4></div></div></div>
|
||||
<p>
|
||||
When used in the label (or name) field, the asperand or
|
||||
at-sign (@) symbol represents the current origin.
|
||||
|
|
@ -10439,7 +10435,7 @@ example.com. NS ns2.example.net.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.6.6.5"></a>The <span class="command"><strong>$ORIGIN</strong></span> Directive</h4></div></div></div>
|
||||
<a name="origin_directive"></a>The <span class="command"><strong>$ORIGIN</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span class="command"><strong>$ORIGIN</strong></span>
|
||||
<em class="replaceable"><code>domain-name</code></em>
|
||||
|
|
@ -10468,7 +10464,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.6.6.6"></a>The <span class="command"><strong>$INCLUDE</strong></span> Directive</h4></div></div></div>
|
||||
<a name="include_directive"></a>The <span class="command"><strong>$INCLUDE</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span class="command"><strong>$INCLUDE</strong></span>
|
||||
<em class="replaceable"><code>filename</code></em>
|
||||
|
|
@ -10504,7 +10500,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.6.6.7"></a>The <span class="command"><strong>$TTL</strong></span> Directive</h4></div></div></div>
|
||||
<a name="ttl_directive"></a>The <span class="command"><strong>$TTL</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span class="command"><strong>$TTL</strong></span>
|
||||
<em class="replaceable"><code>default-ttl</code></em>
|
||||
|
|
@ -10523,7 +10519,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.7.6.7"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</h3></div></div></div>
|
||||
<a name="generate_directive"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</h3></div></div></div>
|
||||
<p>
|
||||
Syntax: <span class="command"><strong>$GENERATE</strong></span>
|
||||
<em class="replaceable"><code>range</code></em>
|
||||
|
|
@ -10953,7 +10949,7 @@ HOST-127.EXAMPLE. MX 0 .
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.7.9.3"></a>Name Server Statistics Counters</h4></div></div></div>
|
||||
<a name="stats_counters"></a>Name Server Statistics Counters</h4></div></div></div>
|
||||
<div class="informaltable"><table border="1">
|
||||
<colgroup>
|
||||
<col width="1.150in" class="1">
|
||||
|
|
@ -11549,7 +11545,7 @@ HOST-127.EXAMPLE. MX 0 .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.7.9.4"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
|
||||
<a name="zone_stats"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
|
||||
<div class="informaltable"><table border="1">
|
||||
<colgroup>
|
||||
<col width="1.150in" class="1">
|
||||
|
|
@ -11703,7 +11699,7 @@ HOST-127.EXAMPLE. MX 0 .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.7.9.5"></a>Resolver Statistics Counters</h4></div></div></div>
|
||||
<a name="resolver_stats"></a>Resolver Statistics Counters</h4></div></div></div>
|
||||
<div class="informaltable"><table border="1">
|
||||
<colgroup>
|
||||
<col width="1.150in" class="1">
|
||||
|
|
@ -12086,7 +12082,7 @@ HOST-127.EXAMPLE. MX 0 .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.7.9.6"></a>Socket I/O Statistics Counters</h4></div></div></div>
|
||||
<a name="socket_stats"></a>Socket I/O Statistics Counters</h4></div></div></div>
|
||||
<p>
|
||||
Socket I/O statistics counters are defined per socket
|
||||
types, which are
|
||||
|
|
@ -12241,7 +12237,7 @@ HOST-127.EXAMPLE. MX 0 .
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id-1.7.7.9.7"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
|
||||
<a name="bind8_compatibility"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
|
||||
<p>
|
||||
Most statistics counters that were available
|
||||
in <span class="command"><strong>BIND</strong></span> 8 are also supported in
|
||||
|
|
|
|||
|
|
@ -45,10 +45,10 @@
|
|||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot_and_setuid"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3.6">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3.7">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#setuid">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
|
||||
</dl>
|
||||
|
|
@ -113,7 +113,7 @@ zone "example.com" {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.8.3"></a><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span>
|
||||
<a name="chroot_and_setuid"></a><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span>
|
||||
</h2></div></div></div>
|
||||
<p>
|
||||
On UNIX servers, it is possible to run <acronym class="acronym">BIND</acronym>
|
||||
|
|
@ -139,7 +139,7 @@ zone "example.com" {
|
|||
</p>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.8.3.6"></a>The <span class="command"><strong>chroot</strong></span> Environment</h3></div></div></div>
|
||||
<a name="chroot"></a>The <span class="command"><strong>chroot</strong></span> Environment</h3></div></div></div>
|
||||
<p>
|
||||
In order for a <span class="command"><strong>chroot</strong></span> environment
|
||||
to
|
||||
|
|
@ -167,7 +167,7 @@ zone "example.com" {
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.8.3.7"></a>Using the <span class="command"><strong>setuid</strong></span> Function</h3></div></div></div>
|
||||
<a name="setuid"></a>Using the <span class="command"><strong>setuid</strong></span> Function</h3></div></div></div>
|
||||
<p>
|
||||
Prior to running the <span class="command"><strong>named</strong></span> daemon,
|
||||
use
|
||||
|
|
|
|||
|
|
@ -44,15 +44,15 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2">Common Problems</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#common_problems">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2.2">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.4">Where Can I Get Help?</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#more_help">Where Can I Get Help?</a></span></dt>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.9.2"></a>Common Problems</h2></div></div></div>
|
||||
<a name="common_problems"></a>Common Problems</h2></div></div></div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.9.2.2"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div>
|
||||
|
|
@ -94,7 +94,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id-1.9.4"></a>Where Can I Get Help?</h2></div></div></div>
|
||||
<a name="more_help"></a>Where Can I Get Help?</h2></div></div></div>
|
||||
<p>
|
||||
The Internet Systems Consortium
|
||||
(<acronym class="acronym">ISC</acronym>) offers a wide range
|
||||
|
|
|
|||
|
|
@ -43,115 +43,100 @@
|
|||
<div class="titlepage"><div><div><h1 class="title">
|
||||
<a name="Bv9ARM.ch10"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>
|
||||
</h1></div></div></div>
|
||||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl class="toc">
|
||||
<dt><span class="section"><a href="Bv9ARM.ch10.html#dns_history">DNS</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch10.html#bind_history">BIND</a></span></dt>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="dns_history"></a>DNS</h2></div></div></div>
|
||||
<p><a name="historical_dns_information"></a>
|
||||
Although the "official" 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 a 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,
|
||||
"Domain Names-Concepts and Facilities", and RFC 1035, "Domain
|
||||
Names-Implementation and Specification" were published and
|
||||
became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
|
||||
built.
|
||||
</p>
|
||||
<p>
|
||||
Although the "official" 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 a 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,
|
||||
"Domain Names-Concepts and Facilities", and RFC 1035, "Domain
|
||||
Names-Implementation and Specification" were published and
|
||||
became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
|
||||
built.
|
||||
</p>
|
||||
The first working domain name server, called "Jeeves", 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 <acronym class="acronym">DNS</acronym> server for
|
||||
Unix machines, the Berkeley Internet
|
||||
Name Domain (<acronym class="acronym">BIND</acronym>) 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).
|
||||
</p>
|
||||
<p>
|
||||
The first working domain name server, called "Jeeves", 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 <acronym class="acronym">DNS</acronym> server for
|
||||
Unix machines, the Berkeley Internet
|
||||
Name Domain (<acronym class="acronym">BIND</acronym>) 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).
|
||||
</p>
|
||||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="bind_history"></a>BIND</h2></div></div></div>
|
||||
Versions of <acronym class="acronym">BIND</acronym> 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 <acronym class="acronym">BIND</acronym>
|
||||
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 <acronym class="acronym">BIND</acronym> for 2 years, from 1985
|
||||
to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development
|
||||
during that time: Doug Kingston, Craig Partridge, Smoot
|
||||
Carl-Mitchell,
|
||||
Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
|
||||
handled by Mike Karels and Øivind Kure.
|
||||
</p>
|
||||
<p>
|
||||
Versions of <acronym class="acronym">BIND</acronym> 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 <acronym class="acronym">BIND</acronym>
|
||||
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 <acronym class="acronym">BIND</acronym> for 2 years, from 1985
|
||||
to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development
|
||||
during that time: Doug Kingston, Craig Partridge, Smoot
|
||||
Carl-Mitchell,
|
||||
Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
|
||||
handled by Mike Karels and Øivind Kure.
|
||||
</p>
|
||||
<acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were
|
||||
released by Digital Equipment
|
||||
Corporation (now Compaq Computer Corporation). Paul Vixie, then
|
||||
a DEC employee, became <acronym class="acronym">BIND</acronym>'s
|
||||
primary caretaker. He 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>
|
||||
<acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were
|
||||
released by Digital Equipment
|
||||
Corporation (now Compaq Computer Corporation). Paul Vixie, then
|
||||
a DEC employee, became <acronym class="acronym">BIND</acronym>'s
|
||||
primary caretaker. He 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>
|
||||
In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by
|
||||
Vixie Enterprises. Paul
|
||||
Vixie became <acronym class="acronym">BIND</acronym>'s principal
|
||||
architect/programmer.
|
||||
</p>
|
||||
<p>
|
||||
In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by
|
||||
Vixie Enterprises. Paul
|
||||
Vixie became <acronym class="acronym">BIND</acronym>'s principal
|
||||
architect/programmer.
|
||||
</p>
|
||||
<acronym class="acronym">BIND</acronym> versions from 4.9.3 onward
|
||||
have been developed and maintained
|
||||
by the Internet Systems Consortium and its predecessor,
|
||||
the Internet Software Consortium, with support being provided
|
||||
by ISC's sponsors.
|
||||
</p>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> versions from 4.9.3 onward
|
||||
have been developed and maintained
|
||||
by the Internet Systems Consortium and its predecessor,
|
||||
the Internet Software Consortium, with support being provided
|
||||
by ISC's sponsors.
|
||||
</p>
|
||||
As co-architects/programmers, Bob Halley and
|
||||
Paul Vixie released the first production-ready version of
|
||||
<acronym class="acronym">BIND</acronym> version 8 in May 1997.
|
||||
</p>
|
||||
<p>
|
||||
As co-architects/programmers, Bob Halley and
|
||||
Paul Vixie released the first production-ready version of
|
||||
<acronym class="acronym">BIND</acronym> version 8 in May 1997.
|
||||
</p>
|
||||
BIND version 9 was released in September 2000 and is a
|
||||
major rewrite of nearly all aspects of the underlying
|
||||
BIND architecture.
|
||||
</p>
|
||||
<p>
|
||||
BIND version 9 was released in September 2000 and is a
|
||||
major rewrite of nearly all aspects of the underlying
|
||||
BIND architecture.
|
||||
</p>
|
||||
BIND versions 4 and 8 are officially deprecated.
|
||||
No additional development is done
|
||||
on BIND version 4 or BIND version 8.
|
||||
</p>
|
||||
<p>
|
||||
BIND versions 4 and 8 are officially deprecated.
|
||||
No additional development is done
|
||||
on BIND version 4 or BIND version 8.
|
||||
</p>
|
||||
<p>
|
||||
<acronym class="acronym">BIND</acronym> development work is made
|
||||
possible today by the sponsorship
|
||||
of several corporations, and by the tireless work efforts of
|
||||
numerous individuals.
|
||||
</p>
|
||||
</div>
|
||||
<acronym class="acronym">BIND</acronym> development work is made
|
||||
possible today by the sponsorship
|
||||
of several corporations, and by the tireless work efforts of
|
||||
numerous individuals.
|
||||
</p>
|
||||
</div>
|
||||
<div class="navfooter">
|
||||
<hr>
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@
|
|||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#id-1.12.3.4">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#more_about_bind">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
</div>
|
||||
|
|
@ -467,7 +467,7 @@
|
|||
</div>
|
||||
<div class="section">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id-1.12.3.4"></a>Other Documents About <acronym class="acronym">BIND</acronym>
|
||||
<a name="more_about_bind"></a>Other Documents About <acronym class="acronym">BIND</acronym>
|
||||
</h3></div></div></div>
|
||||
<p></p>
|
||||
<div class="bibliography">
|
||||
|
|
|
|||
|
|
@ -50,39 +50,39 @@
|
|||
<dl class="toc">
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch01.html">1. Introduction</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.3">Scope of Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.4">Organization of This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.5">Conventions Used in This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#doc_scope">Scope of Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#organization">Organization of This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#conventions">Conventions Used in This Document</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#dns_overview">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.3">DNS Fundamentals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.4">Domains and Domain Names</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.5">Zones</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.6">Authoritative Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.7">Caching Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#id-1.2.6.8">Name Servers in Multiple Roles</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#dns_fundamentals">DNS Fundamentals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#domain_names">Domains and Domain Names</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#zones">Zones</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#auth_servers">Authoritative Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#cache_servers">Caching Name Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch01.html#multi_role">Name Servers in Multiple Roles</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch02.html">2. <acronym class="acronym">BIND</acronym> Resource Requirements</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.2">Hardware requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.3">CPU Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.4">Memory Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.5">Name Server Intensive Environment Issues</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#id-1.3.6">Supported Operating Systems</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#hw_req">Hardware requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#cpu_req">CPU Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#mem_req">Memory Requirements</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#intensive_env">Name Server Intensive Environment Issues</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch02.html#supported_os">Supported Operating Systems</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch03.html">3. Name Server Configuration</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.3.2">A Caching-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.3.3">An Authoritative-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#cache_only_sample">A Caching-only Name Server</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#auth_only_sample">An Authoritative-only Name Server</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.4">Load Balancing</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5">Name Server Operations</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#load_balancing">Load Balancing</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#ns_operations">Name Server Operations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5.2">Tools for Use With the Name Server Daemon</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#id-1.4.5.3">Signals</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#tools">Tools for Use With the Name Server Daemon</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch03.html#signals">Signals</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch04.html">4. Advanced DNS Features</a></span></dt>
|
||||
|
|
@ -91,8 +91,8 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.5">Split DNS</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.5.5">Example split DNS setup</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns">Split DNS</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns_sample">Example split DNS setup</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.5">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
|
||||
|
|
@ -102,13 +102,13 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.9">TSIG Key Based Access Control</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.10">Errors</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.7">TKEY</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.8">SIG(0)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#tkey">TKEY</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#sig0">SIG(0)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.6">Generating Keys</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.7">Signing the Zone</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.9.8">Configuring Servers</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_keys">Generating Keys</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_signing">Signing the Zone</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_config">Configuring Servers</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
|
||||
<dd><dl>
|
||||
|
|
@ -140,7 +140,7 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.8">Specifying the engine on the command line</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.9">Running named with automatic zone re-signing</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#ipv6">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.6">Address Lookups Using AAAA Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.7">Address to Name Lookups Using Nibble Format</a></span></dt>
|
||||
|
|
@ -148,7 +148,7 @@
|
|||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch05.html">5. The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#id-1.6.2">The Lightweight Resolver Library</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#lightweight_resolver">The Lightweight Resolver Library</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch06.html">6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference</a></span></dt>
|
||||
|
|
@ -156,58 +156,56 @@
|
|||
<dt><span class="section"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.4.5">Comment Syntax</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#comment_syntax">Comment Syntax</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.6"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#acl_grammar"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#acl"><span class="command"><strong>acl</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.8"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_grammar"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span class="command"><strong>controls</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.10"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.11"><span class="command"><strong>include</strong></span> Statement Definition and
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#include_grammar"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#include_statement"><span class="command"><strong>include</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#key_grammar"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#key_statement"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_grammar"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_statement"><span class="command"><strong>logging</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_grammar"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_statement"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_grammar"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_statement"><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.12"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.13"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.14"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.15"><span class="command"><strong>logging</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.16"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.17"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.18"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.19"><span class="command"><strong>masters</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.20"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#options_grammar"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#options"><span class="command"><strong>options</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span class="command"><strong>server</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span class="command"><strong>server</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statschannels"><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.25"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_channels"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted-keys"><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.27"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted_keys"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.28"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#managed_keys"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#managed-keys"><span class="command"><strong>managed-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span class="command"><strong>view</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.31"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span class="command"><strong>zone</strong></span>
|
||||
Statement Grammar</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.5.33"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6">Zone File</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_file">Zone File</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.3">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#mx_records">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.5">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.6">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#id-1.7.6.7"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#ipv4_reverse">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_directives">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#generate_directive"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
|
||||
|
|
@ -219,19 +217,19 @@
|
|||
<dt><span class="chapter"><a href="Bv9ARM.ch07.html">7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot_and_setuid"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3.6">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#id-1.8.3.7">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#setuid">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch08.html">8. Troubleshooting</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2">Common Problems</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#common_problems">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2.2">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.3">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.4">Where Can I Get Help?</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch08.html#more_help">Where Can I Get Help?</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="appendix"><a href="Bv9ARM.ch09.html">A. Release Notes</a></span></dt>
|
||||
<dd><dl>
|
||||
|
|
@ -249,10 +247,6 @@
|
|||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="appendix"><a href="Bv9ARM.ch10.html">B. A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch10.html#dns_history">DNS</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch10.html#bind_history">BIND</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="appendix"><a href="Bv9ARM.ch11.html">C. General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt>
|
||||
|
|
@ -260,7 +254,7 @@
|
|||
<dd><dl>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#rfcs">Request for Comments (RFCs)</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#internet_drafts">Internet Drafts</a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#id-1.12.3.4">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
|
||||
<dt><span class="section"><a href="Bv9ARM.ch11.html#more_about_bind">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="appendix"><a href="Bv9ARM.ch12.html">D. BIND 9 DNS Library Support</a></span></dt>
|
||||
|
|
|
|||
Loading…
Reference in a new issue