diff --git a/doc/arm/BV9ARM.1.html b/doc/arm/BV9ARM.1.html index da8e655ece..24e5fe4fd6 100644 --- a/doc/arm/BV9ARM.1.html +++ b/doc/arm/BV9ARM.1.html @@ -7,12 +7,12 @@

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

@@ -130,8 +130,7 @@ Literal user input

- -Courier Bold +Courier Bold

@@ -406,7 +405,7 @@ terminal 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.

- + Though BIND is a Domain Nameserver, it deals primarily in terms of zones. The primary and secondary declarations in the named.conf @@ -440,13 +439,13 @@ 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 brackets. 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 +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 primary 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.

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

    @@ -458,13 +457,13 @@ Adding a zone as a type primary or type slave will tell the server to answer que

    -A DNS server can be primary for some zones and secondary for others or can be only a primary, or only a secondary, 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 -. Primary servers are often also called -masters - and secondary servers are often also called -slaves -. Both primary/master and secondary/slave servers are authoritative for a zone.

    +. Master servers are often also called +primaries + and slave servers are often also called +secondaries +. Both master/primary and slave/secondary servers are authoritative for a zone.

    @@ -527,11 +526,11 @@ Instead of interacting with the nameservers for the root and other domains, a 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 for a given zone and they are queried in turn until the list is exhausted. 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.

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

    -There is no prohibition against declaring a server to be a forwarder even though it has primary and/or secondary 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.

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

    @@ -540,23 +539,30 @@ There is no prohibition against declaring a server to be a forwarder even though 1.4.3.5 Stealth Server
+

- - -A - -stealth server is a primary master server that is neither listed in any root zone files nor advertised as being a server. It is set up to hide the true master server for a zone in order to provide some measure of security, or protect the zone from - -Denial of Service ( - -DoS) attacks, or reduce the load on the main server, or any number of other reasons. It is also used to provide some measure of network redundancy. Slave servers load zone data from it.

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

- +  

-

Return to BINDv9 Administrator Reference Manual table of contents.

+

Return to BINDv9 Administrator Reference Manual table of contents.

diff --git a/doc/arm/BV9ARM.2.html b/doc/arm/BV9ARM.2.html index 1f94761c9d..748670f4a2 100644 --- a/doc/arm/BV9ARM.2.html +++ b/doc/arm/BV9ARM.2.html @@ -8,93 +8,93 @@

    - + Section 2. BIND Resource Requirements

    - + 2.1 Hardware requirements

- -DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers.

+ +DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers.

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

    - + 2.2 CPU Requirements

- -CPU requrements for BINDv9 start at i486 for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.

+ +CPU requirements for BINDv9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.

    - + 2.3 Memory Requirements

- -For BIND 8.x and older versions, the memory of the server had to be large enough to fit the cache and zones loaded off disk. BINDv9 will provide methods to set resource limits, at the expense of limiting the cache 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 for BINDv9 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.

    - + 2.4 Nameserver Intensive Environment Issues

- + For nameserver intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal nameservers query a main nameserver, which has enough memory to build a large cache. This approach minimizes the bandwidth used by external name lookups. The second alternative is to set up second-level internal nameservers to make queries independently. In this configuration, none of the individual machines needs to have as much memory or CPU power as in the first alternative, but this has the disadvantage of making many more external queries, as none of the nameservers share their cached data.

    - + 2.5 Operating Systems Supported by the Internet Software Consortium

- + ISC BINDv9 compiles and runs on the following operating systems:

-
 
-IBM AIX 4.3
-
 
-Compaq Digital/Tru64 UNIX 4.0, 5.0
-
 
-HP HP-UX 11.0
-
 
-SGI IRIX 6.4
-
 
-Red Hat Linux 6.0, 6.1
-
 
-Sun Solaris 2.6, 7
-
 
-FreeBSD 3.3
-
 
-NetBSD 1.4.1 or 1.4.2, with MIT pthreads
+

+IBM AIX 4.3
+

+Compaq Digital/Tru64 UNIX 4.0D
+

+HP HP-UX 11
+

+IRIX64 6.5
+

+Red Hat Linux 6.0, 6.1
+

+Sun Solaris 2.6, 7, 8 (beta)
+

+FreeBSD 3.4-STABLE
+

+NetBSD-current with "unproven" pthreads

 

 
- 
+
  

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

Return to BINDv9 Administrator Reference Manual table of contents.

diff --git a/doc/arm/BV9ARM.3.html b/doc/arm/BV9ARM.3.html index fcc3d9a447..90e0206c11 100644 --- a/doc/arm/BV9ARM.3.html +++ b/doc/arm/BV9ARM.3.html @@ -305,7 +305,7 @@ also-notify

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

+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

    @@ -359,7 +359,7 @@ The host -utility provides a simple DNS lookup using a command-line interface for looking up Internet hostnames. Bu default, the utility interprets between host names and Internet addresses, but its functionality can be extended with the use of options.

    +utility provides a simple DNS lookup using a command-line interface for looking up Internet hostnames. By default, the utility converts between host names and Internet addresses, but its functionality can be extended with the use of options.

@@ -423,25 +423,27 @@ Administrative tools play an integral part in the management of a server.

-ndc
+rndc

-The name daemon control ( -ndc -) program is a shell script utility that allows the system administrator to control the operation of a nameserver. If you run ndc without any options it will display a usage message and prompt for commands until it reads EOF. Several commands are built into ndc, but the full set of commands supported by the nameserver is dynamic and should be discovered using the "help" command. Read the man page for ndc for details on its command syntax.

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

+

+ -Usage:

-

-ndc [-c channel] [-l localsock] [-p pidfile] [-d] [-q] [-s] [-t] [command]
+Usage:

+

+ + + +rndc [-p port] [-m] server command [command ...] +

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

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

    @@ -468,7 +470,7 @@ MRTG  

-

Return to BINDv9 Administrator Reference Manual table of contents.

+

Return to BINDv9 Administrator Reference Manual table of contents.

diff --git a/doc/arm/BV9ARM.4.html b/doc/arm/BV9ARM.4.html index d78d38694f..3f23152db2 100644 --- a/doc/arm/BV9ARM.4.html +++ b/doc/arm/BV9ARM.4.html @@ -8,105 +8,113 @@

    - + Section 4. Advanced Concepts

    - + 4.1 Dynamic Update

- + Dynamic update is the term used for the ability under certain specified conditions to add, modify or delete records or RRsets in the master zone files. Dynamic update is fully described in RFC 2136.

- -Dynamic update is enabled by including an -allow-update{} - clause in the zone declaration. You should allow as few hosts as possible to update your DNS because there is no per-RR security. If a client is authorized to update your DNS, it can do anything with the zone file, including deleting most of the contents or replacing records with different ones. For this reason, many sites delegate a zone which can be dynamically updated, rather than allowing their uppermost domain to be dynamic.

+ +Dynamic update is enabled on a zone-by-zone basis, by including an +allow-update + or +update-policy + clause in the +zone + statement.

- - -Once a zone has been made dynamic, changes can no longer be made by hand without stopping BIND, editing the zone and then restarting BIND. This is to prevent an update being lost, either by the zone file being changed by hand and overwritten immediately by a dynamic update without being reread, or having a handwritten zone file overwrite a dynamic update that has occurred while the zone file was being hand-edited.

+ + +Updating of secure zones (zones using DNSSEC) works as specified in 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.

+

+ + +The zone files of dynamic zones must not be edited by hand. The zone file on disk at any given time may not contain the latest changes performed by dynamic update. The zone file is written to disk only periodically, and changes that have occurred since the zone file was last written to disk are stored only in the zone's journal ( +.jnl +) file. BIND 9 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.1.1 - -Incremental Transfer (IXFR)

    + +4.2 + +Incremental Zone Transfers (IXFR)

- - -If dynamic update is enabled, and incremental transfer (IXFR) is also enabled, BIND will maintain a list of changes for secondary servers to transfer, instead of having to transfer the entire zone file.

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

- - -IXFR is enabled globally by giving a filename for -ixfr-base - and -ixfr-tmp-file -, and -maintain-ixfr-base true -. A server statement with the -use-ixfr - option set to -true - will then enable incremental transfers to that server.

+ + +When acting as a master, BIND 9 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.

- - -IXFR can only track changes made to the zone with dynamic update - no changes can be made by editing the zone file, even with the stop-start procedure above.

-
+ + +When acting as a slave, BIND 9 will attempt to use IXFR unless it is explicitly disabled. For more information about disabling IXFR, see the description of the +request-ixfr + clause of the +server + statement.

    - -4.2 Split DNS

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

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

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

- + 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, Inc. wants its internal clients to be able to resolve external hostnames and to exchange mail with people on the outside. The company also wants its internal resolvers to have access to certain internal-only zones that are not available at all outside of the internal network.

- + In order to accomplish this, the company will set up two sets of nameservers. One set will be on the inside network (in the reserved IP space) and the other set will be on bastion hosts, which are "proxy" hosts that can talk to both sides of its network, in the DMZ.

- + The internal servers will be configured to forward all queries, except queries for site1.example , @@ -126,7 +134,7 @@ site2.internal .

- + To protect the site1.internal and @@ -134,7 +142,7 @@ site1.internal domains, the internal nameservers must be configured to disallow all queries to these domains from any external hosts, including the bastion hosts.

- + The external servers, which are on the bastion hosts, will be configured to serve the "public" version of the site1 and @@ -150,7 +158,7 @@ b.mx.example.com ).

- + In addition, the public site1 and @@ -158,34 +166,34 @@ 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.

- + Here's an example of a wildcard MX record:

-
 
+

 *   IN MX 10 external1.example.com.

 

 
- 
+
 Now that they accept mail on behalf of anything in the internal network, the bastion hosts will need to know how to deliver mail to internal hosts. In order for this to work properly, the resolvers on the bastion hosts will need to be configured to point to the internal nameservers for DNS resolution.

 

 
- 
+
 Queries for internal hostnames will be answered by the internal servers, and queries for external hostnames will be forwarded back out to the DNS servers on the bastion hosts.

 

 
- 
+
 In order for all this to work properly, internal clients will need to be configured to query 
 only
  the internal nameservers for DNS queries. This could also be enforced via selective filtering on the network.

 

 
- 
+
 If everything has been set properly, 
 Example, Inc.
 's internal clients will now be able to:

 
    
 
  • 
 
- 
+
 Look up any hostnames in the 
 site1
  and 
@@ -193,7 +201,7 @@ site2 .example.com
  zones.
    • 
 
  • 
 
- 
+
 Look up any hostnames in the 
 site1.internal
  and 
@@ -201,21 +209,21 @@ site2.internal
  domains.
    • 
 
  • 
 
- 
+
 Look up any hostnames on the Internet.
    • 
 
  • 
 
- 
+
 Exchange mail with internal AND external people.
    • 
 

 

 
- 
+
 Hosts on the Internet will be able to:

 
    
 
  • 
 
- 
+
 Look up any hostnames in the 
 site1
  and 
@@ -223,7 +231,7 @@ site2 .example.com 
 zones.
    • 
 
  • 
 
- 
+
 Exchange mail with anyone in the 
 site1
  and 
@@ -232,36 +240,37 @@ site2 .example.com
 

 

 
- 
+
 Here is an example configuration for the setup we just described above. Note that this is only configuration information; see 
 Sample Configuration and Logging
  for information on how to configure your zone files.

 

 
- 
+
 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 { externals; };             // 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
+

+zone "site1.example.com" { // sample slave zone
   type master;
   file "m/site1.example.com";
-  forwarders { };                          // do normal iterative resolution (do not forward)
+  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";
@@ -270,7 +279,7 @@ zone "site2.example.com" {
   allow-query { internals; externals; };
   allow-transfer { internals; };
 };

-
 
+

 zone "site1.internal" {
   type master;
   file "m/site1.internal";
@@ -278,8 +287,9 @@ zone "site1.internal" {
   allow-query { internals; };
   allow-transfer { internals; }
 };

-
 
-zone "site2.internal" {  type slave;
+

+zone "site2.internal" {
+  type slave;
   file "s/site2.internal";
   masters { 172.16.72.3; };
   forwarders { };
@@ -288,11 +298,11 @@ zone "site2.internal" {  type slave;
 };

 

 
- 
+
 External (bastion host) DNS server config:

-
 
+

 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
-acl externals { bastion-ips-go-here; };
+acl externals { bastion-ips-go-here; };
 options {
   ...
   ...
@@ -302,14 +312,14 @@ options {
   ...
   ...
 };

-
 
-zone "site1.example.com" {         // sample slave zone
+

+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";
@@ -319,9 +329,11 @@ zone "site2.example.com" {
 };

 

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

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

+

 search ...
 nameserver 172.16.72.2
 nameserver 172.16.72.3
@@ -331,78 +343,80 @@ nameserver 172.16.72.4

 
    
 
    
 
- 
-4.3	TSIG
    
+
+4.4	TSIG
 

 

 
- 
+
 Information about TSIG in this section was provided by Brian Wellington of TISLabs. 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.

 

 
- 
-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. There cannot be support for TSIG in stub resolvers, since storing secret keys in 
-/etc/resolv.conf
- is highly insecure.

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

 

 
- 
+
 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-dnsind-simple-secure-update-02.txt
+draft-ietf-dnsext-simple-secure-update-00.txt
+ in
+ 
+
+Internet Drafts
 ). The 
 nsupdate
- program that is shipped with BIND supports TSIG via the "
+ program that is shipped with BIND 8 supports TSIG via the "
 -k
 " command line option.

 

 
    
 
    
 
- 
-4.3.1	Generate Shared Keys for Each Pair of Hosts
    
+
+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 be the same on both 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.3.1.1	Automatic Generation
    
+
+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.

 

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

-
 
+

    La/E5CjG9O+os1jq0a2jdA==

 

 
- 
+
 This string represents a shared secret.

 

 

 
    
 
    
 
- 
-4.3.1.2	Manual Generation
    
+
+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.

 

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

 

 

@@ -410,79 +424,79 @@ Also, a known string can be run through mmencode or a similar program to generat
 
    
 
    
 
- 
-4.3.2	Copying the Shared Secret to Both Machines
    
+
+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.3.3 Informing the Servers of the Key's Existence

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

- + Imagine host1 and 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==";
+  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.

 

 
- 
+
 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.3.4 Instructing the Server to Use the 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 host1's named.conf file, if host2's IP address is 10.1.2.3:

-
 
+

 server 10.1.2.3 {
-		keys {host1-host2.;};
+  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.3.5 TSIG Key Based Access Control

    + +4.4.5 TSIG Key Based Access Control

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

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

-
 
+

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

 

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

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

    - -4.3.6 Errors

    + +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.
@@ -530,61 +546,65 @@ which is printed at debug level 1.

    - -4.4 DNSSEC

    + +4.5 DNSSEC

- -Cryptographc authentication of DNS information is made possible through the DNS Security (DNSSEC) extension to the domain system. This describes the processing of creating and using DNSSEC signed zones. The zones used in this exercise will be "dnssec.example" and "sub.dnssec.example."

+ +Cryptographc authentication of DNS information is made possible through the DNS Security (DNSSEC) extension to the domain system. This describes the processing of creating and using DNSSEC signed zones. The zones used in this exercise will be +dnssec.example + and +sub.dnssec.example +.

  • - + Step 1: Generate zone keys.

- + The following commands generate 640 bit DSA keys to be used as zone keys for the zones:

-
 
+

 src/bin/dnskeygen/dnskeygen -D 640 -z -n dnssec.example.
 src/bin/dnskeygen/dnskeygen -D 640 -z -n sub.dnssec.example.

 

 
- 
+
 In our example, keys with id 64555 and 39020 were generated.

 

 
- 
+
 Four files were created on disk:

 

 
- 
+
 
 Kdnssec.example.+003+64555.key
  (public key)

 

 
- 
+
 
 Kdnssec.example.+003+64555.private
  (private key)

 

 
- 
+
 
 Ksub.dnssec.example.+003+39020.key
  (public key)

 

 
- 
+
 
 Ksub.dnssec.example.+003+39020.private
  (private key)

 

 
- 
+
 The 
 .key
  files contain public keys in DNS RR format, which is base 64. The 
@@ -593,93 +613,103 @@ The 
 
    
 
  • 
 
- 
+
 Step 2: Enter the keys into the zones.
    • 
 

 

 
- 
+
 The parent zone needs its own key and the child key (as glue). The child zone needs its own key.

-
 
+

 cat Kdnssec.example.+003+64555.key >> zone.dnssec.example
 cat Ksub.dnssec.example.+003+39020.key >> zone.dnssec.example
 cat Ksub.dnssec.example.+003+39020.key >> zone.sub.dnssec.example

 

 
- 
+
 Edit the zone files if desired (to move and/or format KEY records, etc.). This is also a good time to add 
 $ORIGIN
  directives to the zone files if they aren't present.

 
    
 
  • 
 
- 
+
 Step 3: Sign the parent zone.
    • 
 

 

 
- 
-The following command uses the zone.dnssec.example as input and creates the zone.dnssec.example.signed file. The key used is the dsa key for dnssec.example with id 64555 (-ki), and statistics are printed (-st). Parent files are generated for each child zone (-ps), and no global parent file is produced (-no-p1).

-
 
+
+The following command uses the zone.dnssec.example as input and creates the zone.dnssec.example.signed file. The key used is the dsa key for dnssec.example with id 64555 (
+-ki
+), and statistics are printed (
+-st
+). Parent files are generated for each child zone (
+-ps
+), and no global parent file is produced (
+-no-p1
+).

+

 contrib/dns_signer/signer/dnssigner -zi zone.dnssec.example \
 -zo zone.dnssec.example.signed -st -k1 dnssec.example dsa 64555 -ps
 -no-p1

 

 
- 
+
 The following files are created:

 

 
- 
+
 
 zone.dnssec.example.signed
  (signed zone)

 

 
- 
+
 
 sub.dnssec.example..PARENT
  (parent file for sub.dnssec.example)

 
    
 
  • 
 
- 
+
 Step 4: Sign the child zone.
    • 
 

 

 
- 
-The following command is similar to the previous one. The main difference is that the input parent file sub.dnssec.example..PARENT is specified (-pi) in addition to the input zone file; this file was generated by the previous call to the signer. Also, the -ps and -no-p1 options are omitted since there are no child zones of this zone. If this zone had child zones, these options should be present.

-
 
+
+The following command is similar to the previous one. The main difference is that the input parent file sub.dnssec.example..PARENT is specified (
+-pi
+) in addition to the input zone file; this file was generated by the previous call to the signer. Also, the -ps and -no-p1 options are omitted since there are no child zones of this zone. If this zone had child zones, these options should be present.

+

 contrib/dns_signer/signer/dnssigner
  -zi zone.sub.dnssec.example \
 -pi sub.dnssec.example..PARENT -zo zone.sub.dnssec.example.signed \
 -st -k1 sub.dnssec.example dsa 39020

 

 
- 
+
 The following file is created:

 

 
- 
+
 
 zone.sub.dnssec.example.signed
  (signed zone)

 
    
 
  • 
 
- 
+
 Step 5: Enter the top-level zone key in the named.conf file for the master server.
    • 
 

 

 
- 
+
 The public key for the top-level signed zone must be present in named.conf, so that the server can verify the data on load (it must be able to traverse a keychain and end at a trusted key). This key is added in a zone pubkey directive (which has a format similar to a KEY record, but not identical). Note that this is not needed for the subzone, as its key is signed by the trusted key in the parent zone.

 

 
- 
+
 This uses the key from Kdnssec.example.+003+64555.key

-
 
+

 zone "dnssec.example" {
 type master;
 file "zone.dnssec.example.signed";
@@ -694,14 +724,14 @@ pubkey 16641 3 3 "AuNiWOmzSHwrzLMWv1C1gbKQBNAHwMeX+C0owQkfmdxjoTJvnmbN
 
    
 
  • 
 
- 
+
 Step 6: Enter the top-level zone key in the named.conf file for any other servers that will trust the key.
    • 
 

 

 
- 
+
 This uses the same key as above.

-
 
+

 trusted-keys {
 		dnssec.example 16641 3 3
        "AuNiWOmzSHwrzLMWv1C1gbKQBNAHwMeX+C0owQkfmdxjoTJvnmbN
@@ -715,7 +745,7 @@ trusted-keys {
 
    
 
  • 
 
- 
+
 Start named.
    • 
 

 
@@ -723,19 +753,19 @@ Start named.
 
    
 
    
 
- 
-4.5	IPv6
    
+
+4.6	IPv6
 

 

 
    
 
    
 
- 
-4.5.1	IPv6 addresses (A6)
    
+
+4.6.1	IPv6 addresses (A6)
 

 

 
- 
+
 IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the DNS to facilitate scalable Internet routing. There are three types of addresses: 
 Unicast
 , an identifier for a single interface; 
@@ -745,48 +775,48 @@ Multicast
 , an identifier for a set of interfaces. Here we describe the global Unicast address scheme. For more information, see RFC 2374.

 

 
- 
+
 The aggregatable global Unicast address format is as follows:

 

 
- 
+
  

 
@@ -794,37 +824,37 @@ The aggregatable global Unicast address format is as follows:

@@ -832,19 +862,19 @@ Interface ID

@@ -852,37 +882,37 @@ Interface ID

@@ -890,63 +920,63 @@ Interface ID

 

 
 

 
- 
+
 3

 		
 
 

 
- 
+
 13

 		
 
 

 
- 
+
 8

 		
 
 

 
- 
+
 24

 		
 
 

 
- 
+
 16

 		
 
-

+

 
- 
+
 64 bits

 		
 

 

 

 
- 
+
 FP

 		
 
 

 
- 
+
 TLA ID

 		
 
 

 
- 
+
 RES

 		
 
 

 
- 
+
 NLA ID

 		
 
 

 
- 
+
 SLA ID

 		
 
 

 
- 
+
 Interface ID

 		
 

 

 

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

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 

 

 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
 <--Site Topology-->

 		
 
 

 
- 
+
  

 		
 

 

 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

 
- 
+
  

 		
 
 

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

 		
 

 

 

 
- 
+
 Where

 
@@ -954,19 +984,19 @@ Format Prefix (001)

@@ -974,19 +1004,19 @@ Top-Level Aggregation Identifier

@@ -994,19 +1024,19 @@ Reserved for future use

@@ -1014,19 +1044,19 @@ Next-Level Aggregation Identifier

@@ -1034,63 +1064,63 @@ Site-Level Aggregation Identifier

 

 
 

 
- 
+
 FP

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Format Prefix (001)

 		
 

 

 

 
- 
+
 TLA ID

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Top-Level Aggregation Identifier

 		
 

 

 

 
- 
+
 RES

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Reserved for future use

 		
 

 

 

 
- 
+
 NLA ID

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Next-Level Aggregation Identifier

 		
 

 

 

 
- 
+
 SLA ID

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Site-Level Aggregation Identifier

 		
 

 

 

 
- 
+
 INTERFACE ID

 		
 
 

 
- 
+
 =

 		
 
 

 
- 
+
 Interface Identifier

 		
 

 

 

 
- 
+
 The `Public Topology' is provided by the upstream provider or ISP, and (roughly) corresponds to the IPv4 `network' section of the address range. The `Site Topology' is where you can subnet this space, much like subnetting an IPv4 class A or B network into class Cs. The `Interface Identifier' is the address of an individual interface on a given network. (With IPv6, addresses belong to interfaces rather than machines.)

 

 
- 
+
 The subnetting capability of IPv6 is much more flexible than that of IPv4: subnetting can now be carried out on bit boundaries, in much the same way as Classless InterDomain Routing (CIDR).

 

 
- 
+
 The internal structure of the `Public Topology' for an A6 global unicast address consists of:

 

 
- 
+
  

 
@@ -1098,85 +1128,85 @@ The internal structure of the `Public Topology' for an A6 global unicast address
 

 

 
 

 
- 
+
 3

 		
 
 

 
- 
+
 13

 		
 
 

 
- 
+
 8

 		
 
 

 
- 
+
 24

 		
 

 

 
- 
+
 FP

 		
 
 

 
- 
+
 TLA ID

 		
 
 

 
- 
+
 RES

 		
 
 

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

 

 
- 
+
 13 TLA (Top Level Aggregator) bits give the prefix of your top-level IP backbone carrier.

 

 
- 
+
 8 Reserved bits

 

 
- 
+
 24 bits for Next Level Aggregators. This allows organizations with a TLA to hand out portions of their IP space to client organizations, so that the client can then split up the network further by filling in more NLA bits, and hand out IPv6 prefixes to their clients, and so forth.

 

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

 

 
- 
+
 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.5.2	Name to Address Lookup
    
+
+4.6.2	Name to Address Lookup
 

 

 
- 
+
 Forward name lookups (host name to IP address) under IPv6 do not necessarily return the complete IPv6 address of the host. Because the provider-assigned prefix may change, the A6 record can simply specify the locally assigned portion of the name, and refer to the provider for the remainder.

 

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

 

 
- 
+
  

 
@@ -1184,31 +1214,31 @@ $ORIGIN example.com.

@@ -1216,49 +1246,52 @@ REFERRAL

 

 
 

 
- 
+
 $ORIGIN example.com.

 		
 

 

 

 
- 
+
 ; NAME

 		
 
 

 
- 
+
 TTL TYPE

 		
 
 

 
- 
+
 BITS IN REFERRAL

 		
 
 

 
- 
+
 ADDRESS

 		
 
 

 
- 
+
 REFERRAL

 		
 

 

 

 
- 
+
 host.example.com.

 		
 
 

 
- 
+
 1h IN A6

 		
 
 

 
- 
+
 0

 		
 
 

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

 		
 
 

 
- 
+
 .

 		
 

 

+
+
+
 

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

 

 
- 
+
  

 
@@ -1266,31 +1299,31 @@ $ORIGIN example.com.

@@ -1298,49 +1331,49 @@ REFERRAL

 

 
 

 
- 
+
 $ORIGIN example.com.

 		
 

 

 

 
- 
+
 ; NAME

 		
 
 

 
- 
+
 TTL TYPE

 		
 
 

 
- 
+
 BITS IN REFERRAL

 		
 
 

 
- 
+
 ADDRESS

 		
 
 

 
- 
+
 REFERRAL

 		
 

 

 

 
- 
+
 host.example.com.

 		
 
 

 
- 
+
 1h IN A6

 		
 
 

 
- 
+
 48

 		
 
 

 
- 
+
 ::9:a00:20ff:fe81:2b32

 		
 
 

 
- 
+
 prefix.example2.com.

 		
 

 

 

 
- 
+
 Then, in example2.com's zone:

 

 
- 
+
  

 
@@ -1348,31 +1381,31 @@ $ORIGIN example.com.

@@ -1380,94 +1413,94 @@ REFERRAL

 

 
 

 
- 
+
 $ORIGIN example.com.

 		
 

 

 

 
- 
+
 ; NAME

 		
 
 

 
- 
+
 TTL TYPE

 		
 
 

 
- 
+
 BITS IN REFERRAL

 		
 
 

 
- 
+
 ADDRESS

 		
 
 

 
- 
+
 REFERRAL

 		
 

 

 

 
- 
+
 prefix.example2.com.

 		
 
 

 
- 
+
 1h IN A6

 		
 
 

 
- 
+
 0

 		
 
 

 
- 
+
 3ffe:8050:201::

 		
 
 

 
- 
+
 .

 		
 

 

 

 
- 
+
 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.5.3	Address to Name Lookup
    
+
+4.6.3	Address to Name Lookup
 

 

 
- 
+
 Reverse IPv6 addresses may appear as one or more hex strings, known as "bitstring labels," each followed by a number of valid bits. A full 128 bits may be specified at the ip6.int top level, or more likely, the provider will delegate you a smaller chunk of addresses for which you will need to supply reverse DNS.

 

 
- 
+
 The address can be split up along arbitrary boundaries, and is written with hex numbers in forward order, rather than in reverse order as IPv4 PTR records are written. The sections between dot separators are reversed as usual. If the number of valid bits in the hex string is less than the string specifies, it is the 
 first N bits
  that are counted. Thus, \[x2/3] gives a bit pattern of 0010, the first three bits of which, 001, are valid.

 

 
- 
+
 The address above, then, is:

 

 
- 
+
 
 \[x3FFE8050020100090A0020FFFE812B32/128].ip6.int.
  (not divided)

 

 
- 
+
 
 \[x00090A0020FFFE812B32/80].\[xFFF402801008/45].\[x2/3].ip6.int.
  (divided into FP, TLA/RES/NLA, and local)

 

 
- 
+
 
 \[x00090A0020FFFE812B32/80].\[x80500201/32].\[xFFF0/13].\[x2/3].ip6.int.
  (divided into FP, TLA, RES/NLA, and local)

 

 
- 
+
 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.5.4	Using DNAME for Delegation of IPv6 Reverse Addresses
    
+
+4.6.4	Using DNAME for Delegation of IPv6 Reverse Addresses
 

 

 
- 
+
 Delegation of reverse addresses is done through the new DNAME RR. In the example above, where 
 \[x2/3].ip6.int.
  needs to delegate
@@ -1481,34 +1514,34 @@ example2.com
 ), the domain administrator would insert a line similar to the following in the 
 \[x2/3].ip6.int.
  zone:

-
 
+

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

 

 
- 
+
 
 example2.com
  would then place into the 
 ip6 
 zone:

-
 
+

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

 

 
- 
+
 Finally, 
 example.com 
 needs to include in the 
 ip6.example.com
  zone:

-
 
+

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

 

 
- 
+
 We suggest that the top of your administrative control (
 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 "
@@ -1516,10 +1549,10 @@ example.com
 ". 

 

 
- 
+
  

-
Return to BINDv9 Administrator Reference Manual table of contents.

 

 
+
Return to BINDv9 Administrator Reference Manual table of contents.

 
 
diff --git a/doc/arm/BV9ARM.5.html b/doc/arm/BV9ARM.5.html
index 05c86f735a..97433beb96 100644
--- a/doc/arm/BV9ARM.5.html
+++ b/doc/arm/BV9ARM.5.html
@@ -14,14 +14,13 @@ Section 5.	BINDv9 Configuration Reference
 

 
 
-BINDv9 configuration is broadly similar to BIND 8.x; however, there are a few new areas of configuration, such as views. BIND 8.x configuration files should work with few alterations in BINDv9, although more complex configurations should be reviewed to check if they can be more efficiently implemented using the new features found in BINDv9.

+BINDv9 configuration is broadly similar to BIND 8.x; however, there are a few new areas of configuration, such as views. BIND 8.x configuration files should work with few alterations in BINDv9, although more complex configurations should be reviewed to check if they can be more efficiently implemented using the new features found in BIND 9.

 

 
 
-BIND 4.9.x configuration files can be converted to the new format by using

-
+BIND 4.9.x configuration files can be converted to the new format by using the Perl script 
 src/bin/named/named-bootconf.pl
-, a shell script that is part of the BIND release kit.

+ from the BIND 8 release kit.

 

 
    
 
    
@@ -41,7 +40,7 @@ Following is a list of elements used throughout the BIND configuration file docu
 
 
 
    
-
+
 
 
 acl_name
@@ -49,7 +48,7 @@ acl_name
 
 
 
    
-
+
 
 The name of an 
 address_match_list
@@ -61,7 +60,7 @@ acl
 
 
 
    
-
+
 
 
 address_match_list
@@ -69,7 +68,7 @@ address_match_list
 
 
 
    
-
+
 
 A list of one or more 
 ip_addr, ip_prefix, key_id, 
@@ -83,7 +82,7 @@ Address Match Lists
 
 
 
    
-
+
 
 
 domain_name
@@ -91,7 +90,7 @@ domain_name
 
 
 
    
-
+
 
 A quoted string which will be used as a DNS name, for example "
 my.test.domain
@@ -101,15 +100,15 @@ my.test.domain
 
 
 
    
-
+
 
 
-dotted-decimal
+dotted_decimal
 
    
 
 
 
    
-
+
 
 One or more integers valued 0 through 255 separated only by dots ("."), such as 
 123
@@ -123,25 +122,61 @@ One or more integers valued 0 through 255 separated only by dots (".")
 
 
 
    
-
+
 
 
-ip_addr
+ip4_addr
 
    
 
 
 
    
-
+
 
-An IP address with exactly four elements in 
-dotted-decimal
+An IPv4 address with exactly four elements in 
+dotted_decimal
  notation.
    
 
 
 
 
 
    
-
+
+
+
+ip6_addr
    
+
+
+
    
+
+
+An IPv6 address, like 
+fe80::200:f8ff:fe01:9742
+.
    
+
+
+
+
+
    
+
+
+
+ip_addr
    
+
+
+
    
+
+
+An 
+ip4_addr
+ or
+ ip6_addr
+.
    
+
+
+
+
+
    
+
 
 
 ip_port
@@ -149,7 +184,7 @@ ip_port
 
 
 
    
-
+
 
 An IP port 
 number
@@ -161,7 +196,7 @@ number
 
 
 
    
-
+
 
 
 ip_prefix
@@ -169,11 +204,11 @@ ip_prefix
 
 
 
    
-
+
 
-An IP network specified in 
-dotted-decimal
- form, followed by "/'' and then the number of bits in the netmask. E.g. 
+An IP network specified as an 
+ip_addr
+, followed by "/'' and then the number of bits in the netmask. E.g. 
 127/8
  is the network 
 127.0.0.0
@@ -191,7 +226,7 @@ dotted-decimal
 
 
 
    
-
+
 
 
 key_name
@@ -199,15 +234,17 @@ key_name
 
 
 
    
-
+
 
-A string representing the name of a shared key, to be used for transaction security.
    
+A 
+domain_name
+ representing the name of a shared key, to be used for transaction security.
    
 
 
 
 
 
    
-
+
 
 
 number
@@ -215,7 +252,7 @@ number
 
 
 
    
-
+
 
 A non-negative integer with an entire range limited by the range of a C language signed integer (2,147,483,647 on a machine with 32 bit integers). Its acceptable value might further be limited by the context in which it is used.
    
 
@@ -223,7 +260,7 @@ A non-negative integer with an entire range limited by the range of a C language
 
 
 
    
-
+
 
 
 path_name
@@ -231,9 +268,9 @@ 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
 ".
    
 
@@ -241,7 +278,7 @@ zones/master/my.test.domain
 
 
 
    
-
+
 
 
 size_spec
@@ -249,7 +286,7 @@ size_spec
 
 
 
    
-
+
 
 A number, the word 
 unlimited
@@ -257,7 +294,7 @@ unlimited
 default
 .
    
 
    
-
+
 
 The maximum value of 
 size_spec
@@ -267,7 +304,7 @@ unlimited
 default
  uses the limit that was in force when the server was started.
    
 
    
-
+
 
 A 
 number
@@ -285,7 +322,7 @@ G
 g
  for gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.
    
 
    
-
+
 
 Integer storage overflow is currently silently ignored during conversion of scaled values, resulting in values less than intended, possibly even negative. Using 
 unlimited
@@ -295,7 +332,7 @@ unlimited
 
 
 
    
-
+
 
 
 yes_or_no
@@ -303,7 +340,7 @@ yes_or_no
 
 
 
    
-
+
 
 Either 
 yes
@@ -337,9 +374,11 @@ Address Match Lists
    
 
 5.1.1.1	Syntax
 

-
[ ! ] (
-address_match_list | ip_address [/number] | acl_name) | key key_id ; [ [ ! ] (address_match_list 
-| ip_address | ip_prefix | acl_name) | key key_id ; [...]]

+
+
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})
+

 

 

 
    
@@ -356,7 +395,7 @@ Address match lists are primarily used to determine access control for various s
 
  1. 
 
 
-an IP address (in dotted-decimal notation)
    2. 
+an IP address (IPv4 or IPv6)
 
  2. 
 
 
@@ -368,16 +407,30 @@ a key ID, as defined by the key statement
    3. 
 
  3. 
 
 
-the name of an address match list previously defined with the acl statment
    4. 
+the name of an address match list previously defined with the 
+acl
+ statment
 
  4. 
 
 
-another address_match_list
    5. 
+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.
    
 
    
 
 
@@ -487,7 +540,7 @@ 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, so whatever follows it will be interpreted as the start of the next 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.
    
 

 
 
@@ -509,14 +562,14 @@ A BINDv9 configuration consists of statements and comments. Statements end with
 
 The following statements are supported:

 

-
+
 
  

 
@@ -532,7 +585,7 @@ defines a named IP address matching list, for access control and other uses

@@ -566,7 +619,7 @@ includes a file

@@ -600,7 +653,7 @@ specifies what the server logs, and where the log messages are sent

@@ -616,7 +669,7 @@ controls global server configuration options and sets defaults for other stateme
 
@@ -632,7 +685,7 @@ sets certain configuration options on a per-server basis

@@ -648,7 +701,7 @@ defines keys that are preconfigured into the server and implicitly trusted. See
 
@@ -664,7 +717,7 @@ defines a view

 

 
 

-
+
 
 
 acl
@@ -524,7 +577,7 @@ acl
 

 
 

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

 		
 

 
 

-
+
 
 
 controls
@@ -540,17 +593,17 @@ controls
 

 
 

-
+
 
 declares control channels to be used by the 
-ndc
+rndc
  utility

 		
 

 

 
 

-
+
 
 
 include
@@ -558,7 +611,7 @@ include
 

 
 

-
+
 
 includes a file

 		
 

 
 

-
+
 
 
 key
@@ -574,7 +627,7 @@ key
 

 
 

-
+
 
 specifies key information for use in authentication and authorization using TSIG. See 
 draft-ietf-dnsind-tsig-13.txt
@@ -584,7 +637,7 @@ draft-ietf-dnsind-tsig-13.txt
 

 
 

-
+
 
 
 logging
@@ -592,7 +645,7 @@ logging
 

 
 

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

 		
 

 
 

-
+
 
 
 options
@@ -608,7 +661,7 @@ options
 

 
 

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

 

 
 

-
+
 
 
 server
@@ -624,7 +677,7 @@ server
 

 
 

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

 		
 

 
 

-
+
 
 
 trusted-keys
@@ -640,7 +693,7 @@ trusted-keys
 

 
 

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

 

 
 

-
+
 
 
 view
@@ -656,7 +709,7 @@ view
 

 
 

-
+
 
 defines a view

 		
 

 
 

-
+
 
 
 zone
@@ -672,41 +725,33 @@ zone
 

 
 

-
+
 
 defines a zone

 		
 

 

 

-
+
 
 The 
 logging
  and 
 options
- statements may only occur once per configuration. 
-logging
- statements are read in first, 
-options
- second. Also, although the 
-options
- statement can appear anywhere in a configuration file, it is suggested that it appear at the beginning, since things like the default directory are not defined until it after it has been read.

+ statements may only occur once per configuration.

 

 
    
 
    
-
+
 
 5.2.1	
 acl
  Statement Grammar
    
 

 

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

+ };

 
 

 
    
@@ -724,9 +769,7 @@ acl
 
 The 
 acl
- statement creates a 
-named
- address match list. It gets its name from a primary use of address match lists: Access Control Lists (ACLs).
    
+ statement assigns a symbolic name to an address match list. It gets its name from a primary use of address match lists: Access Control Lists (ACLs).
    
 
    
 
 
@@ -755,7 +798,7 @@ any
 
    
 
 
-Allows all hosts.
    
+Matches all hosts.
    
 
 
 
@@ -771,7 +814,7 @@ none
 
    
 
 
-Denies all hosts.
    
+Matches no hosts.
    
 
 
 
@@ -787,7 +830,7 @@ localhost
 
    
 
 
-Allows the IP addresses of all interfaces on the system.
    
+Matches the IP addresses of all interfaces on the system.
    
 
 
 
@@ -803,7 +846,7 @@ localnets
 
    
 
 
-Allows any host on a network for which the system has an interface.
    
+Matches any host on a network for which the system has an interface.
    
 
 
 
@@ -814,14 +857,13 @@ Allows 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...;[..]]]
+       [ inet ( ip_addr|*) port ip_port allow { address_match_list} ; [inet...;[...]]]
+       [ unix string permission number owner number group number ; [unix...;[..]]]
 };

 

 

@@ -864,9 +906,19 @@ inet
 ip_port
  on the specified 
 ip_addr
-. Modern telnet clients are capable of speaking directly to these sockets, and the control protocol is ARPAnet-style text. It is recommended that 127.0.0.1 be the only 
+. It is recommended that 127.0.0.1 be the only 
 ip_addr
  used, and this only if you trust all non-privileged users on the local host to manage your nameserver.

+

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

 

 

 
    
@@ -878,8 +930,7 @@ include
  Statement Grammar
 

 

-include "filename
-";

+include "filename";

 
 

 
    
@@ -899,7 +950,7 @@ include
 include
  statement is encountered. The 
 include
- statement facilitates the administration of configuration files by permitting the writing of some things but not others. For example, the statement could include private keys that are readable only by a nameserver.
    
+ 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.
    
 

 

 
    
@@ -911,12 +962,9 @@ key
  Statement Grammar
 

 

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

 

 

@@ -970,34 +1018,30 @@ algorithm_id
 logging
  statement grammar
 
-

+
 logging {
+   [ channel channel_name {
+     ( file path name
+         [ versions (number | unlimited ) ]
+         [ size size spec ]
+       | syslog ( syslog_facility )
+       | null );
 
-    [category (name|default|notify){( name| null);[( name| 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 (name|default|notify){( name| null);[( name| null);[...]]};
+   [ category category_name {
+     channel_name ; [channel_name ; ... ]
+   }; ]
+   ...
+};
+

 
-    [channel (name|null){(file string [( versions( number| unlimited)][ size( string| number| default| unlimited ) ] ) ; } ; ]
 
-    [channel (name|null){ syslog[( string|syslog ) ] ; } ; ]
-
-    [channel (name|null){ null; } ; ]
-
-    [channel (name|null){ severity ( string| debug [ number] | dynamic); } ; ]
-
-    [channel (name|null){ print-time true_or_false ; } ; ]
-
-    [channel (name|null){ print-category true_or_false ;} ; ]
-
-    [channel (name|null){ print-severity true_or_false ; } ;] } ;
-
-

-

-

-
    
-
    
-
-
 5.2.10	
 logging
  statement definition and usage
    
@@ -1024,170 +1068,561 @@ syslog
 . If there is no 
 logging
  statement, the logging configuration will be:
    
-
    
-
-
-
-Note: these categories may change!  Also, additional syntax in BINDv9 may make it possible to limit logging to particular modules.
-
    
 
    
  
    
-
    
+
    
 logging {
      category default { default_syslog; default_debug; };
-     category panic { default_syslog; default_stderr; };
-     category packet { default_debug; };
-     category eventlib { default_debug; };
-		};
    
+};
    
 
    
 
 
-The logging configuration is established as soon as the 
+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 is parsed. If you want to redirect messages about processing of the entire configuration file, the 
-logging
- statement must appear first. Even if you do not redirect configuration file parsing messages, we recommend always putting the logging statement first so that this rule need not be consciously recalled if you ever do need or want the parser's messages relocated.
    
+ 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.
    
+
    
+
      
+
      
+
+
+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.
    
+
    
+
+
+Every 
+channel
+ definition must include a clause that says whether messages selected for the channel go to a file, to a particular syslog facility, or are discarded. It can optionally also limit the message severity level that will be accepted by the channel (default is 
+info
+), and whether to include a 
+named
+-generated time stamp, the category name and/or severity level (default is not to include any).
    
+
    
+
+
+The word 
+null
+ as the destination option for the channel will cause all messages sent to it to be discarded; in that case, other options for the channel are meaningless.
    
+
    
+
+
+The 
+file
+ clause can include limitations both on how large the file is allowed to become, and how many versions of the file will be saved each time the file is opened.
    
+
    
+
+
+The 
+size
+ option for files is simply a hard ceiling on log growth. If the file ever exceeds the size, then 
+named
+ will not write anything more to it until the file is reopened; exceeding the size does not automatically trigger a reopen. The default behavior is not to limit the size of the file.
    
+
    
+
+
+If you use the 
+version
+ log file option, then 
+named
+ will retain that many backup versions of the file by renaming them when opening. For example, if you choose to keep 3 old versions of the file 
+lamers.log
+ then just before it is opened 
+lamers.log.1
+ is renamed to 
+lames.log.2
+, 
+lamers.log.0
+ is renamed to 
+lamers.log.1
+, and 
+lamers.log
+ is renamed to 
+lamers.log.0
+. No rolled versions are kept by default; any existing log file is simply appended. The 
+unlimited
+ keyword is synonymous with 
+99
+ 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;
+    };
    
+
    
+
+
+The argument for the 
+syslog
+ clause is a syslog facility as described in the 
+syslog
+ manual page. How 
+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 
+syslog
+ that only uses two arguments to the 
+openlog()
+ function, then this clause is silently ignored.
    
+
    
+
+
+The 
+severity
+ clause works like 
+syslog
+'s "priorities," except that they can also be used if you are writing straight to a file rather than using 
+syslog
+. Messages which are not at least of the severity level given will not be selected for the channel; messages of higher severity levels will be accepted.
    
+
    
+
+
+If you are using 
+syslog
+, then the 
+syslog.conf
+ priorities will also determine what eventually passes through. For example, defining a channel facility and severity as 
+daemon
+ and 
+debug
+ but only logging 
+daemon.warning
+ via 
+syslog.conf
+ will cause messages of severity 
+info
+ and 
+notice
+ to be dropped. If the situation were reversed, with 
+named
+ writing messages of only 
+warning
+ or higher, then 
+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";
+      severity debug 3;
+  };
    
+
    
+
+
+will get debugging output of level 3 or less any time the server is in debugging mode, regardless of the global debugging level. Channels with 
+dynamic
+ severity use the server's global level to determine what messages to print.
    
+
    
+
+
+If 
+print-time
+ has been turned on, then the date and time will be logged. 
+print-time
+ may be specified for a 
+syslog
+ channel, but is usually pointless since 
+syslog
+ also prints the date and time. If 
+print-category
+ is requested, then the category of the message will be logged as well. Finally, if 
+print-severity
+ is on, then the severity level of the message will be logged. The 
+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 
+The category Phrase
+.
    
+
    
+    channel default_syslog {
+        syslog daemon;     # send 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_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
+    };
    
+
    
+
+
+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.
    
+
    
+
    
+
      
+
      
+
+
+5.2.10.2	
+
+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; };
    
+
    
+
+
+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;
+    default_syslog;
+    default_debug;
+};
    
+
    
+
+
+To discard all messages in a category, specify the 
+null
+ channel:
    
+
    
+category lame-servers { null; };
+category cname { null; };
    
+
    
+
+
+Following are the available categories and brief descriptions of the types of log information they contain.  
+This list is still subject to change.
+ 
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    
+
    
+
+
+
+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; };
+
    
+
    
+
    
+
+
+
+general
    
+    		
+
    
+
+
+The catch-all. Many things still aren't classified into categories, and they all end up here.
    
+
    
+
    
+
+
+
+database
    
+    		
+
    
+
+
+Messages relating to the databases used internally by the name server to store zone and cache data.
    
+
    
+
    
+
+
+
+security
    
+    		
+
    
+
+
+Approval and denial of requests.
    
+
    
+
    
+
+
+
+config
+
    
+    		
+
    
+
+
+Configuration file parsing and processing.
    
+
    
+
    
+
+
+
+resolver
    
+    		
+
    
+
+
+DNS resolution, such as the recursive lookups performed on behalf of clients by a caching name server.
    
+
    
+
    
+
+
+
+xfer-in
+
    
+    		
+
    
+
+
+Zone transfers the server is receiving.
    
+
    
+
    
+
+
+
+xfer-out
+
    
+    		
+
    
+
+
+Zone transfers the server is sending.
    
+
    
+
    
+
+
+
+notify
+
    
+    		
+
    
+
+
+The NOTIFY protocol.
    
+
    
+
    
+
+
+
+client
+
    
+    		
+
    
+
+
+Processing of client requests.
    
+
    
+
    
+
+
+
+network
+
    
+    		
+
    
+
+
+Network operations.
    
+
    
+
    
+
+
+
+update
+
    
+    		
+
    
+
+
+Dynamic updates.
    
+
    
+
    
 

 

 
    
 
    
-
+
 
 5.2.11	
 options
  Statement Grammar
    
 

 

-
+
 
-This is the grammar of option statement format in the 
+This is the grammar of the 
+options
+ statement in the 
 named.conf
  file:

 

-Syntax
 options {
-    [ version version_string; ]
-
-    [ directory path_name; ]
-
-    [ named-xfer path_name; ]
-
-    [ tkey-domain string; ]
-
-    [ tkey-dhkey string number; ]
-
-    [ 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 ; ]
-
-    [ expert_mode yes_or_no ; ]
-
+    [version version_string; ]
+    [directory path_name; ]
+    [ named-xfer path_name; ]
+    [tkey-domain string; ]
+    [tkey-dhkey string number; ]
+    [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 ; ]
 };

 

 

@@ -1221,9 +1656,7 @@ version
 

 
 
-The version the server should report via the 
-ndc
- command or via a query of name 
+The version the server should report via a query of name 
 version.bind
  in class 
 chaos
@@ -1261,12 +1694,13 @@ named-xfer
 

 
 
-The pathname to the 
+
+This option is obsolete.
+  It was used in BIND 8 to specify the pathname to the 
 named-xfer
- program that the server uses for inbound zone transfers. If not specified, the default is system dependent

-(e.g. "
-/usr/sbin/named-xfer
-").

+ program.  In BINDv9, no separate 
+named-xfer
+ program is needed; its functionality is built into the name server.

 
 
 
@@ -1288,7 +1722,9 @@ SIGINT
 ndc dumpdb
 ). If not specified, the default is "
 named_dump.db
-".

+". 
+Not yet implemented in BINDv9.
+

 
 
 
@@ -1304,13 +1740,11 @@ memstatistics-file
 

 
 
-The pathname of the file the server writes memory usage statistics to on exit, if 
-deallocate-on-exit
- is 
-yes
-. 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.
+

 
 
 
@@ -1326,10 +1760,11 @@ 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

-"/etc/named.pid". The pid-file is used by programs like 
-ndc
- that want to send signals to the running nameserver.

+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 
+/etc/named.pid
+. The pid-file is used by programs that want to send signals to the running nameserver.

 
 
 
@@ -1345,13 +1780,11 @@ statistics-file
 

 
 
-The pathname of the file the server appends statistics to when it receives 
-SIGKILL
- signal (
-ndc stats
-). 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
+.

 
 
 
@@ -1386,9 +1819,11 @@ If 
 yes
 , then the 
 AA
- bit is always set on NXDOMAIN responses, even if the server is not actually authoritative. The default is yes. Do not turn off 
-auth-nxdomain
- unless you are sure you know what you are doing, as some older software won't like it.

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

 
 
 
@@ -1404,15 +1839,7 @@ deallocate-on-exit
 

 
 
-If 
-yes
-, then when the server exits it will painstakingly deallocate every object it allocated, and then write a memory usage report to the 
-memstatistics-file
-. The default is 
-no
-, because it is faster to let the operating system clean up. 
-deallocate-on-exit
- is handy for detecting memory leaks.

+This option was used in BIND 8 to enable checking for memory leaks on exit. BINDv9 ignores the option and always performs the checks.

 
 
 
@@ -1463,7 +1890,9 @@ 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.
+

 
 
 
@@ -1479,11 +1908,7 @@ fake-iquery
 

 
 
-If 
-yes
-, the server will simulate the obsolete DNS query type IQUERY. The default is 
-no
-.

+In BIND 8, this option was used to enable simulating the obsolete DNS query type IQUERY. BINDv9 never does IQUERY simulation.

 
 
 
@@ -1507,7 +1932,9 @@ 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).

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

 
 
 
@@ -1523,29 +1950,13 @@ has-old-clients
 

 
 
-Setting the option to 
-yes
- is equivalent to setting the following three options: 
+This option was incorrectly implemented in BIND 8, and is ignored by BINDv9.  To achieve the intended effect of 
+has-old-clients yes
+, specify the two separate options 
 auth-nxdomain yes
-;, 
-maintain-ixfr-base yes
-; and
- rfc2308-type1 no
-;. The use of 
-has-old-clients
- with 
-auth-nxdomain
-, 
-maintain-ixfr-base
  and 
-rfc2308-type1
- is order dependent. The default is 
-no
-.

-

-
-
-(Note that this is a broken implementation iin BIND version 8. It should not be necessary in any but the oldest of BIND installations.)

+rfc2308-type-1 no
+ instead.

 
 
 
@@ -1567,7 +1978,9 @@ yes
 no
 . Note: turning on 
 host-statistics
- can consume huge amounts of memory.

+ can consume huge amounts of memory. 
+Not yet implemented in BINDv9.
+

 
 
 
@@ -1583,10 +1996,10 @@ maintain-ixfr-base
 

 
 
-If 
-yes
-, then a transaction log is kept for Incremental Zone Transfer. The default is 
-no
+
+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
 .

 
 
@@ -1603,11 +2016,7 @@ multiple-cnames
 

 
 
-If 
-yes
-, then multiple CNAME resource records will be allowed for a domain name. The default is 
-no
-. Allowing multiple CNAME records is against standards and is not recommended. Multiple CNAME support is available because previous versions of BIND allowed multiple CNAME records, and these records have been used for load balancing by a number of sites.

+This option was used in BIND 8 to allow a domain name to allow multiple CNAME records in violation of the DNS standards.  BINDv9 currently does not check for multiple CNAMEs in zone data loaded from master files, but such checks may be introduced in a later release.  BINDv9 always strictly enforces the CNAME rules in dynamic updates.

 
 
 
@@ -1631,7 +2040,9 @@ notify
 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.

+ statement. It would only be necessary to turn off this option if it caused slaves to crash. 
+Not yet supported in BINDv9.
+

 
 
 
@@ -1675,12 +2086,31 @@ yes
 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
+. 
+Not yet implemented in BINDv9
 .

 
 
 
 
 

+
+
+
+use-id-pool

+
+
+

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

+
+
+
+
+

 
 
 
@@ -1691,19 +2121,19 @@ treat-cr-as-space
 

 
 
-If 
-yes
-, the server will treat `
+This option was used in BIND 8 to make the server treat `
 \r
-' characters the same way it treats a 
+' characters the same way as 
 <space> 
 "
  
 " or `
 \t
-'. This may be necessary when loading zone files on a UNIX system that were generated on an NT or DOS machine. The default is 
-no
-.

+', 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 `
+\r\n
+' newlines are always accepted, and the option is ignored.

 
 
 
@@ -1764,15 +2194,11 @@ Specifies the IP addresses to be used for forwarding. The default is the empty l
 

 
 
-Forwarding can also be configured on a per-zone basis, allowing for the global forwarding options to be overridden in a variety of ways. You can set particular zones to use different forwarders, or have different 
+Forwarding can also be configured on a per-domain basis, allowing for the global forwarding options to be overridden in a variety of ways. You can set particular domains to use different forwarders, or have different 
 forward only/first behavior
 , or not forward at all. See 
 zone Statement Grammar
  for more information.

-

-
-
-Future versions of BIND will continue to support the forward and forwarders options syntax.

 

 

 
    
@@ -1871,6 +2297,12 @@ 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.
+
    
 

 

 
    
@@ -1967,7 +2399,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
-.
    
+.  
+Not yet implemented in BINDv9.
+
    
 
 
 
@@ -2006,6 +2440,12 @@ will enable the nameserver on port 53 for the IP address 5.6.7.8, and on port 12
 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 
+listen-on-v6
+ option may be added in a later release.
    
 

 

 
    
@@ -2019,7 +2459,9 @@ listen-on
 
 If the server doesn't know the answer to a question, it will query other nameservers. 
 query-source
- specifies the address and port used for such queries. If 
+ specifies the address and port used for such queries. For queries sent over IPv6, there is a separate 
+query-source-v6
+ option.  If 
 address
  is 
 *
@@ -2029,9 +2471,10 @@ INADDR_ANY
 port
  is 
 *
- or is omitted, a random unprivileged port will be used. The default 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 *

 

 
 
@@ -2070,9 +2513,52 @@ max-transfer-time-in
 

 
 
-Inbound zone transfers (
-named-xfer
- processes) running longer than this many minutes will be terminated. The default is 120 minutes (2 hours).

+Inbound zone transfers running longer than this many minutes will be terminated. The default is 120 minutes (2 hours).

+
+
+
+
+

+
+
+
+max-transfer-idle-in

+
+
+

+
+
+Inbound zone transfers making no progress in this many minutes will be terminated. The default is 60 minutes (1 hour).

+
+
+
+
+

+
+
+
+max-transfer-time-out

+
+
+

+
+
+Outbound zone transfers running longer than this many minutes will be terminated. The default is 120 minutes (2 hours).

+
+
+
+
+

+
+
+
+max-transfer-idle-out

+
+
+

+
+
+Outbound zone transfers making no progress in this many minutes will be terminated.  The default is 60 minutes (1 hour).

 
 
 
@@ -2094,7 +2580,7 @@ one-answer
 many-answers
  packs as many resource records as possible into a message. 
 many-answers
- is more efficient, but is only known to be understood by BIND 8.x and patched versions of BIND 4.9.5. The default is 
+ is more efficient, but is only known to be understood by BINDv9, BIND 8.x and patched versions of BIND 4.9.5. The default is 
 one-answer
 . 
 transfer-format
@@ -2134,7 +2620,7 @@ transfers-out
 

 
 
-This option will be used in the future to limit the number of concurrent outbound zone transfers. It is checked for syntax, but is otherwise ignored.

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

 
 
 
@@ -2150,9 +2636,7 @@ transfers-per-ns
 

 
 
-The maximum number of inbound zone transfers (
-named-xfer 
-processes) 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
@@ -2178,7 +2662,7 @@ transfer-source
 
 
 transfer-source
- determines which local address will be bound to the  TCP connection used to fetch all zones transferred inbound by the server. 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 
+ determines which local address will be bound to IPv4 TCP connections used to fetch zones transferred inbound by the server. 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
  option for the zone being transferred, if one is specified. This statement sets the 
 transfer-source
@@ -2193,6 +2677,23 @@ zone
 
 
 

+
+
+
+transfer-source-v6

+
+
+

+
+
+Like 
+transfer-source
+, but for zone transfers performed using IPv6.

+
+
+
+
+

 
 
 
@@ -2205,7 +2706,9 @@ 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.
+

 
 
 
@@ -2233,7 +2736,9 @@ 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).

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

 
 
 
@@ -2248,9 +2753,7 @@ also-notify
 

 
 
-The server's usage of many system resources can be limited. Some operating systems don't support some of the limits. On such systems, a warning will be issued if the unsupported limit is used. Some operating systems don't support limiting resources, and on these systems a 
-cannot set resource limits on this system
- message will be logged.

+The server's usage of many system resources can be limited. Some operating systems don't support some of the limits. On such systems, a warning will be issued if the unsupported limit is used. Some operating systems don't support limiting resources.

 

 
 
@@ -2287,7 +2790,9 @@ coresize
 
 The maximum size of a core dump. The default is 
 default
-.

+. 
+Not yet implemented in BINDv9.
+

 
 
 
@@ -2305,7 +2810,9 @@ datasize
 
 The maximum amount of data memory the server may use. The default is 
 default
-.

+. 
+Not yet implemented in BINDv9.
+

 
 
 
@@ -2333,7 +2840,9 @@ 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.
+

 
 
 
@@ -2351,7 +2860,9 @@ 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.
+

 
 
 
@@ -2369,27 +2880,64 @@ stacksize
 
 The maximum amount of stack memory the server may use. The default is 
 default
-.

+. 
+Not yet implemented in BINDv9.
+

+
+
+
+
+

+
+
+
+tcp-clients

+
+
+

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

+
+
+
+
+

+
+
+recursive-clients

+
+
+

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

 
 
 
+

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

 
 

 
    
 
    
-
+
 
 5.2.12.9	Periodic Task Intervals
    
 

 

-
+
 
  

 

 

 
 

-
+
 
 
 cleaning-interval
@@ -2397,7 +2945,7 @@ cleaning-interval
 

 
 

-
+
 
 The server will remove expired resource records from the cache every 
 cleaning-interval 
@@ -2407,7 +2955,7 @@ minutes. The default is 60 minutes. If set to 0, no  periodic cleaning will occu
 

 
 

-
+
 
 
 heartbeat-interval
@@ -2415,17 +2963,19 @@ 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.
+

 		
 

 

 
 

-
+
 
 
 interface-interval
@@ -2433,7 +2983,7 @@ interface-interval
 

 
 

-
+
 
 The server will scan the network interface list every 
 interface-interval
@@ -2445,7 +2995,7 @@ listen-on
 

 
 

-
+
 
 
 statistics-interval
@@ -2453,11 +3003,13 @@ 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.
+

 		
 

 

@@ -2493,13 +3045,23 @@ will prefer servers on network 10 the most, followed by hosts on network 1.2.0.0
 
 
 The default topology is

-

+

     topology { localhost; localnets; };

+

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

 

 

 
    
 
    
-
+
 
 5.2.12.11	
 
@@ -2587,6 +3149,16 @@ sortlist {
            { localhost; localnets; };
            { localnets; };
 };

+

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

 
 

 
    
@@ -2610,10 +3182,7 @@ 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
 
    
 
    
 
@@ -2720,6 +3289,16 @@ rrset-order
 
 
 is used.
    
+
    
+
+
+
+The 
+
+rrset-order
+
+ statement is not yet implemented in BINDv9.
+
    
 

 

 
    
@@ -2746,7 +3325,9 @@ 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.
+
    
 
 
 
@@ -2770,7 +3351,9 @@ max-ncache-ttl
  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.
    
+ 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.
+
    
 
 
 
@@ -2786,7 +3369,9 @@ 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.
+
    
 
 
 
@@ -2804,7 +3389,7 @@ The minimum number of root servers that is required for a request for the root s
 
 use-ixfr
  is deprecated in BINDv9. If you need to disable IXFR to a particular server or servers see information on the  
-support-ixfr
+provide-ixfr
  option in the Server Statement description (
 server Statement Grammar
  , below) and  in the description of Incremental Transfer (IXFR) (
@@ -2824,18 +3409,12 @@ server
  Statement Grammar
 

 

-server ip_addr {
-
-    [ bogus yes_or_no ; ]
-
-    [ support-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 ; [...]] } ; ]
 };

 

 

@@ -2858,17 +3437,53 @@ 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.
+

 

 
 
+The 
+provide-ixfr
+ clause determines whether the local server, acting as master, will respond with an incremental zone transfer when the given remote server, a slave, requests it. If set to 
+yes
+, incremental transfer will be provided whenever possible. If set to 
+no
+, all transfers to the remote server will be nonincremental. If not set, the value of the 
+provide-ixfr 
+option in the global options block is used as a default.

+

+
+
+The 
+request-ixfr
+ clause determines whether the local server, acting as a slave, will request incremental zone transfers from the given remote server, a master. If not set, the value of the 
+request-ixfr
+ option in the global options block is used as a default.

+

+
+
+IXFR requests to servers that do not support IXFR will automatically fall back to AXFR.  Therefore, there is no need to manually list which servers support IXFR and which ones do not; the global default of 
+yes
+ should always work. The purpose of the 
+provide-ixfr
+ and 
+request-ixfr
+ clauses is to make it possible to disable the use of IXFR even when both master and slave claim to support it, for example if one of the servers is buggy and crashes or corrupts data when IXFR is used.

+

+
+
 The server supports two zone transfer methods. The first, 
 one-answer
 , uses one DNS message per resource record transferred. 
 many-answers
  packs as many resource records as possible into a message. 
 many-answers
- is more efficient, but is only known to be understood by BIND 8.2 and patched versions of BIND 4.9.5. You can specify which method to use for a server with the 
+ is more efficient, but is only known to be understood by BIND 9, BIND 8.x, and patched versions of BIND 4.9.5. You can specify which method to use for a server with the 
 transfer-format 
 option. If 
 transfer-format 
@@ -2897,6 +3512,12 @@ key
  statement must come before the 
 server
  statement that references it. When a request is sent to the remote server, a request signature will be generated using the key specified here and appended to the message. A request originating from the remote server is not required to be signed by this key.

+

+
+
+Although the grammar of the 
+keys
+ clause allows for multiple keys, only a single key per server is currently supported.

 

 

 
    
@@ -2909,10 +3530,8 @@ trusted-keys
 

 

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

 

 

@@ -2945,627 +3564,6 @@ Each trusted key is associated with a domain name. Its attributes are the non-ne
 
 
 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.

-

-
    
-
    
-
-
-5.2.16.1	The 
-channel
- Phrase
    
-

-

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

-

-
-
-Every 
-channel
- definition must include a clause that says whether messages selected for the channel go to a file, to a particular syslog facility, or are discarded. It can optionally also limit the message severity level that will be accepted by the channel (default is 
-info
-), and whether to include a 
-named
--generated time stamp, the category name and/or severity level (default is not to include any).

-

-
-
-The word 
-null
- as the destination option for the channel will cause all messages sent to it to be discarded; in that case, other options for the channel are meaningless.

-

-
-
-The 
-file
- clause can include limitations both on how large the file is allowed to become, and how many versions of the file will be saved each time the file is opened.

-

-
-
-The 
-size
- option for files is simply a hard ceiling on log growth. If the file ever exceeds the size, then 
-named
- will not write anything more to it until the file is reopened; exceeding the size does not automatically trigger a reopen. The default behavior is not to limit the size of the file.

-

-
-
-If you use the 
-version
- log file option, then 
-named
- will retain that many backup versions of the file by renaming them when opening. For example, if you choose to keep 3 old versions of the file 
-lamers.log
- then just before it is opened 
-lamers.log.1
- is renamed to 
-lames.log.2
-, 
-lamers.log.0
- is renamed to 
-lamers.log.1
-, and 
-lamers.log
- is renamed to 
-lamers.log.0
-. No rolled versions are kept by default; any existing log file is simply appended. The 
-unlimited
- keyword is synonymous with 
-99
- 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;
-    };

-

-
-
-The argument for the 
-syslog
- clause is a syslog facility as described in the 
-syslog
- manual page. How 
-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 
-syslog
- that only uses two arguments to the 
-openlog()
- function, then this clause is silently ignored.

-

-
-
-The 
-severity
- clause works like 
-syslog
-'s "priorities," except that they can also be used if you are writing straight to a file rather than using 
-syslog
-. Messages which are not at least of the severity level given will not be selected for the channel; messages of higher severity levels will be accepted.

-

-
-
-If you are using 
-syslog
-, then the 
-syslog.conf
- priorities will also determine what eventually passes through. For example, defining a channel facility and severity as 
-daemon
- and 
-debug
- but only logging 
-daemon.warning
- via 
-syslog.conf
- will cause messages of severity 
-info
- and 
-notice
- to be dropped. If the situation were reversed, with 
-named
- writing messages of only 
-warning
- or higher, then 
-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 "ndc trace". 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";
-      severity debug 3;
-  };

-

-
-
-will get debugging output of level 3 or less any time the server is in debugging mode, regardless of the global debugging level. Channels with 
-dynamic
- severity use the server's global level to determine what messages to print.

-

-
-
-If 
-print-time
- has been turned on, then the date and time will be logged. 
-print-time
- may be specified for a 
-syslog
- channel, but is usually pointless since 
-syslog
- also prints the date and time. If 
-print-category
- is requested, then the category of the message will be logged as well. Finally, if 
-print-severity
- is on, then the severity level of the message will be logged. The 
-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-Apr-1997 15:05:32.863 default: notice: Ready to answer queries.

-

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

-

-    channel default_syslog {
-        syslog daemon;     # send 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_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
-    };

-

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

-

-

-
    
-
    
-
-
-5.2.16.2	
-
-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; };

-

-
-
-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; default_syslog; default_debug; };

-

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

-

-    category lame-servers { null; };
-    category cname { null; };

-

-
-
-Following are the available categories and brief descriptions of the types of log information they contain.

-

-
-
- 

-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-

-

-
-
-
-default
-

-		
-

-
-
-The catch-all. Many things still aren't classified into categories, and they all end up here. Also, if you don't specify any channels for a category, the default category is used instead. If you do not define the default category, the following definition is used:

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

-

-

-
-
-
-config
-

-		
-

-
-
-High-level configuration file processing.

-

-

-
-
-
-parser
-

-		
-

-
-
-Low-level configuration file processing.

-

-

-
-
-
-queries
-

-		
-

-
-
-A short log message is generated for every query the server receives.

-

-

-
-
-
-lame-servers
-

-		
-

-
-
-Messages like "Lame server on..."

-

-

-
-
-
-statistics
-

-		
-

-
-
-Statistics.

-

-

-
-
-
-panic
-

-		
-

-
-
-If the server has to shut itself down due to an internal problem, it will log the problem in this category as well as in the problem's native category. If you do not define the panic category, the following definition is used:

-
-category panic { default_syslog; default_stderr; };
-

-

-

-
-
-
-update
-

-		
-

-
-
-Dynamic updates.

-

-

-
-
-
-ncache
-

-		
-

-
-
-Negative caching.

-

-

-
-
-
-xfer-in
-

-		
-

-
-
-Zone transfers the server is receiving.

-

-

-
-
-
-xfer-out
-

-		
-

-
-
-Zone transfers the server is sending.

-

-

-
-
-
-db
-

-		
-

-
-
-All database operations.

-

-

-
-
-
-eventlib
-

-		
-

-
-
-Debugging info from the event system. Only one channel may be specified for this category, and it must be a file channel. If you do not define the eventlib category, the following definition is used:

-
-category eventlib{ default_debug; };
-

-

-

-
-
-
-packet
-

-		
-

-
-
-Dumps of packets received and sent. Only one channel may be specified for this category, and it must be a file channel. If you do not define the packet category, the following definition is used:

-
-category packet { default_debug; };
-

-

-

-
-
-
-notify
-

-		
-

-
-
-The NOTIFY protocol.

-

-

-
-
-
-cname
-

-		
-

-
-
-Messages like "... points to a CNAME".

-

-

-
-
-
-security
-

-		
-

-
-
-Approved/unapproved requests.

-

-

-
-
-
-os
-

-		
-

-
-
-Operating system problems.

-

-

-
-
-
-insist
-

-		
-

-
-
-Internal consistency check failures.

-

-

-
-
-
-maintenance
-

-		
-

-
-
-Periodic maintenance events.

-

-

-
-
-
-load
-

-		
-

-
-
-Zone loading messages.

-

-

-
-
-
-response-checks
-

-		
-

-
-
-Messages arising from response checking, such as "Malformed response...", "wrong ans. name...", "unrelated additional info...", "invalid RR type...", and "bad referral...".

-

-

 

 

 
    
@@ -3578,8 +3576,8 @@ view
 

 

 view "name" {
-      [allow-query address_match_list; [allow-query address_match_list; [...]]] [zone_statement; [zone_statement;[....]]
-
+      ... 
+       [zone_statement[zone_statement; [....]]
 };

 

 

@@ -3596,17 +3594,9 @@ view
 
 
 view
- statements are used to provide a different view of the same namespace to different clients, depending upon which 
-allow-query
- statement they match. A 
-view
- statement with no 
-allow-query
- statement is the default view, for any client that does not match a specific view. The 
-view
- statement should contain a list of zone definitions for each zone that needs differing answers. Zones that are specified outside the 
-view
- statement are common to all views.
+ statements are used to provide a different view of the same namespace to different clients.  
+They are not yet fully implemented.
+
 
 
 
@@ -3624,32 +3614,32 @@ zone
  Statement Grammar
 
 

-zone string [class] [{ 
-    type (master|slave|hint|stub|forward) ;
-    [ allow-query { address_match_list } ; ]
-    [ allow-transfer { address_match_list } ; ]
-    [ allow-update { 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 ; ]
-    [ recursive-clients number; ]
-    [ tcp-clients number; ]
-    [ transfer-source (ip_addr | *) ; ]
-}];

+zone  string [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 | *) ; ]}]
+;

 
 

 
    
@@ -3735,19 +3725,19 @@ forward
 
    
 
 
-A forward zone is used to direct all queries in it to other servers.
    
-
    
-
-
-The specification of options in such a zone will override any global options declared in the options statement.
    
-
    
-
-
-If no 
+A "forward zone" is a way to configure forwarding on a per-domain basis.  A 
+zone
+ statement of type 
+forward
+ can contain a 
+forward
+ and/or 
 forwarders
- statement is present in the zone or an empty list for 
+ statement, which will apply to queries within the domain given by the zone name.If no 
 forwarders
- is given, then no forwarding will be done for the zone, cancelling the effects of any forwarders in the 
+ statement is present or an empty list for 
+forwarders
+ is given, then no forwarding will be done for the domain, cancelling the effects of any forwarders in the 
 options
  statement. Thus if you want to use this type of zone to change the behavior of the global 
 forward
@@ -3767,7 +3757,7 @@ 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.
    
 
 
 
@@ -3797,7 +3787,7 @@ class is for an information service from MIT's Project Athena. It is used to sha
 hs    
  is a synonym for hesiod.
    
 
    
-
+
 
 Another MIT development was CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the 
 chaos
@@ -3806,14 +3796,14 @@ chaos
 
    
 
      
 
      
-
+
 
 5.2.20.3	Zone Options
      
 
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
@@ -4042,7 +4142,7 @@ Represents a public key for this zone. It is needed when this is the top level a
 
      
 
      
 
 
      
-
+
 
 
 allow-query
@@ -3821,7 +3811,7 @@ allow-query
 
      		
 
 
      
-
+
 
 See the description of 
 allow-query
@@ -3833,7 +3823,7 @@ Access Control
 
      
 
 
      
-
+
 
 
 allow-transfer
@@ -3841,7 +3831,7 @@ allow-transfer
 
      		
 
 
      
-
+
 
 See the description of 
 allow-transfer
@@ -3853,7 +3843,7 @@ Access Control
 
      
 
 
      
-
+
 
 
 allow-update
@@ -3861,15 +3851,47 @@ allow-update
 
      		
 
 
      
-
+
 
-Specifies which hosts are allowed to submit Dynamic DNS updates to the server. The default is to deny updates from all hosts.
      
+Specifies which hosts are allowed to submit Dynamic DNS updates for master zones. The default is to deny updates from all hosts.
      
       		
 
      
 
      
 
 
      
-
+
+
+update-policy
      
+      		
+
      
+
+
+Specifies a "Simple Secure Update" policy. See description below.
      
+
      
+
      
+
+
+
+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. 
+Update forwarding is not yet implemented.
+
      
+
      
+
      
+
 
 
 also-notify
@@ -3877,7 +3899,7 @@ also-notify
 
      		
 
 
      
-
+
 
 Only meaningful if 
 notify
@@ -3888,13 +3910,16 @@ also-notify
 .
      
 
 also-notify
- is not meaningful for stub zones. The default is the empty list.
      
+ is not meaningful for stub zones. The default is the empty list.
      
+
+Not yet implemented in BINDv9.
+
      
       		
 
      
 
      
 
 
      
-
+
 
 
 check-names
@@ -3902,17 +3927,20 @@ check-names
 
      		
 
 
      
-
+
 
 See 
 Name Checking
-.
      
+.
      
+
+Not yet implemented in BINDv9.
+
      
       		
 
      
 
      
 
 
      
-
+
 
 
 dialup
@@ -3920,19 +3948,22 @@ dialup
 
      		
 
 
      
-
+
 
 See the description of 
 dialup
  under 
 Boolean Options
-.
      
+.
      
+
+Not yet implemented in BINDv9.
+
      
       		
 
      
 
      
 
 
      
-
+
 
 
 forward
@@ -3940,19 +3971,22 @@ forward
 
      		
 
 
      
-
+
 
 Only meaningful if the zone has a forwarders list. The 
 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.
      
+ would allow a normal lookup to be tried.
      
+
+Not yet implemented in BINDv9.
+
      
       		
 
      
 
      
 
 
      
-
+
 
 
 forwarders
@@ -3960,33 +3994,39 @@ 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.
+
      
       		
 
      
 
      
 
 
      
-
+
 
 
-ixfr_base
+ixfr-base
 
      
       		
 
 
      
-
+
 
-Specifies the file name used for IXFR transaction log file.
      
+Specifies the file name for the transaction log file used for dynamic update and IXFR.
      
       		
 
      
 
      
 
 
      
-
+
 
 
 max-transfer-time-in
@@ -3994,7 +4034,7 @@ max-transfer-time-in
 
      		
 
 
      
-
+
 
 See the description of 
 max-transfer-time-in
@@ -4006,7 +4046,67 @@ Zone Transfers
 
      
 
 
      
-
+
+
+
+max-transfer-idle-in
+
      
+      		
+
      
+
+
+See the description of 
+max-transfer-idle-in
+ under 
+Zone Transfers
+.
      
+
      
+
      
+
+
+
+max-transfer-time-out
+
      
+      		
+
      
+
+
+See the description of 
+max-transfer-time-outn
+ under 
+Zone Transfers
+.
      
+
      
+
      
+
+
+
+max-transfer-idle-out
+
      
+      		
+
      
+
+
+See the description of 
+max-transfer-idle-out
+ under 
+Zone Transfers
+.
      
+
      
+
      
+
 
 
 notify
@@ -4014,7 +4114,7 @@ notify
 
      		
 
 
      
-
+
 
 See the description of 
 notify
@@ -4026,7 +4126,7 @@ Boolean Options
 
      
 
 
      
-
+
 
 
 pubkey
@@ -4034,7 +4134,7 @@ 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.
      
 
      
 
 
      
-
+
 
 
 transfer-source
@@ -4050,7 +4150,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 
 closest to
@@ -4062,26 +4162,178 @@ allow-transfer
 
      
 
    
 
    
+
    
+
      
+
      
+
+
+5.2.20.4	Dynamic Update Policies
      
+
    
+
    
+
+
+BINDv9 supports two alternative methods of granting clients the right to perform dynamic updates to a zone, configured by the 
+allow-update
+ and 
+update-policy
+ option, respectively.
    
+
    
+
+
+The 
+allow-update
+ clause works the same way as in previous versions of BIND. It grants given clients the permission to update any record of any name in the zone.
    
+
    
+
+
+The 
+update-policy
+ clause is new in BINDv9 and allows more fine-grained control over what updates are allowed. A set of rules is specified, where each rule either grants or denies permissions for one or more names to be updated by one or more identities.  If the dynamic update request message is signed (that is, it includes either a TSIG or SIG(0) record), the identity of the signer can be determined.
    
+
    
+
+
+Rules are specified in the 
+update-policy
+ zone option, and are only meaninful for master zones.  When the 
+update-policy
+ statement is present, it is a configuration error for the 
+allow-update
+ statement to be present.  The 
+update-policy
+ statement only examines the signer of a message; the source address is not relevant.
    
+
    
+
+
+A rule defition looks like:
    
+
    
+
+
+(
+ 
+
+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.
    
+
    
+
+
+The identity field specifies a name or a wildcard name.  The nametype field has 4 values: 
+name
+, 
+subdomain
+, 
+wildcard
+, and 
+self
+. 
    
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
    
+
    
+
+
+name
    
+    		
+
    
+
+
+Matches when the updated name is the same as the name in the name field.
    
+
    
+
    
+
+
+subdomain
    
+    		
+
    
+
+
+Matches when the updated name is a subdomain of the name in the name field.
    
+
    
+
    
+
+
+wildcard
    
+    		
+
    
+
+
+Matches when the updated name is a valid expansion of the wildcard name in the name field.
    
+
    
+
    
+
+
+self
    
+    		
+
    
+
+
+Matches when the updated name is the same as the message signer. The name field is ignored.
    
+
    
+
    
+
+
+If no types are specified, the rule matches all types except SIG, NS, SOA, and NXT. Types may be specified by name, including "any" (which matches all types except NXT, which can never be updated).
    
+
    
 

 
 

 
    
 
    
-
+
 
-5.3	The Zone File
    
+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.

 

@@ -5135,7 +5387,9 @@ $ORIGIN      2.1.10.in-addr.arpa
 

 
 
-(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.)

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

 

 

 
    
@@ -5231,7 +5485,7 @@ $ORIGIN
 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 
+ 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.
    
 

@@ -5259,7 +5513,7 @@ Set the default Time To Live (TTL) for subsequent records with undefined TTLs. V
 
 
 $TTL
- is defined in RFC 2308.

+ is defined in RFC 2308.

 

 

 

@@ -5268,7 +5522,7 @@ $TTL
 
 
 5.3.6	BIND Master File Extension: the  
-$generate
+$GENERATE
  Directive
 
 

@@ -5389,22 +5643,32 @@ 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. 
+It is not yet implemented in BINDv9.
+

 

 

 
    
 
    
 
 
-5.3.7	Discussion of Nameserver Signals
    
+5.3.7	Signals
 

 

 
 
-The BIND nameserver, named, is controlled by means of signals. The following table describes signals that BIND sends and their effects when sent to the server process using the kill command.

-

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

+

+
 
- 

+  

 
@@ -5441,16 +5701,40 @@ SIGTERM

 
 
-Dumps the primary and secondary database files. Used to save modified data on shutdown if the server is compiled with dynamic updating enabled.

+Causes the server to clean up and exit.

+
+
+
+
+
+
+
+
+

 

 
@@ -5421,11 +5685,7 @@ SIGHUP
 
 Causes the server to read 
 named.conf
- and reload the database. If the server is built with the 
-FORCED_RELOAD
- compile-time option, then 
-SIGHUP
- will also cause the server to check the serial number on all secondary zones. Normally the serial numbers are only checked at the SOA-specified intervals.

+ and reload the database. 

 		
 

 

 

+

+
+
+SIGINT

+		
+

+
+
+Causes the server to clean up and exit.

+

+

+
+
+SIGQUIT

+		
+

+
+
+Causes the server to clean up and exit.

 		
 

 

-

-
-
-  

-
Return to BINDv9 Administrator Reference Manual table of contents.

 

 
+
Return to BINDv9 Administrator Reference Manual table of contents.

 
 
diff --git a/doc/arm/BV9ARM.6.html b/doc/arm/BV9ARM.6.html
index 15cbbd2367..1e0348a35b 100644
--- a/doc/arm/BV9ARM.6.html
+++ b/doc/arm/BV9ARM.6.html
@@ -8,56 +8,58 @@
 
    
 
    
 
- 
+
 Section 6.	Security Considerations
    
 

 

 
    
 
    
 
- 
+
 6.1	
- 
+
 Access Control Lists
    
 

 

 
- 
+
 Access Control Lists (ACLs), are address match lists that you can set up and nickname for future use in 
 allow-query
 , 
 allow-recursion
 , 
-blackhole allow-transfer
+blackhole
+, 
+allow-transfer
 , etc.

 

 
- 
+
 Using ACLs allows you to have finer control over who can access your nameserver, without cluttering up your config files with huge lists of IP addresses.

 

 
- 
+
 It is a 
 good idea
  to use ACLs, and to control access to your server. Limiting access to your server by outside parties can help prevent spoofing and DoS attacks against your server.

 

 
- 
+
 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; };

 

 
- 
+
 // 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 {
   ...
   ...
@@ -67,7 +69,7 @@ options {
   blackhole { bogusnets; };
   ...
 };

-
 
+

 zone "example.com" {
   type master;
   file "m/example.com";
@@ -75,11 +77,11 @@ zone "example.com" {
 };

 

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

@@ -91,16 +93,16 @@ ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos
 
    
 
    
 
- 
+
 6.2	
 chroot
  and 
-set_uid
+setuid
  (for UNIX servers)
    
 

 

 
- 
+
 On UNIX servers, it is possible to run BIND in a 
 chrooted
  environment (
@@ -110,13 +112,15 @@ chroot()
 " 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 <user> ) and in a nonprivileged group ( -g <group> ). We suggest running as a nonpriveleged user when using the 
+
+Another useful feature in the UNIX version of BIND is the ability to run the daemon as a nonprivileged user ( 
+-u
+ <user> ). We suggest running as a nonprivileged user when using the 
 chroot
  feature.

 

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

@@ -125,34 +129,36 @@ chroot()
 , and to run 
 named
  
-set_uid
- and 
-set_gid
- it to user 202 and group 202:

-
 
-/usr/local/bin/named -u 202 -g 202 -t /var/named

+setuid
+ to user 202:

+

+/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. 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 is the root of the filesystem. You will need 
-/dev/null
+ environment to work properly in a particular directory (e.g. 
+/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
+ is the root of the filesystem. You will need 
+/dev/null
 , and any library directories and files that BIND needs to run on your system.  Please consult your operating system's instructions if you need help figuring out which library files you need to copy over to the 
 chroot()
  sandbox.

 

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

@@ -161,16 +167,14 @@ chroot()
 
    
 
    
 
- 
+
 6.2.2	Using 
-set_uid
-/
-set_gid
+setuid
 
    
 

 

 
- 
+
 Prior to running the 
 named
  daemon, use the 
@@ -184,30 +188,18 @@ chown
 
    
 
    
 
- 
+
 6.3	Dynamic updates
    
 

 

 
- 
-Since dynamic updates do not have per-RR security, access to the dynamic update facility should be strictly limited. The traditional way to do this has been host-based, but BINDv9 allows tranaction signature (TSIG) signed updates to cryptographically verify the 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.

 

-
- 
-
- (Note: The syntax for this not finalized.)
-

-

-
- 
-See also 
-Incremental Transfer (IXFR)
-.

-

-
- 
- 

-
Return to BINDv9 Administrator Reference Manual table of contents.

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

 

+
Return to BINDv9 Administrator Reference Manual table of contents.

 
 
diff --git a/doc/arm/BV9ARM.7.html b/doc/arm/BV9ARM.7.html
index b6478982ec..322ee56001 100644
--- a/doc/arm/BV9ARM.7.html
+++ b/doc/arm/BV9ARM.7.html
@@ -8,150 +8,150 @@
 
    
 
    
 
- 
+
 Section 7.	Troubleshooting
    
 

 

 
    
 
    
 
- 
+
 7.1	Common Log Messages and What They Mean
    
 

 

 
    
 
    
 
- 
+
 lame server
    
 

-
 
+

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

 

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

 

 
- 
+
 If this is a zone under your control, check each of the nameservers to ensure that they are configured to answer questions properly.

 

 
- 
+
 If it's a zone out on the Internet, it would be nice to notify the owners of the domain in question so that they can take a look at it. In practice, though, not many people have time to do this.

 

 

 
    
 
    
 
- 
+
 bad referral
    
 

-
 
+

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

 

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

 

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

 

 

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

 

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

 

 

 
    
 
    
 
- 
+
 rejected zone
    
 

-
 
+

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

 

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

 

 

 
    
 
    
 
- 
+
 no NS RRs found
    
 

-
 
+

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

 

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

 

 

 
    
 
    
 
- 
+
 no default TTL set
    
 

-
 
+

 ns named[111]: Zone "foo.com" (file foo.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 section 3.2.3, "Setting TTLs" in this document, for information on how to use $TTL.

 

 

 
    
 
    
 
- 
+
 no root nameserver for class
    
 

-
 
+

 findns: No root nameservers for class IN?

 

 
- 
+
 Your nameserver is having problems finding the root nameservers. Check your root hints file to make sure it is not corrupted. Also, make sure that your nameserver can reach the Internet.

 

 
- 
+
 If you are running an internal root nameserver, make sure it's configured properly and is answering queries.

 

 

 
    
 
    
 
- 
+
 address already in use
    
 

-
 
+

 ctl_server: bind: Address already in use

 

 
- 
+
 This usually indicates that another copy of BIND is already running. Verify that you have killed old copies of the daemon.

 

 
- 
+
 This can also pop up if you originally ran named as "root" and now run it as a regular user. named may have left behind an ndc control socket that is owned by root if it crashed, or was not killed gracefully.

 

 
- 
+
 This means that the regular user wouldn't be able to delete it, so it would think named is still running. The solution is to remove any ndc sockets in /usr/local/etc, or /var/run, etc.

 

 

@@ -159,20 +159,20 @@ This means that the regular user wouldn't be able to delete it, so it would thin
 
    
 
    
 
- 
+
 7.2	Common Problems
    
 

 

 
    
 
    
 
- 
+
 7.2.1	It's not working; how can I figure out what's wrong?
    
 

 

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

 

@@ -181,47 +181,49 @@ Sample Configuration and Logging
 
    
 
    
 
- 
+
 7.3	Incrementing and Changing the Serial Number
    
 

 

-
- 
-Zone serial numbers are just numbers--they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. A number of people have been testing these numbers for Y2K compliance and have set the number to the year 2000 to see if it will work. They then try to restore the old serial number. This will cause problems with BIND, because serial numbers are used to indicate that a zone has been updated. If the serial number on the secondary server is lower than the serial number on the primary, the secondary server will attempt to update its copy of the zone.

+
+
+Zone serial numbers are just numbers--they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. A number of people have been testing these numbers for Y2K compliance and have set the number to the year 2000 to see if it will work. They then try to restore the old serial number. This will cause problems, because serial numbers are used to indicate that a zone has been updated. If the serial number on the secondary server is lower than the serial number on the primary, the secondary server will attempt to update its copy of the zone.

 

 
- 
+
 Setting the serial number to a lower number on the primary server than the secondary server means that the secondary will not perform updates to its copy of the zone.

 

 
- 
+
 The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all secondaries have updated to the new zone serial number, then reset the number to what you want it to be, and reload the zone again.

 

 

 
    
 
    
 
- 
+
 7.4	Where Can I Get Help?
    
 

 

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

 

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

-
-http://www.isc.org/services/support/
+info@isc.org
+or visit the ISC web page at 
+the ISC web site
  to read more.

 

 
- 
+
  

-
Return to BINDv9 Administrator Reference Manual table of contents.

+
+

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

 
 
 
diff --git a/doc/arm/BV9ARM.8.html b/doc/arm/BV9ARM.8.html
index fdf2e192fc..e6fc8cdfe9 100644
--- a/doc/arm/BV9ARM.8.html
+++ b/doc/arm/BV9ARM.8.html
@@ -3,120 +3,120 @@
 
 
 
- Section 7.	Troubleshooting
+ Appendices
 
 
    
 
    
-
- 
+
+
 Appendices
    
 

 
 

 

 
- 
+
 Appendix A. Acknowledgements

 

 

 
- 
+
 A Brief History of the DNS and BIND

 

 
- 
+
 Although the "official" beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and 883. From 1984 to 1987, the ARPAnet (the precursor to today's Internet) became a testbed of experimentation for developing the new naming/addressing scheme in an rapidly expanding, operational network environment. New RFCs were written and published in 1987 that modified the original documents to incorporate improvements based on the working model. RFC 1034, "Domain Names-Concepts and Facilities," and RFC 1035, "Domain Names-Implementation and Specification" were published and became the standards upon which all DNS implementations are built.

 

 
- 
+
 The first working domain name server, called "Jeeves," was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 machines located at the University of Southern California's Information Sciences Institute (USC-ISI) and SRI International's Network Information Center (SRI-NIC). A DNS server for Unix machines, the Berkeley Internet Name Domain (BIND) package, was written soon after by a group of graduate students at the University of California at Berkeley under a grant from the US Defense Advanced Research Projects Administration (DARPA). Versions of BIND through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark Painter, David Riggle and Songnian Zhou made up the initial BIND project team. After that, additional work on the software package was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation employee on loan to the CSRG, worked on BIND for 2 years, from 1985 to 1987. Many other people also contributed to BIND development during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently handled by Mike Karels and O. Kure.

 

 
- 
+
 BIND versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then a DEC employee, became BIND's primary caretaker. Paul was assisted by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.

 

 
- 
+
 BIND Version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became BIND's principal architect/programmer.

 

 
- 
+
 BIND versions from 4.9.3 onward have been developed and maintained by the Internet Software Consortium with support being provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of BIND version 8 in May 1997.

 

 
- 
-
-BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.
+
+BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.
 

 

 

 

 

 
- 
+
 
- 
+
 Appendix B. Historical DNS Information

 

 

 
- 
+
 Classes of resource records

 

 

 
- 
+
 HS = hesiod

 

 

 

 
- 
+
 CH = chaos

 

 

+
Return to BINDv9 Administrator Reference Manual table of contents.

 

 

 

 
- 
+
 Appendix C. Bibliography (and Suggested Reading)

 

 

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

 
 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/
+ http://www.ietf.org/rfc/
 .

 

 

 
- 
+
 Standards

 

 
- 
+
 RFC974. Partridge, C. 
 Mail Routing and the Domain System
 . January 1986. (Standard 

 

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

 

 
- 
+
 RFC1035.  Mockapetris, P. V. 
 Domain Names - Implementation and Specification
 . November 1987.

@@ -124,35 +124,35 @@ Domain Names - Implementation and Specification
 

 

 
- 
+
 Proposed Standards

 

 
- 
+
 RFC2181. Elz, R., R. Bush. 
 Clarifications to the DNS Specification
 . July 1997.

 

 
- 
+
 RFC2308. Andrews, M. 
 Negative Caching of DNS Queries
 . March 1998.

 

 
- 
+
 RFC1995. Ohta, M. 
 Incremental Zone Transfer in DNS
 . August 1996.

 

 
- 
+
 RFC1996. Vixie, P. 
 A Mechanism for Prompt Notification of Zone Changes
 . August 1996.

 

 
- 
+
 RFC2136. Vixie, P., S. Thomson, Y. Rekhter, J. Bound. 
 Dynamic Updates in the Domain Name System
 . April 1997.

@@ -160,11 +160,11 @@ Dynamic Updates in the Domain Name System
 

 

 
- 
+
 Proposed Standards Still Under Development

 

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

 

 
- 
+
 RFC1886. Thomson, S., C. Huitema. 
 DNS Extensions to support IP version 6
 . S. December 1995.

 

 
- 
+
 RFC2065. Eastlake, 3rd, D., C. Kaufman. 
 Domain Name System Security Extensions
 . January 1997.

 

 
- 
+
 RFC2137. Eastlake, 3rd,  D. 
 Secure Domain Name System Dynamic Update
 . April 1997.

@@ -192,23 +192,23 @@ Secure Domain Name System Dynamic Update
 

 

 
- 
+
 Other Important RFCs About DNS Implementation

 

 
- 
+
 RFC1535. Gavron, E. 
 A Security Problem and Proposed Correction With Widely Deployed DNS Software.
  October 1993.

 

 
- 
+
 RFC1536. Kumar, A., J. Postel, C. Neuman, P. Danzig, S. Miller. 
 Common DNS Implementation Errors and Suggested Fixes
 . October 1993.

 

 
- 
+
 RFC1982. Elz, R., R. Bush. 
 Serial Number Arithmetic
 . August 1996.

@@ -216,41 +216,41 @@ Serial Number Arithmetic
 

 

 
- 
+
 Resource Record Types

 

 
- 
+
 RFC1183. Everhart, C.F., L. A. Mamakos, R. Ullmann, P. Mockapetris.  
 New DNS RR Definitions
 . October 1990.

 

 
- 
+
 RFC1706. Manning, B., R. Colella. 
 DNS NSAP Resource Records
 . October 1994.

 

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

 

 
- 
+
 RFC1876. Davis, C., P. Vixie, T. Goodwin, I. Dickinson. 
 A Means for Expressing Location Information in the Domain Name System
 . January 1996.

 

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

 

 
- 
+
 
 RFC2163. Allocchio, A. U
 
@@ -262,7 +262,7 @@ January 1998.
 

 

 
- 
+
 RFC2230. Atkinson, R. 
 Key Exchange Delegation Record for the DNS
 .  October 1997.

@@ -270,29 +270,29 @@ Key Exchange Delegation Record for the DNS
 

 

 
- 
+
 DNS and the Internet

 

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

 

 
- 
+
 RFC1123.  Braden, R. 
 Requirements for Internet Hosts - Application and Support
 . October 1989.

 

 
- 
+
 RFC1591. Postel, J. D
 omain Name System Structure and Delegation
 . March 1994.

 

 
- 
+
 RFC2317. Eidnes, H., G. de Groot, P. Vixie. 
 Classless IN-ADDR.ARPA Delegation
 . March 1998.

@@ -300,29 +300,29 @@ Classless IN-ADDR.ARPA Delegation
 

 

 
- 
+
 DNS Operations

 

 
- 
+
 RFC1537. Beertema, P. 
 Common DNS Data File Configuration Errors
 . October 1993.

 

 
- 
+
 RFC1912. Barr, D. 
 Common DNS Operational and Configuration Errors
 . February 1996.

 

 
- 
+
 RFC2182. Elz, R. R. Bush, S. Bradner, M. Patton. 
 Selection and Operation of Secondary DNS Servers
 . July 1997.

 

 
- 
+
 RFC2219. Hamilton, M., R. Wright. 
 Use of DNS Aliases for Network Services.
  October 1997.

@@ -330,47 +330,47 @@ Use of DNS Aliases for Network Services.
 

 

 
- 
+
 Other DNS-related RFCs

 

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

 

 
- 
+
 RFC1464. Rosenbaum, R. 
 Using the Domain Name System To Store Arbitrary String Attributes
 . May 1993.

 

 
- 
+
 RFC1713. Romao, A. 
 Tools for DNS Debugging
 . November 1994.

 

 
- 
+
 RFC1794. Brisco, T. 
 DNS Support for Load Balancing
 . April 1995.

 

 
- 
+
 RFC2240. Vaughan, O. 
 A Legal Basis for Domain Name Allocation
 . November1997.

 

 
- 
+
 RFC2345. Klensin, J., T. Wolf, G. Oglesby. 
 Domain Names and Company Name Retrieval
 . May 1998.

 

 
- 
+
 RFC2352. Vaughan, O. 
 A Convention For Using Legal Names as Domain Names
 . May 1998.

@@ -378,11 +378,11 @@ A Convention For Using Legal Names as Domain Names
 

 

 
- 
+
 Obsolete and Unimplemented Experimental RRs

 

 
- 
+
 RFC1712. Farrell, C., M. Schulze, S. Pleitner, D. Baldoni. 
 DNS Encoding of Geographical Location
 . November 1994.

@@ -391,36 +391,25 @@ DNS Encoding of Geographical Location
 

 

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

@@ -459,17 +448,17 @@ draft-skwan-utf8-dns-02.txt
 

 

 
- 
+
 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). 
 TSIG guide for BIND 8.2+
 . E-mail to private mailing list (private communication). 22 April 1999.

@@ -477,16 +466,16 @@ TSIG guide for BIND 8.2+
 

 

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

+
Return to BINDv9 Administrator Reference Manual table of contents.

 

 

 
diff --git a/doc/arm/BV9ARM.PDF b/doc/arm/BV9ARM.PDF
index 4d9c56ebfa..0974407ef8 100644
Binary files a/doc/arm/BV9ARM.PDF and b/doc/arm/BV9ARM.PDF differ
diff --git a/doc/arm/BV9ARM.css b/doc/arm/BV9ARM.css
new file mode 100644
index 0000000000..0b2bed3931
--- /dev/null
+++ b/doc/arm/BV9ARM.css
@@ -0,0 +1,1460 @@
+A:link {
+	color: blue;
+	text-decoration: underline;
+}
+A:visited {
+	color: purple;
+	text-decoration: underline;
+}
+A:active {
+	color: red;
+	text-decoration: underline;
+}
+H1.1Level, H2.1Level, H3.1Level, H4.1Level, H5.1Level, H6.1Level {
+	text-align: left;
+	text-indent: -36.000000pt;
+	margin-top: 28.000000pt;
+	margin-bottom: 14.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 36.000000pt;
+	font-size: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.1LevelContinued {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 6.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 36.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;
+}
+THROW AWAY.1LevelTOC {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 14.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 12.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+H1.2Level, H2.2Level, H3.2Level, H4.2Level, H5.2Level, H6.2Level {
+	text-align: left;
+	text-indent: -27.000000pt;
+	margin-top: 14.000000pt;
+	margin-bottom: 14.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 63.000000pt;
+	font-size: 12.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+LI.2Level-bullet1 {
+	text-align: left;
+	text-indent: -9.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 81.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;
+}
+LI.2Level-bullet2 {
+	text-align: left;
+	text-indent: -9.000000pt;
+	margin-top: 6.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 81.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.2Level-fixed {
+	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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ff00ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+LI.2Level-numList1 {
+	text-align: left;
+	text-indent: -18.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 81.000000pt;
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+LI.2Level-numList2 {
+	text-align: left;
+	text-indent: -36.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 99.000000pt;
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.2LevelContinued {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 63.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.2LevelContinued1 {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 63.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.2LevelContinued2 {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 63.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.2LevelTOC {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+H1.3Level, H2.3Level, H3.3Level, H4.3Level, H5.3Level, H6.3Level {
+	text-align: left;
+	text-indent: -36.000000pt;
+	margin-top: 14.000000pt;
+	margin-bottom: 14.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 99.000000pt;
+	font-size: 12.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+PRE.3Level-fixed {
+	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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+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: 10.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #ff00ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.3LevelContinued {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 1.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 99.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.3LevelContinued1 {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 99.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;
+}
+P.3LevelContinued2 {
+	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: 10.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #ff00ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier New;
+}
+THROW AWAY.3LevelTOC {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+H1.4Level, H2.4Level, H3.4Level, H4.4Level, H5.4Level, H6.4Level {
+	text-align: left;
+	text-indent: -45.000000pt;
+	margin-top: 12.000000pt;
+	margin-bottom: 12.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 144.000000pt;
+	font-size: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+LI.4Level-bullet1 {
+	text-align: left;
+	text-indent: 72.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 81.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;
+}
+LI.4Level-bullet2 {
+	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: 3.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: Helvetica;
+}
+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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+PRE.4Level-fixedSmall {
+	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: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.4LevelContinued {
+	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: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+THROW AWAY.4LevelTOC {
+	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: medium;
+	font-style: Regular;
+	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;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 12.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+H1.AppendixLevel1, H2.AppendixLevel1, H3.AppendixLevel1, H4.AppendixLevel1, H5.AppendixLevel1, H6.AppendixLevel1 {
+	text-align: left;
+	text-indent: -36.000000pt;
+	margin-top: 14.000000pt;
+	margin-bottom: 4.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 36.000000pt;
+	font-size: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+THROW AWAY.AppendixLevel1TOC {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 14.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 12.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+H1.AppendixLevel2, H2.AppendixLevel2, H3.AppendixLevel2, H4.AppendixLevel2, H5.AppendixLevel2, H6.AppendixLevel2 {
+	text-align: left;
+	text-indent: -27.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 63.000000pt;
+	font-size: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+THROW AWAY.AppendixLevel2TOC {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+H1.AppendixLevel3, H2.AppendixLevel3, H3.AppendixLevel3, H4.AppendixLevel3, H5.AppendixLevel3, H6.AppendixLevel3 {
+	text-align: left;
+	text-indent: -36.000000pt;
+	margin-top: 13.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 99.000000pt;
+	font-size: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+THROW AWAY.AppendixLevel3TOC {
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	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.Bib3 {
+	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.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;
+}
+P.Body {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.Body1 {
+	text-align: left;
+	text-indent: 0.000000pt;
+	margin-top: 6.000000pt;
+	margin-bottom: 6.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 10.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody {
+	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: 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.CellBody-fixedfont {
+	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: Medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody-fixedfontLG {
+	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: Medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody-fixedfontLG1 {
+	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: Medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody1 {
+	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: 11.000000pt;
+	font-weight: medium;
+	font-style: Italic;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.CellBody11 {
+	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: 11.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.CellBody2 {
+	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: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+H1.CellBody21, H2.CellBody21, H3.CellBody21, H4.CellBody21, H5.CellBody21, H6.CellBody21 {
+	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: 11.000000pt;
+	font-weight: Medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody3 {
+	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: 11.000000pt;
+	font-weight: medium;
+	font-style: Oblique;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody4 {
+	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: 11.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.CellBody5 {
+	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: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.CellBody6 {
+	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: medium;
+	font-style: Oblique;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.comment {
+	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: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+P.Comment {
+	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: medium;
+	font-style: Regular;
+	color: #ff00ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+THROW AWAY.Footer {
+	text-align: justify;
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+THROW AWAY.Footer1 {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+THROW AWAY.Header {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+H1.Header1, H2.Header1, H3.Header1, H4.Header1, H5.Header1, H6.Header1 {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.Mapping-Table-Cell {
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.Mapping-Table-Cell1 {
+	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: 18.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.Mapping-Table-Cell10 {
+	text-align: justify;
+	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-Cell11 {
+	text-align: justify;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+P.Mapping-Table-Cell12 {
+	text-align: justify;
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+P.Mapping-Table-Cell13 {
+	text-align: justify;
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+P.Mapping-Table-Cell14 {
+	text-align: justify;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+P.Mapping-Table-Cell15 {
+	text-align: justify;
+	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: Times New Roman;
+}
+P.Mapping-Table-Cell16 {
+	text-align: justify;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 18.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+P.Mapping-Table-Cell2 {
+	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: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+P.Mapping-Table-Cell3 {
+	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: Times;
+}
+P.Mapping-Table-Cell31 {
+	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: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.Mapping-Table-Cell32 {
+	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: 11.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.Mapping-Table-Cell33 {
+	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: medium;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+P.Mapping-Table-Cell4 {
+	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: Courier;
+}
+P.Mapping-Table-Cell5 {
+	text-align: justify;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 14.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+P.Mapping-Table-Cell6 {
+	text-align: justify;
+	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-Cell7 {
+	text-align: justify;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times New Roman;
+}
+P.Mapping-Table-Cell8 {
+	text-align: justify;
+	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: Italic;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+P.Mapping-Table-Cell9 {
+	text-align: justify;
+	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: Courier;
+}
+P.Mapping-Table-Title {
+	text-align: justify;
+	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: medium;
+	font-style: Regular;
+	color: #ffffff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+H1.Subhead2, H2.Subhead2, H3.Subhead2, H4.Subhead2, H5.Subhead2, H6.Subhead2 {
+	text-align: left;
+	text-indent: 63.000000pt;
+	margin-top: 12.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 10.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+LI.Subhead2-noBullet {
+	text-align: left;
+	text-indent: -55.799988pt;
+	margin-top: 12.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 118.799988pt;
+	font-size: 10.000000pt;
+	font-weight: medium;
+	font-style: Regular;
+	color: #0000ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+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: 12.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title {
+	text-align: center;
+	text-indent: 0.000000pt;
+	margin-top: 0.000000pt;
+	margin-bottom: 0.000000pt;
+	margin-right: 0.000000pt;
+	margin-left: 0.000000pt;
+	font-size: 18.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Arial;
+}
+EM.CharFmt {
+	text-decoration: underline ;
+}
+EM.CharFmt1 {
+	font-family: Courier;
+}
+EM.Command {
+	font-size: 7.000000pt;
+	font-family: Courier;
+}
+EM.Comment {
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Italic;
+	color: #ff00ff;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Times;
+}
+EM.Comment21 {
+	font-size: 10.000000pt;
+	font-style: Italic;
+	color: #ff00ff;
+	font-family: Arial;
+}
+EM.doc-title {
+	font-style: Italic;
+}
+EM.doc-title1 {
+	font-style: Italic;
+	font-family: Times New Roman;
+}
+EM.Emphasis {
+	font-style: Italic;
+}
+EM.grammar_literal {
+	font-size: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Courier;
+}
+KBD.Literal-user-input {
+}
+EM.Optional-meta-syntax {
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Italic;
+}
+EM.pathname {
+	font-size: 10.000000pt;
+	font-style: Italic;
+}
+EM.production_target {
+	font-size: 10.000000pt;
+	font-weight: Bold;
+	font-style: Regular;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
+CODE.Program-Process {
+	font-size: 12.000000pt;
+	font-weight: Bold;
+	font-family: Courier;
+}
+EM.URL {
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Italic;
+	font-family: Times New Roman;
+}
+EM.variable {
+	font-size: 11.000000pt;
+	font-weight: medium;
+	font-style: Oblique;
+	color: #000000;
+	text-decoration: none;
+	vertical-align: baseline;
+	text-transform: none;
+	font-family: Helvetica;
+}
diff --git a/doc/arm/BV9ARM.HTML b/doc/arm/BV9ARM.html
similarity index 70%
rename from doc/arm/BV9ARM.HTML
rename to doc/arm/BV9ARM.html
index 25eb108702..c16274a72b 100644
--- a/doc/arm/BV9ARM.HTML
+++ b/doc/arm/BV9ARM.html
@@ -13,48 +13,48 @@
 

 
BIND version 9
Administrator Reference Manual

 
DRAFT
-

-
February 1, 2000
-

+

+March 19, 2000
 

 
+

 

-
Warning! this draft document is the property of the Internet Software Consortium (ISC) and contains proprietary ISC information. It is being distributed for review purposes ONLY. The information in this document is subject to change. Do not redistribute!

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

 

-
+

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