From 6b07f707e118652c501afbd5381e56c4220b08fb Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Mon, 12 Jun 2000 20:42:37 +0000 Subject: [PATCH] new ARM version from Mary --- doc/arm/Bv9ARM.1.html | 236 ++-- doc/arm/Bv9ARM.2.html | 6 +- doc/arm/Bv9ARM.3.html | 349 +++--- doc/arm/Bv9ARM.4.html | 696 ++++++----- doc/arm/Bv9ARM.5.html | 2598 +++++++++++++++++++++++------------------ doc/arm/Bv9ARM.6.html | 104 +- doc/arm/Bv9ARM.7.html | 96 +- doc/arm/Bv9ARM.8.html | 196 ++-- doc/arm/Bv9ARM.css | 397 ++++++- doc/arm/Bv9ARM.html | 58 +- 10 files changed, 2616 insertions(+), 2120 deletions(-) diff --git a/doc/arm/Bv9ARM.1.html b/doc/arm/Bv9ARM.1.html index 949b3790e8..8cc2eaf912 100644 --- a/doc/arm/Bv9ARM.1.html +++ b/doc/arm/Bv9ARM.1.html @@ -5,69 +5,66 @@ Section 1. Introduction -

    Section 1. Introduction

    -

The Internet Domain Name System (DNS) consists of the syntax to specify the names of entities in the Internet in a hierarchical manner, the rules used for delegating authority over names, and the system implementation that actually maps names to Internet addresses. DNS data is maintained in a group of distributed hierarchical databases.

-
    +

    1.1 Scope of Document

    -
+

The Berkeley Internet Name Domain (BIND) implements an Internet nameserver for a number of operating systems. This document provides basic information about the installation and care of the Internet Software Consortium (ISC) BIND version 9 software package for system administrators.

-
    +

    1.2 Organization of This Document

    -
+

-In this document, -Section 1 - introduces the basic DNS and BIND concepts. -Section 2 - describes resource requirements for running BIND in various environments. Information in -Section 3 - is +In this document, +Section 1 + introduces the basic DNS and BIND concepts. +Section 2 + describes resource requirements for running BIND in various environments. Information in +Section 3 + is task-oriented - in its presentation and is organized functionally, to aid in the process of installing the BINDv9 software. The task-oriented section is followed by -Section 4 -, which contains more advanced concepts that the system administrator may need for implementing certain options. The contents of -Section 5 - are organized as in a reference manual to aid in the ongoing maintenance of the software. -Section 6 - addresses security considerations, and -Section 7 - contains troubleshooting help. The main body of the document is followed by several -Appendices - which contain useful reference information, such as a + in its presentation and is organized functionally, to aid in the process of installing the BINDv9 software. The task-oriented section is followed by +Section 4 +, which contains more advanced concepts that the system administrator may need for implementing certain options. The contents of +Section 5 + are organized as in a reference manual to aid in the ongoing maintenance of the software. +Section 6 + addresses security considerations, and +Section 7 + contains troubleshooting help. The main body of the document is followed by several +Appendices + which contain useful reference information, such as a Glossary - and a + and a Bibliography , as well as historic information related to BIND and the Domain Name System.

-

    1.3 Conventions Used in This Document

    -
+

@@ -78,7 +75,7 @@ In this document, we use the following general typographic conventions:

- + To describe:

@@ -86,8 +83,8 @@ To describe:

- -Style: + +We use the style:

@@ -96,13 +93,14 @@ Style:

-a pathname, filename, URL, hostname, mailing list name, or new term or concept

+a pathname, filename, URL, hostname,
+mailing list name, or new term or concept

- + Italic

@@ -166,16 +164,16 @@ The following conventions are used in descriptions of the BIND configuration fil

- -When describing: + +To describe:

- -Style Used: + +We use the style:

@@ -190,8 +188,8 @@ keywords

- -Sans Serif Bold + +Sans Serif Bold

@@ -276,93 +274,93 @@ Text is enclosed in square brackets

-
    +

    1.4 Discussion of Domain Name System (DNS) Basics and BIND

    -
+

-The purpose of this document is to explain the installation and basic upkeep of the BIND software package, and we begin by reviewing the fundamentals of the domain naming system as they relate to BIND. BIND consists of a +The purpose of this document is to explain the installation and basic upkeep of the BIND software package, and we begin by reviewing the fundamentals of the domain naming system as they relate to BIND. BIND consists of a nameserver (or "daemon") called named and a resolver - library. The BIND server runs in the background, servicing queries on a well known network port. The standard port for UDP and TCP, usually port 53, is specified in - /etc/services -. The + library. The BIND server runs in the background, servicing queries on a well known network port. The standard port for the User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), usually port 53, is specified in + + +/etc/services +. The resolver is a set of routines residing in a system library that provides the interface that programs can use to access the domain name services.

-
    +

    1.4.1 Nameservers

    -
+

-A nameserver (NS) is a program that stores information about named resources and responds to queries from programs called +A nameserver (NS) is a program that stores information about named resources and responds to queries from programs called resolvers which act as client processes. The basic function of an NS is to provide information about network objects by answering queries.

-With the nameserver, the network can be broken into a hierarchy of domains. The name space is organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The name of the domain is the concatenation of all the labels of the domains from the root to the current domain. This is represented in written form as a string of labels listed from right to left and separated by dots. A label need only be unique within its domain. The whole name space is partitioned into areas called +With the nameserver, the network can be broken into a hierarchy of domains. The name space is organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The name of the domain is the concatenation of all the labels of the domains from the root to the current domain. This is represented in written form as a string of labels listed from right to left and separated by dots. A label need only be unique within its domain. The whole name space is partitioned into areas called zones -, each starting at a domain and extending down to the leaf domains or to domains where other zones start. Zones usually represent administrative boundaries. For example, a domain name for a host at the company +, each starting at a domain and extending down to the leaf domains or to domains where other zones start. Zones usually represent administrative boundaries. For example, a domain name for a host at the company Example, Inc. would be:

- + ourhost.example.com

-The top level domain for corporate organizations is +where com -; + is the top level domain to which +ourhost.example.com + belongs, example - is a subdomain of -.com -; and + is a subdomain of +com +, and ourhost is the name of the host.

-The specifications for the domain nameserver are defined in RFC1034, RFC1035 and RFC974. These documents can be found in
+The specifications for the domain nameserver are defined in the RFC 1034, RFC 1035 and RFC 974. These documents can be found in
/usr/src/etc/named/doc - in 4.4BSD or are available via -FTP - from
+ in 4.4BSD or are available via File Transfer Protocol (FTP) from
ftp://www.isi.edu/in-notes/ or via the Web at http://www.ietf.org/rfc/ -. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related -man - pages: +. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related man pages: named and resolver .

-
    +

    1.4.2 Types of Zones

    -
+

@@ -370,57 +368,59 @@ As we stated previously, a zone is a point of delegation in the DNS tree. A zone

-To properly operate a nameserver, it is important to understand the difference between a +To properly operate a nameserver, it is important to understand the difference between a zone - and a + and a domain .

-As an example, consider the +For instance, consider the example.com - domain, which includes names such as + domain which includes names such as host.aaa.example.com -and +and host.bbb.example.com - even though the + even though the example.com - zone includes only delegations for the + zone includes only delegations for the aaa.example.com - and + and bbb.example.com - zones. A zone can map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other nameservers. Every name in the DNS tree is a + zones. A zone can map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other nameservers. Every name in the DNS tree is a domain -, even if it is +, even if it is terminal -, that is, has no +, that is, has no subdomains -. Every subdomain is a domain and every domain except the root is also a subdomain. The terminology is not intuitive and it is suggested that you read RFCs 1033, 1034, and 1035 to gain a complete understanding of this difficult and subtle topic.

+. Every subdomain is a domain and every domain except the root is also a subdomain. The terminology is not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to gain a complete understanding of this difficult and subtle topic.

Though BIND is a Domain Nameserver, it deals primarily in terms of zones. The primary and secondary declarations in the named.conf - file specify zones, not domains. When you ask some other site if it is willing to be a secondary server for your + file specify zones, not domains. When you ask some other site if it is willing to be a secondary server for your domain , you are actually asking for secondary service for some collection of zones.

-Each zone will have one +Each zone will have one primary master - (also called + (also called primary -) server which loads the zone contents from some local file edited by humans or perhaps generated mechanically from some other local file which is edited by humans. There there will be some number of -secondary master -servers, which load the zone contents using the DNS protocol (that is, the secondary servers will contact the primary and fetch the zone data using TCP). This set of servers--the primary and all of its secondaries--should be listed in the NS records in the parent zone and will constitute a +) server which loads the zone contents from some local file edited by humans or perhaps generated mechanically from some other local file which is edited by humans. There there will be some number of +slave + (also called +secondary) +servers, which load the zone contents using the DNS protocol (that is, the secondary servers will contact the primary and fetch the zone data using TCP). This set of servers--the primary and all of its secondaries--should be listed in the NS records in the parent zone and will constitute a delegation . This set of servers must also be listed in the zone file itself, usually under the @ - name which indicates the + name which indicates the top level - or + or root of the current zone. You can list servers in the zone's top-level @ @@ -430,115 +430,117 @@ root

-Any servers listed in the NS records must be configured as - -authoritative for the zone. A server is authoritative for a zone when it has been configured to answer questions for that zone with authority, which it does by setting the "authoritative answer" (AA) bit in reply packets. A server may be authoritative for more than one zone. The authoritative data for a zone is composed of all of the Resource Records (RRs)--the data associated with names in a tree-structured name space--attached to all of the nodes from the top node of the zone down to leaf nodes or nodes above - -cuts around the bottom edge of the zone.

+Any servers listed in the NS records must be configured as +authoritative + for the zone. A server is authoritative for a zone when it has been configured to answer questions for that zone with authority, which it does by setting the "authoritative answer" (AA) bit in reply packets. A server may be authoritative for more than one zone. The authoritative data for a zone is composed of all of the Resource Records (RRs)--the data associated with names in a tree-structured name space--attached to all of the nodes from the top node of the zone down to leaf nodes or nodes above cuts around the bottom edge of the zone.

Adding a zone as a type master or type slave will tell the server to answer questions for the zone authoritatively. If the server is able to load the zone into memory without any errors it will set the AA bit when it replies to queries for the zone. See RFCs 1034 and 1035 for more information about the AA bit.

-
    +

    1.4.3 Servers

    -
+

-A DNS server can be master for some zones and slave for others or can be only a master, or only a slave, or can serve no zones and just answer queries via its +A DNS server can be master for some zones and slave for others or can be only a master, or only a slave, or can serve no zones and just answer queries via its cache -. Master servers are often also called +. Master servers are often also called primaries - and slave servers are often also called + and slave servers are often also called secondaries . Both master/primary and slave/secondary servers are authoritative for a zone.

-All servers keep data in their cache until the data expires, based on a TTL (Time To Live) field which is maintained for all resource records.

+All servers keep data in their cache until the data expires, based on a Time To Live (TTL) field which is maintained for all resource records.

-
    +
    1.4.3.1 Master Server
    -
+

-The -primary master - server is the ultimate source of information about a domain. The primary master is an authoritative server configured to be the source of zone transfer for one or more secondary servers. The primary master server obtains data for the zone from a file on disk.

+The +primary master server + is the ultimate source of information about a domain. The primary master is an authoritative server configured to be the source of zone transfer for one or more secondary servers. The primary master server obtains data for the zone from a file on disk.

-
    +
    1.4.3.2 Slave Server
    -
+

-A +A slave server -, also called a +, also called a secondary server -, is an authoritative server that uses zone transfers from the primary master server to retrieve the zone data. Optionally, the slave server obtains zone data from a cache on disk. Slave servers provide necessary redundancy. All secondary/slave servers are named in the NS resource records (RRs) for the zone.

+, is an authoritative server that uses zone transfers from the primary master server to retrieve the zone data. Optionally, the slave server obtains zone data from a cache on disk. Slave servers provide necessary redundancy. All secondary/slave servers are named in the NS RRs for the zone.

-
    +
    1.4.3.3 Caching Only Server
    -
+

-Some servers are +Some servers are caching only servers . This means that the server caches the information that it receives and uses it until the data expires. A caching only server is a server that is not authoritative for any zone. This server services queries and asks other servers, who have the authority, for the information it needs.

-
    +
    1.4.3.4 Forwarding Server
    -
+

-Instead of interacting with the nameservers for the root and other domains, a +Instead of interacting with the nameservers for the root and other domains, a forwarding server - always forwards queries it cannot satisfy from its authoritative data or cache to a fixed list of other servers. The forwarded queries are also known as -recursive queries, -the same type as a client would send to a server. There may be one or more servers forwarded to, and they are queried in turn until the list is exhausted or an answer is found. A forwarding server is typically used when you do not wish all the servers at a given site to interact with the rest of the Internet servers. A typical scenario would involve a number of internal DNS servers, and an internet firewall. The servers which cannot pass packets through the firewall would forward to the server which can, which would ask the internet DNS servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete cache of information that all the workstations can take advantage of.

+ always forwards queries it cannot satisfy from its authoritative data or cache to a fixed list of other servers. The forwarded queries are also known as +recursive queries +, the same type as a client would send to a server. There may be one or more servers forwarded to, and they are queried in turn until the list is exhausted or an answer is found. A forwarding server is typically used when you do not wish all the servers at a given site to interact with the rest of the Internet servers. A typical scenario would involve a number of internal DNS servers and an Internet firewall. Servers unable to pass packets through the firewall would forward to the server that can do it, and that server would query the Internet DNS servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete cache of information that all the workstations can take advantage of.

There is no prohibition against declaring a server to be a forwarder even though it has master and/or slave zones as well; the effect will still be that anything in the local server's cache or zones will be answered, and anything else will be forwarded using the forwarders list.

-
    +
    1.4.3.5 Stealth Server
    -
+

-A stealth server is a server that answers authoritatively for a zone, but is not listed in that zone's NS records. Stealth servers can be used as a way to centralize distribution of a zone, without having to edit the zone on a remote nameserver. Where the master file for a zone resides on a stealth server in this way, it is often referred to as a "hidden primary" configuration. Stealth servers can also be a way to keep a local copy of a zone for rapid access to the zone's records, even if all "official" nameservers for the zone are inaccessible.

+A +stealth server + is a server that answers authoritatively for a zone, but is not listed in that zone's NS records. Stealth servers can be used as a way to centralize distribution of a zone, without having to edit the zone on a remote nameserver. Where the master file for a zone resides on a stealth server in this way, it is often referred to as a "hidden primary" configuration. Stealth servers can also be a way to keep a local copy of a zone for rapid access to the zone's records, even if all "official" nameservers for the zone are inaccessible.

+ diff --git a/doc/arm/Bv9ARM.2.html b/doc/arm/Bv9ARM.2.html index 20a50567b6..9242475b65 100644 --- a/doc/arm/Bv9ARM.2.html +++ b/doc/arm/Bv9ARM.2.html @@ -25,7 +25,7 @@ DNS hardware requirements have traditionally been quite modest. For many install

-The DNSSEC and IPv6 features of BINDv9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BINDv9 is now fully multithreaded, allowing full utilization of multiprocessor systems, for installations that need it.

+The DNSSEC and IPv6 features of BINDv9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. BINDv9 is now fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.

    @@ -49,7 +49,7 @@ CPU requirements for BINDv9 range from i486-class machines for serving of static

    -The memory of the server has to be large enough to fit the cache and zones loaded off disk. Future releases of BINDv9 will provide methods to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. It is still good practice to have enough memory to load all zone and cache data into memory--unfortunately, the best way to determine this for a given installation is to watch the nameserver in operation. After a few weeks, the server process should reach a relatively stable size where entries are expiring from the cache as fast as they are being inserted. Ideally, the resource limits should be set higher than this stable size.

    +The memory of the server has to be large enough to fit the cache and zones loaded off disk. Future releases of BINDv9 will provide methods to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. It is still good practice to have enough memory to load all zone and cache data into memory--unfortunately, the best way to determine this for a given installation is to watch the nameserver in operation. After a few weeks the server process should reach a relatively stable size where entries are expiring from the cache as fast as they are being inserted. Ideally, the resource limits should be set higher than this stable size.

    @@ -86,6 +86,8 @@ Sun Solaris 2.6, 7, 8 (beta)
    FreeBSD 3.4-STABLE
    NetBSD-current with "unproven" pthreads

+ diff --git a/doc/arm/Bv9ARM.3.html b/doc/arm/Bv9ARM.3.html index a505907f16..18348e86cd 100644 --- a/doc/arm/Bv9ARM.3.html +++ b/doc/arm/Bv9ARM.3.html @@ -5,251 +5,260 @@ Section 3. Nameserver Configuration -
    +

    - + Section 3. Nameserver Configuration

    -
+

- + In this section we provide some suggested configurations along with guidelines for their use. We also address the topic of reasonable option setting.

-
    +

    - + 3.1 Sample Configuration and Logging

    -
+ 

-
-logging {
-        channel named_log {
-             file "logs/named.log";
-             print-time yes;
-             print-category yes;
-             print-severity yes;
-             severity info;
+logging {
+       channel named_log {
+           file "logs/named.log";
+           print-time yes;
+           print-category yes;
+           print-severity yes;
+           severity info;
 };
-       channel security_log {
-             file "logs/security.log " versions 7 ;
-             print-time yes ;
+       channel security_log {
+           file "logs/security.log" versions 7 ;
+           print-time yes;
 };
-       category default { named_log; default_debug; };
-             category security { security_log };
+       category default { named_log; default_debug; };
+       category security { security_log };
 };
-                                                    // The two corporate subnets.
-                                                    // Use real IP numbers
-                                                    // here in the real world.
-acl corpnet { 192.168.4.0/24; 192.168.7.0/24; };
-                              // The options statement.
-options {
-   directory "/etc/namedb";      // Directory
-   pid-file "named.pid";         // Put .pid file in named directory.
-   check-names master fail;              // Fail on db errors in master zones.
-   check-names slave warn;               // Warn about db errors
-                                                    // in slave zones.
-   check-names response warn;            // Warn about invalid responses
-   use-id-pool yes;                      // Help prevent spoofing
-   host-statistics yes;                  // Keep track of hosts/servers
-                                                    // we've talked to.
-   listen-on { 192.168.7.20; };                     // Listen on this address.
+							// The two corporate subnets.
+							// Use real IP numbers
+							// here in the real world.
+acl corpnet { 192.168.4.0/24; 192.168.7.0/24; };
+							// The options statement.
+options {	
+   directory "/etc/namedb";				// Directory
+   pid-file "named.pid";				// Put .pid file in named directory.
+   check-names master fail;				// Fail on db errors in master zones.
+   check-names slave warn;				// Warn about db errors
+							// in slave zones.
+   check-names response warn;				// Warn about invalid responses
+   use-id-pool yes;					// Help prevent spoofing
+   host-statistics yes;					// Keep track of hosts/servers
+							// we've talked to.
+   listen-on { 192.168.7.20; };				// Listen on this address.
    query-source address 192.168.7.20 port 53 ;
-                                                    // Source queries from port 53
-                                                    // to get past firewall.
-   allow-transfer { none; };             // Don't allow anyone to
-                                                    // transfer zones.
-   allow-query { corpnet; };                        // Allow only corpnets to query server.
-                                                    // Helps prevent DoS, spoofing.
-   allow-recursion { corpnet; };                    // Same, except this is for recursion.
+							// Source queries from port 53
+							// to get past firewall.
+   allow-transfer { none; };				// Don't allow anyone to
+							// transfer zones.
+   allow-query { corpnet; };				// Allow only corpnets to query server.
+							// Helps prevent DoS, spoofing.
+   allow-recursion { corpnet; };			// Same, except this is for recursion.
 };
-
-   include "keys.conf";                   // Include a keys.conf with
-                                                     // TSIG/DNSSEC keys.
-                                                     // Shouldn't be readable to anyone
-                                                     // except BIND user.
-   zone "."{ type hint; file "local/named.root";
-};                                                    // root hints
-
-   zone "0.0.127.IN-ADDR.ARPA" {
-   type master; file "local/localhost.db"; notify no;
-                                                     // localhost
-};
-
-   zone "example.com" {                      // Example zone for "example.com".
-   type master;                             // It's a master zone.
-   file "m/example.com.db";                 // The file is here.
-   allow-query { any; };                      // Allow anyone to query.
-   allow-transfer { corpnet; };                         // Only allow corp nets to transfer zone.
-}; 
- 
-   zone "offsite.example.com" {              // Example zone for an off-site corp zone.
-   type slave;                                        // It's a slave zone.
-   masters { 192.168.4.12; };                                // The master is at this address.
-   file "s/offsite.example.com.db";             // The file is here.
-   notify no;                                             // Don't worry about NOTIFYing.
-allow-query { any; };                                 // Allow anyone to query.
+
+
+

+include "keys.conf";					// Include a keys.conf with
+								// TSIG/DNSSEC keys.
+								// Shouldn't be readable to anyone
+								// except BIND user.
+zone "."{ type hint; file "local/named.root"; };
+								// root hints
+zone "0.0.127.IN-ADDR.ARPA" {
+
+

+        type master; file "local/localhost.db"; notify no;
+								// localhost
+};
+
zone "example.com" {			// Example zone for "example.com".
+type master;				// It's a master zone.
+file "m/example.com.db";		// The file is here.
+allow-query { any; };			// Allow anyone to query.
+allow-transfer { corpnet; };		// Only allow corp nets to transfer zone.
 };
 
+

+zone "offsite.example.com" {		// Example zone for an off-site corp zone.
+type slave;					// It's a slave zone.
+masters { 192.168.4.12; };			// The master is at this address.
+file "s/offsite.example.com.db";		// The file is here.
+notify no;				// Don't worry about NOTIFYing.
+allow-query { any; };				// Allow anyone to query.
+};
-
    +

    - + 3.2 Load Balancing and Round Robin

    -
+

- + Primitive load balancing can be achieved in DNS using multiple A records for one name.

- -For example, if you have three WWW servers with network addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a record like the following means that clients will connect to each machine one third of the time:

-
 
+
+For example, if you have three WWW servers with network addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records like the following means that clients will connect to each machine one third of the time:

+

  

 

 

 
 

-
- 
+
 Name

 		
 
 

-
- 
+
 TTL

 		
 
 

-
- 
+
 CLASS

 		
 
 

-
- 
+
 TYPE

 		
 
 

-
- 
+
 Resource Record (RR) Data

 		
 

 

 
 

-
- 
-www

+
+
+www
+

 		
 
 

-
- 
-10m

+
+
+600
+

 		
 
 

-
- 
-IN

+
+
+IN
+

 		
 
 

-
- 
-A

+
+
+A
+

 		
 
 

-
- 
-10.0.0.1

+
+
+10.0.0.1
+

 		
 

 

 
 

-
- 
+
+
+
  

 		
 
 

-
- 
-10m

+
+
+600
+

 		
 
 

-
- 
-IN

+
+
+IN
+

 		
 
 

-
- 
-A

+
+
+A
+

 		
 
 

-
- 
-10.0.0.2

+
+
+10.0.0.2
+

 		
 

 

 
 

-
- 
+
+
+
  

 		
 
 

-
- 
-10m

+
+
+600
+

 		
 
 

-
- 
-IN

+
+
+IN
+

 		
 
 

-
- 
-A

+
+
+A
+

 		
 
 

-
- 
-10.0.0.3

+
+
+10.0.0.3
+

 		
 

 

 

-
- 
-When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. This is known as cyclic or round-robin ordering.In the example above, the first client will receive the records in the order 1,2,3; the second client will receive them in the order 2,3,1; and the third 3,1,2. Most clients will use the first record returned, and discard the rest.

+
+When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. This is known as cyclic or round-robin ordering. In the example above, the first client will receive the records in the order 1, 2, 3; the second client will receive them in the order 2, 3, 1; and the third 3, 1, 2. Most clients will use the first record returned and discard the rest.

 

-
- 
+
 For more detail on ordering responses, check the 
 rrset-order
  substatement in the 
@@ -259,50 +268,52 @@ RRset Ordering
 .
-
    +

    - - -3.3 Notify

    -
+ +3.3 +Notify +

- - -DNS Notify is a mechanism that allows master nameservers to notify their slave servers of changes to a zone's data and that a query should be initiated to discover the new data. DNS Notify is turned on by default.

+ +DNS Notify is a mechanism that allows master nameservers to notify their slave servers of changes to a zone's data and that a query should be initiated to discover the new data.

- + DNS Notify is fully documented in RFC 1996. See also the description of the zone option also-notify - on + in Zone Transfers +. More information about +notify + can be found in Boolean Options .

-
    +

    - + 3.4 Nameserver Operations

    -
+
-
    +

    3.4.1 Tools for Use With the Nameserver Daemon

    -
+

There are several indispensable diagnostic, administrative and monitoring tools available to the system administrator for controlling and debugging the nameserver daemon. We describe several in this section

-
    +
    3.4.1.1 Diagnostic Tools
    -
+
@@ -406,12 +417,12 @@ nslookup man page.

-
    +
    3.4.1.2 Administrative Tools
    -
+

@@ -427,7 +438,9 @@ rndc The remote name daemon control ( rndc -) program is a program that allows the system administrator to control the operation of a nameserver. If you run rndc without any options it will display a usage message.

+) program is a program that allows the system administrator to control the operation of a nameserver. If you run +rndc + without any options it will display a usage message.

@@ -438,30 +451,14 @@ Usage:

-For more information and a list of available commands and options, see the rndc man page.

+For more information and a list of available commands and options, see the +rndc + man page.

+
+
-
    -
    - - -3.4.1.3 Monitoring Tools
    -
-
-
-
- - -MRTG
-

- - - -MRTG - is primarily a router traffic grapher, but can be used to monitor BIND DNS servers, as well. The `stat' script, supplied with MRTG in the MRTG `contrib/stat' directory, can be used to monitor numbers of queries, and counts of various sorts of responses.

-
- -

Return to BINDv9 Administrator Reference Manual + diff --git a/doc/arm/Bv9ARM.4.html b/doc/arm/Bv9ARM.4.html index 1f066128f7..c954b1ec17 100644 --- a/doc/arm/Bv9ARM.4.html +++ b/doc/arm/Bv9ARM.4.html @@ -5,19 +5,21 @@ Section 4. Advanced Concepts -

    +

    Section 4. Advanced Concepts

    -
+
-
    +

    -4.1 Dynamic Update

    -
+4.1 + +Dynamic Update +

@@ -35,9 +37,11 @@ zone

-Updating of secure zones (zones using DNSSEC) works as specified in the +Updating of secure zones (zones using DNSSEC) is modelled after the simple-secure-update - proposal. SIG and NXT records affected by updates are automatically regenerated by the server using an online zone key. Update authorization is based on transaction signatures and an explicit server policy.

+ proposal, a work in progress in the DNS Extensions working group of the IETF. (See +http://www.ietf.org/html.charters/dnsext-charter.html + for information about the DNS Extensions working group.) SIG and NXT records affected by updates are automatically regenerated by the server using an online zone key. Update authorization is based on transaction signatures and an explicit server policy.

@@ -46,24 +50,23 @@ The zone files of dynamic zones must not be edited by hand. The zone file on dis ) file. BINDv9 currently does not update the zone file when it exits like BIND 8 does, so editing the zone file manually is unsafe even when the server has been shut down.

-
    +

    4.2 Incremental Zone Transfers (IXFR)

    -
+

-The incremental zone transfer protocol (IXFR, RFC1995--see the list of proposed standards on in Appendix C on -Proposed Standards -) is a way for slave servers to transfer only changed data, instead of having to transfer the entire zone every time it changes.

+The incremental zone transfer (IXFR) protocol is a way for slave servers to transfer only changed data, instead of having to transfer the entire zone. The IXFR protocol is documented in RFC 1995. See the list of proposed standards in Appendix C, +Proposed Standards.

-When acting as a master, BINDv9 supports IXFR for those zones where the necessary change history information is available. These include master zones maintained by dynamic update and slave zones whose data was obtained by IXFR, but not manually maintained master zones nor slave zones obtained by AXFR.

+When acting as a master, BINDv9 supports IXFR for those zones where the necessary change history information is available. These include master zones maintained by dynamic update and slave zones whose data was obtained by IXFR, but not manually maintained master zones nor slave zones obtained by performing a full zone transfer (AXFR).

@@ -74,24 +77,28 @@ server statement.

-
    +

    4.3 Split DNS

    -
+

-Setting up different views, or visibility, of DNS space to internal, as opposed to external, resolvers is usually referred to as a "Split DNS" or "Split Brain DNS" setup. There are several reasons an organization would want to set its DNS up this way.

+Setting up different views, or visibility, of DNS space to internal, as opposed to external, resolvers is usually referred to as a +Split DNS + or +Split Brain DNS + setup. There are several reasons an organization would want to set up its DNS this way.

-One common reason for setting up a DNS system this way is to hide "internal" DNS information from "external" clients on the Internet. There is some debate as to whether or not this is actually useful. Internal DNS information leaks out in many ways (via e-mail headers, for example) and most savvy "attackers" can find the information they need using other means.

+One common reason for setting up a DNS system this way is to hide "internal" DNS information from "external" clients on the Internet. There is some debate as to whether or not this is actually useful. Internal DNS information leaks out in many ways (via email headers, for example) and most savvy "attackers" can find the information they need using other means.

-Another common reason for setting up a Split DNS system is to allow internal networks that are behind filters or RFC1918 space (reserved IP space, as documented in RFC 1918) to resolve DNS on the Internet. Split DNS can also be used to allow mail from outside back in to the internal network.

+Another common reason for setting up a Split DNS system is to allow internal networks that are behind filters or RFC 1918 space (reserved IP space, as documented in RFC 1918) to resolve DNS on the Internet. Split DNS can also be used to allow mail from outside back in to the internal network.

@@ -101,7 +108,7 @@ Here is an example of a split DNS setup:

Let's say a company named Example, Inc. - (example.com) has several corporate sites that have an internal network with reserved IP space and an external DMZ (the demilitarized zone, or "outside" section of a network) that is available to the public.

+ (example.com) 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.

@@ -155,9 +162,9 @@ site1 site2.example.com zones. This could include things such as the host records for public servers ( www.example.com -, + and ftp.example.com -), and mail exchanger records ( +), and mail exchange (MX) records ( a.mx.example.com and b.mx.example.com @@ -169,13 +176,14 @@ In addition, the public site1 and site2.example.com - 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.

+ 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.

Here's an example of a wildcard MX record:

 
-*   IN MX 10 external1.example.com.
+* IN MX 10 external1.example.com. +

@@ -248,206 +256,216 @@ site2.example.com 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 -See Sample Configuration and Logging. -

+Sample Configuration and Logging +.

- + Internal DNS server config:

-
 
-
-
-acl internals { 172.16.72.0/24; 192.168.1.0/24; };
-acl externals { bastion-ips-go-here; };
+

+acl internals { 172.16.72.0/24; 192.168.1.0/24; };
+acl externals { bastion-ips-go-here; };
 options {
     ...
     ...
     forward only;
-    forwarders { bastion-ips-go-here; };			//forward to external servers
-    allow-transfer { none; };				// sample allow-transfer (no one)
-    allow-query { internals; externals; };			// restrict query access
-    allow-recursion { internals; };			// restrict recursion
+    forwarders { bastion-ips-go-here; };															// forward to external servers
+    allow-transfer { none; };															// sample allow-transfer (no one)
+    allow-query { internals; externals; };															// restrict query access
+    allow-recursion { internals; };															// restrict recursion
     ...
     ...
-};
-
-zone "site1.example.com" { // sample slave zone
-  type master;
-  file "m/site1.example.com";
-  forwarders { };          // do normal iterative resolution (do not forward)
-  allow-query { internals; externals; };
-  allow-transfer { internals; };
-};
-
-zone "site2.example.com" {
-  type slave;
-  file "s/site2.example.com";
+};
+

+

+zone "site1.example.com" { 															// sample slave zone
+  type master;
+  file "m/site1.example.com";
+  forwarders { }; 															// do normal iterative
+															// resolution (do not forward)
+  allow-query { internals; externals; };
+  allow-transfer { internals; };
+};
+

+

+zone "site2.example.com" {
+  type slave;
+  file "s/site2.example.com"
   masters { 172.16.72.3; };
   forwarders { };
-  allow-query { internals; externals; };
-  allow-transfer { internals; };
-};
-
-zone "site1.internal" {
-  type master;
-  file "m/site1.internal";
+  allow-query { internals; externals; };
+  allow-transfer { internals; };
+};
+

+

+zone "site1.internal
+" {
+  type master;
+  file "m/site1.internal";
   forwarders { };
-  allow-query { internals; };
-  allow-transfer { internals; }
-};
-
-zone "site2.internal" {
-  type slave;
-  file "s/site2.internal";
+  allow-query { internals; };
+  allow-transfer { internals; }
+};
+

+

+zone "site2.internal" {
+  type slave;
+  file "s/site2.internal";
   masters { 172.16.72.3; };
   forwarders { };
-  allow-query { internals };
-  allow-transfer { internals; }
-};
-
-
-External (bastion host) DNS server config:
- 
-
-acl internals { 172.16.72.0/24; 192.168.1.0/24; };
-acl externals { bastion-ips-go-here; };
+  allow-query { internals };
+  allow-transfer { internals; }
+};
+

+

+
+
+External (bastion host) DNS server config:

+

+acl internals { 172.16.72.0/24; 192.168.1.0/24; };
+acl externals { bastion-ips-go-here; };
 options {
   ...
   ...
-  allow-transfer { none; };                  // sample allow-transfer (no one)
-  allow-query { internals; externals; };     // restrict query access
-  allow-recursion { internals; externals; }; // restrict recursion
+  allow-transfer { none; };															// sample allow-transfer (no one)
+  allow-query { internals; externals; };															// restrict query access
+  allow-recursion { internals; externals; };															// restrict recursion
   ...
   ...
-};
-
-zone "site1.example.com" {        // sample slave zone
-  type master;
-  file "m/site1.foo.com";
-  allow-query { any; };
-  allow-transfer { internals; externals; };
-};
-
-zone "site2.example.com" {
-  type slave;
-  file "s/site2.foo.com";
-  masters { another_bastion_host_maybe; };
-  allow-query { any; };
-  allow-transfer { internal; externals; }
-};
-
-
-In the resolv.conf (or equivalent) on the bastion host(s):
- 
-search ...
+};
+

+

+zone "site1.example.com" {															// sample slave zone
+  type master;
+  file "m/site1.foo.com";
+  allow-query { any; };
+  allow-transfer { internals; externals; };
+};
+

+

+zone "site2.example.com" {
+  type slave;
+  file "s/site2.foo.com";
+  masters { another_bastion_host_maybe; };
+  allow-query { any; };
+  allow-transfer { internals; externals; }
+};
+

+

+
+
+In the 
+resolv.conf
+ (or equivalent) on the bastion host(s):

+

+search ...
 nameserver 172.16.72.2
 nameserver 172.16.72.3
 nameserver 172.16.72.4
 

-
-
    +

    - -4.4 TSIG

    -
+ +4.4 + +TSIG +

- -This is a short guide to setting up TSIG based transaction security in BIND. It describes changes to the configuration file as well as what changes are required for different features, including the process of creating transaction keys and using transaction signatures with BIND.

+ +This is a short guide to setting up Transaction SIGnatures (TSIG) based transaction security in BIND. It describes changes to the configuration file as well as what changes are required for different features, including the process of creating transaction keys and using transaction signatures with BIND.

- -BIND primarily supports TSIG for server-server communication. This includes zone transfer, notify, and recursive query messages. The resolver bundled with BIND 8.2 has limited support for TSIG, but it is doubtful that support will be integrated into any client applications.

+ +BIND primarily supports TSIG for server to server communication. This includes zone transfer, notify, and recursive query messages. The resolver bundled with BIND 8.2 has limited support for TSIG, but it is doubtful that support will be integrated into any client applications.

- -TSIG might be most useful for dynamic update. A primary server for a dynamic zone should use access control to control updates, but IP-based access control is insufficient. Key-based access control is far superior (see -draft-ietf-dnsext-simple-secure-update-00.txt - in Appendix C on -Request for Comments (RFCs) -). The + +TSIG might be most useful for dynamic update. A primary server for a dynamic zone should use access control to control updates, but IP-based access control is insufficient. Key-based access control is far superior. See RFC 2845 in the +Proposed Standards +section of the Appendix. The nsupdate - program that is shipped with BIND 8 supports TSIG via the
-" + program that is shipped with BIND 8 supports TSIG via the " -k " command line option.

-
    +

    - + 4.4.1 Generate Shared Keys for Each Pair of Hosts

    -
+

- + A shared secret is generated to be shared between host1 and host2. The key name is chosen to be "host1-host2.", which is arbitrary. The key name must be the same on both hosts.

-
    +
    - + 4.4.1.1 Automatic Generation
    -
+

The following command will generate a 128 bit (16 byte) HMAC-MD5 key as described above. Longer keys are better, but shorter keys are easier to read. Note that the maximum key length is 512 bits; keys longer than that will be digested with MD5 to produce a 128 bit key.

- -

-src/bin/dnskeygen/dnskeygen -H 128 -h -n host1-host2.
+

+bin/dnssec/dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.
+

-The key is in the file "Khost1-host2.+157+00000.private". Nothing actually uses this file, but the base64 encoded string following "Key:" can be extracted:

+The key is in the file "Khost1-host2.+157+00000.private". Nothing actually uses this file, but the base-64 encoded string following "Key:" can be extracted:


-   La/E5CjG9O+os1jq0a2jdA==
+ La/E5CjG9O+os1jq0a2jdA== +

- + This string represents a shared secret.

-
    +
    - + 4.4.1.2 Manual Generation
    -
+

- -The shared secret is simply a random sequence of bits, encoded in base64. Most ASCII strings are valid base64 strings (assuming the length is a multiple of 4 and only valid characters are used), so the shared secret can be manually generated.

+ +The shared secret is simply a random sequence of bits, encoded in base-64. Most ASCII strings are valid base-64 strings (assuming the length is a multiple of 4 and only valid characters are used), so the shared secret can be manually generated.

- + Also, a known string can be run through mmencode - or a similar program to generate base64 encoded data.

+ or a similar program to generate base-64 encoded data.

-
    +

    - + 4.4.2 Copying the Shared Secret to Both Machines

    -
+

- + This is beyond the scope of DNS. A secure transport mechanism should be used. This could be secure FTP, ssh, telephone, etc.

-
    +

    - + 4.4.3 Informing the Servers of the Key's Existence

    -
+

@@ -458,36 +476,36 @@ host 2 are both servers. The following is added to each server's named.conf file:

- -
- 
-key host1-host2. {
-  algorithm hmac-md5;
-  secret "La/E5CjG9O+os1jq0a2jdA==";
-};
-
+

+key 
+host1-host2. {
+  algorithm hmac-md5;
+  secret "La/E5CjG9O+os1jq0a2jdA==";
+};
 

 

 
- 
+
 The algorithm, hmac-md5, is the only one supported by BIND. The secret is the one generated above. Since this is a secret, it is recommended that either 
 named.conf
- be non-world readable, or the key directive be added to a non-world readable file that's included by named.conf.

+ be non-world readable, or the key directive be added to a non-world readable file that is included by 
+named.conf
+.

 

 
- 
+
 At this point, the key is recognized. This means that if the server receives a message signed by this key, it can verify the signature. If the signature succeeds, the response is signed by the same key.
-
    +

    - + 4.4.4 Instructing the Server to Use the Key

    -
+

- + Since keys are shared between two hosts only, the server must be told when keys are to be used. The following is added to the named.conf file for @@ -495,107 +513,82 @@ host1 , if the IP address of host2 is 10.1.2.3:

- -
-
-server 10.1.2.3 {
-  keys {host1-host2.;};
+

+server 
+10.1.2.3 {
+  keys { host1-host2. ;};
 };
 

 

 
- 
+
 Multiple keys may be present, but only the first is used. This directive does not contain any secrets, so it may be in a world-readable file.

 

 
- 
+
 If host1 sends a message that is a response to that address, the message will be signed with the specified key. host1 will expect any responses to signed messages to be signed with the same key.

 

 
- 
+
 A similar statement must be present in host2's configuration file (with host1's address) for host2 to sign non-response messages to host1.
-
    +

    - + 4.4.5 TSIG Key Based Access Control

    -
+

- -BIND allows IP addresses and ranges to be specified in ACL definitions and -allow-{ query - -| + +BIND allows IP addresses and ranges to be specified in ACL definitions and
-transfer - -| - -update } - directives. This has been extended to allow TSIG keys also. The above key would be denoted -key host1-host2 -.

+allow-{ query | transfer | update } +directives. This has been extended to allow TSIG keys also. The above key would be denoted +key host1-host2. +

- + An example of an allow-update directive would be:

- - -
-allow-update {key host1-host2.;};
-
+

+allow-update { key host1-host2. ;};
 

 

 
- 
+
 This allows dynamic updates to succeed only if the request was signed by a key named "
 host1-host2.
-"

+".
-
    +

    - + 4.4.6 Errors

    -
+

- + The processing of TSIG signed messages can result in several errors. If a signed message is sent to a non-TSIG aware server, a FORMERR will be returned, since the server will not understand the record. This is a result of misconfiguration, since the server must be explicitly configured to send a TSIG signed message to a specific server.

- + If a TSIG aware server receives a message signed by an unknown key, the response will be unsigned with the TSIG extended error code set to BADKEY. If a TSIG aware server receives a message with a signature that does not validate, the response will be unsigned with the TSIG extended error code set to BADSIG. If a TSIG aware server receives a message with a time outside of the allowed range, the response will be signed with the TSIG extended error code set to BADTIME, and the time values will be adjusted so that the response can be successfully verified. In any of these cases, the message's rcode is set to NOTAUTH.

-

- - -TSIG verification errors are logged by the server as

- -
-
-"ns_req: TSIG verify failed - (reason)"
- 
-
-

- - -which is printed at debug level 1.

-
    +

    - + 4.5 TKEY

    -
+

- + TKEY is a mechanism for automatically generating a shared secret between two hosts. There are several "modes" of @@ -609,7 +602,7 @@ TKEY can also be used to delete shared secrets that it had previously generated.

- + The TKEY process is initiated by a client or server by sending a signed @@ -623,18 +616,20 @@ TKEY mode, Diffie-Hellman keys are exchanged, and the shared secret is derived by both participants.

-
    +

    -4.6 DNSSEC Secured Zones

    -
+4.6 + +DNSSEC +

-Cryptographic authentication of DNS information is made possible through the DNS Security ( +Cryptographic authentication of DNS information is possible through the DNS Security ( DNSSEC -) extension to the domain system. This describes the processing of creating and using DNSSEC signed zones.

+) extension, defined in RFC 2535. This section describes the creation and use of DNSSEC signed zones.

@@ -650,12 +645,12 @@ There must also be communication with the administrators of the parent and/or ch For other servers to trust data in this zone, they must either be statically configured with this zone's zone key or the zone key of another zone above this one in the DNS tree.

-
    +

    4.6.1 Generating Keys

    -
+

@@ -677,18 +672,18 @@ child.example

- -dnssec-keygen - --a + +dnssec-keygen + +-a DSA - --b + +-b 768 - --n + +-n ZONE @@ -715,17 +710,17 @@ To generate another key with the same properties, repeat the above command.

-The public keys should be inserted into the zone file with $ -INCLUDE +The public keys should be inserted into the zone file with +$INCLUDE statements.

-
    +

    4.6.2 Creating a Keyset

    -
+

@@ -749,24 +744,22 @@ The following command generates a key set containing the above key and another k

- -dnssec-makekeyset - --t + +dnssec-makekeyset + +-t 3600 - --s + +-s now - --e + +-e now+864000 Kchild.example.+003+12345 - - \ Kchild.example.+003+23456

@@ -778,12 +771,12 @@ child.example.keyset . This file should be transmitted to the parent to be signed. It includes the keys, as well as signatures over the key set generated by the zone keys themselves, which are used to prove ownership of the private keys and encode the desired validity period.

-
    +

    4.6.3 Signing the Child's Keyset

    -
+

@@ -807,14 +800,14 @@ The following command signs the child's key set with the zone keys:

- -dnssec-signkey + +dnssec-signkey grand.child.example.keyset -Kchild.example.+003+12345 +Kchild.example.+003+12345 -\ + Kchild.example.+003+23456

@@ -826,12 +819,12 @@ grand.child.example.signedkey . This file should be both transmitted back to the child and retained. It includes all keys (the child's keys) from the keyset file and signatures generated by this zone's zone keys.

-
    +

    4.6.4 Signing the Zone

    -
+

@@ -855,14 +848,14 @@ SIG The following command signs the zone, assuming it is in a file called zone.child.example -. By default, all zone keys which have an available private key are used to generate signatures.:

+. By default, all zone keys which have an available private key are used to generate signatures.

- -dnssec-signzone - --o + +dnssec-signzone + +-o child.example zone.child.example

@@ -876,12 +869,12 @@ named.conf as the input file for the zone.

-
    +

    4.6.5 Configuring Servers

    -
+

@@ -889,23 +882,26 @@ Unlike in BIND 8, data is not verified on load in BINDv9, so zone keys for autho

-The public key for any security root must be present in the configuration file's trusted-keys statement, as described later in this document.

+The public key for any security root must be present in the configuration file's
+ +trusted-keys + statement, as described later in this document.

-
    +

    4.7 IPv6

    -
+
-
    +

    4.7.1 IPv6 addresses (A6)

    -
+

@@ -927,174 +923,174 @@ The aggregatable global Unicast address format is as follows:

-

+ -3

+3 		-

+ -13

+13 		-

+ -8

+8 		-

+ -24

+24 		-

+ -16

+16 		-

+ -64 bits

+64 bits
-

+ -FP

+FP 		-

+ -TLA ID

+TLA ID 		-

+ -RES

+RES 		-

+ -NLA ID

+NLA ID 		-

+ -SLA ID

+SLA ID 		-

+ -Interface ID

+Interface ID
-

+ -<------ Public Topology ------>

+<------ Public Topology ------> 		-

+ - 

+  		-

+ - 

+ 
-

+ - 

+  		-

+ - 

+  		-

+ - 

+  		-

+ - 

+  		-

+ -<-Site Topology->

+<-Site Topology-> 		-

+ - 

+ 
-

+ - 

+  		-

+ - 

+  		-

+ - 

+  		-

+ - 

+  		-

+ - 

+  		-

+ -<------ Interface Identifier ------>

+<------ Interface Identifier ------>
@@ -1305,7 +1301,7 @@ NLA ID

-A 3 bit FP (Format Prefix) of 001 indicates this is a global unicast address. FP lengths for other types of addresses may vary.

+A 3 bit FP (Format Prefix) of 001 indicates this is a global Unicast address. FP lengths for other types of addresses may vary.

@@ -1321,28 +1317,26 @@ A 3 bit FP (Format Prefix) of 001 indicates this is a global unicast address. FP

-There is no particular structure for the Site topology section. Organizations can allocate these bits in any way they desire, in the same way as they would subnet an IPv4 class A (8 bit prefix) network.

+There is no particular structure for the Site topology section. Organizations can allocate these bits in any way they desire, in the same way as they would subnet an IPv4 class A (8-bit prefix) network.

-The Interface identifier must be unique on that network. On ethernet networks, one way to ensure this is to set the address to the first three bytes of the hardware address, "FFFE", then the last three bytes of the hardware address. The lowest significant bit of the first byte should then be complemented. Addresses are written as 32-bit blocks separated with a colon, and leading zeros of a block may be omitted, for example:

- -
-3ffe:8050:201:9:a00:20ff:fe81:2b32
-
+The Interface Identifier must be unique on that network. On ethernet networks, one way to ensure this is to set the address to the first three bytes of the hardware address, "FFFE", then the last three bytes of the hardware address. The lowest significant bit of the first byte should then be complemented. Addresses are written as 32-bit blocks separated with a colon, and leading zeros of a block may be omitted, for example:

+
 
+3ffe:8050:201:9:a00:20ff:fe81:2b32
 

 

-
+
  
-IPv6 address specifications are likely to contain long strings of zeros, so the architects have included a shorthand for specifying them. The double colon ("::") indicates the longest possible string of zeros that can fit, and can be used only once in an address.

+IPv6 address specifications are likely to contain long strings of zeros, so the architects have included a shorthand for specifying them. The double colon ('::') indicates the longest possible string of zeros that can fit, and can be used only once in an address.
-
    +

    4.7.2 Name to Address Lookup

    -
+

@@ -1350,12 +1344,7 @@ Forward name lookups (host name to IP address) under IPv6 do not necessarily ret

-A complete IPv6 A6 record that provides the full 128 bit address looks like:

-

- - - 

- +This is an example of a complete IPv6 A6 record that provides the full 128 bit address:

@@ -1434,10 +1423,6 @@ host.example.com.

Note that the number preceding the address is the number of bits to be provided via the referral. This is probably the easiest way to roll out an IPv6 installation, though you may wish to provide a reference to your provider assigned prefix:

-

- - - 

@@ -1516,10 +1501,6 @@ prefix.example2.com.

Then, in example2.com's zone:

-

- - - 

@@ -1600,12 +1581,12 @@ prefix.example2.com.

The referral where there are no more bits is to ".", the root zone. Be warned that excessive use of this chaining can lead to extremely poor name resolution for people trying to access your hosts.

-
    +

    4.7.3 Address to Name Lookup

    -
+

@@ -1644,12 +1625,12 @@ The address above, then, is:

These strings are all equivalent. The combined TLA/RES/NLA in the second example bears no resemblance to any string in the address because it is offset by three bits.

-
    +

    4.7.4 Using DNAME for Delegation of IPv6 Reverse Addresses

    -
+

@@ -1666,12 +1647,9 @@ example2.com ), the domain administrator would insert a line similar to the following in the \[x2/3].ip6.int. zone:

- -
-CODE> 
-$ORIGIN \[x2/3].ip6.int.
-\[xFFF0/13] 1h IN DNAME ip6.example2.com.
-
+
 
+$ORIGIN \[x2/3].ip6.int.
+\[xFFF0/13] 1h IN DNAME ip6.example2.com.
 

 

 
@@ -1681,14 +1659,10 @@ example2.com
  would then place into the 
 ip6 
 zone:

- 
-
-
-$ORIGIN ip6.example.com.
-\[x80500201/32] 1h IN DNAME ip6.example.com.
-
+
 
+$ORIGIN ip6.example.com.
+\[x80500201/32] 1h IN DNAME ip6.example.com.
 

-
 

 
  
@@ -1697,10 +1671,8 @@ example.com 
 needs to include in the 
 ip6.example.com
  zone:

- 
-
-
-$ORIGIN ip6.example.com.
+
 
+$ORIGIN ip6.example.com.
 \[x00090A0020FFFE812B32/80] 1h IN PTR host.example.com.
 

 

@@ -1711,6 +1683,8 @@ example.com
 , in this case) provide all the bits required for reverse and forward resolution to allow name resolution even if the network is disconnected from the Internet. This will also allow operation with DNSSEC if you set up a false trusted server for "." containing only  delegations for your forward and reverse zones directly to the top of your administrative control. This should be signed with a key trusted by all of your clients, equivalent to the real key for ".".
-

Return to BINDv9 Administrator Reference Manual +

diff --git a/doc/arm/Bv9ARM.5.html b/doc/arm/Bv9ARM.5.html index 1f64433a6d..86b81815a5 100644 --- a/doc/arm/Bv9ARM.5.html +++ b/doc/arm/Bv9ARM.5.html @@ -1,16 +1,16 @@ - + Section 5. BINDv9 Configuration Reference -
    +

    Section 5. BINDv9 Configuration Reference

    -
+

@@ -22,12 +22,12 @@ BIND 4.9.x configuration files can be converted to the new format by using the P src/bin/named/named-bootconf.pl from the BIND 8 release kit.

-
    +

    5.1 Configuration file elements

    -
+

@@ -39,12 +39,12 @@ Following is a list of elements used throughout the BIND configuration file docu
-

+

acl_name -

+

@@ -59,12 +59,12 @@ acl

-

+

address_match_list -

+

@@ -91,40 +91,36 @@ Address Match Lists

-

+

domain_name -

+

-A quoted string which will be used as a DNS name, for example -" - +A quoted string which will be used as a DNS name, for example " my.test.domain - -" -.

+".
-

+

dotted_decimal -

+

-One or more integers valued 0 through 255 separated only by dots (`.'), such as +One or more integers valued 0 through 255 separated only by dots ('.'), such as 123 , 45.67 @@ -135,12 +131,12 @@ One or more integers valued 0 through 255 separated only by dots (`.'), such as

-

+

ip4_addr -

+

@@ -153,12 +149,12 @@ dotted_decimal

-

+

ip6_addr -

+

@@ -171,12 +167,12 @@ fe80::200:f8ff:fe01:9742

-

+

ip_addr -

+

@@ -193,12 +189,12 @@ ip6_addr

-

+

ip_port -

+

@@ -208,17 +204,17 @@ An IP port number . number - is limited to 0 through 65535, with values below 1024 typically restricted to root-owned processes. In some cases an asterisk (`*') character can be used as a placeholder to select a random high-numbered port.

+ is limited to 0 through 65535, with values below 1024 typically restricted to root-owned processes. In some cases an asterisk ('*') character can be used as a placeholder to select a random high-numbered port.
-

+

ip_prefix -

+

@@ -226,7 +222,7 @@ ip_prefix An IP network specified as an ip_addr -, followed by a slash (`/') and then the number of bits in the netmask. For example, +, followed by a slash ('/') and then the number of bits in the netmask. For example, 127/8 is the network 127.0.0.0 @@ -243,12 +239,12 @@ ip_addr

-

+

key_name -

+

@@ -261,12 +257,12 @@ domain_name

-

+

number -

+

@@ -277,43 +273,43 @@ A non-negative integer with an entire range limited by the range of a C language

-

+

path_name -

+

-A quoted string which will be used as a pathname, such as -" +A quoted string which will be used as a pathname, such as +" zones/master/my.test.domain - -" + +" .
-

+

size_spec -

+

-A number, the word -unlimited -, or the word -default +A number, the word +unlimited +, or the word +default .

@@ -332,20 +328,20 @@ default size_spec A number - can optionally be followed by a scaling factor: -K - or -k + can optionally be followed by a scaling factor: +K + or +k -for kilobytes, -M - or -m - for megabytes, and -G - or -g +for kilobytes, +M + or +m + for megabytes, and +G + or +g for gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.

@@ -357,99 +353,85 @@ unlimited

-

+

yes_or_no -

+

-Either -yes - or -no -. The words -true - and -false - are also accepted, as are the numbers -1 - and -0 +Either +yes + or +no +. The words +true + and +false + are also accepted, as are the numbers +1 + and +0 .

-
    +

    5.1.1 Address Match Lists

    -
+
-
    +
    - + 5.1.1.1 Syntax
    -
-
-
-address_match_list = address_match_list_element ;
-  [ address_match_list_element; ... ]
-address_match_list_element = [ ! ] (ip_address [/length] |
-   key key_id | acl_name | { address_match_list } )
-
+

+address_match_list = address_match_list_element ;
+  [ address_match_list_element; ... ]
+address_match_list_element = [ ! ] (ip_address [/length] |
+  keykey_id | acl_name | { address_match_list } )
-
    +
    5.1.1.2 Definition and Usage
    -
+

Address match lists are primarily used to determine access control for various server operations. They are also used to define priorities for querying other nameservers and to set the addresses on which named will listen for queries. The elements which constitute an address match list can be any of the following:

+
    -
  • - - -an IP address (IPv4 or IPv6)
    • -
  • - - -an IP prefix (in the "/"-notation)
    • -
  • - - -a key ID, as defined by the key statement
    • -
  • - - -the name of an address match list previously defined with the -acl - statment
    • -
  • - - -a nested address match list enclosed in braces
    • +
  • an IP address (IPv4 or IPv6) + +
  • an IP prefix (in the '/'-notation) + +
  • a key ID, as defined by the key statement + +
  • the name of an address match list previously defined with the acl statement + +
  • a nested address match list enclosed in braces
+

-Elements can be negated with a leading exclamation mark ("!"), and the match list names "any", "none", "localhost" and "localnets" are predefined. More information on those names can be found in the description of the acl statement.

+Elements can be negated with a leading exclamation mark ('!') and the match list names "any," "none," "localhost" and "localnets" are predefined. More information on those names can be found in the description of the acl statement.

@@ -477,24 +459,25 @@ Because of the first-match aspect of the algorithm, an element that defines a su fixes that problem by having 1.2.3.13 blocked by the negation but all other 1.2.3.* hosts fall through.

+
-
    +

    5.1.2 Comment Syntax

    -
+

The BINDv9 comment syntax allows for comments to appear anywhere that white space may appear in a BIND configuration file. To appeal to programmers of all kinds, they can be written in C, C++, or shell/perl constructs.

-
    +
    5.1.2.1 Syntax
    -
+

@@ -503,12 +486,12 @@ The BINDv9 comment syntax allows for comments to appear anywhere that white spac # This is a BIND comment as in common UNIX shells and perl

-
    +
    5.1.2.2 Definition and Usage
    -
+

@@ -559,19 +542,18 @@ For example:

-WARNING: you cannot use the semicolon (";") character to start a comment such as you would in a zone file. The semicolon indicates the end of a configuration statement.

-
+WARNING: you cannot use the semicolon (';') character to start a comment such as you would in a zone file. The semicolon indicates the end of a configuration statement.

-
    +

    5.2 Configuration File Grammar

    -
+

@@ -587,7 +569,7 @@ The following statements are supported:

-

+

@@ -598,12 +580,12 @@ acl

-defines a named IP address matching list, for access control and other uses

+defines a named IP address matching list, for access control and other uses.
-

+

@@ -616,12 +598,12 @@ controls declares control channels to be used by the rndc - utility

+ utility.
-

+

@@ -632,12 +614,12 @@ include

-includes a file

+includes a file.
-

+

@@ -648,14 +630,12 @@ key

-specifies key information for use in authentication and authorization using TSIG. See -draft-ietf-dnsind-tsig-13.txt - for more information.

+specifies key information for use in authentication and authorization using TSIG.
-

+

@@ -666,12 +646,12 @@ logging

-specifies what the server logs, and where the log messages are sent

+specifies what the server logs, and where the log messages are sent.
-

+

@@ -682,12 +662,12 @@ options

-controls global server configuration options and sets defaults for other statements

+controls global server configuration options and sets defaults for other statements.
-

+

@@ -698,12 +678,12 @@ server

-sets certain configuration options on a per-server basis

+sets certain configuration options on a per-server basis.
-

+

@@ -714,12 +694,12 @@ trusted-keys

-defines keys that are preconfigured into the server and implicitly trusted. See RFC 2535 for more information.

+defines trusted DNSSEC keys.
-

+

@@ -730,12 +710,12 @@ view

-defines a view

+defines a view.
-

+

@@ -746,7 +726,7 @@ zone

-defines a zone

+defines a zone.
@@ -759,33 +739,31 @@ logging options statements may only occur once per configuration.

-
    +

    5.2.1 acl Statement Grammar

    -
- -
-
-acl acl-name { 
-    address_match_list 
-};
+
+

+acl acl-name {
+    address_match_list
+};
-
    +

    - + 5.2.2 acl Statement Definition and Usage

    -
+

@@ -809,12 +787,12 @@ The following ACLs are built-in:

-
+

any -

+

@@ -825,12 +803,12 @@ Matches all hosts.

-
+

none -

+

@@ -841,12 +819,12 @@ Matches no hosts.

-
+

localhost -

+

@@ -857,12 +835,12 @@ Matches the IP addresses of all interfaces on the system.

-
+

localnets -

+

@@ -874,35 +852,35 @@ Matches any host on a network for which the system has an interface.

-
    +

    5.2.3 -control +controls Statement Grammar

    -
- + + 
-
-controls {
-   [ inet (ip_addr|*) port ip_port allow { address_match_list } ;
-      [ inet...;[...]]]
-   [ unix string permission number owner number group number ;
-      [ unix...;[..]]]
-};
+controls {
+   [ inet (ip_addr|*) port ip_port allow { address_match_list };
+      [ inet...;[...]]]
+   [ unix string permission number owner number group number ;
+      [ unix...;[..]]]
+};
+
-
    +

    5.2.4 controls Statement Definition and Usage

    -
+

@@ -940,39 +918,43 @@ ip_addr

- + The controls - + statement is not yet implemented in BINDv9. The server always listens for control connections on IP address 127.0.0.1, port 953.

-
    +

    5.2.5 include Statement Grammar

    -
-
-
-include filename;
-
-
+

+ + + +include + +filename + +; +

-
    +

    5.2.6 include Statement Definition and Usage

    -
+

@@ -985,162 +967,132 @@ include statement facilitates the administration of configuration files by permitting the reading or writing of some things but not others. For example, the statement could include private keys that are readable only by a nameserver.

-
    +

    5.2.7 key Statement Grammar

    -
- + +

+ + 

-key key_id {
-    algorithm string;
-    secret string;
-};
-
+
+key key_id {
+    algorithm string;
+    secret string;
+};
+
-
    +

    5.2.8 key Statement Definition and Usage

    -
+

- + The key - statement defines a key ID which can be used in a server statement to associate an authentication method with a particular nameserver.

+ statement defines a shared secret key for use with TSIG. See +See TSIG. +.

- + -A key ID must be created with the -key - statement before it can be used in a server definition or an address match list.

+The +key_id +, also known as the key name, is a domain name uniquely identifying the key. It can be used in a "server" statement to cause requests sent to that server to be signed with this key, or in address match lists to verify that incoming requests have been signed with a key matching this name, algorithm, and secret.

The algorithm_id - is a string that specifies a security/authentication algorithm. The only algorithm currently supported with tsig authentication is -hmac-md5 + is a string that specifies a security/authentication algorithm. The only algorithm currently supported with TSIG authentication is +hmac-md5 . The secret_string is the secret to be used by the algorithm, and is treated as a base-64 encoded string.

-

- - -The -key - statement is intended for use in transaction security. Unless included in a server statement, it is not used to sign any requests. It is used to verify requests matching the -key_id - and -algorithm_id -, and sign replies to those requests.

-
    +

    5.2.9 logging Statement Grammar

    -
- -
-
-logging {
-   [ channel channel_name {
-     ( file path name
-         [ versions ( number | unlimited ) ]
-         [ size size spec ]
-       | syslog ( syslog_facility )
-       | null );
 
-     [ severity (critical | error | warning | notice |
-                 info | debug [ level ] | dynamic ); ]
-     [ print-category yes or no; ]
-     [ print-severity yes or no; ]
-     [ print-time yes or no; ] 
-   }; ]
-
-   [ category category_name { 
-     channel_name ; [ channel_name ; ... ] 
-   }; ]
-
-   ... 
+

+logging {
+   [ channel channel_name {
+     ( file path name
+         [ versions ( number | unlimited ) ]
+         [ size size spec ]
+       | syslog ( syslog_facility )
+       | null );
+     [ severity (critical | error | warning | notice |
+                 info | debug [ level ] | dynamic ); ]
+     [ print-category yes or no; ]
+     [ print-severity yes or no; ]
+     [ print-time yes or no; ]
+   }; ]
+   [ category category_name {
+     channel_name ; [ channel_name ; ... ]
+   }; ]
+   ...
 };
 

-
-

    - +` 5.2.10 logging Statement Definition and Usage

    -
-

- - -The -logging - statement configures a wide variety of logging options for the nameserver. Its -channel - phrase associates output methods, format options and severity levels with a name that can then be used with the -category - phrase to select how various classes of messages are logged.

-

- - -Only one -logging - statement is used to define as many channels and categories as are wanted. If there are multiple -logging - statements in a configuration, the first defined determines the logging, and warnings are issued for the others via the default -syslog -. If there is no -logging - statement, the logging configuration will be:

-

- 
- -
-logging {
-     category default { default_syslog; default_debug; };
-};
-
+

+The logging statement configures a wide variety of logging options for the nameserver. Its channel phrase associates output methods, format options and severity levels with a name that can then be used with the category phrase to select how various classes of messages are logged. +

+

+Only one logging statement is used to define as many channels and categories as are wanted. If there is no logging statement, the logging configuration will be: +

+
+logging {
+     category default { default_syslog; default_debug; };
+};
+

- + In BINDv9, the logging configuration is only established when the entire configuration file has been parsed. In BIND 8, it was established as soon as the logging - statement was parsed. When the server is starting up, all logging messages regarding syntax errors in the configuration file go to the default channels, or to standard error if the + statement was parsed. When the server is starting up, all logging messages regarding syntax errors in the configuration file go to the default channels, or to standard error if the " -g - option was specified.

+" option was specified.

-
    +
    5.2.10.1 The channel Phrase
    -
+

-All log output goes to one or more "channels"; you can make as many of them as you want.

+All log output goes to one or more +channels +; you can make as many of them as you want.

@@ -1197,19 +1149,15 @@ unlimited in current BIND releases.

- + Example usage of the size and versions options:

- - -
-
-    channel an_example_level {
-        file "lamers.log" versions 3 size 20m;
-        print-time yes;
-        print-category yes;
+

+    channel an_example_level {
+        file "lamers.log" versions 3 size 20m;
+        print-time yes;
+        print-category yes;
     };
 

-
 

 
  
@@ -1221,7 +1169,7 @@ syslog
 syslog
  will handle messages sent to this facility is described in the 
 syslog.conf
- manual page. If you have a system which uses a very old version of 
+ man page. If you have a system which uses a very old version of 
 syslog
  that only uses two arguments to the 
 openlog()
@@ -1264,24 +1212,23 @@ syslogd
  would print all messages it received from the channel.

 

 
- 
+
 The server can supply extensive debugging information when it is in debugging mode. If the server's global debug level is greater than zero, then debugging mode will be active. The global debug level is set either by starting the 
 named
  server with the "
 -d
 " flag followed by a positive integer, or by running 
 rndc trace
- (
+ (
 the latter method is not yet implemented
 ). The global debug level can be set to zero, and debugging mode turned off, by running 
 ndc notrace
-. All debugging messages in the server have a debug level, and higher debug levels give more detailed output. Channels that specify a specific debug severity, e.g.

- 
-
-  channel specific_debug_level {
-      file "foo";
+. All debugging messages in the server have a debug level, and higher debug levels give more detailed output. Channels that specify a specific debug severity, for example:

+

+  channel specific_debug_level {
+      file "foo";
       severity debug 3;
-        };
+  };
 

 

 
@@ -1309,52 +1256,51 @@ print-
  options may be used in any combination, and will always be printed in the following order: time, category, severity. Here is an example where all three 
 print-
  options are on:

-

+

+

 
  
 
 28-Feb-2000 15:05:32.863 general: notice: running
-

+

 

 
- 
+
 There are four predefined channels that are used for 
 named
-'s default logging as follows. How they are used is described in the section 
+'s default logging as follows. How they are used is described in 
 The category Phrase
 .

 
-
-
-    channel default_syslog {
-        syslog daemon;    // end to syslog's daemon facility
-        severity info;    // only send priority info and higher
+

+    channel default_syslog {
+        syslog daemon;				// end to syslog's daemon facility
+        severity info;				// only send priority info and higher
     };
-    channel default_debug {
-        file "named.run";  // write to named.run in
-                          // the working directory
-                          // Note: stderr is used instead of
-                          // "named.run"
-                          // if the server is started
-                          // with the "-f" option.
-        severity dynamic  // log at the server's
-                          // current debug level
+    channel default_debug {
+        file "named.run";			// write to named.run in
+						// the working directory
+						// Note: stderr is used instead of
+						// "named.run"
+						// if the server is started
+						// with the '-f' option.
+        severity dynamic			// log at the server's
+						// current debug level
     };
-    channel default_stderr {  // writes to stderr
-        file "<stderr>";   // this is illustrative only;
-                          // there's currently no way of
-                          // specifying an internal file
-                          // descriptor in the configuration
-                          // language.
-        severity info;    // only send priority info and higher
+    channel default_stderr {				// writes to stderr
+        file "<stderr>";			// this is illustrative only;
+						// there's currently no way of
+						// specifying an internal file
+						// descriptor in the configuration
+						// language.
+        severity info;				// only send priority info and higher
     };
-    channel null {
-       null;                // toss anything sent to this channel
+    channel null {
+       null;					// toss anything sent to this channel
     };
 

-
 

-
+
  
 The 
 default_debug
@@ -1362,22 +1308,23 @@ default_debug
 named.run
  in the server's working directory.  For security reasons, when the "
 -u
-"command line option is used, the 
+" command line option is used, the 
 named.run
  file is created only after 
 named
  has changed to the new UID, and any debug output generated while 
 named
- is starting up and still running as root is discarded.  If you need to capture this output, you must run the server with the 
+ is starting up and still running as root is discarded.  If you need to capture this output, you must run the server with the "
 -g
- option and redirect standard error to a file.

+" option and redirect standard error to a file.

 

 
  
 Once a channel is defined, it cannot be redefined. Thus you cannot alter the built-in channels directly, but you can modify the default logging by pointing categories at channels you have defined.

 

+
-
    +
    @@ -1386,58 +1333,47 @@ Once a channel is defined, it cannot be redefined. Thus you cannot alter the bui The category Phrase
    -
+

There are many categories, so you can send the logs you want to see wherever you want, without seeing logs you don't want. If you don't specify a list of channels for a category, then log messages in that category will be sent to the default category instead. If you don't specify a default category, the following "default default" is used:

- -
-    category default { default_syslog; default_debug; };
-
+

+    category default { default_syslog; default_debug; };
 

-

-
- 
-As an example, let's say you want to log security events to a file, but you also want keep the default logging behavior. You'd specify the following:

- 
-
-
-channel my_security_channel {
-    file "my_security_file";
-    severity info;
+As an example, let's say you want to log security events to a file, but you also want keep the default logging behavior. You'd specify the following:
+

+channel my_security_channel {
+    file "my_security_file";
+    severity info;
 };
-category security {
-    my_security_channel;
+category security {
+    my_security_channel;
     default_syslog;
     default_debug;
-};
-
+};
 

 

 
  
 To discard all messages in a category, specify the 
-null
- channel:

-
-
-category lame-servers { null; };
-category cname { null; };
-
+null channel:

+

+category xfer-out { null; };
+category notify { null; };
 

 

 
  
-Following are the available categories and brief descriptions of the types of log information they contain.  
+Following are the available categories and brief descriptions of the types of log information they contain.  
 This list is still subject to change.
  

 

 

 
-

+

 
  
 
@@ -1449,14 +1385,14 @@ default
 
  
 The default category defines the logging options for those categories where no specific configuration has been defined. If you do not define a default category, the following definition is used:

-
-category default { default_syslog; default_debug; };
+
+category default { default_syslog; default_debug; };
 

 		
 

 

 
-

+

 
  
 
@@ -1472,7 +1408,7 @@ The catch-all. Many things still aren't classified into categories, and they all
 

 

 
-

+

 
  
 
@@ -1488,7 +1424,7 @@ Messages relating to the databases used internally by the name server to store z
 

 

 
-

+

 
  
 
@@ -1504,7 +1440,7 @@ Approval and denial of requests.

 

 

 
-

+

 
  
 
@@ -1520,7 +1456,7 @@ Configuration file parsing and processing.

 

 

 
-

+

 
  
 
@@ -1536,7 +1472,7 @@ DNS resolution, such as the recursive lookups performed on behalf of clients by
 

 

 
-

+

 
  
 
@@ -1552,7 +1488,7 @@ Zone transfers the server is receiving.

 

 

 
-

+

 
  
 
@@ -1568,7 +1504,7 @@ Zone transfers the server is sending.

 

 

 
-

+

 
  
 
@@ -1584,7 +1520,7 @@ The NOTIFY protocol.

 

 

 
-

+

 
  
 
@@ -1600,7 +1536,7 @@ Processing of client requests.

 

 

 
-

+

 
  
 
@@ -1616,7 +1552,7 @@ Network operations.

 

 

 
-

+

 
  
 
@@ -1634,14 +1570,14 @@ Dynamic updates.

 
 
 

-
    
+
 
    
 
  
 5.2.11	
 options
  Statement Grammar
    
-

+
 

 
  
@@ -1650,83 +1586,81 @@ option
  statement in the 
 named.conf
  file:

-
-
-options {
-    [ version version_string; ]
-    [ directory path_name; ]
-    [ named-xfer path_name; ]
-    [ tkey-domain domainname; ]
-    [ tkey-dhkey keyname keyid; ]
-    [ dump-file path_name; ]
-    [ memstatistics-file path_name; ]
-    [ pid-file path_name; ]
-    [ statistics-file path_name; ]
-    [ auth-nxdomain yes_or_no; ]
-    [ deallocate-on-exit yes_or_no; ]
-    [ dialup yes_or_no; ]
-    [ fake-iquery yes_or_no; ]
-    [ fetch-glue yes_or_no; ]
-    [ has-old-clients yes_or_no; ]
-    [ host-statistics yes_or_no; ]
-    [ multiple-cnames yes_or_no; ]
-    [ notify yes_or_no; ]
-    [ recursion yes_or_no; ]
-    [ rfc2308-type1 yes_or_no; ]
-    [ use-id-pool yes_or_no; ]
-    [ maintain-ixfr-base yes_or_no; ]
-    [ forward ( only | first ); ]
-    [ forwarders { [ in_addr ; [ in_addr ; ... ] ] }; ]
-    [ check-names ( master | slave | response )( warn | fail | ignore ); ]
-    [ allow-query { address_match_list }; ]
-    [ allow-transfer { address_match_list }; ]
-    [ allow-recursion { address_match_list }; ]
-    [ blackhole { address_match_list }; ]
-    [ listen-on [ port ip_port ] { address_match_list }; ]
-    [ query-source [ address ( ip_addr | * ) ] [ port ( ip_port | * ) ]; ]
-    [ max-transfer-time-in number; ]
-    [ max-transfer-time-out number; ]
-    [ max-transfer-idle-in number; ]
-    [ max-transfer-idle-out number; ]
-    [ tcp-clients number; ]
-    [ recursive-clients number; ]
-    [ serial-queries number; ]
-    [ transfer-format ( one-answer | many-answers ); ]
-    [ transfers-in  number; ]
-    [ transfers-out number; ]
-    [ transfers-per-ns number; ]
-    [ transfer-source ip_addr; ]
-    [ also-notify { ip_addr; [ ip_addr; ... ] }; ]
-    [ max-ixfr-log-size number; ]
-    [ coresize size_spec ; ]
-    [ datasize size_spec ; ]
-    [ files size_spec ; ]
-    [ stacksize size_spec ; ]
-    [ cleaning-interval number; ]
-    [ heartbeat-interval number; ]
-    [ interface-interval number; ]
-    [ statistics-interval number; ]
-    [ topology { address_match_list }; ]
-    [ sortlist { address_match_list };]
-    [ rrset-order { order_spec ; [ order_spec ; ... ] ] };
-    [ lame-ttl number; ]
-    [ max-ncache-ttl number; ]
-    [ min-roots number; ]
-    [ use-ixfr yes_or_no ; ]
-    [ treat-cr-as-space yes_or_no ; ]
-};
-
+

+options {
+    [ version version_string; ]
+    [ directory path_name; ]
+    [ named-xfer path_name; ]
+    [ tkey-domain domainname; ]
+    [ tkey-dhkey keyname keyid; ]
+    [ dump-file path_name; ]
+    [ memstatistics-file path_name; ]
+    [ pid-file path_name; ]
+    [ statistics-file path_name; ]
+    [ auth-nxdomain yes_or_no; ]
+    [ deallocate-on-exit yes_or_no; ]
+    [ dialup yes_or_no; ]
+    [ fake-iquery yes_or_no; ]
+    [ fetch-glue yes_or_no; ]
+    [ has-old-clients yes_or_no; ]
+    [ host-statistics yes_or_no; ]
+    [ multiple-cnames yes_or_no; ]
+    [ notify yes_or_no; ]
+    [ recursion yes_or_no; ]
+    [ rfc2308-type1 yes_or_no; ]
+    [ use-id-pool yes_or_no; ]
+    [ maintain-ixfr-base yes_or_no; ]
+    [ forward ( only | first ); ]
+    [ forwarders { [ in_addr ; [ in_addr ; ... ] ] }; ]
+    [ check-names ( master | slave | response )( warn | fail | ignore ); ]
+    [ allow-query { address_match_list }; ]
+    [ allow-transfer { address_match_list }; ]
+    [ allow-recursion { address_match_list }; ]
+    [ blackhole { address_match_list }; ]
+    [ listen-on [ port ip_port ] { address_match_list }; ]
+    [ query-source [ address ( ip_addr | * ) ] [ port (ip_port | * ) ]; ]
+    [ max-transfer-time-in number; ]
+    [ max-transfer-time-out number; ]
+    [ max-transfer-idle-in number; ]
+    [ max-transfer-idle-out number; ]
+    [ tcp-clients number; ]
+    [ recursive-clients number; ]
+    [ serial-queries number; ]
+    [ transfer-format ( one-answer | many-answers ); ]
+    [ transfers-in  number; ]
+    [ transfers-out number; ]
+    [ transfers-per-ns number; ]
+    [ transfer-source ip_addr; ]
+    [ also-notify { ip_addr; [ ip_addr; ... ] }; ]   
+    [ max-ixfr-log-size number; ]
+    [ coresize size_spec ; ]
+    [ datasize size_spec ; ]
+    [ files size_spec ; ]
+    [ stacksize size_spec ; ]
+    [ cleaning-interval number; ]
+    [ heartbeat-interval number; ]
+    [ interface-interval number; ]
+    [ statistics-interval number; ]
+    [ topology { address_match_list }; ]
+    [ sortlist { address_match_list }; ]
+    [ rrset-order { order_spec ; [ order_spec ; ... ] ] };
+    [ lame-ttl number; ]
+    [ max-ncache-ttl number; ]
+    [ sig-validity-interval number ; ]
+    [ min-roots number; ]
+    [ use-ixfr yes_or_no ; ]
+    [ treat-cr-as-space yes_or_no ; ]};
 

 

 

-
    
+
 
    
 
  
 5.2.12	
 options
  Statement Definition and Usage
    
-

+
 

 
  
@@ -1738,7 +1672,7 @@ options
 

 

 
-

+

 
  
 
@@ -1749,7 +1683,7 @@ version
 

 
  
-The version the server should report via a query of name 
+The version the server should report via a query of name 
 version.bind
  in class 
 chaos
@@ -1758,7 +1692,7 @@ chaos
 

 

 
-

+

 
  
 
@@ -1769,16 +1703,16 @@ directory
 

 
  
-The working directory of the server. Any non-absolute pathnames in the configuration file will be taken as relative to this directory. The default location for most server output files (e.g. 
+The working directory of the server. Any non-absolute pathnames in the configuration file will be taken as relative to this directory. The default location for most server output files (e.g. 
 named.run
-) is this directory. If a directory is not specified, the working directory defaults to `
+) is this directory. If a directory is not specified, the working directory defaults to `
 .
 ', the directory from which the server was started. The directory specified should be an absolute path.

 		
 

 

 
-

+

 
  
 
@@ -1789,7 +1723,7 @@ named-xfer
 

 
  
-
+
 This option is obsolete.
   It was used in BIND 8 to specify the pathname to the 
 named-xfer
@@ -1800,7 +1734,7 @@ named-xfer
 

 

 
-

+

 
  
 
@@ -1830,7 +1764,7 @@ domainname
 

 

 
-

+

 
  
 
@@ -1848,7 +1782,7 @@ TKEY
 

 

 
-

+

 
  
 
@@ -1863,16 +1797,16 @@ The pathname of the file the server dumps the database to when it receives 
  signal (
 ndc dumpdb
-). If not specified, the default is 
+). If not specified, the default is 
 named_dump.db
-. 
+. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -1883,16 +1817,16 @@ memstatistics-file
 

 
  
-The pathname of the file the server writes memory usage statistics to on exit.  If not specified, the default is 
+The pathname of the file the server writes memory usage statistics to on exit. If not specified, the default is 
 named.memstats
-. 
+. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -1904,16 +1838,16 @@ pid-file
 
  
 The pathname of the file the server writes its process ID in. If not specified, the default is operating system dependent, but is usually

-
+
 /var/run/named.pid
- or 
+ or 
 /etc/named.pid
 . The pid-file is used by programs that want to send signals to the running nameserver.

 		
 

 

 
-

+

 
  
 
@@ -1924,23 +1858,23 @@ statistics-file
 

 
  
-The pathname of the file the server appends statistics to. If not specified, the default is 
+The pathname of the file the server appends statistics to. If not specified, the default is 
 named.stats
-. 
+. 
 Not yet implemented in BINDv9
 .

 		
 

 

 

-
    
+
 
    
 
  
 5.2.12.1	
  
 Boolean Options
    
-

+
 

 
  
@@ -1948,7 +1882,7 @@ Boolean Options
 

 

 
-

+

 
  
 
@@ -1959,20 +1893,20 @@ auth-nxdomain
 

 
  
-If 
-yes
+If 
+yes
 , then the 
 AA
- bit is always set on NXDOMAIN responses, even if the server is not actually authoritative. The default is 
-no
-; this is a change from BIND 8. If you are using very old DNS software, you may need to set it to 
-yes
+ bit is always set on NXDOMAIN responses, even if the server is not actually authoritative. The default is 
+no
+; this is a change from BIND 8. If you are using very old DNS software, you may need to set it to 
+yes
 .

 		
 

 

 
-

+

 
  
 
@@ -1988,7 +1922,7 @@ This option was used in BIND 8 to enable checking for memory leaks on exit. BIND
 

 

 
-

+

 
  
 
@@ -1999,12 +1933,12 @@ dialup
 

 
  
-If 
-yes
+If 
+yes
 , then the server treats all zones as if they are doing zone transfers across a dial on demand dialup link, which can be brought up by traffic originating from this server. This has different effects according to zone type and concentrates the zone maintenance so that it all happens in a short interval, once every 
 heartbeat-interval
- and hopefully during the one call. It also suppresses some of the normal zone maintenance traffic. The default is 
-no
+ and hopefully during the one call. It also suppresses some of the normal zone maintenance traffic. The default is 
+no
 .

 

 
@@ -2026,14 +1960,14 @@ If the zone is a master then the server will send out a NOTIFY request to all th
 If the zone is a slave or stub then the server will suppress the regular "zone up to date" queries and only perform them when the

 
 heartbeat-interval
- expires.  
+ expires.  
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2049,7 +1983,7 @@ In BIND 8, this option was used to enable simulating the obsolete DNS query type
 

 

 
-

+

 
  
 
@@ -2060,20 +1994,30 @@ fetch-glue
 

 
  
-If 
-yes
- (the default), the server will fetch "glue" resource records it doesn't have when constructing the additional data section of a response. (Information present outside of the authoritative nodes in the zone is called "glue" information). 
-fetch-glue no 
+(Information present outside of the authoritative nodes in the zone is called 
+glue
+ information). If 
+yes
+ (the default), the server will fetch glue resource records it doesn't have when constructing the additional data section of a response. 
+fetch-glue 
+
+no
+
+ 
 can be used in conjunction with 
-recursion no 
-to prevent the server's cache from growing or becoming corrupted (at the cost of requiring more work from the client). 
+recursion 
+
+no
+
+ 
+to prevent the server's cache from growing or becoming corrupted (at the cost of requiring more work from the client). 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2086,17 +2030,23 @@ has-old-clients
  
 This option was incorrectly implemented in BIND 8, and is ignored by BINDv9.  To achieve the intended effect of

 
-has-old-clients yes
+has-old-clients 
+
+yes
 , specify the two separate options 
-auth-nxdomain yes
+auth-nxdomain 
+
+yes
  and 
-rfc2308-type-1 no
+rfc2308-type1 
+
+no
  instead.

 		
 

 

 
-

+

 
  
 
@@ -2107,20 +2057,20 @@ host-statistics
 

 
  
-If 
-yes
-, then statistics are kept for every host that the nameserver interacts with. The default is 
-no
+If 
+yes
+, then statistics are kept for every host that the nameserver interacts with. The default is 
+no
 . Note: turning on 
 host-statistics
- can consume huge amounts of memory. 
+ can consume huge amounts of memory. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2131,16 +2081,18 @@ maintain-ixfr-base
 

 
  
-
+
 This option is obsolete
 .  It was used in BIND 8 to determine whether a transaction log was kept for Incremental Zone Transfer. BINDv9 maintains a transaction log whenever possible.  If you need to disable outgoing incremental zone transfers, use 
-provide-ixfr no
+provide-ixfr 
+
+no
 .

 		
 

 

 
-

+

 
  
 
@@ -2156,7 +2108,7 @@ This option was used in BIND 8 to allow a domain name to allow multiple CNAME re
 

 

 
-

+

 
  
 
@@ -2167,22 +2119,23 @@ notify
 

 
  
-If 
-yes
- (the default), DNS NOTIFY messages are sent when a zone the server is authoritative for changes. The use of NOTIFY speeds synchronization between the master and its slaves. Slave servers that receive a NOTIFY message and understand it will contact the master server for the zone and see if they need to do a zone transfer, and if they do, they will initiate it immediately. The 
+If 
+yes
+ (the default), DNS NOTIFY messages are sent when a zone the server is authoritative for changes. See  Notify
+, for more information. The 
 notify
  option may also be specified in the 
 zone
  statement, in which case it overrides the 
 options notify
- statement. It would only be necessary to turn off this option if it caused slaves to crash. 
-Not yet supported in BINDv9.
+ statement. It would only be necessary to turn off this option if it caused slaves to crash
+.
 

 		
 

 

 
-

+

 
  
 
@@ -2193,10 +2146,10 @@ recursion
 

 
  
-If 
-yes
-, and a DNS query requests recursion, then the server will attempt to do all the work required to answer the query. If recursion is not on, the server will return a referral to the client if it doesn't know the answer. The default is 
-yes
+If 
+yes
+, and a DNS query requests recursion, then the server will attempt to do all the work required to answer the query. If recursion is not on, the server will return a referral to the client if it doesn't know the answer. The default is 
+yes
 . See also 
 fetch-glue
  above.

@@ -2204,7 +2157,7 @@ fetch-glue
 

 

 
-

+

 
  
 
@@ -2213,22 +2166,20 @@ rfc2308-type1
 

 
 

-
+
  
-If 
-yes
-, the server will send NS records along with the SOA record for negative answers. You need to set this to 
-no
- if you have an old BIND server using you as a forwarder that does not understand negative answers which contain both SOA and NS records or you have an old version of sendmail. The correct fix is to upgrade the broken server or sendmail. The default is 
-no
-. 
+Setting this to 
+yes
+ will cause the server to send NS records along The default is 
+no
+. 
 Not yet implemented in BINDv9
 .

 		
 

 

 
-

+

 
  
 
@@ -2239,14 +2190,14 @@ use-id-pool
 

 
  
-
+
 This option is obsolete
 .  BINDv9 always allocates query IDs from a pool.

 		
 

 

 
-

+

 
  
 
@@ -2257,30 +2208,28 @@ treat-cr-as-space
 

 
  
-This option was used in BIND 8 to make the server treat `
+This option was used in BIND 8 to make the server treat "
 \r
-' characters the same way as 
+" characters the same way as 
 <space> 
-`
- 
-` or `
+" " or "
 \t
-', to facilitate loading of zone files on a UNIX system that were generated on an NT or DOS machine. In BINDv9, both UNIX `
+", to facilitate loading of zone files on a UNIX system that were generated on an NT or DOS machine. In BINDv9, both UNIX "
 \n
-' and NT/DOS `
+" and NT/DOS "
 \r\n
-' newlines are always accepted, and the option is ignored.

+" newlines are always accepted, and the option is ignored.

 		
 

 

 

 

-
    
+
 
    
 
  
 5.2.12.2	Forwarding
    
-

+
 

 
  
@@ -2292,7 +2241,7 @@ The forwarding facility can be used to create a large site-wide cache on a few s
 

 

 
-

+

 
  
 
@@ -2312,7 +2261,7 @@ only
 

 

 
-

+

 
  
 
@@ -2337,14 +2286,14 @@ zone Statement Grammar
  for more information.

 
 

-
    
+
 
    
 
  
 5.2.12.3	
  
 Name Checking
    
-

+
 

 
  
@@ -2360,7 +2309,7 @@ Three checking methods are available:

 

 

 
-

+

 
  
 
@@ -2376,7 +2325,7 @@ No checking is done.

 

 

 
-

+

 
  
 
@@ -2392,7 +2341,7 @@ Names are checked against their expected client contexts. Invalid names are logg
 

 

 
-

+

 
  
 
@@ -2417,12 +2366,10 @@ check-names response fail
 
  
 The defaults are:

- 
-
-    check-names master fail;
+

+    check-names master fail;
     check-names slave warn;
-    check-names response ignore;
-

+    check-names response ignore;

 

 
  
@@ -2434,23 +2381,22 @@ zone
 options check-names
  statement. When used in a 
 zone
- statement, the area is not specified (because it can be deduced from the zone type).

-

-
- 
-
-Name checking is not yet implemented in BINDv9.
+ statement, the area is not specified because it can be deduced from the zone type.

+

+

+Name checking is not yet implemented in BINDv9.
 

 

+
 

-
    
+
 
    
 
  
 5.2.12.4	
  
 Access Control
    
-

+
 

 
  
@@ -2464,7 +2410,7 @@ Address Match Lists
 
@@ -2545,12 +2491,12 @@ Not yet implemented in BINDv9.

 

 
-

+

 
  
 
@@ -2486,7 +2432,7 @@ options allow-query
 

 

 
-

+

 
  
 
@@ -2502,7 +2448,7 @@ Specifies which hosts are allowed to make recursive queries through this server.
 

 

 
-

+

 
  
 
@@ -2524,7 +2470,7 @@ options allow-transfer
 

 

 
-

+

 
  
 
@@ -2535,9 +2481,9 @@ blackhole
 

 
  
-Specifies a list of addresses that the server will not accept queries from or use to resolve a query. Queries from these addresses will not be responded to. The default is 
-none
-.  
+Specifies a list of addresses that the server will not accept queries from or use to resolve a query. Queries from these addresses will not be responded to. The default is 
+none
+.  
 Not yet implemented in BINDv9.
 

 		
 

 

 

-
    
+
 
    
 
  
 5.2.12.5	Interfaces
    
-

+
 

 
  
@@ -2558,18 +2504,22 @@ The interfaces and ports that the server will answer queries from may be specifi
 listen-on
  option. 
 listen-on
- takes an optional port, and an 
-address_match_list
+ takes an optional port, and an 
+address_match_list
 . The server will listen on all interfaces allowed by the address match list. If a port is not specified, port 53 will be used.

 

 
  
-Multiple listen-on statements are allowed. For example,

- 
-
-listen-on { 5.6.7.8; };
+Multiple 
+listen-on
+ statements are allowed. For example,

+

+
+ 
+
+listen-on { 5.6.7.8; };

 listen-on port 1234 { !1.2.3.4; 1.2/16; };
-

+

 

 
  
@@ -2581,19 +2531,60 @@ If no 
 listen-on
  is specified, the server will listen on port 53 on all interfaces.

 

-
+
  
-The listen-on option only applies to IPv4.  Currently, the server always listens for IPv6 requests on a wildcard address and port 53.  A separate 
+The 
 listen-on-v6
- option may be added in a later release.

+ option is used to specify the ports on which the server will listen for incoming queries sent using IPv6.

+

+
+ 
+The server does not bind a separate socket to each IPv6 interface address as it does for IPv4. Instead, it always listens on the IPv6 wildcard address. Therefore, the only values allowed for the 
+address_match_list
+ argument to the 
+listen-on-v6
+ statement are "
+{ any; }
+" and "
+{ none; }
+".

+

+
+ 
+Multiple 
+listen-on-v6
+ options can be used to listen on multiple ports:

+

+
+ 
+
+listen-on-v6 port 53 { any; };

+listen-on-v6 port 1234 { any; };
+

+

+
+ 
+To make the server not listen on any IPv6 address, use

+

+
+ 
+
+listen-on-v6 { none; };
+

+

+
+ 
+If no 
+listen-on-v6 
+statement is specified, the server will listen on port 53 on the IPv6 wildcard address.

 

 

-
    
+
 
    
 
  
 5.2.12.6	Query Address
    
-

+
 

 
  
@@ -2612,11 +2603,18 @@ port
  is 
 *
  or is omitted, a random unprivileged port will be used. The defaults are

- 
-
-query-source address * port *;
+

+
+ 
+
+query-source address * port *;
+

+

+
+ 
+
 query-source-v6 address * port *
-

+

 

 
  
@@ -2625,14 +2623,14 @@ query-source
  currently applies only to UDP queries; TCP queries always use a wildcard IP address and a random unprivileged port.

 

 

-
    
+
 
    
 
  
 5.2.12.7	
  
 Zone Transfers
    
-

+
 

 
  
@@ -2644,7 +2642,7 @@ BIND has mechanisms in place to facilitate zone transfers and set limits on the
 

 

 
-

+

 
  
 
@@ -2655,7 +2653,7 @@ also-notify
 

 
  
-Defines a global list of IP addresses that are also sent NOTIFY messages whenever a fresh copy of the zone is loaded. This helps to ensure that copies of the zones will quickly converge on "stealth" servers. If an 
+Defines a global list of IP addresses that are also sent NOTIFY messages whenever a fresh copy of the zone is loaded. This helps to ensure that copies of the zones will quickly converge on stealth servers. If an 
 also-notify
  list is given in a 
 zone
@@ -2667,14 +2665,12 @@ zone notify
 no
 , the IP addresses in the global 
 also-notify
- list will not be sent NOTIFY messages for that zone. The default is the empty list (no global notification list). 
-Not yet implemented in BINDv9.
-

+ list will not be sent NOTIFY messages for that zone. The default is the empty list (no global notification list).

 		
 

 

 
-

+

 
  
 
@@ -2690,7 +2686,7 @@ Inbound zone transfers running longer than this many minutes will be terminated.
 

 

 
-

+

 
  
 
@@ -2706,7 +2702,7 @@ Inbound zone transfers making no progress in this many minutes will be terminate
 

 

 
-

+

 
  
 
@@ -2722,7 +2718,7 @@ Outbound zone transfers running longer than this many minutes will be terminated
 

 

 
-

+

 
  
 
@@ -2742,7 +2738,7 @@ Outbound zone transfers making no progress in this many minutes will be terminat
 

 

 
-

+

 
  
 
@@ -2755,14 +2751,14 @@ serial-queries
  
 Slave servers will periodically query master servers to find out if zone serial numbers have changed. Each such query uses a minute amount of the slave server's network bandwidth, but more importantly each query uses a small amount of memory in the slave server while waiting for the master server to respond. The 
 serial-queries 
-option sets the maximum number of concurrent serial-number queries allowed to be outstanding at any given time. The default is 4. Note: If a server loads a large (tens or hundreds of thousands) number of slave zones, then this limit should be raised to the high hundreds or low thousands -- otherwise the slave server may never actually become aware of zone changes in the master servers. Beware, though, that setting this limit arbitrarily high can spend a considerable amount of your slave server's network, CPU, and memory resources. As with all tunable limits, this one should be changed gently and monitored for its effects. 
+option sets the maximum number of concurrent serial-number queries allowed to be outstanding at any given time. The default is 4. Note: If a server loads a large (tens or hundreds of thousands) number of slave zones, then this limit should be raised to the high hundreds or low thousands, otherwise the slave server may never actually become aware of zone changes in the master servers. Beware, though, that setting this limit arbitrarily high can spend a considerable amount of your slave server's network, CPU, and memory resources. As with all tunable limits, this one should be changed gently and monitored for its effects. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2790,7 +2786,7 @@ server
 

 

 
-

+

 
  
 
@@ -2801,14 +2797,16 @@ transfers-in
 

 
  
-The maximum number of inbound zone transfers that can be running concurrently. The default value is 10. Increasing 
+The maximum number of inbound zone transfers that can be running concurrently. The default value is 
+10
+. Increasing 
 transfers-in
  may speed up the convergence of slave zones, but it also may increase the load on the local system.

 		
 

 

 
-

+

 
  
 
@@ -2819,12 +2817,14 @@ transfers-out
 

 
  
-The maximum number of outbound zone transfers that can be running concurrently. Zone transfer requests in excess of the limit will be refused. The default value is 10.

+The maximum number of outbound zone transfers that can be running concurrently. Zone transfer requests in excess of the limit will be refused. The default value is 
+10
+.

 		
 

 

 
-

+

 
  
 
@@ -2835,7 +2835,9 @@ transfers-per-ns
 

 
  
-The maximum number of inbound zone transfers that can be concurrently transferring from a given remote nameserver. The default value is 2. Increasing 
+The maximum number of inbound zone transfers that can be concurrently transferring from a given remote nameserver. The default value is 
+2
+. Increasing 
 transfers-per-ns
  may speed up the convergence of slave zones, but it also may increase the load on the remote nameserver. 
 transfers-per-ns
@@ -2848,7 +2850,7 @@ server
 

 

 
-

+

 
  
 
@@ -2875,7 +2877,7 @@ zone
 

 

 
-

+

 
  
 
@@ -2894,12 +2896,12 @@ transfer-source
 

 

 

-
    
+
 
    
 
  
 5.2.12.8	Resource Limits
    
-

+
 

 
  
@@ -2927,7 +2929,7 @@ Configuration File Grammar
 

 

 
-

+

 
  
 
@@ -2938,16 +2940,16 @@ coresize
 

 
  
-The maximum size of a core dump. The default is 
-default
-. 
+The maximum size of a core dump. The default is 
+default
+. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2958,16 +2960,16 @@ datasize
 

 
  
-The maximum amount of data memory the server may use. The default is 
-default
-. 
+The maximum amount of data memory the server may use. The default is 
+default
+. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -2978,10 +2980,10 @@ files
 

 
  
-The maximum number of files the server may have open concurrently. The default is 
-unlimited
-. Note: on some operating systems the server cannot set an unlimited value and cannot determine the maximum number of open files the kernel can support. On such systems, choosing 
-unlimited
+The maximum number of files the server may have open concurrently. The default is 
+unlimited
+. Note: on some operating systems the server cannot set an unlimited value and cannot determine the maximum number of open files the kernel can support. On such systems, choosing 
+unlimited
  will cause the server to use the larger of the 
 rlim_max
  for 
@@ -2990,14 +2992,14 @@ RLIMIT_NOFILE
 sysconf(_SC_OPEN_MAX)
 . If the actual kernel limit is larger than this value, use 
 limit files 
-to specify the limit explicitly. 
+to specify the limit explicitly. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -3010,14 +3012,14 @@ max-ixfr-log-size
  
 The 
 max-ixfr-log-size
- will be used in a future release of the server to limit the size of the transaction log kept for Incremental Zone Transfer. 
+ will be used in a future release of the server to limit the size of the transaction log kept for Incremental Zone Transfer. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -3028,12 +3030,14 @@ recursive-clients
 

 
  
-The maximum number of simultaneous recursive lookup the server will perform on behalf of clients.  The default is 100.

+The maximum number of simultaneous recursive lookup the server will perform on behalf of clients.  The default is 
+100
+.

 		
 

 

 
-

+

 
  
 
@@ -3044,16 +3048,16 @@ stacksize
 

 
  
-The maximum amount of stack memory the server may use. The default is 
-default
-. 
+The maximum amount of stack memory the server may use. The default is 
+default
+. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -3064,24 +3068,25 @@ tcp-clients
 

 
  
-The maximum number of simultaneous client TCP connections that the server will accept. The default is 100.

+The maximum number of simultaneous client TCP connections that the server will accept. The default is 
+100
+.

 		
 

 

-

-
- 
-
-Resource limits are not yet implemented in BINDv9.
+

+

+Resource limits are not yet implemented in BINDv9.
 

 

+

 

-
    
+
 
    
 
  
 5.2.12.9	Periodic Task Intervals
    
-

+
 

 
  
@@ -3089,7 +3094,7 @@ Resource limits are not yet implemented in BINDv9.
 
@@ -3168,14 +3189,14 @@ Not yet implemented in BINDv9.

 

 
-

+

 
  
 
@@ -3102,12 +3107,16 @@ cleaning-interval
  
 The server will remove expired resource records from the cache every 
 cleaning-interval 
-minutes. The default is 60 minutes. If set to 0, no  periodic cleaning will occur.

+minutes. The default is 
+60
+ minutes. If set to 
+0
+, no  periodic cleaning will occur.

 		
 

 

 
-

+

 
  
 
@@ -3120,14 +3129,18 @@ heartbeat-interval
  
 The server will perform zone maintenance tasks for all zones marked  
 dialup yes
- whenever this interval expires. The default is 60 minutes.  Reasonable values are up to 1 day (1440 minutes). If set to 0, no zone maintenance for these zones will occur. 
+ whenever this interval expires. The default is 
+60
+ minutes.  Reasonable values are up to 1 day (1440 minutes). If set to 
+0
+, no zone maintenance for these zones will occur. 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -3140,14 +3153,18 @@ interface-interval
  
 The server will scan the network interface list every 
 interface-interval
- minutes. The default is 60 minutes. If set to 0,  interface scanning will only occur when the configuration file is  loaded. After the scan, listeners will be started on any new interfaces (provided they are allowed by the 
+ minutes. The default is 
+60
+ minutes. If set to 
+0
+,  interface scanning will only occur when the configuration file is  loaded. After the scan, listeners will be started on any new interfaces (provided they are allowed by the 
 listen-on
  configuration). Listeners on interfaces that have gone away will be cleaned up.

 		
 

 

 
-

+

 
  
 
@@ -3160,7 +3177,11 @@ statistics-interval
  
 Nameserver statistics will be logged every 
 statistics-interval
- minutes. The default is 60. If set to 0, no statistics will be logged. 
+ minutes. The default is 
+60
+. If set to 
+0
+, no statistics will be logged. 
 Not yet implemented in BINDv9.
 

 		
 

 

 

-
    
+
 
    
 
  
 5.2.12.10	
  
 Topology
    
-

+
 

 
  
@@ -3184,9 +3205,8 @@ topology
  statement takes an 
 address_match_list
  and interprets it in a special way. Each top-level list element is assigned a distance. Non-negated elements get a distance based on their position in the list, where the closer the match is to the start of the list, the shorter the distance is between it and the server. A negated match will be assigned the maximum distance from the server. If there is no match, the address will get a distance which is further than any non-negated list element, and closer than any negated element. For example,

- 
-
-    topology {
+

+    topology {
     10/8;
     !1.2.3/24;
     { 1.2/16; 3/8; };
@@ -3200,24 +3220,25 @@ will prefer servers on network 10 the most, followed by hosts on network 1.2.0.0
 
  
 The default topology is

- 
-
-CODE>    topology { localhost; localnets; };
-
-

+

+
+ 
+
+    topology { localhost; localnets; };
+

 

 
  
-
+
 The 
 
 topology
-
+
  option is not yet implemented in BINDv9.
 

 

 

-
    
+
 
    
 
  
@@ -3226,11 +3247,11 @@ topology
 The 
 sortlist
  Statement
    
-

+
 

 
  
-Resource Records (RRs) are the data associated with the names in a  domain name space. The data is maintained in the form of sets of RRs. The order of RRs in a set is, by default, not significant. Therefore, to control the sorting of records in a set resource records, or 
+Resource Records (RRs) are the data associated with the names in a  domain name space. The data is maintained in the form of sets of RRs. The order of RRs in a set is, by default, not significant. Therefore, to control the sorting of records in a set resource records, or 
 RRset
 , you must use the 
 sortlist
@@ -3239,14 +3260,16 @@ sortlist
 
  
 RRs are explained more fully in 
-See Types of Resource Records and When to Use Them.
+Types of Resource Records and When to Use Them
 . Specifications for RRs are documented in RFC 1035.

 

 
  
-When returning multiple RRs, the nameserver will normally return them in 
-Round Robin 
-order, i.e. after each request, the first RR is put at the end of the list. The client resolver code should rearrange the RRs as appropriate, i.e. using any addresses on the local net in preference to other addresses. However, not all resolvers can do this or are correctly configured. When a client is using a local server the sorting can be performed in the server, based on the client's address. This only requires configuring the nameservers, not all the clients.

+When returning multiple RRs the nameserver will normally return them in 
+Round Robin
+
+ 
+order, that is, after each request the first RR is put at the end of the list. The client resolver code should rearrange the RRs as appropriate, that is, using any addresses on the local net in preference to other addresses. However, not all resolvers can do this or are correctly configured. When a client is using a local server the sorting can be performed in the server, based on the client's address. This only requires configuring the nameservers, not all the clients.

 

 
  
@@ -3279,66 +3302,64 @@ topology
 In the following example, any queries received from any of the addresses of the host itself will get responses preferring addresses on any of the locally connected networks. Next most preferred are addresses on the 192.168.1/24 network, and after that either the 192.168.2/24 or

 192.168.3/24 network with no preference shown between these two networks. Queries received from a host on the 192.168.1/24 network will prefer other addresses on that network to the 192.168.2/24 and

 192.168.3/24 networks. Queries received from a host on the 192.168.4/24 or the 192.168.5/24 network will only prefer other addresses on their directly connected networks.

- 
-
-sortlist {
-    { localhost;            // IF   the local host
-        { localnets;        // THEN first fit on the
-            192.168.1/24;   //   following nets
+

+sortlist {
+    { localhost;					// IF   the local host
+        { localnets;					// THEN first fit on the
+            192.168.1/24;					//   following nets
             { 192,168.2/24; 192.168.3/24; }; }; };
-    { 192.168.1/24;         // IF   on class C 192.168.1
-        { 192.168.1/24;     // THEN use .1, or .2 or .3
+    { 192.168.1/24;					// IF   on class C 192.168.1
+        { 192.168.1/24;					// THEN use .1, or .2 or .3
             { 192.168.2/24; 192.168.3/24; }; }; };
-    { 192.168.2/24;         // IF   on class C 192.168.2
-        { 192.168.2/24;    // THEN use .2, or .1 or .3
+    { 192.168.2/24;					// IF   on class C 192.168.2
+        { 192.168.2/24;					// THEN use .2, or .1 or .3
             { 192.168.1/24; 192.168.3/24; }; }; };
-    { 192.168.3/24;        // IF   on class C 192.168.3
-        { 192.168.3/24;    // THEN use .3, or .1 or .2
+    { 192.168.3/24;					// IF   on class C 192.168.3
+        { 192.168.3/24;					// THEN use .3, or .1 or .2
             { 192.168.1/24; 192.168.2/24; }; }; };
     { { 192.168.4/24; 192.168.5/24; };
-                          // if .4 or .5, prefer that net
+							// if .4 or .5, prefer that net
     };
 };
 

-
 

 
  
 The following example will give reasonable behavior for the local host and hosts on directly connected networks. It is similar to the behavior of the address sort in BIND 8.x. Responses sent to queries from the local host will favor any of the directly connected networks. Responses sent to queries from any other hosts on a directly connected network will prefer addresses on that same network. Responses to other queries will not be sorted.

- 
-
-
-sortlist {
-           { localhost; localnets; };
-           { localnets; };
+

+
+
+
+sortlist {

+           { localhost; localnets; };

+           { localnets; };

 };
-

-
+

 

 
  
-
+
 The 
 
 sortlist
-
+
  option is not yet implemented in BINDv9.
 

 

 

-
    
+
 
    
 
  
 5.2.12.12	
  
 RRset Ordering
    
-

+
 

 
  
 When multiple records are returned in an answer it may be useful to configure the order of the records placed into the response. For example, the records for a zone might be configured always to be returned in the order they are defined in the zone file. Or perhaps a random shuffle of the records as they are returned is wanted. The 
-rrset-order
+ 
  statement permits configuration of the ordering made of the records in a multiple record response. The default, if no ordering is defined, is a cyclic ordering (round robin).

 

 
@@ -3346,13 +3367,9 @@ rrset-order
 An 
 order_spec
  is defined as follows:

- 
-
-
-[ class class_name ][ type type_name ][ name "domain_name"]
-      order ordering
+
[ class class_name ][ type type_name ][ name "domain_name"]
+      order ordering
 

-
 

 
  
@@ -3360,9 +3377,9 @@ If no class is specified, the default is 
 ANY
 . If no type is specified, the default is 
 ANY
-. If no name is specified, the default is `
+. If no name is specified, the default is "
 *
-'.

+".

 

 
  
@@ -3376,7 +3393,7 @@ ordering
 

 

 
-

+

 
  
 
@@ -3392,7 +3409,7 @@ Records are returned in the order they are defined in the zone file.

 

 

 
-

+

 
  
 
@@ -3408,7 +3425,7 @@ Records are returned in some random order.

 

 

 
-

+

 
  
 
@@ -3425,42 +3442,36 @@ Records are returned in a round-robin order.

 

 

 
- 
+
 For example:

- 
-
-    rrset-order {
-        class IN type A name "host.example.com" order random;
-        order cyclic;
-    };
-
+

+    rrset-order {
+        class IN type A name "host.example.com" order random;
+        order cyclic;
+    };
 

 

 
  
-will cause any responses for type 
-A
- records in class 
-IN
- that have "host.example.com" as a suffix, to always be returned in random order. All other records are returned in cyclic order.

+will cause any responses for type A records in class IN that have "
+host.example.com
+" as a suffix, to always be returned in random order. All other records are returned in cyclic order.

 

 
- 
+
 If multiple 
 rrset-order
  statements appear, they are not combined--the last one applies.

 

 
- 
+
 If no 
 rrset-order
  statement is specified, then a default one of:

- 
-
-    rrset-order { class ANY type ANY name "*"; order cyclic 
-     };
+

+    rrset-order { class ANY type ANY name "*"; order cyclic ;
+ };
 

-
 

 
  
@@ -3468,21 +3479,23 @@ is used.

 

 
  
-
+
 The 
 
 rrset-order
-
+
  statement is not yet implemented in BINDv9.
 

 

 

-
    
+
 
    
 
  
-5.2.12.13	Tuning
    
-

+5.2.12.13	
+ 
+Tuning
+
 

 
  
@@ -3490,7 +3503,7 @@ rrset-order
 
+
+
+
+
+
+
+
+

 

 
-

+

 
  
 
@@ -3501,14 +3514,18 @@ lame-ttl
 

 
  
-Sets the number of seconds to cache a lame server indication. 0 disables caching. (This is NOT recommended.) Default is 600 (10 minutes). Maximum value is 1800 (30 minutes). 
+Sets the number of seconds to cache a lame server indication. 0 disables caching. (This is NOT recommended.) Default is 
+600
+ (10 minutes). Maximum value is 
+1800
+ (30 minutes). 
 Not yet implemented in BINDv9.
 

 		
 

 

 
-

+

 
  
 
@@ -3524,17 +3541,35 @@ max-ncache-ttl
  is used to set a maximum retention time for these answers in the server in seconds. The default

 
 max-ncache-ttl
- is 10800 seconds (3 hours).

+ is 
+10800
+ seconds (3 hours).

 
 max-ncache-ttl
- cannot exceed the maximum retention time for ordinary (positive) answers (7 days) and will be silently truncated to 7 days if set to a value which is greater that 7 days. 
-Not yet implemented in BINDv9.
-

+ cannot exceed 7 days and will be silently truncated to 7 days if set to a greater value.

 		
 

 

 
+

+
+ 
+
+max-cache-ttl
+

+		
 

+
+ 
+
+max-cache-ttl
+ sets the maximum time for which the server will cache ordinary (positive) answers. The default is one week (7 days).

+

+

 
  
 
@@ -3545,36 +3580,58 @@ min-roots
 

 
  
-The minimum number of root servers that is required for a request for the root servers to be accepted. Default is 2. 
+The minimum number of root servers that is required for a request for the root servers to be accepted. Default is 
+2
+. 
 Not yet implemented in BINDv9.
 

 		
 

+

+
+ 
+
+sig-validity-interval
+

+		
+

+
+
+Specifies the number of days into the future when DNSSEC signatures automatically generated as a result of dynamic updates (see 
+See Dynamic Update.
+ ) will expire. The default is 
+30
+ days. The signature inception time is unconditionally set to one hour before the current time to allow for a limited amount of clock skew.

+

 

 

 

-
    
+
 
    
 
  
 5.2.12.14	Deprecated Features
    
-

+
 

 
- 
+
 
 use-ixfr
- is deprecated in BINDv9. If you need to disable IXFR to a particular server or servers see information on the  
+ is deprecated in BINDv9. If you need to disable IXFR to a particular server or servers see the information on the  
 provide-ixfr
- option in the Server Statement description (
+ option in 
 server Statement Grammar
- , below) and  in the description of Incremental Transfer (IXFR) in the section 
+. See also the description of Incremental Transfer (IXFR) in the section 
 Incremental Zone Transfers (IXFR)
 .

 

 
 

-
    
+
 
    
 
  
@@ -3583,35 +3640,38 @@ server
 
  
  Statement Grammar
    
-

-
- 
-
-server ip_addr {
-    [ bogus yes_or_no ; ]
-    [ provide-ixfr yes_or_no ; ]
-    [ request-ixfr yes_or_no ; ]
-    [ transfers number ; ]
-    [ transfer-format (one-answer | many-answers) ; ]
-    [ keys { string ; [ string ; [...]] } ; ]
-};
-
-

+
+

+server ip_addr {
+     [ bogus yes_or_no ; ]
+
+    [ provide-ixfr yes_or_no ; ]
+
+    [ request-ixfr yes_or_no ; ]
+
+    [ transfers number ; ]
+
+    [ transfer-format ( one-answer | many-answers ) ; ]
+
+    [ keys { string ; [ string ; [...]] } ; ]

+};
 

 

 

-
    
+
 
    
 
  
 5.2.14	
 server
  Statement Definition and Usage
    
-

+
 

 
  
-The server statement defines the characteristics to be associated with a remote nameserver.

+The 
+server
+ statement defines the characteristics to be associated with a remote nameserver.

 

 
  
@@ -3619,11 +3679,11 @@ If you discover that a remote server is giving out bad data, marking it as bogus
 bogus
  is 
 no
-. 
+. 
 The 
 
 bogus
-
+
  clause is not yet implemented in BINDv9.
 

 

@@ -3679,7 +3739,11 @@ options
  
 
 transfers
- is used to limit the number of concurrent in-bound zone transfers from the specified server.

+ is used to limit the number of concurrent inbound zone transfers from the specified server. If no 
+transfers
+ clause is specified, the limit is set according to the 
+transfers-per-ns
+ option.

 

 
  
@@ -3702,82 +3766,71 @@ keys
  clause allows for multiple keys, only a single key per server is currently supported.

 

 

-
    
+
 
    
 
  
 5.2.15	
 trusted-keys
  Statement Grammar
    
-

- 
+
 
-trusted-keys {
-    string number number number string ;
-    [ string number number number string ; [...]]
-};
-
+trusted-keys {

+    string number number number string ;

+    [ string number number number string ; [...]]

+};
 

 

 

-
    
+
 
    
 
  
 5.2.16	
 trusted-keys
  Statement Definition and Usage
    
-

+
 

-
+
  
-The trusted-keys statement is for use with DNSSEC-style security, originally specified in RFC 2065. DNSSEC is meant to provide three distinct services: key distribution, data origin authentication, and transaction and request authentication. A complete description of DNSSEC and its use is beyond the scope of this document, and readers interested in more information should start with RFC 2065 and then continue with the relevant 
-Internet Drafts 
-(IDs) documents. A list of the IDs pertaining to DNSSEC can be found in 
-Internet Drafts
-  in Appendix C of this document. (Their filenames begin with "
-draft-ietf-dnssec
-."). IDs are RFCs in the preliminary stages of development--they are the working drafts of IETF working groups--and can be obtained via anonymous FTP from

-
-ftp://www.isi.edu/internet-drafts/ or ftp://www.ietf.org/rfcs/
-. 

+The 
+trusted-keys
+ statement defines DNSSEC security roots. DNSSEC is described in 
+DNSSEC
+. A security root is defined when the public key for a non-authoritative zone is known, but cannot be securely obtained through DNS, either because it is the  DNS root zone or its parent zone is unsigned. Once a key has been configured as a trusted key, it is treated as if it had been validated and proven secure. The resolver attempts DNSSEC validation on all DNS data in subdomains of a security root.

 

-
+
  
-Each trusted key is associated with a domain name. Its attributes are the non-negative integral flags, protocol, and algorithm, as well as a base-64 encoded string representing the key.

-

-
- 
-A trusted key is added when a public key for a non-authoritative zone is known, but cannot be securely obtained through DNS. This occurs when a signed zone is a child of an unsigned zone. Adding the trusted key here allows data signed by that zone to be considered secure.

+The 
+trusted-keys
+ statement can contain multiple key entries, each consisting of the key's domain name, flags, protocol, algorithm, and the base-64 representation of the key data.

 

 

-
    
+
 
    
 
  
 5.2.17	
 view
  Statement Grammar
    
-

+
 
- 
-view view name {
-      match_clients { address_match_list } ;
-      [view_option; ...]
-     [zone_statement; ...]]
-};
-
+view view name {

+      match_clients { address_match_list } ;

+      [view_option; ...]

+      [zone_statement; ...]]

+};
 

 

 

-
    
+
 
    
 
  
 5.2.18	
 view
  Statement Definition and Usage
    
-

+
 

 
  
@@ -3789,8 +3842,8 @@ view
  
 Each 
 view
- statement defines a view of the DNS namespace that will be seen by those clients whose IP addresses match the 
-address_match_list
+ statement defines a view of the DNS namespace that will be seen by those clients whose IP addresses match the 
+address_match_list
  of the view's 
 match-clients
  clause.  The order of the 
@@ -3807,7 +3860,7 @@ Zones defined within a 
 view
  statement will be only be accessible to clients that match the 
 view
-.  By defining a zone of the same name in multiple views, different zone data can be given to different clients, e.g. "internal" and "external" clients in a split DNS setup.

+.  By defining a zone of the same name in multiple views, different zone data can be given to different clients, for example, "internal" and "external" clients in a split DNS setup.

 

 
  
@@ -3842,91 +3895,89 @@ view
  statements.

 

 
- 
+
 Here is an example of a typical split DNS setup implemented using 
 view
  statements.

- 
-
-
-view "internal" {               // This should match our internal networks.
-      match-clients { 10.0.0.0/8; };      // Provide recursive service to internal clients only.
-      recursion yes;
-                         // Provide a complete view of the example.com zone
-                         // including addresses of internal hosts.
-      zone "example.com" {
-            type master;
-            file "example-internal.db";
+

+view "internal" {
+               // This should match our internal networks.
+      match-clients { 10.0.0.0/8; };
+               // Provide recursive service to internal clients only.
+      recursion yes;
+               // Provide a complete view of the example.com zone
+               // including addresses of internal hosts.
+      zone "example.com" {
+            type master;
+            file "example-internal.db";
       };
-};
- 
-view "external" {
-      match-clients { any; };
-                          // Refuse recursive service to external clients.
-      recursion no;
-                         // Provide a restricted view of the example.com zone
-                         // containing only publicly accessible hosts.
-      zone "example.com" {
-           type master;
-           file "example-external.db";
-      };
-};
+  };
+

+

+  view "external" {
+      match-clients { any; };
+               // Refuse recursive service to external clients.
+      recursion no;
+               // Provide a restricted view of the example.com zone
+               // containing only publicly accessible hosts.
+      zone "example.com" {
+           type master;
+           file "example-external.db";
+      };
+  };
 

-
 

 

-
    
+
 
    
 
- 
+
 5.2.19	
 zone
 
  
  Statement Grammar
    
-

- 
-
-
-zone zone name [class] [{ 
-    type ( master|slave|hint|stub|forward ) ;
-    [ allow-query { address_match_list } ; ]
-    [ allow-transfer { address_match_list } ; ]
-    [ allow-update { address_match_list } ; ]
-    [ update-policy { update_policy_rule [...] } ; ]
-    [ allow-update-forwarding { address_match_list } ; ]
-    [ also-notify { [ ip_addr ; [ip_addr ; [...]]] } ; ]
-    [ check-names (warn|fail|ignore) ; ]
-    [ dialup true_or_false ; ]
-    [ file string ; ]
-    [ forward (only|first) ; ]
-    [ forwarders { [ ip_addr ; [ ip_addr ; [...]]] } ; ]
-    [ ixfr-base string ; ]
-    [ ixfr-tmp-file string ; ]
-    [ maintain-ixfr-base true_or_false ; ]
-    [ masters [port number] { ip_addr ; [ip_addr ; [...]] } ; ]
-    [ max-ixfr-log-size number ; ]
-    [ max-transfer-idle-in number ; ]
-    [ max-transfer-idle-out number ; ]
-    [ max-transfer-time-in number ; ]
-    [ max-transfer-time-out number ; ]
-    [ notify true_or_false ; ]
-    [ pubkey number number number string ; ]
-    [ transfer-source (ip_addr | *) ; ]
-}];
-

+
+

+zone zone name [class] [{
+   type ( master|slave|hint|stub|forward) ;
+       [ allow-query { address_match_list } ; ]
+       [ allow-transfer { address_match_list } ; ]
+       [ allow-update { address_match_list } ; ]
+       [ update-policy { update_policy_rule [...] } ; ]
+       [ allow-update-forwarding{ address_match_list } ; ]
+       [ also-notify { [ ip_addr ;[ip_addr ; [...]]] } ; ]
+       [ check-names (warn|fail|ignore) ; ]
+       [ dialup true_or_false ; ]
+       [ file string ; ]
+       [ forward (only|first) ; ]
+       [ forwarders { [ ip_addr ; [ ip_addr ; [...]]] } ; ]
+       [ ixfr-base string ; ]
+       [ ixfr-tmp-file string ;]
+       [ maintain-ixfr-base true_or_false ; ]
+       [ masters [port number]{ ip_addr ; [ip_addr ; [...]] } ;  ]
+       [ max-ixfr-log-size number ; ]
+       [ max-transfer-idle-in number ; ]
+       [ max-transfer-idle-out number ; ]
+       [ max-transfer-time-in number ; ]
+       [ max-transfer-time-out number ; ]
+       [ notify true_or_false ; ]
+       [ pubkey number number number string ; ]
+       [ transfer-source (ip_addr | *) ; ]
+       [ sig-validity-interval number ; ]}]
+;

 

 

-
    
+
 
    
 
  
 5.2.20	
 zone
  Statement Definition and Usage
    
-

+
 

-
    
+
 
    
 
  
@@ -3934,10 +3985,10 @@ zone
 
@@ -3950,10 +4001,10 @@ The server has a master copy of the data for the zone and will be able to provid
 
@@ -3961,22 +4012,22 @@ slave
    
 
  
-A slave zone is a replica of a master zone. The masters list specifies one or more IP addresses that the slave contacts to update its copy of the zone. If a port is specified, the slave then checks to see if the zone is current and zone transfers will be done to the port given. If a file is specified, then the replica will be written to this file whenever the zone is changed, and reloaded from this file on a server restart. Use of a file is recommended, since it often speeds server start-up and eliminates a needless waste of bandwidth. Note that for large numbers (in the tens or hundreds of thousands) of zones per server, it is best to use a two level naming scheme for zone file names. For example, a slave server for the zone 
+A slave zone is a replica of a master zone. The masters list specifies one or more IP addresses that the slave contacts to update its copy of the zone. If a port is specified, the slave then checks to see if the zone is current and zone transfers will be done to the port given. If a file is specified, then the replica will be written to this file whenever the zone is changed, and reloaded from this file on a server restart. Use of a file is recommended, since it often speeds server start-up and eliminates a needless waste of bandwidth. Note that for large numbers (in the tens or hundreds of thousands) of zones per server, it is best to use a two level naming scheme for zone file names. For example, a slave server for the zone 
 example.com
  might place the zone contents into a file called
    
-
+
 ex/example.com
- where 
-ex/
- is just the first two letters of the zone name. (Most operating systems behave very slowly if you put 100K files into a single directory.)
    
+ where 
+ex/ 
+is just the first two letters of the zone name. (Most operating systems behave very slowly if you put 100K files into a single directory.)
    
 
     
@@ -3984,15 +4035,17 @@ stub
 
    
 
  
-A stub zone is like a slave zone, except that it replicates only the NS records of a master zone instead of the entire zone.
    
+A stub zone is like a slave zone, except that it replicates only the NS records of a master zone instead of the entire zone. 
+Stub zones are not yet implemented in BINDv9.
+
    
 
     
@@ -4008,7 +4061,7 @@ forward
 forward
  and/or 
 forwarders
- statement, which will apply to queries within the domain given by the zone name.If no 
+ statement, which will apply to queries within the domain given by the zone name. If no 
 forwarders
  statement is present or an empty list for 
 forwarders
@@ -4016,15 +4069,17 @@ forwarders
 options
  statement. Thus if you want to use this type of zone to change the behavior of the global 
 forward
- option (i.e., "forward first to", then "forward only", or vice versa, but want to use the same servers as set globally) you need to respecify the global forwarders.
    
+ option (that is, "forward first to", then "forward only", or vice versa, but want to use the same servers as set globally) you need to respecify the global forwarders. 
+Domain-specific forwarding is not yet implemented in BINDv9.
+
    
 
     
@@ -4032,44 +4087,46 @@ hint
    
 
  
-The initial set of root nameservers is specified using a "hint zone". When the server starts up, it uses the root hints to find a root nameserver and get the most recent list of root nameservers.
    
+The initial set of root nameservers is specified using a "hint zone". When the server starts up, it uses the root hints to find a root nameserver and get the most recent list of root nameservers. If no hint zone is specified for class IN, the server users a compiled-in default set of root servers hints. Classes other than IN have no built-in defaults hints.
    
 
    
 
-
    
+
    
 
  
-
+
 master
 
    
 
    
 
    
 
-
    
+
    
 
  
-
+
 slave
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
-
+
 stub
 
    
 
    
 
    
 
-
    
+
    
 
  
-
+
 forward
 
    
 
    
 
    
 
-
    
+
    
 
  
-
+
 hint
 
    
     		
 
 
 
    
 
    
-

+
 

 

-
    
+
 
    
 
  
 5.2.20.2	Class
    
-

+
 

 
  
-The zone's name may optionally be followed by a class. If a class is not specified, class 
-in
- (for 
-internet
+The zone's name may optionally be followed by a class. If a class is not specified, class 
+IN
+ (for 
+Internet
 ), is assumed. This is correct for the vast majority of cases.

 

 
  
-The 
-hesiod 
-class is named for an information service from MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword 
-hs
+The 
+hesiod
+
+ 
+class is named for an information service from MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword 
+HS
  is a synonym for hesiod.

 

 
  
-Another MIT development is CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the 
-chaos
+Another MIT development is CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the 
+CHAOS
  class.

 

 

-
    
+
 
    
 
  
@@ -4077,7 +4134,7 @@ chaos
 
+
+
+
+
    
 
    
 
-
    
+
    
 
  
 
@@ -4097,7 +4154,7 @@ Access Control
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4117,7 +4174,7 @@ Access Control
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4133,7 +4190,7 @@ Specifies which hosts are allowed to submit Dynamic DNS updates for master zones
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4144,12 +4201,14 @@ update-policy
 
    
 
  
-Specifies a "Simple Secure Update" policy. See description below.
    
+Specifies a "Simple Secure Update" policy. See description in 
+Dynamic Update Policies
+.
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4160,14 +4219,14 @@ allow-update-forwarding
 
    
 
  
-Specifies which hosts are allowed to submit Dynamic DNS updates to slave zones to be forwarded to the master. The default is to deny update forwarding from all hosts. 
+Specifies which hosts are allowed to submit Dynamic DNS updates to slave zones to be forwarded to the master. The default is to deny update forwarding from all hosts. 
 Update forwarding is not yet implemented.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4180,22 +4239,21 @@ also-notify
  
 Only meaningful if 
 notify
- is active for this zone. The set of machines that will receive a 
-DNS NOTIFY
- message for this zone is made up of all the listed nameservers for the zone (other than the primary master) plus any IP addresses specified with 
+ is active for this zone. The set of machines that will receive a 
+DNS NOTIFY
+ message for this zone is made up of all the listed nameservers (other than the primary master) for the zone plus any IP addresses specified with 
 also-notify
 .
    
 
 also-notify
- is not meaningful for stub zones. The default is the empty list.
    
-
-Not yet implemented in BINDv9.
+ is not meaningful for stub zones. The default is the empty list
+.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4209,14 +4267,14 @@ check-names
 See 
 Name Checking
 .
    
-
+
 Not yet implemented in BINDv9.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4232,14 +4290,14 @@ dialup
  under 
 Boolean Options
 .
    
-
+
 Not yet implemented in BINDv9.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4255,14 +4313,14 @@ only
  value causes the lookup to fail after trying the forwarders and getting no answer, while 
 first
  would allow a normal lookup to be tried.
    
-
+
 Not yet implemented in BINDv9.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4276,17 +4334,17 @@ forwarders
 Used to override the list of global forwarders. If it is not specified in a zone of type 
 forward
 , no forwarding is done for the zone; the global options are not used.
    
-
    
+
    
 
  
-
+
 Not yet implemented in BINDv9.
 
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4297,12 +4355,14 @@ ixfr-base
 
    
 
  
-Specifies the file name for the transaction log file used for dynamic update and IXFR.
    
+Was used in BIND 8 to specify the name of the transaction log (journal) file for dynamic update and IXFR. BINDv9 ignores the option and constructs the name of the journal file by appending ".
+jnl
+" to the name of the zone file.
    
     		
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4323,7 +4383,7 @@ Zone Transfers
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4344,7 +4404,7 @@ Zone Transfers
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4357,7 +4417,7 @@ max-transfer-time-out
  
 See the description of
    
 
-max-transfer-time-outn
+max-transfer-time-out
  under 
 Zone Transfers
 .
    
@@ -4365,7 +4425,7 @@ Zone Transfers
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4386,7 +4446,7 @@ Zone Transfers
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4406,7 +4466,7 @@ Boolean Options
 
    
 
    
 
-
    
+
    
 
  
 
@@ -4417,12 +4477,32 @@ pubkey
 
    
 
  
-Represents a public key for this zone. It is needed when this is the top level authoritative zone served by this server and there is no chain of trust to a trusted key. It is considered secure, so that data that it signs will be considered secure. The DNSSEC flags, protocol, and algorithm are specified, as well as a base-64 encoded string representing the key.
    
+In BIND 8, this option was intended for specifying a public zone key for verification of signatures in DNSSEC signed zones when they are loaded from disk. BINDv9 does not verify signatures on loading and ignores the option.
    
     		
 
    
 
    
 
+
    
+
+ 
+
+sig-validity-interval
+
    
+    		
 
    
+
+ 
+See the description of 
+sig-validity-interval
+ under 
+Tuning
+.
    
+
    
+
    
 
  
 
@@ -4433,7 +4513,7 @@ transfer-source
 
    
 
  
-Determines which local address will be bound to the TCP connection used to fetch this zone. If not set, it defaults to a system controlled value which will usually be the address of the interface 
+Determines which local address will be bound to the TCP connection used to fetch this zone. If not set, it defaults to a system controlled value which will usually be the address of the interface 
 closest to
  the remote end. This address must appear in the remote end's 
 allow-transfer
@@ -4441,15 +4521,17 @@ allow-transfer
 
    		
 
    
 
    
-

+
 

 

-
    
+
 
    
 
  
-5.2.20.4	Dynamic Update Policies
    
-

+5.2.20.4	
+ 
+Dynamic Update Policies
+
 

 
  
@@ -4475,7 +4557,7 @@ update-policy
  
 Rules are specified in the 
 update-policy
- zone option, and are only meaninful for master zones.  When the 
+ zone option, and are only meaningful for master zones.  When the 
 update-policy
  statement is present, it is a configuration error for the 
 allow-update
@@ -4486,36 +4568,36 @@ update-policy
 
  
 A rule definition looks like:

- 
-
-( grant | deny ) identity nametype nam [ types ]
-
+

+( grant | deny ) identity nametype name [ types ]
 

 

 
  
-Each rule grants or denies privileges.  Once a messages has successfully matched a rule, the operation is immediately granted or denied - no further rules are examined.  A rule is matched when the signer matches the identity field, the name matches the name field, and the type is specified in the type field.

+Each rule grants or denies privileges.  Once a messages has successfully matched a rule, the operation is immediately granted or denied and no further rules are examined.  A rule is matched when the signer matches the identity field, the name matches the name field, and the type is specified in the type field.

 

 
  
-The identity field specifies a name or a wildcard name.  The nametype field has 4 values: 
+The identity field specifies a name or a wildcard name.  The nametype field has 4 values: 
 name
-, 
+, 
 subdomain
-, 
+, 
 wildcard
-, and 
+, and 
 self
+
+
 . 

 

 

 
-

+

 
  
 
 name
-

+

 		
 
 

@@ -4526,12 +4608,12 @@ Matches when the updated name is the same as the name in the name field.

 

 

 
-

+

 
  
 
 subdomain
-

+

 		
 
 

@@ -4542,12 +4624,12 @@ Matches when the updated name is a subdomain of the name in the name field.

 

 

 
-

+

 
  
 
 wildcard
-

+

 		
 
 

@@ -4558,12 +4640,12 @@ Matches when the updated name is a valid expansion of the wildcard name in the n
 

 

 
-

+

 
  
 
 self
-

+

 		
 
 

@@ -4581,32 +4663,32 @@ If no types are specified, the rule matches all types except SIG, NS, SOA, and N
 
 
 

-
    
+
 
    
 
  
 5.3	 Zone File
    
-

+
 

-
    
+
 
    
 
  
 5.3.1	
  
 Types of Resource Records and When to Use Them
    
-

+
 

 
  
 This section, largely borrowed from RFC 1034, describes the concept of a Resource Record (RR) and explains when each is used. Since the publication of RFC 1034, several new RRs have been identified and implemented in the DNS. These are also included.

 

-
    
+
 
    
 
  
 5.3.1.1	Resource Records
    
-

+
 

 
  
@@ -4618,7 +4700,7 @@ RRset Ordering
 

 
  
-The components of a RR are

+The components of a Resource Record are

 

 

 
@@ -4694,7 +4776,7 @@ the type and sometimes class-dependent data that describes the resource.

 

 
  
-The following are 
+The following are 
 types
  of valid RRs (some of these listed, although not obsolete, are experimental (x) or historical (h) and no longer in general use):

 
@@ -4996,7 +5078,7 @@ X25

 
  
-The following 
+The following 
 classes
  of resource records are currently valid in the DNS:

 
 

@@ -5019,16 +5101,16 @@ the Internet system.

 

 
  
-For information about other, older classes of RRs, see 
-Historical DNS Information
- of Appendix B .

+For information about other, older classes of RRs, see 
+Classes of Resource Records
+ of the Appendix.

 
 
 

 

 
  
-
+
 RDATA
  is the type-dependent or class-dependent data that describes the resource:

 
@@ -5043,7 +5125,7 @@ A

 
  
-for the IN class, a 32 bit IP address

+for the IN class, a 32 bit IP address.

@@ -5071,7 +5153,7 @@ CNAME

 
  
-a domain name

+a domain name.

@@ -5127,7 +5209,7 @@ PTR

 
  
-a fully qualified doman name.

+a fully qualified domain name.

@@ -5159,12 +5241,12 @@ The meaning of the TTL field is a time limit on how long an RR can be kept in a
 The data in the RDATA section of RRs is carried as a combination of binary strings and domain names.  The domain names are frequently used as "pointers" to other data in the DNS.

-
    
+
 
    
 
  
 5.3.1.2	Textual expression of RRs
    
-

+
 

 
  
@@ -5188,122 +5270,158 @@ For example, we might show the RRs carried in a message as: 

 

 
 
 
 

 
 
 

 

 
 
 

 

 
 

 

 
-

+
 
  
-ISI.EDU.

+
+ISI.EDU.
+
 		
 
-

+
 
  
-MX

+
+MX
+
 		
 
-

+
 
  
-10 VENERA.ISI.EDU.

+
+10 VENERA.ISI.EDU.
+
 		
 

 

 
-

+
 
  
- 

+
+
+ 
 		
 
-

+
 
  
-MX

+
+MX
+
 		
 
-

+
 
  
-10 VAXA.ISI.EDU

+
+10 VAXA.ISI.EDU
+
 		
 

 

 
-

+
 
  
-VENERA.ISI.EDU

+
+VENERA.ISI.EDU
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-128.9.0.32

+
+128.9.0.32
+
 		
 

 

 
-

+
 
  
- 

+
+
+ 
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-10.1.0.52

+
+10.1.0.52
+
 		
 

 

 
-

+
 
  
-VAXA.ISI.EDU

+
+VAXA.ISI.EDU
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-10.2.0.27

+
+10.2.0.27
+
 		
 

 

 
-

+
 
  
- 

+
+
+ 
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-128.9.0.33

+
+128.9.0.33
+
 		
 

 

@@ -5322,60 +5440,72 @@ Similarly we might see:

 

 

 
-

+
 
  
-XX.LCS.MIT.EDU. IN

+
+XX.LCS.MIT.EDU. IN
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-10.0.0.44

+
+10.0.0.44
+
 		
 

 

 
-

+
 
  
-CH

+
+CH
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-MIT.EDU. 2420

+
+MIT.EDU. 2420
+
 		
 

 

 

 
  
-This example shows two addresses for 
+This example shows two addresses for 
 XX.LCS.MIT.EDU
 , each of a different class.

 
 
 

-
    
+
 
    
 
  
 5.3.2	Discussion of MX Records
    
-

+
 

 
  
@@ -5383,7 +5513,7 @@ As described above, domain servers store information as a series of resource rec
 

 
  
-MX records are used to control delivery of email. The data specified in the record is a priority and a domain name. The priority controls the order in which email delivery is attempted, with the lowest number first. If two priorities are the same, a server is chosen randomly. If no servers at a given priority are responding, the mail transport agent will fall back to the next largest priority. Priority numbers do not have any absolute meaning - they are relevant only respective to other MX records for that domain name. The domain name given is the machine to which the mail will be delivered. It 
+MX records are used to control delivery of email. The data specified in the record is a priority and a domain name. The priority controls the order in which email delivery is attempted, with the lowest number first. If two priorities are the same, a server is chosen randomly. If no servers at a given priority are responding, the mail transport agent will fall back to the next largest priority. Priority numbers do not have any absolute meaning - they are relevant only respective to other MX records for that domain name. The domain name given is the machine to which the mail will be delivered. It 
 must
  have an associated A record--a CNAME is not sufficient.

 

@@ -5397,179 +5527,235 @@ For example:

 

 

 
-

+
 
  
-example.com.

+
+example.com.
+
 		
 
-

+
 
  
-IN

+
+IN
+
 		
 
-

+
 
  
-MX

+
+MX
+
 		
 
-

+
 
  
-10

+
+10
+
 		
 
-

+
 
  
-mail.foo.com.

+
+mail.example.com.
+
 		
 

 

 
-

+
 
  
- 

+
+
+ 
 		
 
-

+
 
  
-IN

+
+IN
+
 		
 
-

+
 
  
-MX

+
+MX
+
 		
 
-

+
 
  
-10

+
+10
+
 		
 
-

+
 
  
-mail2.foo.com.

+
+mail2.example.com.
+
 		
 

 

 
-

+
 
  
- 

+
+
+ 
 		
 
-

+
 
  
-IN

+
+IN
+
 		
 
-

+
 
  
-MX

+
+MX
+
 		
 
-

+
 
  
-20

+
+20
+
 		
 
-

+
 
  
-mail.backup.org.

+
+mail.backup.org.
+
 		
 

 

 
-

+
 
  
-mail.example.com.

+
+mail.example.com.
+
 		
 
-

+
 
  
-IN

+
+IN
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-10.0.0.1

+
+10.0.0.1
+
 		
 
-

+
 
  
- 

+
+
+ 
 		
 

 

 
-

+
 
  
-mail2.example.com.

+
+mail2.example.com.
+
 		
 
-

+
 
  
-IN

+
+IN
+
 		
 
-

+
 
  
-A

+
+A
+
 		
 
-

+
 
  
-10.0.0.2

+
+10.0.0.2
+
 		
 
-

+
 
  
- 

+
+
+ 
 		
 

 

 

 
  
-Mail delivery will be attempted to mail.foo.com and mail2.foo.com (in any order), and if neither of those succeed, delivery to mail.backup.org will be attempted.

+Mail delivery will be attempted to 
+mail.example.com
+ and 
+mail2.example.com
+ (in any order), and if neither of those succeed, delivery to 
+mail.backup.org
+ will be attempted.

 

 

-
    
+
 
    
 
  
 5.3.3	
  
 Setting TTLs
    
-

+
 

 
  
@@ -5629,41 +5815,81 @@ Each RR can have a TTL as the second field in the RR, which will control how lon
 

 
  
-All of these TTLs default to units of seconds, though units can be explicitly specified, e.g. 
-1h30m
+All of these TTLs default to units of seconds, though units can be explicitly specified, for example, 
+1h30m
 . 

 

 

-
    
+
 
    
 
  
 5.3.4	Inverse Mapping in IPv4
    
-

+
 

 
  
-Reverse name resolution (i.e., translation from IP address to name) is achieved by means of the in-addr.arpa domain and PTR records. Entries in the in-addr.arpa domain are made in least-to-most significant order, read left to right. This is the opposite order to the way IP addresses are usually written. Thus, a machine with an IP address of 10.1.2.3 would have a corresponding in-addr.arpa name of

+Reverse name resolution (that is, translation from IP address to name) is achieved by means of the 
+in-addr.arpa
+ domain and PTR records. Entries in the in-addr.arpa domain are made in least-to-most significant order, read left to right. This is the opposite order to the way IP addresses are usually written. Thus, a machine with an IP address of 10.1.2.3 would have a corresponding in-addr.arpa name of

 3.2.1.10.in-addr.arpa. This name should have a PTR resource record whose data field is the name of the machine or, optionally, multiple PTR records if the machine has more than one name. For example, in the 
 example.com
  domain:

 

-$ORIGIN      2.1.10.in-addr.arpa
-3            IN PTR foo.example.com.

+
+ 
+
+
+
+
+
+
+
+
+
+

+

+
+ 
+
+$ORIGIN
+

+		
+

+
+ 
+
+2.1.10.in-addr.arpa
+

+

+

+
+ 
+
+3
+

+		
+

+
+ 
+
+IN PTR foo.example.com.
+

+

 

 
- 
+
 (Note: The 
 $ORIGIN
  lines in the examples are for providing context to the examples only--they do not necessarily appear in the actual usage. They are only used here to indicate that the example is relative to the listed origin.)

 

 

-
    
+
 
    
 
  
 5.3.5	Other Zone File Directives
    
-

+
 

 
  
@@ -5679,22 +5905,37 @@ $INCLUDE
 $TTL.
 

 

-
    
+
 
    
 
-
+ 
 5.3.5.1	The 
 $ORIGIN
  Directive
    
-

+
 

 
-
-Syntax: $ORIGIN < domain-name > [<comment>]
+ 
+Syntax: 
+$ORIGIN <
+
+domain-name
+
+> 
+
+[
+
+<
+
+comment
+
+>
+
+]
 

 

 
-
+ 
 
 $ORIGIN 
 sets the domain name that will be appended to any unqualified records. When a zone is first read in there is an implicit 
@@ -5708,41 +5949,59 @@ $ORIGIN
  is appended to the domain specified in the 
 $ORIGIN
  argument if it is not absolute.

- 
-
-$ORIGIN example.com
+

+$ORIGIN example.com
 WWW     CNAME   MAIN-SERVER
 

 

 
-
+ 
 is equivalent to

- 
-
-WWW.EXAMPLE.COM CNAME MAIN-SERVER.EXAMPLE.COM.
-
+

+WWW.EXAMPLE.COM CNAME MAIN-SERVER.EXAMPLE.COM.
 

 

 

-
    
+
 
    
 
-
+ 
 5.3.5.2	The 
 $INCLUDE
  Directive
    
-

+
 

 
-
-
-Syntax: $INCLUDE < filename> [< origin>] [<comment>]
-

+ 
+Syntax: 
+$INCLUDE <
+
+filename
+
+> 
+
+[
+
+<
+
+origin
+
+>
+
+] [
+
+<
+
+comment
+
+>
+
+]
 

 

 
-
-Read and process the file 
+ 
+Read and process the file 
 filename
  as if it were included into the file at this point.  If 
 origin
@@ -5753,58 +6012,71 @@ $ORIGIN
  is used.

 

 
-
+ 
 
-NOTE:
- The behavior when 
+NOTE: 
+The behavior when 
 origin
  is specified differs from that described in RFC 1035. The origin and current domain revert to the values they were prior to the 
 $INCLUDE
  once the file has been read.

 

 

-
    
+
 
    
 
-
+ 
 5.3.5.3	The 
 $TTL
  Directive
    
-

+
 

 
-
-
-Syntax: $TTL <default-ttl> [<comment>]
-
-

+ 
+Syntax: 
+$TTL <
+
+default-ttl
+
+> 
+
+[
+
+<
+
+comment
+
+>
+
+]
 

 

 
-
+ 
 Set the default Time To Live (TTL) for subsequent records with undefined TTLs. Valid TTLs are of the range 0-2147483647 seconds.

 

 
-
+ 
 
 $TTL
  is defined in RFC 2308.

 

 

 

-
    
+
 
    
 
-
+ 
 5.3.6	BIND Master File Extension: the  
 $GENERATE
  Directive
    
-

-

-$GENERATE

+
+
 
+$GENERATE
+

 

 
-
+ 
 Syntax: 
 $GENERATE <
 
@@ -5836,40 +6108,42 @@ comment
 

 

 
-
+ 
 
 $GENERATE
  is used to create a series of resource records that only differ from each other by an iterator. 
 $GENERATE 
 can be used to easily generate the sets of records required to support sub /24 reverse delegations described in RFC 2317: Classless IN-ADDR.ARPA delegation.

 

-$ORIGIN 0.0.192.IN-ADDR.ARPA.
+$ORIGIN 0.0.192.IN-ADDR.ARPA.
 $GENERATE 1-2 0 NS SERVER$.EXAMPLE.
-$GENERATE 1-127 $ CNAME $.0

+$GENERATE 1-127 $ CNAME $.0
+
 

 
-
+ 
 is equivalent to

 

-0.0.0.192.IN-ADDR.ARPA NS SERVER1.EXAMPLE.
+0.0.0.192.IN-ADDR.ARPA NS SERVER1.EXAMPLE.
 0.0.0.192.IN-ADDR.ARPA NS SERVER2.EXAMPLE.
 1.0.0.192.IN-ADDR.ARPA CNAME 1.0.0.0.192.IN-ADDR.ARPA
 2.0.0.192.IN-ADDR.ARPA CNAME 2.0.0.0.192.IN-ADDR.ARPA
 ...
 127.0.0.192.IN-ADDR.ARPA CNAME 127.0.0.0.192.IN-ADDR.ARPA
-.

+.
+
 

 
-
+ 
 
 
  

 

 

 
-

+

 
-
+ 
 
 range
 

@@ -5877,15 +6151,15 @@ range
 		
 

 
-
+ 
 This can be one of two forms: start-stop or start-stop/step. If the first form is used then step is set to 1. All of start, stop and step must be positive.

 		
 

 

 
-

+

 
-
+ 
 
 lhs
 

@@ -5893,7 +6167,7 @@ lhs
 		
 

 
-
+ 
 
 lhs
  describes the owner name of the resource records to be created.      Any single 
@@ -5913,9 +6187,9 @@ is appended to the name.

 

 

 
-

+

 
-
+ 
 
 type
 

@@ -5923,15 +6197,15 @@ type
 		
 

 
-
+ 
 At present the only supported types are PTR, CNAME and NS.

 		
 

 

 
-

+

 
-
+ 
 
 rhs
 

@@ -5939,43 +6213,43 @@ rhs
 		
 

 
-
+ 
 rhs is a domain name. It is processed similarly to lhs.

 		
 

 

 

 
-
+ 
 The 
 $GENERATE
- directive is a BIND extension and not part of the standard zone file format. 
+ directive is a BIND extension and not part of the standard zone file format. 
 It is not yet implemented in BINDv9.
 

 

 

-
    
+
 
    
 
-
+ 
 5.3.7	Signals
    
-

+
 

 
-
+ 
 Certain UNIX signals cause the name server to take specific actions, as described in the following table.  These signals can be sent using the 
 kill
  command.

 

 
-
+ 
  

 

 

 
-

+

 
-
+ 
 
 SIGHUP
 

@@ -5983,7 +6257,7 @@ SIGHUP
 		
 

 
-
+ 
 Causes the server to read 
 named.conf
  and reload the database. 

@@ -5991,9 +6265,9 @@ named.conf
 

 

 
-

+

 
-
+ 
 
 SIGTERM
 

@@ -6001,13 +6275,13 @@ SIGTERM
 		
 

 
-
+ 
 Causes the server to clean up and exit.

 		
 

 

 
-

+

 
  
 
@@ -6017,15 +6291,15 @@ SIGINT
 

 

 
-
+ 
 Causes the server to clean up and exit.

 		
 

 

 
-

+

 
-
+ 
 
 SIGQUIT
 

@@ -6040,6 +6314,8 @@ Causes the server to clean up and exit.

 

 

 
+
 
 
diff --git a/doc/arm/Bv9ARM.6.html b/doc/arm/Bv9ARM.6.html
index 9b70e597f2..84f3e8de1d 100644
--- a/doc/arm/Bv9ARM.6.html
+++ b/doc/arm/Bv9ARM.6.html
@@ -5,21 +5,21 @@
 
  Section 6.	Security Considerations
 
-
    
+
 
    
 
  
 Section 6.	Security Considerations
    
-

+
 

-
    
+
 
    
 
  
 6.1	
  
 Access Control Lists
    
-

+
 

 
  
@@ -51,51 +51,54 @@ Here is an example of how to properly apply ACLs:

  
 // Set up an ACL named "bogusnets" that will block RFC1918 space,

 // which is commonly used in spoofing attacks.

- 
-
-acl bogusnets{ 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; };
-
+

+acl bogusnets { 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24;
+ 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; };
 

 

 
- 
+
 // Set up an ACL called our-nets. Replace this with the real IP numbers.

- 
-
-acl our-nets { x.x.x.x/24; x.x.x.x/21; };  
-options {
+

+acl our-nets { x.x.x.x/24; x.x.x.x/21; }; 

+

+options {
+
+  ...
   ...
-  ...
-  allow-query { our-nets; };
-  allow-recursion { our-nets; };
-  ...
-  blackhole { bogusnets; };
-  ...
-};
-
-zone "example.com" {
-  type master;
-  file "m/example.com";
-  allow-query { any; };
+
+  allow-query { our-nets; };
+  allow-recursion { our-nets; };
+  ...
+
+  blackhole { bogusnets; };
+  ...
+
+};
+

+

+zone "example.com" {
+  type master;
+  file "m/example.com";
+  allow-query { any; };
 };
 

-
 

 
  
 This allows recursive queries of the server from the outside unless recursion has been previously disabled.

 

-
+
  
 For more information on how to use ACLs to protect your server, see the 
 AUSCERT
  advisory at

-
-ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos
+
+ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos
 

 

 

-
    
+
 
    
 
  
@@ -104,7 +107,7 @@ chroot
  and 
 setuid
  (for UNIX servers)
    
-

+
 

 
  
@@ -112,12 +115,12 @@ On UNIX servers, it is possible to run BIND in a 
 chrooted
  environment (
 chroot()
-) by specifying the "
+) by specifying the '
 -t
-" option. This can help improve system security by placing BIND in a "sandbox," which will limit the damage done if a server is compromised.

+' option. This can help improve system security by placing BIND in a "sandbox," which will limit the damage done if a server is compromised.

 

 
- 
+
 Another useful feature in the UNIX version of BIND is the ability to run the daemon as a nonprivileged user ( 
 -u
  <
@@ -126,8 +129,7 @@ user
 chroot
  feature.

 

-
- 
+
 Here is an example command line to load BIND in a 
 chroot()
  sandbox, 

@@ -142,20 +144,20 @@ setuid
 /usr/local/bin/named -u 202 -t /var/named
 
 

-
    
+
 
    
 
- 
+
 6.2.1	The 
 chroot
  Environment
    
-

+
 

 
- 
+
 In order for a 
 chroot()
- environment to work properly in a particular directory (e.g., 
+ environment to work properly in a particular directory (for example, 
 /var/named
 ), you will need to set up an environment that includes everything BIND needs to run. From BIND's point of view, 
 /var/named
@@ -166,23 +168,23 @@ chroot()
  sandbox.

 

 
- 
+
 If you are running an operating system that supports static binaries, you can also compile BIND statically and avoid the need to copy system libraries over to your 
 chroot()
  sandbox.

 

 

-
    
+
 
    
 
- 
+
 6.2.2	Using the 
 setuid
  Function 
    
-

+
 

 
- 
+
 Prior to running the 
 named
  daemon, use the 
@@ -193,21 +195,23 @@ chown
 

 

 

-
    
+
 
    
 
- 
+
 6.3	Dynamic Updates
    
-

+
 

 
- 
+
 Access to the dynamic update facility should be strictly limited. In earlier versions of BIND the only way to do this was based on the IP address of the host requesting the update. BINDv9 also supports authenticating updates cryptographically by means of transaction signatures (TSIG). The use of TSIG is strongly recommended.

 

 
  
 Some sites choose to keep all dynamically updated DNS data in a subdomain and delegate that subdomain to a separate zone. This way, the top-level zone containing critical data such as the IP addresses of public web and mail servers need not allow dynamic update at all.

 

+
 
 
diff --git a/doc/arm/Bv9ARM.7.html b/doc/arm/Bv9ARM.7.html
index ece6c8f614..33eeee98a1 100644
--- a/doc/arm/Bv9ARM.7.html
+++ b/doc/arm/Bv9ARM.7.html
@@ -25,18 +25,18 @@ Section 7.	Troubleshooting
  
 lame server
 
-
 
-ns named[111]: Lame server on 'www.foo.com' (in 'foo.com'?): [192.168.0.2].53 'ns2.foo.com'
+

+ns named[111]: Lame server on 'www.example.com' (in 'example.com'?): [192.168.0.2].53 'ns2.example.com'
 

 

 
  
 This is a harmless error message. It means that the server at 192.168.0.2 (
-ns2.foo.com
+ns2.example.com
 ) is listed as a nameserver for "
-foo.com
+example.com
 ", but it doesn't really know anything about 
-foo.com
+example.com
 .

 

 
@@ -54,36 +54,36 @@ If it's a zone out on the Internet, it would be nice to notify the owners of the
  
 bad referral
 
-
 
-ns named[111]: bad referral (other.com !< subdomain.other.com)
+

+ns named[111]: bad referral (other.com !< subdomain.other.com)
 

 

 
  
 This indicates that your nameserver (
-ns.foo.com
+ns.example.com
 ) queried the nameserver for 
-foo2.com
+example2.com
  to find out how to get to 
-subdomain.foo2.com
-. 
-foo2.com
+subdomain.example2.com
+. The name server 
+example2.com
  told your nameserver that 
-subdomain.foo2.com
+subdomain.example2.com
  was delegated to some 
-other.foo2.com
+other.example2.com
 , so your nameserver queried that.

 

 
  
 
-someother.foo2.com
+someother.example2.com
  didn't think that 
-subdomain.foo2.com
+subdomain.example2.com
  had been delegated to it, so it referred your server (
-ns.foo.com
+ns.example.com
 ) back to the 
-foo2.com
+example2.com
  nameserver.

 
 

@@ -93,13 +93,15 @@ foo2.com
  
 not authoritative for
 
-
 
-ns named-xfer[111]: [192.168.0.1] not authoritative for foo.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0
+

+ns named-xfer[111]: [192.168.0.1] not authoritative for example.com, SOA query got rcode 0, aa 0, ancount 1, aucount 0
 

 

 
  
-This error usually shows up on a slave server. It indicates that the master server is not answering authoritatively for the zone. This usually happens when the zone is rejected (while named is loading) on the master server. Check the logs on the master server. If ancount -- 0, you may be pointing at the wrong master server for the zone.

+This error usually shows up on a slave server. It indicates that the master server is not answering authoritatively for the zone. This usually happens when the zone is rejected (while 
+named
+ is loading) on the master server. Check the logs on the master server. If ancount -- 0, you may be pointing at the wrong master server for the zone.

 

 

 
    
@@ -108,14 +110,14 @@ This error usually shows up on a slave server. It indicates that the master serv
  
 rejected zone
 

-
 
-ns named[111]: master zone "foo.com" (IN) rejected due to errors (serial111)
+

+ns named[111]: master zone "example.com" (IN) rejected due to errors (serial111)
 

 

 
  
 This indicates that the 
-foo.com
+example.com
  zone was rejected because of an error in the zone file. Check the lines above this error. 
 named
  will usually tell you what it didn't like and where to find it in the zone file.

@@ -127,14 +129,14 @@ named
  
 no NS RRs found
 
-
 
-ns named[111]: Zone "foo.com" (file foo.com.db): no NS RRs found at zonetop
+

+ns named[111]: Zone "example.com" (file example.com.db): no NS RRs found at zonetop
 

 

 
  
 The 
-foo.com.db
+example.com.db
  file is missing NS records at the top of the zone (in the SOA section). Check to make sure they exist and that there is white space (spaces or tabs) in front of them. White spaces matter here.

 

 

@@ -144,17 +146,21 @@ foo.com.db
  
 no default TTL set
 
-
 
-ns named[111]: Zone "foo.com" (file foo.com.db): No default TTL set using SOA minimum instead
+

+ns named[111]: Zone "example.com" (file example.com.db): No default TTL set using SOA minimum instead
 

 

 
  
-You need to add a $TTL to the top of the 
-foo.com.db
- zone file. See RFC2308, or 
+You will need to add a 
+$TTL
+ to the top of the 
+example.com.db
+ zone file. See RFC 2308, or 
 Setting TTLs
- in this document, for information on how to use $TTL.

+ for information on how to use 
+$TTL
+.

 

 

 
    
@@ -163,8 +169,8 @@ Setting TTLs
  
 no root nameserver for class
 

-
 
-findns: No root nameservers for class IN?
+

+findns: No root nameservers for class IN?
 

 

 
@@ -182,8 +188,8 @@ If you are running an internal root nameserver, make sure it is configured prope
  
 address already in use
 
-
 
-ctl_server: bind: Address already in use
+

+ctl_server: bind: Address already in use
 

 

 
@@ -221,7 +227,7 @@ This means that the regular user wouldn't be able to delete it, so it would thin
 
  
 The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand (see the sample configurations in 
-Sample Configuration and Logging
+Sample Configuration and Logging.
 ). The log files provide a source of hints and information that can be used to figure out what went wrong and how to fix the problem.

 

 
@@ -255,23 +261,19 @@ The solution to this is to add 2147483647 (2^31-1) to the number, reload the zon
 

 
  
-The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND, DHCP and INN servers. Four levels of premium support are available and each level includes support for all ISC programs, significant discounts on products and training, and a recognized priority on bug fixes and non-funded feature requests. In addition, ISC offers a standard support agreement package which includes services ranging from bug fix announcements to remote support. It also includes training in BIND, DHCP or INN.

+The Internet Software Consortium (ISC) offers a wide range of support and service agreements for BIND and DHCP servers. Four levels of premium support are available and each level includes support for all ISC programs, significant discounts on products and training, and a recognized priority on bug fixes and non-funded feature requests. In addition, ISC offers a standard support agreement package which includes services ranging from bug fix announcements to remote support. It also includes training in BIND and DHCP.

 

 
  
-To discuss arrangements for support, contact 
-info@isc.org
-
- 
+To discuss arrangements for support, contact 
+info@isc.org
 or visit the ISC web page at

 
-http://www.isc.org/services/support/
+http://www.isc.org/services/support/
  to read more.

+
 
-
-
-
 
 
diff --git a/doc/arm/Bv9ARM.8.html b/doc/arm/Bv9ARM.8.html
index 2193ce6a02..e99ba96429 100644
--- a/doc/arm/Bv9ARM.8.html
+++ b/doc/arm/Bv9ARM.8.html
@@ -5,7 +5,6 @@
 
  Appendices
 
-

 

 
  
@@ -15,11 +14,11 @@ Appendices

 
  
 Appendix A. Acknowledgements
-

-

-
+

+

+
  
-A Brief History of the DNS and BIND

+A.1	A Brief History of the DNS and BIND
 

 
  
@@ -44,25 +43,25 @@ BIND versions from 4.9.3 onward have been developed and maintained by the Intern
 
  
 BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.

-

-
-

-

+
+

 
  
-
+Appendix B.		
  
-Appendix B. Historical DNS Information

+Historical DNS Information
 

-

+

 
  
-Classes of resource records

+B.1	
+ 
+Classes of Resource Records
 

-

+

 
  
-HS = hesiod

+B.1.1	HS = hesiod
 

 
  
@@ -73,10 +72,10 @@ hs
  is a synonym for hesiod.

 

 

-

+

 
  
-CH = chaos

+B.1.2	CH = chaos
 

 
  
@@ -85,37 +84,37 @@ chaos
  class is used to specify zone data for the MIT-developed CHAOSnet, a LAN protocol created in the mid-1970s.

 

 

-

-

-

+
+

 
  
-
+Appendix C.		
  
-Appendix C. Bibliography (and Suggested Reading)

+Bibliography (and Suggested Reading)
 

-

+

 
  
-
+C.1	
  
-C.1 Request for Comments (RFCs)

+Request for Comments (RFCs)
 

 
  
-Specification documents for the Internet protocol suite, including the DNS, are published as part of the Request for Comments (RFCs) series of technical notes. The standards themselvers are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at 

+Specification documents for the Internet protocol suite, including the DNS, are published as part of the Request for Comments (RFCs) series of technical notes. The standards themselves are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at 

 
 ftp://www.isi.edu/in-notes/RFCxxx.txt
  (where 
 xxx
- is the number of the RFC). RFCs are also available via the Web at 
-http://www.ietf.org/rfc/
+ is the number of the RFC). RFCs are also available via the Web at
+ 

+http://www.ietf.org/rfc/
 .

 

-

+

 
  
-Standards

+C.1.1	Standards
 

 
  
@@ -125,7 +124,7 @@ Mail Routing and the Domain System
 

 
  
-RFC1034.  Mockapetris, P.V.  
+RFC1034.  Mockapetris, P.V. 
 Domain Names - Concepts and Facilities
 . P.V. November 1987.

 

@@ -136,12 +135,12 @@ Domain Names - Implementation and Specification
 . November 1987.

 

 

-

+

 
  
-
+C.1.2	
  
-Proposed Standards

+Proposed Standards
 

 
  
@@ -172,18 +171,24 @@ A Mechanism for Prompt Notification of Zone Changes
 RFC2136. Vixie, P., S. Thomson, Y. Rekhter, J. Bound. 
 Dynamic Updates in the Domain Name System
 . April 1997.

+

+
+ 
+RFC2845. Vixie, P., O. Gudmundsson, D. Eastlake 3rd, B. Wellington. 
+Secret Key Transaction Authentication for DNS (TSIG)
+. May 2000.

 

 

-

+

 
  
-Proposed Standards Still Under Development

+C.1.3	Proposed Standards Still Under Development
 

 
  
 
 Note:
- the following list of RFCs are undergoing major revision by the IETF. (See the Internet Drafts section, below, for current versions).

+ the following list of RFCs are undergoing major revision by the IETF.

 

 
  
@@ -204,10 +209,10 @@ Secure Domain Name System Dynamic Update
 . April 1997.

 

 

-

+

 
  
-Other Important RFCs About DNS Implementation

+C.1.4	Other Important RFCs About DNS Implementation
 

 
  
@@ -228,10 +233,10 @@ Serial Number Arithmetic
 . August 1996.

 

 

-

+

 
  
-Resource Record Types

+C.1.5	Resource Record Types
 

 
  
@@ -247,7 +252,7 @@ DNS NSAP Resource Records
 

 
  
-RFC2168. Danie1,R.,  M. Mealling. 
+RFC2168. Daniel, R.,  M. Mealling. 
 Resolution of Uniform Resource Identifiers using the Domain Name System. June 1997.
 

 

@@ -259,15 +264,15 @@ A Means for Expressing Location Information in the Domain Name System
 

 
  
-RFC2052. Gulbrandsen,A., P. Vixie. 
+RFC2052. Gulbrandsen, A., P. Vixie. 
 A DNS RR for Specifying the Location of Services.
  October 1996.

-

+

 
  
 RFC2163. Allocchio, A. U
 sing the Internet DNS to Distribute MIXER Conformant Global Address Mapping
-.January 1998.

+. January 1998.

 

 
  
@@ -276,15 +281,15 @@ Key Exchange Delegation Record for the DNS
 .  October 1997.

 

 

-

+

 
  
-DNS and the Internet

+C.1.6	DNS and the Internet
 

 
  
 RFC1101. Mockapetris, P. V. 
-Dns Encoding of Network Names and Other Types
+DNS Encoding of Network Names and Other Types
 . April 1989.

 

 
@@ -306,10 +311,10 @@ Classless IN-ADDR.ARPA Delegation
 . March 1998.

 

 

-

+

 
  
-DNS Operations

+C.1.7	DNS Operations
 

 
  
@@ -336,21 +341,16 @@ Use of DNS Aliases for Network Services.
  October 1997.

 

 

-

+

 
  
-Other DNS-related RFCs

-

-

-

-
-

-

+C.1.8	Other DNS-related RFCs

+

 
  
 
 Note:
- the following list of RFCs, although DNS-related, are not concerned with implementing software.
+ the following list of RFCs, although DNS-related, are not concerned with implementing software.

 

 
  
@@ -387,11 +387,12 @@ Domain Names and Company Name Retrieval
 RFC2352. Vaughan, O. 
 A Convention For Using Legal Names as Domain Names
 . May 1998.

+

 

-

+

 
  
-Obsolete and Unimplemented Experimental RRs

+C.1.9	Obsolete and Unimplemented Experimental RRs
 

 
  
@@ -399,76 +400,31 @@ RFC1712. Farrell, C., M. Schulze, S. Pleitner, D. Baldoni. 
 . November 1994.

 

+
 

-

+

 
  
-
+C.2	
  
-C.2 Internet Drafts

+Internet Drafts
 

 
  
 Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs in the preliminary stages of development. Implementors are cautioned not to regard IDs as archival, and they should not be quoted or cited in any formal documents unless accompanied by the disclaimer that they are "works in progress." IDs have a lifespan of six months after which they are deleted unless updated by their authors.

-

-
- 
-IDs can be obtained via FTP from

-
-ftp://www.isi.edu/internet-drafts/
- or from 
-http://www.ietf.org/1id-abstracts.html
-.

-

-
- 
-
-draft-duerst-dns-i18n-01.txt

-draft-ietf-dhc-dhcp-dns-10.txt

-draft-ietf-dnsind-apl-rr-03.txt

-draft-ietf-dnsind-dddd-01.txt

-draft-ietf-dnsind-dhcp-rr-00.txt

-draft-ietf-dnsind-edns1-03.txt

-draft-ietf-dnsind-iana-dns-04.txt

-draft-ietf-dnsind-indirect-key-00.txt

-draft-ietf-dnsind-keyreferral-00.txt

-draft-ietf-dnsind-kitchen-sink-02.txt

-draft-ietf-dnsind-local-compression-05.txt

-draft-ietf-dnsind-local-names-07.txt

-draft-ietf-dnsind-rfc2052bis-05.txt

-draft-ietf-dnsind-rollover-00.txt

-draft-ietf-dnsind-sec-rr-00.txt

-draft-ietf-dnsind-sigalgopt-00.txt

-draft-ietf-dnsind-simple-secure-update-02.txt

-draft-ietf-dnsind-test-tlds-13.txt

-draft-ietf-dnsind-tkey-01.txt

-draft-ietf-dnsind-tsig-13.txt

-draft-ietf-dnsind-verify-00.txt

-draft-ietf-dnssec-ar-00.txt

-draft-ietf-dnssec-as-map-05.txt

-draft-ietf-dnssec-key-handling-00.txt

-draft-ietf-dnssec-secfail-00.txt

-draft-ietf-dnssec-update2-00.txt

-draft-ietf-ipngwg-2292bis-00.txt

-draft-ietf-ipngwg-dns-lookups-05.txt

-draft-dunlap-dns-duxfr-00.txt

-draft-schroeppel-dnsind-ecc-00.txt

-draft-skwan-gss-tsig-04.txt

-draft-skwan-utf8-dns-02.txt
-

 

 

-

+

 
  
-C.3 Electronic Mail Communication

-

+C.3	Electronic Mail Communication
+

 
  
 Wellington, Brian (bwellington@tislabs.com). 
 DNSSEC usage document
 . E-mail to David Conrad (David_Conrad@isc.org). 15 March 1999.

-

+

 
  
 Wellington, Brian (bwellington@tislabs.com). 
@@ -476,20 +432,20 @@ TSIG guide for BIND 8.2+
 . E-mail to private mailing list (private communication). 22 April 1999.

 

 

-

+

 
  
-C.4 Other BIND Documents

-

+C.4	Other BIND Documents
+

 
  
 Albitz, Paul and Cricket Liu. 1998. 
 DNS and BIND
 . Sebastopol, CA: O'Reilly and Associates.

-
-
Return to BINDv9 Administrator Reference Manual table of contents.

-
 

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

 
DRAFT
 

-May, 2000

+June, 2000
 
 
 

 

 
Warning! This DRAFT document is the property of the Internet Software Consortium (ISC) and contains proprietary ISC information. The information in this document is subject to change.

+
 

 

 
@@ -28,40 +29,43 @@ May, 2000
  
 Table of Contents
 
-
    
-
    
-
+
+
    
+
 Section 1.	Introduction 
-
    
-
    
-
+
    
+
    
+
 Section 2.	BIND Resource Requirements
-
    
-
    
-
+
    
+
    
+
 Section 3.	Nameserver Configuration
-
    
-
    
-
+
    
+
    
+
 Section 4.	Advanced Concepts
-
    
-
    
-
+
    
+
    
+
 Section 5.	BINDv9 Configuration Reference
-
    
-
    
-
+
    
+
    
+
 Section 6.	Security Considerations
-
    
-
    
-
+
    
+
    
+
 Section 7.	Troubleshooting
-
    
-
    
-
-Appendices
-

+
+

+Appendices
+

+
 

+

+Copyright ©2000 Internet Software Consortium
+