diff --git a/doc/arm/BV9ARM.PDF b/doc/arm/BV9ARM.PDF deleted file mode 100644 index 0974407ef8..0000000000 Binary files a/doc/arm/BV9ARM.PDF and /dev/null differ diff --git a/doc/arm/BV9ARM.1.html b/doc/arm/Bv9ARM.1.html similarity index 72% rename from doc/arm/BV9ARM.1.html rename to doc/arm/Bv9ARM.1.html index 24e5fe4fd6..6c39ad2c6b 100644 --- a/doc/arm/BV9ARM.1.html +++ b/doc/arm/Bv9ARM.1.html @@ -2,7 +2,7 @@ - + Section 1. Introduction
    @@ -34,30 +34,30 @@ The Berkeley Internet Name Domain (BIND) implements an Internet nameserver for a 1.2 Organization of This Document
-

+

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

@@ -71,20 +71,24 @@ Bibliography

-In this document, the following general typographic conventions are used:

+In this document, we use the following general typographic conventions:

@@ -92,30 +96,14 @@ Style Used:

-A pathname, filename, URL, hostname, or mailing list name

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

- - - - @@ -124,13 +112,14 @@ Times Italic

-Literal user input

+literal user input

@@ -139,14 +128,14 @@ Courier Bold

-Variable user input

+variable user input

@@ -155,14 +144,14 @@ Courier Italic

-Program output

+program output

@@ -174,16 +163,20 @@ The following conventions are used in descriptions of the BIND configuration fil
-

+

-When describing:

+ +To describe: +

 -

+

-Style Used:

+ +Style: +
-

+

- -Times Italic -

-
-

- - -A new term or concept

-		 -

- - - -Times Italic + +Italic

-

+

-Courier Bold + +Fixed Width Bold

-

- +

+ - -Courier Italic + +Fixed Width Italic

- -Courier Plain + +Fixed Width

@@ -194,11 +187,11 @@ Style Used:

keywords

@@ -210,12 +203,12 @@ Arial Bold variables

@@ -226,11 +219,11 @@ Arial Italic "meta-syntactic" information (within brackets when optional)

@@ -242,11 +235,11 @@ Courier Italic Command line input

@@ -261,8 +254,8 @@ Program output

- -Courier Plain + +Fixed Width

@@ -277,7 +270,7 @@ Optional input

-Text is enclosed in square brackets

+Text is enclosed in square brackets

-

+

-When describing:

+ +When describing: +

 -

+

-Style Used:

+ +Style Used: +
-

+

- -Arial Bold + +Sans Serif Bold

-

+

- -Arial Italic -

+ +Sans Serif Italic +
-

+

- -Courier Italic + +Fixed Width Italic

-

+

-Courier Bold +Fixed Width Bold

@@ -292,15 +285,15 @@ Text is enclosed in square brackets

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

@@ -313,49 +306,49 @@ resolver

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

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

- + ourhost.example.com

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

The specifications for the domain nameserver are defined in RFC1034, RFC1035 and RFC974. These documents can be found in
- + /usr/src/etc/named/doc in 4.4BSD or are available via FTP from
- + ftp://www.isi.edu/in-notes/ - or via the Web at + or via the Web at http://www.ietf.org/rfc/ -. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related +. (See Appendix C for complete information on finding and retrieving RFCs.) It is also recommended that you read the related man pages: named @@ -377,31 +370,31 @@ As we stated previously, a zone is a point of delegation in the DNS tree. A zone

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

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

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

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

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

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

    @@ -457,11 +450,11 @@ Adding a zone as a type master or type slave will tell the server to answer ques

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

    @@ -478,9 +471,9 @@ All servers keep data in their cache until the data expires, based on a TTL (Tim

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

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

    @@ -492,9 +485,9 @@ primary master

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

@@ -508,7 +501,7 @@ secondary server

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

@@ -522,11 +515,11 @@ caching only servers

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

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

@@ -539,30 +532,13 @@ 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 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.

-

- + - 

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

-

Return to BINDv9 Administrator Reference Manual table of contents.

+

Return to BINDv9 Administrator Reference Manual diff --git a/doc/arm/BV9ARM.2.html b/doc/arm/Bv9ARM.2.html similarity index 79% rename from doc/arm/BV9ARM.2.html rename to doc/arm/Bv9ARM.2.html index 748670f4a2..6e9f6a566e 100644 --- a/doc/arm/BV9ARM.2.html +++ b/doc/arm/Bv9ARM.2.html @@ -2,99 +2,90 @@ - + Section 2. BIND Resource Requirements

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

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

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

-

-
-
- 

+

+
+ 
+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 diff --git a/doc/arm/BV9ARM.3.html b/doc/arm/Bv9ARM.3.html similarity index 58% rename from doc/arm/BV9ARM.3.html rename to doc/arm/Bv9ARM.3.html index 90e0206c11..ae29cd873a 100644 --- a/doc/arm/BV9ARM.3.html +++ b/doc/arm/Bv9ARM.3.html @@ -2,271 +2,259 @@ - + Section 3. Nameserver Configuration

    - + Section 3. Nameserver Configuration

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

    - + 3.1 - + Sample Configuration and Logging

-

-logging {
-       channel named_log {
-           file "logs/named.log";
-           print-time yes;
-           print-category yes;
-           print-severity yes;
-           severity info;
+

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

-

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

-

-zone "0.0.127.IN-ADDR.ARPA" {

-

-        type master; file "local/localhost.db"; notify no;
-                                          // localhost
-};

-

- 

-

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

-

- 

-

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

    - + 3.2 Load Balancing and Round Robin

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

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

-

+
 
  

 

 

 
-

+

 
-
+ 
 Name

 		
 
-

+

 
-
+ 
 TTL

 		
 
-

+

 
-
+ 
 CLASS

 		
 
-

+

 
-
+ 
 TYPE

 		
 
-

+

 
-
+ 
 Resource Record (RR) Data

 		
 

 

 
-

+

 
-
-
-www
-

+ 
+www

 		
 
-

+

 
-
+ 
 10m

 		
 
-

+

 
-
-
-IN
-

+ 
+IN

 		
 
-

+

 
-
+ 
 A

 		
 
-

+

 
-
+ 
 10.0.0.1

 		
 

 

 
-

+

 
-
+ 
  

 		
 
-

+

 
-
+ 
 10m

 		
 
-

+

 
-
-
-IN
-

+ 
+IN

 		
 
-

+

 
-
+ 
 A

 		
 
-

+

 
-
+ 
 10.0.0.2

 		
 

 

 
-

+

 
-
+ 
  

 		
 
-

+

 
-
+ 
 10m

 		
 
-

+

 
-
-
-IN
-

+ 
+IN

 		
 
-

+

 
-
+ 
 A

 		
 
-

+

 
-
+ 
 10.0.0.3

 		
 

 

 

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

 

 
-
+ 
 For more detail on ordering responses, check the 
 rrset-order
  substatement in the 
 options
- statement in 
+ statement in 
 RRset Ordering
 .
@@ -274,54 +262,56 @@ RRset Ordering

    - + 3.3 Notify

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

- - + + DNS Notify is fully documented in RFC 1996. See also the description of the zone option also-notify - in section 3.1.3.7, "Zone transfers."

+ on +Zone Transfers +.

    - - + + 3.4 Nameserver Operations

    - + 3.4.1 Tools for Use With the Nameserver Daemon

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

    - + 3.4.1.1 Diagnostic Tools
- + dig

- + The domain information groper ( dig ) is a command line tool that can be used to gather information from the Domain Name System servers. Dig has two modes: simple interactive mode for a single query, and batch mode which executes a query for each in a list of several query lines. All query options are accessible from the command line.

@@ -329,30 +319,30 @@ dig
- + Usage
-

+
 
 dig [@server] domain [<query-type>] [<query-class>]
 [+<query-option>] [-<dig-option>] [%comment]

 

 
-
+ 
 The usual simple use of dig will take the form

-

+
 
 dig @server domain query-type query-class

 

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

- + The @@ -364,113 +354,114 @@ utility provides a simple DNS lookup using a command-line interface for looking

- + Usage
-

+
 
 host [-l] [-v] [-w] [-r] [-d] [-t querytype] [-a] host [server]
- + nslookup

- + nslookup - is a program used to query Internet domain nameservers. nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query nameservers for information about various hosts and domains or to print a list of hosts in a domain. Non-interactive mode is used to print just the name and requested information for a host or domain.

+ is a program used to query Internet domain nameservers. +nslookup + has two modes: interactive and non-interactive. Interactive mode allows the user to query nameservers for information about various hosts and domains or to print a list of hosts in a domain. Non-interactive mode is used to print just the name and requested information for a host or domain.

- + Usage
-

+
 
 nslookup [-option ...] [host-to-find | -[server]]

 

 
-
+ 
 Interactive mode is entered when no arguments are given (the default nameserver will be used) or when the first argument is a hyphen (-) and the second argument is the host name or Internet address of a nameserver.

 

 
-
+ 
 Non-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument. The optional second argument specifies the host name or address of a nameserver.

 

 
-
-The options listed under the "set" command (see the nslookup man page for details) can be specified in the .nslookuprc file in the user's home directory if they are listed one per line. Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial time-out to 10 seconds, type:

-

+ 
+The options listed under the "set" command (see the 
+nslookup
+ man page for details) can be specified in the 
+.nslookuprc
+ file in the user's home directory if they are listed one per line. Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial time-out to 10 seconds, type:

+
 
 nslookup -query=hinfo -timeout=10

 

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

+ 
+For more information and a list of available commands and options, see the 
+nslookup
+ man page.
    - + 3.4.1.2 Administrative Tools

- + Administrative tools play an integral part in the management of a server.

- + rndc

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

- + Usage:

-

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

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

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

    - + 3.4.1.3 Monitoring Tools
- + MRTG

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

-

- - - 

-

Return to BINDv9 Administrator Reference Manual table of contents.

+

Return to BINDv9 Administrator Reference Manual diff --git a/doc/arm/BV9ARM.4.html b/doc/arm/Bv9ARM.4.html similarity index 55% rename from doc/arm/BV9ARM.4.html rename to doc/arm/Bv9ARM.4.html index 3f23152db2..25c7d47d8c 100644 --- a/doc/arm/BV9ARM.4.html +++ b/doc/arm/Bv9ARM.4.html @@ -2,29 +2,29 @@ - + Section 4. Advanced Concepts

    - + 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 on a zone-by-zone basis, by including an allow-update or @@ -34,40 +34,40 @@ zone statement.

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

+) file. BINDv9 currently does not update the zone file when it exits like BIND 8 does, so editing the zone file manually is unsafe even when the server has been shut down.

    - + 4.2 - + Incremental Zone Transfers (IXFR)

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

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

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

- -When acting as a slave, BIND 9 will attempt to use IXFR unless it is explicitly disabled. For more information about disabling IXFR, see the description of the + +When acting as a slave, BINDv9 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 @@ -77,440 +77,480 @@ server

    - + 4.3 Split DNS

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

+ +Setting up different views, or visibility, of DNS space to internal, as opposed to external, resolvers is usually referred to as a "Split DNS" or "Split Brain DNS" setup. There are several reasons an organization would want to set 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.

+ +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 + +The internal servers will be configured to forward all queries, except queries for site1.example -, +, site2.example -, +, site1.example.com -, and +, and site2.example.com -, to the servers in the DMZ. These internal servers will have complete sets of information for +, to the servers in the DMZ. These internal servers will have complete sets of information for site1.example.com -, +, site2.example.com , - site1.internal -, and + + +site1.internal +, and site2.internal .

- -To protect the -site1.internal + +To protect the + site1.interna + +l and - site2.internal + + +site2.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 + +The external servers, which are on the bastion hosts, will be configured to serve the "public" version of the site1 - and + and site2.example.com - zones. This could include things such as the host records for public servers ( + zones. This could include things such as the host records for public servers ( www.example.com -, +, ftp.example.com -), and mail exchanger records ( +), and mail exchanger records ( a.mx.example.com - and + and b.mx.example.com ).

- -In addition, the public + +In addition, the public site1 - and -site2 .example.com - zones should have special MX records that contain wildcard (*) records pointing to the bastion hosts. This is needed because external mail servers do not have any other way of looking up how to deliver mail to those internal hosts. With the wildcard records, the mail will be delivered to the bastion host, which can then forward it on to internal hosts.

+ and +site2.example.com + zones should have special MX records that contain wildcard ("*") records pointing to the bastion hosts. This is needed because external mail servers do not have any other way of looking up how to deliver mail to those internal hosts. With the wildcard records, the mail will be delivered to the bastion host, which can then forward it on to internal hosts.

- + 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 
+ 
+Look up any hostnames in the 
 site1
- and 
-site2 .example.com
+ and 
+site2.example.com
  zones.
    • 
 
  • 
 
-
-Look up any hostnames in the 
+ 
+Look up any hostnames in the 
 site1.internal
- and 
+ and 
 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 
+ 
+Look up any hostnames in the 
 site1
- and 
-site2 .example.com 
+ and 
+site2.example.com 
 zones.
    • 
 
  • 
 
-
-Exchange mail with anyone in the 
+ 
+Exchange mail with anyone in the 
 site1
- and 
-site2 .example.com
+ and 
+site2.example.com
  zones.
    • 
 

 

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

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

 

 
-
+ 
 Internal 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 {
     ...
     ...
     forward only;
-    forwarders { bastion-ips-go-here; };  // forward to external servers
-    allow-transfer { none; };                    // sample allow-transfer (no one)
-    allow-query { internals; externals; };       // restrict query access
-    allow-recursion { internals; };              // restrict recursion
+    forwarders { bastion-ips-go-here; };			//forward to external servers
+    allow-transfer { none; };				// sample allow-transfer (no one)
+    allow-query { internals; externals; };			// restrict query access
+    allow-recursion { internals; };			// restrict recursion
     ...
     ...
-};

-

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

-

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

-

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

-

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

-

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

-

+  allow-query { internals };
+  allow-transfer { internals; }
+};
+
+
+External (bastion host) DNS server config:
+ 
+
 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
-acl externals { bastion-ips-go-here; };
+acl externals { bastion-ips-go-here; };
 options {
   ...
   ...
-  allow-transfer { none; };                  // sample allow-transfer (no one)
-  allow-query { internals; externals; };     // restrict query access
-  allow-recursion { internals; externals; }; // restrict recursion
+  allow-transfer { none; };                  // sample allow-transfer (no one)
+  allow-query { internals; externals; };     // restrict query access
+  allow-recursion { internals; externals; }; // restrict recursion
   ...
   ...
-};

-

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

-

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

-

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

-

-search ...
+};
+
+zone "site1.example.com" {        // sample slave zone
+  type master;
+  file "m/site1.foo.com";
+  allow-query { any; };
+  allow-transfer { internals; externals; };
+};
+
+zone "site2.example.com" {
+  type slave;
+  file "s/site2.foo.com";
+  masters { another_bastion_host_maybe; };
+  allow-query { any; };
+  allow-transfer { internal; externals; }
+};
+
+
+In the resolv.conf (or equivalent) on the bastion host(s):
+ 
+search ...
 nameserver 172.16.72.2
 nameserver 172.16.72.3
-nameserver 172.16.72.4

+nameserver 172.16.72.4
+

+

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

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

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

    - + 4.4.1 Generate Shared Keys for Each Pair of Hosts

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

    - + 4.4.1.1 Automatic Generation

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

-

+
+

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

 

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

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

    - + 4.4.2 Copying the Shared Secret to Both Machines

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

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

- -Imagine host1 and host 2 are both servers. The following is added to each server's named.conf file:

-

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

+};
+
+

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

-

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

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

+};
+

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

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

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

    - + 4.4.5 TSIG Key Based Access Control

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

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

-

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

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

@@ -519,26 +559,30 @@ host1-host2.

    - + 4.4.6 Errors

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

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

- + TSIG verification errors are logged by the server as

-

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

- + which is printed at debug level 1.

@@ -546,226 +590,325 @@ which is printed at debug level 1.

    - -4.5 DNSSEC

    + +4.5 TKEY

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

-

- - +TKEY + is a mechanism for automatically generating a shared secret between two hosts. There are several "modes" of +TKEY + that specify how the key is generated or assigned. BIND implements only one of these modes, the Diffie-Hellman key exchange. Both hosts are required to have a Diffie-Hellman KEY record (although this record is not required to be present in a zone). The +TKEY + process must use signed messages, signed either by TSIG or SIG(0). The result of +TKEY + is a shared secret that can be used to sign messages with TSIG. +TKEY + can also be used to delete shared secrets that it had previously generated.

+

+ + The -.key - files contain public keys in DNS RR format, which is base 64. The -.private - files contain private keys, with each field encoded in base 64.

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

-

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

-

-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";
-pubkey 16641 3 3 "AuNiWOmzSHwrzLMWv1C1gbKQBNAHwMeX+C0owQkfmdxjoTJvnmbN
-       CdbGM/fnejQhEXsRT5l3NLy0H4UCX3ElGJT49n3nFb2jPuDYbkPh
-       VV4sLfLJzQs/RWeQmQnNFF2HNmwksWlPvUT66k4mqJDtIk60Dio6
-       1PML5sVDMQns7Zukq4aSn4jzRGkbDGhB9S3yzXVMVjYDwlM9frW9
-       Ayt0vqDa0zG+V52YiCSOdFGWJ0bSFa8sTwcp4BEVUt/Kg2Zo4VAy
-       +AeYLcQLb6vDZUX8x/BPByKKptfXirhNPv43xE6vT4xCxYPhvyDk
-       Y7Qlf4W+/sSNNKE7P/JAKmQxxXAVPoXtBpa6";
-};
-
    -
  • - - -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
-       CdbGM/fnejQhEXsRT5l3NLy0H4UCX3ElGJT49n3nFb2jPuDYbkPh
-       VV4sLfLJzQs/RWeQmQnNFF2HNmwksWlPvUT66k4mqJDtIk60Dio6
-       1PML5sVDMQns7Zukq4aSn4jzRGkbDGhB9S3yzXVMVjYDwlM9frW9
-       Ayt0vqDa0zG+V52YiCSOdFGWJ0bSFa8sTwcp4BEVUt/Kg2Zo4VAy
-       +AeYLcQLb6vDZUX8x/BPByKKptfXirhNPv43xE6vT4xCxYPhvyDk
-       Y7Qlf4W+/sSNNKE7P/JAKmQxxXAVPoXtBpa6";
-}
-
    -
  • - - -Start named.
    • -
+TKEY + process is initiated by a client or server by sending a signed +TKEY + query (including any appropriate KEYs) to a TKEY-aware server. The server response, if it indicates success, will contain a +TKEY + record and any appropriate keys. After this exchange, both participants have enough information to determine the shared secret; the exact process depends on the +TKEY + mode. When using the Diffie-Hellman +TKEY + mode, Diffie-Hellman keys are exchanged, and the shared secret is derived by both participants.

+
+
+
    +

    + + +4.6 DNSSEC Secured Zones

    +
+

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

+

+ + +In order to set up a DNSSEC secure zone, there are a series of steps which must be followed. BINDv9 ships with several tools that are used in this process, which are explained in more detail below. In all cases, the " +-h +" option prints a full list of parameters.

+

+ + +There must also be communication with the administrators of the parent and/or child zone to transmit keys and signatures. A zone's security status must be indicated by the parent zone for a DNSSEC capable resolver to trust its data.

+

+ + +For other servers to trust data in this zone, they must either be statically configured with this zone's zone key or the zone key of another zone above this one in the DNS tree.

+
+
    +

    + + +4.6.1 Generating Keys

    +
+

+ + +The +dnssec-keygen + program is used to generate keys.

+

+ + +A secure zone must contain one or more zone keys. The zone keys will sign all other records in the zone, as well as the zone keys of any secure delegated zones. Zone keys must have the same name as the zone, a name type of +ZONE +, and must be usable for authentication. It is recommended that zone keys be mandatory to implement a cryptographic algorithm; currently the only key mandatory to implement an algorithm is DSA.

+

+ + +The following command will generate a 768 bit DSA key for the +child.example + zone:

+

+ + + +dnssec-keygen + +-a + +DSA + +-b + +768 + +-n + +ZONE + +child.example +.

+

+ + +Two output files will be produced: +Kchild.example.+003+12345.key + and +Kchild.example.+003+12345.private + (where 12345 is an example of a key identifier). The key file names contain the key name ( +child.example +), algorithm (3 is DSA, 1 is RSA, etc.), and the key identifier (12345 in this case). The private key (in the +.private + file) is used to generate signatures, and the public key (in the +.key + file) is used for signature verification.

+

+ + +To generate another key with the same properties, repeat the above command.

+

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

+
+
+
    +

    + + +4.6.2 Creating a Keyset

    +
+

+ + +The +dnssec-makekeyset + program is used to create a key set from one or more keys.

+

+ + +Once the zone keys have been generated, a key set must be built for transmission to the administrator of the parent zone, so that the parent zone can sign the keys with its own zone key and correctly indicate the security status of this zone. When building a key set, the list of keys to be included and the TTL of the set must be specified, and the desired signature validity period of the parent's signature may also be specified.

+

+ + +The list of keys to be inserted into the key set may also included non-zone keys present at the apex. +dnssec-makekeyset + may also be used at non-apex names.

+

+ + +The following command generates a key set containing the above key and another key similarly generated, with a TTL of 3600 and a signature validity period of 10 days starting from now.

+

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

+

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

+
+
+
    +

    + + +4.6.3 Signing the Child's Keyset

    +
+

+ + +The +dnssec-signkey + program is used to sign one child's keyset.

+

+ + +If the +child.example + zone has any delegations which are secure, for example, +grand.child.example +, the +child.example + administrator should receive keyset files for each secure subzone. These keys must be signed by this zone's zone keys.

+

+ + +The following command signs the child's key set with the zone keys:

+

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

+

+ + +One output file is produced: +grand.child.example.signedkey +. This file should be both transmitted back to the child and retained. It includes all keys (the child's keys) from the keyset file and signatures generated by this zone's zone keys.

+
+
+
    +

    + + +4.6.4 Signing the Zone

    +
+

+ + +The +dnssec-signzone + program is used to sign a zone.

+

+ + +Any +signedkey + files corresponding to secure subzones should be present, as well as a +signedkey + file for this zone generated by the parent (if there is one). The zone signer will generate +NXT + and +SIG + records for the zone, as well as incorporate the zone key signature from the parent and indicate the security status at all delegation points.

+

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

+

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

+

+ + +One output file is produced: +zone.child.example.signed +. This file should be referenced by +named.conf + as the input file for the zone.

+
+
+
    +

    + + +4.6.5 Configuring Servers

    +
+

+ + +Unlike in BIND 8, data is not verified on load in BINDv9, so zone keys for authoritative zones do not need to be specified in the configuration file.

+

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

+

    - -4.6 IPv6

    + +4.7 IPv6

    - -4.6.1 IPv6 addresses (A6)

    + +4.7.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; @@ -775,208 +918,208 @@ 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:

- +  

-

+

- + 3

 -

+

- + 13

 -

+

- + 8

 -

+

- + 24

 -

+

- + 16

 -

+

- + 64 bits
-

+

- + FP

 -

+

- + TLA ID

 -

+

- + RES

 -

+

- + NLA ID

 -

+

- + SLA ID

 -

+

- + Interface ID
-

+

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

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

 -

+

- +  

 -

+

- +  
-

+

- +  

 -

+

- +  

 -

+

- +  

 -

+

- +  

 -

+

- -<--Site Topology-->

+ +<-Site Topology->

 -

+

- +  
-

+

- +  

 -

+

- +  

 -

+

- +  

 -

+

- +  

 -

+

- +  

 -

+

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

- + Where

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

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

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

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

@@ -1064,63 +1207,71 @@ 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 +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:

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

- +  

@@ -1128,379 +1279,380 @@ 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.

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

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

-

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

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

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

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

    - -4.6.2 Name to Address Lookup

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

- +  

+
-

+

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

- +  

-

+

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

- +  

-

+

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

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

    + +4.7.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 + +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. + + +\[x3FFE8050020100090A0020FFFE812B32/128].ip6.int. (not divided)

- - -\[x00090A0020FFFE812B32/80].\[xFFF402801008/45].\[x2/3].ip6.int. + + +\[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. + + +\[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.6.4 Using DNAME for Delegation of IPv6 Reverse Addresses

    + +4.7.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 @@ -1514,45 +1666,51 @@ example2.com ), the domain administrator would insert a line similar to the following in the \[x2/3].ip6.int. zone:

-

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

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

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

+\[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 " -. -".

-

- - - 

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

-

Return to BINDv9 Administrator Reference Manual table of contents.

+

Return to BINDv9 Administrator Reference Manual diff --git a/doc/arm/BV9ARM.5.html b/doc/arm/Bv9ARM.5.html similarity index 75% rename from doc/arm/BV9ARM.5.html rename to doc/arm/Bv9ARM.5.html index 97433beb96..99b1f63bbd 100644 --- a/doc/arm/BV9ARM.5.html +++ b/doc/arm/Bv9ARM.5.html @@ -1,57 +1,57 @@ - + - + Section 5. BINDv9 Configuration Reference

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

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

- -BIND 4.9.x configuration files can be converted to the new format by using the Perl script -src/bin/named/named-bootconf.pl + +BIND 4.9.x configuration files can be converted to the new format by using the Perl script +src/bin/named/named-bootconf.pl from the BIND 8 release kit.

    - + 5.1 Configuration file elements

- + Following is a list of elements used throughout the BIND configuration file documentation:

- +  

@@ -362,94 +388,87 @@ false

    - + 5.1.1 - + Address Match Lists

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

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

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

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

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

- + The addition of the key clause made the name of this syntactic element something of a misnomer, since security keys can be used to validate access without regard to a host or network address. Nonetheless, the term "address match list" is still used throughout the documentation.

- + When a given IP address or prefix is compared to an address match list, the list is traversed in order until an element matches. The interpretation of a match depends on whether the list is being used for access control, defining listen-on ports, or as a topology, and whether the element was negated.

- + When used as an access control list, a non-negated match allows access and a negated match denies access. If there is no match, access is denied. The clauses allow-query, allow-transfer, allow-update and blackhole all use address match lists like this. Similarly, the listen-on option will cause the server to not accept queries on any of the machine's addresses which do not match the list.

- + When used with the topology clause, a non-negated match returns a distance based on its position on the list (the closer the match is to the start of the list, the shorter the distance is between it and the server). A negated match will be assigned the maximum distance from the server. If there is no match, the address will get a distance which is further than any non-negated list element, and closer than any negated element.

- + Because of the first-match aspect of the algorithm, an element that defines a subset of another element in the list should come before the broader element, regardless of whether either is negated. For example, in
1.2.3/24; ! 1.2.3.13; @@ -462,23 +481,23 @@ Because of the first-match aspect of the algorithm, an element that defines a su

    - + 5.1.2 Comment Syntax

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

    - + 5.1.2.1 Syntax

- + /* This is a BIND comment as in C */
// This is a BIND comment as in C++
# This is a BIND comment as in common UNIX shells and perl

@@ -487,60 +506,60 @@ The BINDv9 comment syntax allows for comments to appear anywhere that white spac
    - + 5.1.2.2 Definition and Usage

- + Comments may appear anywhere that whitespace may appear in a BIND configuration file.

- + C-style comments start with the two characters /* (slash, star) and end with */ (star, slash). Because they are completely delimited with these characters, they can be used to comment only a portion of a line or to span multiple lines.

- + C-style comments cannot be nested. For example, the following is not valid because the entire comment ends with the first */:

- + /* This is the start of a comment.
This is still part of the comment.
/* This is an incorrect attempt at nesting a comment. */
This is no longer in any comment. */

- + C++-style comments start with the two characters // (slash, slash) and continue to the end of the physical line. They cannot be continued across multiple physical lines; to have one logical comment span multiple lines, each line must use the // pair.

- + For example:

- + // This is the start of a comment. The next line
// is a new comment, even though it is logically
// part of the previous comment.

- + Shell-style (or perl-style, if you prefer) comments start with the character # (number sign) and continue to the end of the physical line, like C++ comments.

- + For example:

- + # This is the start of a comment. The next line
# is a new comment, even though it is logically
# part of the previous comment.

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

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

@@ -548,53 +567,53 @@ WARNING: you cannot use the ";" (semicolon) character to start a comme

    - + 5.2 - + Configuration File Grammar

- + A BINDv9 configuration consists of statements and comments. Statements end with a semicolon. Statements and comments are the only elements that can appear without enclosing braces. Many statements contain a block of substatements, which are also terminated with a semicolon.

- + The following statements are supported:

- +  

-
+

- - -acl_name -

+ + +acl_name +

- -The name of an -address_match_list + +The name of an +address_match_list as defined by the acl statement.

@@ -59,58 +59,72 @@ acl
-
+

- - -address_match_list -

+ + +address_match_list +

- -A list of one or more -ip_addr, ip_prefix, key_id, -or -acl_name - elements, as described in + +A list of one or more +ip_addr + +, + +ip_prefix + +, + +key_id + +, +or +acl_name + elements, as described in Address Match Lists .
-
+

- - -domain_name -

+ + +domain_name +

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

+ +" +.
-
+

- - -dotted_decimal -

+ + +dotted_decimal +

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

-
+

- - -ip4_addr -

+ + +ip4_addr +

- -An IPv4 address with exactly four elements in -dotted_decimal + +An IPv4 address with exactly four elements in +dotted_decimal notation.
-
+

- - -ip6_addr

+ + +ip6_addr +

- + An IPv6 address, like fe80::200:f8ff:fe01:9742 .

@@ -156,59 +171,62 @@ fe80::200:f8ff:fe01:9742
-
+

- - -ip_addr

+ + +ip_addr +

- -An -ip4_addr + +An +ip4_addr or - ip6_addr + + +ip6_addr .
-
+

- - -ip_port -

+ + +ip_port +

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

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

- - -ip_prefix -

+ + +ip_prefix +

- -An IP network specified as an -ip_addr -, followed by "/'' and then the number of bits in the netmask. E.g. + +An IP network specified as an +ip_addr +, followed by a slash (`/') and then the number of bits in the netmask. For example, 127/8 is the network 127.0.0.0 @@ -225,135 +243,143 @@ ip_addr

-
+

- - -key_name -

+ + +key_name +

- -A -domain_name + +A +domain_name representing the name of a shared key, to be used for transaction security.
-
+

- - -number -

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

- - -path_name -

+ + +path_name +

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

+ +" +.
-
+

- - -size_spec -

+ + +size_spec +

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

- -The maximum value of -size_spec - is that of unsigned long integers on the machine. -unlimited - requests unlimited use, or the maximum available amount. -default + +The maximum value of +size_spec + is that of unsigned long integers on the machine. An +unlimited + +size_spec + requests unlimited use, or the maximum available amount. A +default size_spec uses the limit that was in force when the server was started.

- -A -number - can optionally be followed by a scaling factor: -K - or -k -for kilobytes, -M - or -m - for megabytes, and -G - or -g + +A +number + can optionally be followed by a scaling factor: +K + or +k + + +for kilobytes, +M + or +m + for megabytes, and +G + or +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 + +Integer storage overflow is currently silently ignored during conversion of scaled values, resulting in values less than intended, possibly even negative. Using +unlimited is the best way to safely set a really large number.
-
+

- - -yes_or_no -

+ + +yes_or_no +

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

- + acl -

+

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

- + controls -

+

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

@@ -602,33 +621,33 @@ rndc
-
+

- + include -

+

- + includes a file
-
+

- + key -

+

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

@@ -636,104 +655,104 @@ draft-ietf-dnsind-tsig-13.txt
-
+

- + logging -

+

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

- + options -

+

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

- + server -

+

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

- + trusted-keys -

+

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

- + view -

+

- + defines a view
-
+

- + zone -

+

- + defines a zone

- + The logging and @@ -743,53 +762,56 @@ options

    - + 5.2.1 acl Statement Grammar

-

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

    - + 5.2.2 acl - + Statement Definition and Usage

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

- + Note that an address match list's name must be defined with acl before it can be used elsewhere; no forward references are allowed.

- + The following ACLs are built-in:

- +  

@@ -805,7 +827,7 @@ Matches all hosts.

@@ -821,7 +843,7 @@ Matches no hosts.

@@ -837,7 +859,7 @@ Matches the IP addresses of all interfaces on the system.

@@ -855,29 +877,35 @@ Matches any host on a network for which the system has an interface.

    - + 5.2.3 -controls +control 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...;[..]]]
+};
+
+

    - + 5.2.4 controls Statement Definition and Usage

- + The controls statement declares control channels to be used by system administrators to affect the operation of the local nameserver. These control channels are used by the @@ -885,7 +913,7 @@ ndc utility to send commands to and retrieve non-DNS results from a nameserver.

- + A UNIX control channel is a "first in first out" (FIFO) named pipe in the file system, and access to it is controlled by normal file system permissions. It is created by named with the specified file mode bits (see the @@ -899,7 +927,7 @@ permission so the number is interpreted as octal. Also note that the user and group ownership specified as owner and group must be given as numbers, not names. It is recommended that the permissions be restricted to administrative personnel only to prevent random users on the system from having the ability to manage the local nameserver.

- + An inet control channel is a TCP/IP socket accessible to the Internet, created at the specified @@ -911,7 +939,7 @@ ip_addr used, and this only if you trust all non-privileged users on the local host to manage your nameserver.

- + The @@ -924,26 +952,30 @@ controls

    - + 5.2.5 include Statement Grammar

-

-include "filename";
+ +
+
+include filename;
+
+

    - + 5.2.6 include Statement Definition and Usage

- + The include statement inserts the specified file at the point that the @@ -956,51 +988,54 @@ include

    - + 5.2.7 key Statement Grammar

-

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

    - + 5.2.8 key Statement Definition and Usage

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

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

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

- + The key statement is intended for use in transaction security. Unless included in a server statement, it is not used to sign any requests. It is used to verify requests matching the @@ -1013,42 +1048,50 @@ algorithm_id

    - + 5.2.9 logging - statement grammar

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

 
+   ... 
+};
+
+
+
+
    +

    + + 5.2.10 logging - statement definition and usage

    + Statement Definition and Usage

- + The logging statement configures a wide variety of logging options for the nameserver. Its @@ -1070,13 +1113,16 @@ logging statement, the logging configuration will be:


  
-

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

+};
+
+

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

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

+-generated time stamp, the category name and/or severity level (the 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 @@ -1127,7 +1171,7 @@ 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 @@ -1153,22 +1197,27 @@ unlimited in current BIND releases.

- + Example usage of the size and versions options:

-

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

- + The argument for the syslog clause is a syslog facility as described in the syslog - manual page. How + man page. How syslog will handle messages sent to this facility is described in the syslog.conf @@ -1179,7 +1228,7 @@ openlog() function, then this clause is silently ignored.

- + The severity clause works like @@ -1189,7 +1238,7 @@ 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 @@ -1215,7 +1264,7 @@ 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 " @@ -1227,20 +1276,22 @@ 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";
+ 
+
+  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. @@ -1260,108 +1311,143 @@ print- options are on:

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

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

-

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

+       null;                // toss anything sent to this channel
+    };
+
+

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

+

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

    - + 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; };
+ +
+    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;
+ 
+
+
+channel my_security_channel {
+    file "my_security_file";
+    severity info;
 };
-category security {
-    my_security_channel;
+category security {
+    my_security_channel;
     default_syslog;
     default_debug;
-};

+};
+
+

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

-

-category lame-servers { null; };
-category cname { null; };
+
+
+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.

- + any
@@ -797,7 +819,7 @@ any

- + Matches all hosts.
- + none
@@ -813,7 +835,7 @@ none

- + Matches no hosts.
- + localhost
@@ -829,7 +851,7 @@ localhost

- + Matches the IP addresses of all interfaces on the system.
- + localnets
@@ -845,7 +867,7 @@ localnets

- + Matches any host on a network for which the system has an interface.
@@ -1547,96 +1637,99 @@ Dynamic updates.

    - + 5.2.11 options Statement Grammar

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

-

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

    - + 5.2.12 options Statement Definition and Usage

- + The options statement sets up global options to be used by BIND. This statement may appear only once in a configuration file. If more than one occurrence is found, the first occurrence determines the actual options used, and a warning will be generated. If there is no @@ -1645,19 +1738,19 @@ options

-
+

- + 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; }; @@ -1370,173 +1456,177 @@ category default { default_syslog; default_debug; };

-
+

- + -general

+general +

- + The catch-all. Many things still aren't classified into categories, and they all end up here.
-
+

- + -database

+database +

- + Messages relating to the databases used internally by the name server to store zone and cache data.
-
+

- + -security

+security +

- + Approval and denial of requests.
-
+

- + config -

+

- + Configuration file parsing and processing.
-
+

- + -resolver

+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.
+ + + + + + + + @@ -1792,79 +1936,79 @@ Not yet implemented in BINDv9
    - + 5.2.12.1 - + Boolean Options
-

+

- +  

-
+

- + version -

+

- -The version the server should report via a query of name -version.bind + +The version the server should report via a query of name +version.bind in class chaos . The default is the real version number of this server.

@@ -1665,35 +1758,37 @@ chaos
-
+

- + directory -

+

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

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

- + named-xfer -

+

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

-
+

+ + + +tkey-domain +

+
 +

+ + +The domain appended to the names of all shared keys generated with +TKEY +. When a client requests a +TKEY + exchange, it may or may not specify the desired name for the key. If present, the name of the shared key will be " +client specified part +" + " +tkey-domain +". Otherwise, the name of the shared key will be " +random hex digits +" + " +tkey-domain +". In most cases, the +domainname + should be the server's domain name.

+
+

+ + + +tkey-dhkey +

+		 +

+ + +The Diffie-Hellman key used by the server to generate shared keys with clients using the Diffie-Hellman mode of +TKEY +. The server must be able to load the public and private keys from files in the working directory. In most cases, the keyname should be the server's host name.

+
+

- + dump-file - +

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

-
+

- + memstatistics-file -

+

- -The pathname of the file the server writes memory usage statistics to on exit. If not specified, the default is " -named.memstats -". + +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.

-
+

- + 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 + +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 @@ -1769,20 +1913,20 @@ The pathname of the file the server writes its process ID in. If not specified,

-
+

- + statistics-file -

+

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

-
+

- + auth-nxdomain -

+

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

- + deallocate-on-exit -

+

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

- + dialup -

+

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

- + The dialup option may also be specified in the @@ -1874,20 +2018,12 @@ options dialup statement.

- -If the zone is a -master - then the server will send out a NOTIFY request to all the slaves. This will trigger the zone serial number check in the slave (providing it supports NOTIFY) allowing the -slave - to verify the zone while the connection is active.

+ +If the zone is a master then the server will send out a NOTIFY request to all the slaves. This will trigger the zone serial number check in the slave (providing it supports NOTIFY) allowing the slave to verify the zone while the connection is active.

- -If the zone is a -slave - or -stub - then the server will suppress the regular "zone up to date" queries and only perform them when the
+ +If the zone is a slave or stub then the server will suppress the regular "zone up to date" queries and only perform them when the
heartbeat-interval expires. @@ -1897,40 +2033,38 @@ Not yet implemented in BINDv9.

-
+

- + fake-iquery -

+

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

- + fetch-glue -

+

- + If yes (the default), the server will fetch "glue" resource records it doesn't have when constructing the additional data section of a response. (Information present outside of the authoritative nodes in the zone is called "glue" information). -fetch-glue - -no - can be used in conjunction with +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). Not yet implemented in BINDv9. @@ -1939,18 +2073,19 @@ Not yet implemented in BINDv9.

-
+

- + has-old-clients -

+

- -This option was incorrectly implemented in BIND 8, and is ignored by BINDv9. To achieve the intended effect of + +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 @@ -1961,21 +2096,21 @@ rfc2308-type-1 no

-
+

- + host-statistics -

+

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

-
+

- + maintain-ixfr-base -

+

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

-
+

- + multiple-cnames -

+

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

- + notify -

+

- -If -yes + +If +yes (the default), DNS NOTIFY messages are sent when a zone the server is authoritative for changes. The use of NOTIFY speeds synchronization between the master and its slaves. Slave servers that receive a NOTIFY message and understand it will contact the master server for the zone and see if they need to do a zone transfer, and if they do, they will initiate it immediately. The notify option may also be specified in the @@ -2047,21 +2182,21 @@ Not yet supported in BINDv9.

-
+

- + recursion -

+

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

@@ -2069,23 +2204,23 @@ fetch-glue
-
+

- + rfc2308-type1 -

+

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

@@ -2093,16 +2228,17 @@ Not yet implemented in BINDv9
-
+

- + -use-id-pool

+use-id-pool +

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

@@ -2110,24 +2246,24 @@ This option is obsolete
-
+

- + treat-cr-as-space -

+

- + This option was used in BIND 8 to make the server treat ` \r ' characters the same way as <space> -" +` -" or ` +` or ` \t ', to facilitate loading of zone files on a UNIX system that were generated on an NT or DOS machine. In BINDv9, both UNIX ` \n @@ -2142,61 +2278,61 @@ This option was used in BIND 8 to make the server treat ` - + 5.2.12.2 Forwarding

- + The forwarding facility can be used to create a large site-wide cache on a few servers, reducing traffic over links to external nameservers. It can also be used to allow queries by servers that do not have direct access to the Internet, but wish to look up exterior names anyway. Forwarding occurs only on those queries for which the server is not authoritative and does not have the answer in its cache.

- +  

-
+

- + forward -

+

- -This option is only meaningful if the forwarders list is not empty. A value of -first -, the default, causes the server to query the forwarders first, and if that doesn't answer the question the server will then look for the answer itself. If -only + +This option is only meaningful if the forwarders list is not empty. A value of +first +, the default, causes the server to query the forwarders first, and if that doesn't answer the question the server will then look for the answer itself. If +only is specified, the server will only query the forwarders.
-
+

- + forwarders -

+

- + Specifies the IP addresses to be used for forwarding. The default is the empty list (no forwarding).

- + 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 +, or not forward at all. See zone Statement Grammar for more information.

@@ -2204,90 +2340,92 @@ zone Statement Grammar
    - + 5.2.12.3 - + Name Checking

- + The server can check domain names based upon their expected client contexts. For example, a domain name used as a hostname can be checked for compliance with the RFCs defining valid hostnames.

- + Three checking methods are available:

- +  

-
+

- + ignore -

+

- + No checking is done.
-
+

- + warn -

+

- + Names are checked against their expected client contexts. Invalid names are logged, but processing continues normally.
-
+

- + fail -

+

- + Names are checked against their expected client contexts. Invalid names are logged, and the offending data is rejected.

- + The server can check names in three areas: master zone files, slave zone files, and in responses to queries the server has initiated. If check-names response fail has been specified, and answering the client's question would require sending an invalid name to the client, the server will send a REFUSED response code to the client.

- + The defaults are:

-

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

+    check-names response ignore;
+

- + check-names may also be specified in the @@ -2299,7 +2437,7 @@ zone statement, the area is not specified (because it can be deduced from the zone type).

- + Name checking is not yet implemented in BINDv9.

@@ -2308,35 +2446,35 @@ Name checking is not yet implemented in BINDv9.
    - + 5.2.12.4 - + Access Control

- -Access to the server can be restricted based on the IP address of the requesting system. See + +Access to the server can be restricted based on the IP address of the requesting system. See Address Match Lists for details on how to specify IP address lists.

- +  

-
+

- + allow-query -

+

- + Specifies which hosts are allowed to ask ordinary questions. allow-query may also be specified in the @@ -2348,33 +2486,33 @@ options allow-query

-
+

- + allow-recursion -

+

- + Specifies which hosts are allowed to make recursive queries through this server. If not specified, the default is to allow recursive queries from all hosts.

-
+

- + allow-transfer -

+

- + Specifies which hosts are allowed to receive zone transfers from the server. allow-transfer may also be specified in the @@ -2386,17 +2524,17 @@ options allow-transfer

-
+

- + 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 . @@ -2410,12 +2548,12 @@ Not yet implemented in BINDv9.

    - + 5.2.12.5 Interfaces

- + The interfaces and ports that the server will answer queries from may be specified using the listen-on option. @@ -2425,24 +2563,26 @@ address_match_list . The server will listen on all interfaces allowed by the address match list. If a port is not specified, port 53 will be used.

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

-

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

- + will enable the nameserver on port 53 for the IP address 5.6.7.8, and on port 1234 of an address on the machine in net 1.2 that is not 1.2.3.4.

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

@@ -2451,12 +2591,12 @@ listen-on-v6
    - + 5.2.12.6 Query Address

- + 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. For queries sent over IPv6, there is a separate @@ -2472,12 +2612,14 @@ port is * or is omitted, a random unprivileged port will be used. The defaults are

-

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

- + Note: query-source currently applies only to UDP queries; TCP queries always use a wildcard IP address and a random unprivileged port.

@@ -2486,244 +2628,33 @@ query-source
    - + 5.2.12.7 - + Zone Transfers

- + BIND has mechanisms in place to facilitate zone transfers and set limits on the amount of load that transfers place on the system. The following options apply to zone transfers.

- +  

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
-
- - - -max-transfer-time-in -
-

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

-
-
- - - -transfer-format -
-		 -

- - -The server supports two zone transfer methods. -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 BINDv9, BIND 8.x and patched versions of BIND 4.9.5. The default is -one-answer -. -transfer-format - may be overridden on a per-server basis by using the -server - statement.

-
-
- - - -transfers-in -
-		 -

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

-
-
- - - -transfers-out -
-		 -

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

-
-
- - - -transfers-per-ns -
-		 -

- - -The maximum number of inbound zone transfers that can be concurrently transferring from a given remote nameserver. The default value is 2. Increasing -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 - may be overridden on a per-server basis by using the -transfers - phrase of the -server - statement.

-
-
- - - -transfer-source -
-		 -

- - - -transfer-source - 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 - for all zones, but can be overridden on a per-zone basis by including a
- -transfer-source - statement within the -zone - block in the configuration file.

-
-
- - - -transfer-source-v6
-		 -

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

-
-
- - - -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. -Not yet implemented in BINDv9. -

-
-
- - + + also-notify -
+

- - + + Defines a global list of IP addresses that are also sent NOTIFY messages whenever a fresh copy of the zone is loaded. This helps to ensure that copies of the zones will quickly converge on "stealth" servers. If an also-notify list is given in a @@ -2741,22 +2672,241 @@ Not yet implemented in BINDv9.

+

+ + + +max-transfer-time-in +

+		 +

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

+
+

+ + + +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. +Not yet implemented in BINDv9. +

+
+

+ + + +transfer-format +

+		 +

+ + +The server supports two zone transfer methods. +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 BINDv9, BIND 8.x and patched versions of BIND 4.9.5. The default is +one-answer +. +transfer-format + may be overridden on a per-server basis by using the +server + statement.

+
+

+ + + +transfers-in +

+		 +

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

+
+

+ + + +transfers-out +

+		 +

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

+
+

+ + + +transfers-per-ns +

+		 +

+ + +The maximum number of inbound zone transfers that can be concurrently transferring from a given remote nameserver. The default value is 2. Increasing +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 + may be overridden on a per-server basis by using the +transfers + phrase of the +server + statement.

+
+

+ + + +transfer-source +

+		 +

+ + + +transfer-source + 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 + for all zones, but can be overridden on a per-zone basis by including a
+ +transfer-source + statement within the +zone + block in the configuration file.

+
+

+ + + +transfer-source-v6 +

+		 +

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

+
    - + 5.2.12.8 Resource Limits

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

- + Scaled values are allowed when specifying resource limits. For example, 1G can be used instead of @@ -2767,29 +2917,29 @@ unlimited default uses the limit that was in force when the server was started. See the description of size_spec - in + in Configuration File Grammar for more details.

- +  

+ + + + - - - -
-
+

- + coresize -

+

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

@@ -2797,19 +2947,19 @@ Not yet implemented in BINDv9.
-
+

- + datasize -

+

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

@@ -2817,21 +2967,21 @@ Not yet implemented in BINDv9.
-
+

- + files -

+

- -The maximum number of files the server may have open concurrently. The default is -unlimited -. Note: on some operating systems the server cannot set an unlimited value and cannot determine the maximum number of open files the kernel can support. On such systems, choosing -unlimited + +The maximum number of files the server may have open concurrently. The default is +unlimited +. Note: on some operating systems the server cannot set an unlimited value and cannot determine the maximum number of open files the kernel can support. On such systems, choosing +unlimited will cause the server to use the larger of the rlim_max for @@ -2847,17 +2997,17 @@ Not yet implemented in BINDv9.

-
+

- + 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. @@ -2867,19 +3017,35 @@ Not yet implemented in BINDv9.

-
+

+ + + +recursive-clients +

+
 +

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

+
+

- + stacksize - +

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

@@ -2887,37 +3053,24 @@ Not yet implemented in BINDv9.
-
+

- + -tcp-clients

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

@@ -2926,27 +3079,27 @@ Resource limits are not yet implemented in BINDv9.
    - + 5.2.12.9 Periodic Task Intervals

- +  

@@ -4786,13 +5050,13 @@ for the IN class, a 32 bit IP address

@@ -4800,13 +5064,13 @@ maps a domain name to an IPv6 address, with a provision for indirection for lead @@ -4814,13 +5078,13 @@ a domain name

@@ -4828,13 +5092,13 @@ provides alternate naming to an entire subtree of the domain name space, rather @@ -4842,13 +5106,13 @@ a 16 bit preference value (lower is better) followed by a host name willing to a @@ -4856,13 +5120,13 @@ a fully qualified domain name.

@@ -4870,75 +5134,75 @@ a fully qualified doman name.

-
+

- + cleaning-interval -

+

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

@@ -2954,17 +3107,17 @@ minutes. The default is 60 minutes. If set to 0, no periodic cleaning will occu
-
+

- + 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. @@ -2974,17 +3127,17 @@ Not yet implemented in BINDv9.

-
+

- + interface-interval -

+

- + The server will scan the network interface list every interface-interval minutes. The default is 60 minutes. If set to 0, interface scanning will only occur when the configuration file is loaded. After the scan, listeners will be started on any new interfaces (provided they are allowed by the @@ -2994,17 +3147,17 @@ listen-on

-
+

- + statistics-interval -

+

- + Nameserver statistics will be logged every statistics-interval minutes. The default is 60. If set to 0, no statistics will be logged. @@ -3018,38 +3171,43 @@ Not yet implemented in BINDv9.

    - + 5.2.12.10 - + Topology

- + All other things being equal, when the server chooses a nameserver to query from a list of nameservers, it prefers the one that is topologically closest to itself. The topology statement takes an address_match_list and interprets it in a special way. Each top-level list element is assigned a distance. Non-negated elements get a distance based on their position in the list, where the closer the match is to the start of the list, the shorter the distance is between it and the server. A negated match will be assigned the maximum distance from the server. If there is no match, the address will get a distance which is further than any non-negated list element, and closer than any negated element. For example,

-

-    topology {
+ 
+
+    topology {
     10/8;
     !1.2.3/24;
     { 1.2/16; 3/8; };
-    };

+    };
+

- + will prefer servers on network 10 the most, followed by hosts on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the exception of hosts on network 1.2.3 (netmask 255.255.255.0), which is preferred least of all.

- + The default topology is

-

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

- + The @@ -3062,16 +3220,16 @@ topology

    - + 5.2.12.11 - + The sortlist Statement

- + Resource Records (RRs) are the data associated with the names in a domain name space. The data is maintained in the form of sets of RRs. The order of RRs in a set is, by default, not significant. Therefore, to control the sorting of records in a set resource records, or RRset , you must use the @@ -3079,26 +3237,26 @@ sortlist statement.

- -RRs are explained more fully in + +RRs are explained more fully in See Types of Resource Records and When to Use Them. . Specifications for RRs are documented in RFC 1035.

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

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

- + The sortlist statement (see below) takes an address_match_list and interprets it even more specifically than the topology - statement does (see + statement does (see Topology ). Each top level statement in the sortlist @@ -3109,7 +3267,7 @@ address_match_list ) of each top level list is checked against the source address of the query until a match is found.

- + Once the source address of the query has been matched, if the top level statement contains only one element, the actual primitive element that matched the source address is used to select the address in the response to move to the beginning of the response. If the statement is a list of two elements, then the second element is treated like the address_match_list in a @@ -3117,12 +3275,13 @@ topology statement. Each top level element is assigned a distance and the address in the response with the minimum distance is moved to the beginning of the response.

- + In the following example, any queries received from any of the addresses of the host itself will get responses preferring addresses on any of the locally connected networks. Next most preferred are addresses on the 192.168.1/24 network, and after that either the 192.168.2/24 or
192.168.3/24 network with no preference shown between these two networks. Queries received from a host on the 192.168.1/24 network will prefer other addresses on that network to the 192.168.2/24 and
192.168.3/24 networks. Queries received from a host on the 192.168.4/24 or the 192.168.5/24 network will only prefer other addresses on their directly connected networks.

-

-sortlist {
+ 
+
+sortlist {
     { localhost;            // IF   the local host
         { localnets;        // THEN first fit on the
             192.168.1/24;   //   following nets
@@ -3139,19 +3298,25 @@ sortlist {
     { { 192.168.4/24; 192.168.5/24; };
                           // if .4 or .5, prefer that net
     };
-};

+};
+
+

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

-

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

+};
+
+

- + The @@ -3164,108 +3329,115 @@ sortlist

    - + 5.2.12.12 - + RRset Ordering

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

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

+
 

 
-
+ 
 If no class is specified, the default is 
 ANY
 . If no type is specified, the default is 
 ANY
-. If no name is specified, the default is "
+. If no name is specified, the default is `
 *
-".

+'.

 

 
-
+ 
 The legal values for 
 ordering
  are:

 

 
-
+ 
  

 

 

 
-

+

 
-
+ 
 
 fixed
-

+

 		
 
 

 
-
+ 
 Records are returned in the order they are defined in the zone file.

 		
 

 

 
-

+

 
-
+ 
 
 random
-

+

 		
 
 

 
-
+ 
 Records are returned in some random order.

 		
 

 

 
-

+

 
-
+ 
 
 cyclic
-

+

 		
 
 

 
-
+ 
 Records are returned in a round-robin order.

 		
 

 

 

 
-
+ 
 For example:

-

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

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

 

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

 

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

 

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

-

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

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

+
 

 
-
+ 
 is used.

 

 
-
+ 
 
 The 
 
@@ -3304,27 +3480,27 @@ rrset-order
 
    
 
    
 
-
+ 
 5.2.12.13	Tuning
    
 

 

 
-
+ 
  

 

 

 
-

+

 
-
+ 
 
 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). 
 Not yet implemented in BINDv9.
 

@@ -3332,17 +3508,17 @@ Not yet implemented in BINDv9.
 

 

 
-

+

 
-
+ 
 
 max-ncache-ttl
-

+

 		
 
 

 
-
+ 
 To reduce network traffic and increase performance the server stores negative answers. 
 max-ncache-ttl
  is used to set a maximum retention time for these answers in the server in seconds. The default

@@ -3358,17 +3534,17 @@ Not yet implemented in BINDv9.
 

 

 
-

+

 
-
+ 
 
 min-roots
-

+

 		
 
 

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

@@ -3380,59 +3556,65 @@ Not yet implemented in BINDv9.
 
    
 
    
 
-
+ 
 5.2.12.14	Deprecated Features
    
 

 

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

+ , below) and  in the description of Incremental Transfer (IXFR) in the section 
+Incremental Zone Transfers (IXFR)
+.

 
 
 

 
    
 
    
-
-
+
+ 
 5.2.13	
 server
 
-
+ 
  Statement Grammar
    
 

-

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

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

+

 

 

 
    
 
    
 
-
+ 
 5.2.14	
 server
  Statement Definition and Usage
    
 

 

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

 

 
-
+ 
 If you discover that a remote server is giving out bad data, marking it as bogus will prevent further queries to it. The default value of 
 bogus
  is 
@@ -3446,7 +3628,7 @@ bogus
 

 

 
-
+ 
 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 
@@ -3458,7 +3640,7 @@ 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 
@@ -3466,7 +3648,7 @@ 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 
@@ -3476,14 +3658,14 @@ 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 9, BIND 8.x, 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 BINDv9, 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 
@@ -3494,13 +3676,13 @@ options
  statement will be used.

 

 
-
+ 
 
 transfers
  is used to limit the number of concurrent in-bound zone transfers from the specified server.

 

 
-
+ 
 The 
 keys
  clause is used to identify a 
@@ -3514,7 +3696,7 @@ 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.

@@ -3523,129 +3705,222 @@ keys
 
    
 
    
 
-
+ 
 5.2.15	
 trusted-keys
  Statement Grammar
    
 

-

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

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

 

 

 
    
 
    
 
-
+ 
 5.2.16	
 trusted-keys
  Statement Definition and Usage
    
 

 

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

+  in Appendix C of this document. (Their filenames begin with "
+draft-ietf-dnssec
+."). IDs are RFCs in the preliminary stages of development--they are the working drafts of IETF working groups--and can be obtained via anonymous FTP from

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

 

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

 

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

 

 

 
    
 
    
 
-
+ 
 5.2.17	
 view
  Statement Grammar
    
 

-

-view "name" {
-      ... 
-       [zone_statement[zone_statement; [....]]
-};

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

 

 

 
    
 
    
-
-
+
+ 
 5.2.18	
 view
  Statement Definition and Usage
    
 

 

-
-
-
+
+ 
+The 
 view
- statements are used to provide a different view of the same namespace to different clients.  
-They are not yet fully implemented.
-
-
-
-
-

+ statement is a powerful new feature of BINDv9 that lets a name server answer a DNS query differently depending on who is asking. It is particularly useful for implementing split DNS setups without having to run multiple servers.

+

+
+ 
+Each 
+view
+ statement defines a view of the DNS namespace that will be seen by those clients whose IP addresses match the 
+address_match_list
+ of the view's 
+match-clients
+ clause.  The order of the 
+view
+ statements is significant--a client query will be resolved in the context of the first 
+view
+ whose 
+match-clients 
+list matches the client's IP address.

+

+
+ 
+Zones defined within a 
+view
+ statement will be only be accessible to clients that match the 
+view
+.  By defining a zone of the same name in multiple views, different zone data can be given to different clients, e.g. "internal" and "external" clients in a split DNS setup.

+

+
+ 
+Many of the options given in the 
+options
+ statement can also be used within a 
+view
+ statement, and then apply only when resolving queries with that view.  When no a view-specific value is given, the value in the 
+options
+ statement is used as a default.  Also, zone options can have default values specified in the 
+view
+ statement; these view-specific defaults take precedence over those in the 
+options
+ statement. 

+

+
+ 
+Views are class specific.  If no class is given, class IN is assumed.

+

+
+ 
+If there are no 
+view
+ statements in the config file, a default view that matches any client is automatically created in class IN, and any 
+zone
+ statements specified on the top level of the configuration file are considered to be part of this default view.  If any explicit 
+view
+ statements are present, all 
+zone
+ statements must occur inside 
+view
+ statements.

+

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

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

+
 

 

 
    
 
    
-
-
+
+ 
 5.2.19	
 zone
 
-
+ 
  Statement Grammar
    
 

-

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

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

 

 

 
    
 
    
 
-
+ 
 5.2.20	
 zone
  Statement Definition and Usage
    
@@ -3654,38 +3929,38 @@ zone    
 
      
 
      
 
-
+ 
 5.2.20.1	Zone Types
      
 
@@ -3767,12 +4042,12 @@ The initial set of root nameservers is specified using a "hint zone".
 
        
 
        
 
-
+ 
 5.2.20.2	Class
        
 
      
 
-
+ 
 The zone's name may optionally be followed by a class. If a class is not specified, class 
 in
  (for 
@@ -3780,16 +4055,16 @@ internet
 ), is assumed. This is correct for the vast majority of cases.
      
 
-
+ 
 The 
 hesiod 
-class is for an information service from MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword 
+class is named for an information service from MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword 
 hs
  is a synonym for hesiod.
      
 
-
-Another MIT development was CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the 
+ 
+Another MIT development is CHAOSnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the 
 chaos
  class.
      
@@ -3797,92 +4072,94 @@ chaos
 
        
 
        
 
-
+ 
 5.2.20.3	Zone Options
        
 
      
 
      
 
-
      
+
      
 
-
-
-master
-
      
+ 
+
+master
+
      
       		
 
 
      
 
-
+ 
 The server has a master copy of the data for the zone and will be able to provide authoritative answers for it.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-
-slave
-
      
+ 
+
+slave
+
      
       		
 
 
      
 
-
+ 
 A slave zone is a replica of a master zone. The masters list specifies one or more IP addresses that the slave contacts to update its copy of the zone. If a port is specified, the slave then checks to see if the zone is current and zone transfers will be done to the port given. If a file is specified, then the replica will be written to this file whenever the zone is changed, and reloaded from this file on a server restart. Use of a file is recommended, since it often speeds server start-up and eliminates a needless waste of bandwidth. Note that for large numbers (in the tens or hundreds of thousands) of zones per server, it is best to use a two level naming scheme for zone file names. For example, a slave server for the zone 
 example.com
  might place the zone contents into a file called
      
@@ -3698,33 +3973,33 @@ ex/
 
      
 
      
 
-
      
+
      
 
-
-
-stub
-
      
+ 
+
+stub
+
      
       		
 
 
      
 
-
+ 
 A stub zone is like a slave zone, except that it replicates only the NS records of a master zone instead of the entire zone.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-
-forward
-
      
+ 
+
+forward
+
      
       		
 
 
      
 
-
+ 
 A "forward zone" is a way to configure forwarding on a per-domain basis.  A 
 zone
  statement of type 
@@ -3741,22 +4016,22 @@ forwarders
 options
  statement. Thus if you want to use this type of zone to change the behavior of the global 
 forward
- option (i.e., "forward first to, " then "forward only," or vice versa, but want to use the same servers as set globally) you need to respecify the global forwarders.
      
+ option (i.e., "forward first to", then "forward only", or vice versa, but want to use the same servers as set globally) you need to respecify the global forwarders.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-
-hint
-
      
+ 
+
+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.
      
       		
 
      
 
 
 
 
      
@@ -4452,13 +4716,13 @@ a host address.
      
       
@@ -4466,13 +4730,13 @@ an IPv6 address.
      
       
@@ -4480,13 +4744,13 @@ Obsolete format of IPv6 address
      
       
@@ -4494,13 +4758,13 @@ AFSDB
      
       
@@ -4508,13 +4772,13 @@ identifies the canonical name of an alias.
      
       
@@ -4522,13 +4786,13 @@ for delegation of reverse addresses. Replaces the domain name specified with ano
 
@@ -4536,13 +4800,13 @@ identifies the CPU and OS used by a host.
      
       
@@ -4550,13 +4814,13 @@ ISDN
      
       
@@ -4564,13 +4828,13 @@ stores a public key associated with a DNS name.
      
       
@@ -4578,13 +4842,13 @@ LOC
      
       
@@ -4592,13 +4856,13 @@ identifies a mail exchange for the domain.  See RFC 974 for details.
      
       
@@ -4606,13 +4870,13 @@ the authoritative nameserver for the domain.
      
       
@@ -4620,13 +4884,13 @@ used in DNSSEC to securely indicate that RRs with an owner name in a certain nam
 
@@ -4634,13 +4898,13 @@ a pointer to another part of the domain name space.
      
       
@@ -4648,13 +4912,13 @@ RP
      
       
@@ -4662,13 +4926,13 @@ RT
      
       
@@ -4676,13 +4940,13 @@ SIG
      
       
@@ -4690,13 +4954,13 @@ identifies the start of a zone of authority.
      
       
@@ -4704,13 +4968,13 @@ information about well known network services (replaces WKS).
      
       
@@ -4718,20 +4982,20 @@ WKS
      
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 allow-query
-
      
+
      
       		
 
 
      
-
-
+
+ 
 See the description of 
 allow-query
- under 
+ under 
 Access Control
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 allow-transfer
-
      
+
      
       		
 
 
      
-
-
+
+ 
 See the description of 
 allow-transfer
- under 
+ under 
 Access Control
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 allow-update
-
      
+
      
       		
 
 
      
-
-
+
+ 
 Specifies which hosts are allowed to submit Dynamic DNS updates for master zones. The default is to deny updates from all hosts.
      
       		
 
      
 
      
 
-
      
-
-
-update-policy
      
+
      
+
+ 
+
+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.
 
      
@@ -3890,17 +4167,17 @@ Update forwarding is not yet implemented.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 also-notify
-
      
+
      
       		
 
 
      
-
-
+
+ 
 Only meaningful if 
 notify
  is active for this zone. The set of machines that will receive a 
@@ -3918,18 +4195,18 @@ Not yet implemented in BINDv9.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 check-names
-
      
+
      
       		
 
 
      
-
-
-See 
+
+ 
+See 
 Name Checking
 .
      
 
@@ -3939,20 +4216,20 @@ Not yet implemented in BINDv9.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 dialup
-
      
+
      
       		
 
 
      
-
-
+
+ 
 See the description of 
 dialup
- under 
+ under 
 Boolean Options
 .
      
 
@@ -3962,17 +4239,17 @@ Not yet implemented in BINDv9.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 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 
@@ -3985,23 +4262,23 @@ Not yet implemented in BINDv9.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 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.
 
      
@@ -4009,149 +4286,153 @@ Not yet implemented in BINDv9.
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 ixfr-base
-
      
+
      
       		
 
 
      
-
-
+
+ 
 Specifies the file name for the transaction log file used for dynamic update and IXFR.
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 max-transfer-time-in
-
      
+
      
       		
 
 
      
-
-
-See the description of 
+
+ 
+See the description of
      
+
 max-transfer-time-in
- under 
+ under 
 Zone Transfers
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 max-transfer-idle-in
-
      
+
      
       		
 
 
      
-
-
-See the description of 
+
+ 
+See the description of
      
+
 max-transfer-idle-in
- under 
+ under 
 Zone Transfers
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 max-transfer-time-out
-
      
+
      
       		
 
 
      
-
-
-See the description of 
+
+ 
+See the description of
      
+
 max-transfer-time-outn
- under 
+ under 
 Zone Transfers
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 max-transfer-idle-out
-
      
+
      
       		
 
 
      
-
-
-See the description of 
+
+ 
+See the description of
      
+
 max-transfer-idle-out
- under 
+ under 
 Zone Transfers
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 notify
-
      
+
      
       		
 
 
      
-
-
+
+ 
 See the description of 
 notify
- under 
+ under 
 Boolean Options
 .
      
       		
 
      
 
      
 
-
      
-
-
+
      
+
+ 
 
 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
-
      
+
      
       		
 
 
      
-
-
+
+ 
 Determines which local address will be bound to the TCP connection used to fetch this zone. If not set, it defaults to a system controlled value which will usually be the address of the interface 
 closest to
  the remote end. This address must appear in the remote end's 
@@ -4166,12 +4447,12 @@ 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 
@@ -4179,19 +4460,19 @@ 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 
@@ -4203,45 +4484,20 @@ 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
-
- ]
-
      
+ 
+A rule definition looks like:
      
+ 
+
      +( grant | deny ) identity nametype nam [ 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
 , 
@@ -4254,65 +4510,73 @@ self
 
      
 
      
 
-
      
+
      
 
-
-name
      
+ 
+
+name
+
      
       		
 
 
      
 
-
+ 
 Matches when the updated name is the same as the name in the name field.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-subdomain
      
+ 
+
+subdomain
+
      
       		
 
 
      
 
-
+ 
 Matches when the updated name is a subdomain of the name in the name field.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-wildcard
      
+ 
+
+wildcard
+
      
       		
 
 
      
 
-
+ 
 Matches when the updated name is a valid expansion of the wildcard name in the name field.
      
       		
 
      
 
      
 
-
      
+
      
 
-
-self
      
+ 
+
+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).
      
+ 
+If no types are specified, the rule matches all types except SIG, NS, SOA, and NXT. Types may be specified by name, including "ANY" (ANY matches all types except NXT, which can never be updated).
      
 
 
 
@@ -4320,53 +4584,53 @@ If no types are specified, the rule matches all types except SIG, NS, SOA, and N
 
        
 
        
 
-
+ 
 5.3	 Zone File
        
 
      
 
      
 
        
 
        
 
-
+ 
 5.3.1	
-
+ 
 Types of Resource Records and When to Use Them
        
 
      
 
      
 
-
+ 
 This section, largely borrowed from RFC 1034, describes the concept of a Resource Record (RR) and explains when each is used. Since the publication of RFC 1034, several new RRs have been identified and implemented in the DNS. These are also included.
      
 
      
 
        
 
        
 
-
+ 
 5.3.1.1	Resource Records
        
 
      
 
      
 
-
-A domain name identifies a node.  Each node has a set of resource information, which may be empty.  The set of resource information associated with a particular name is composed of separate RRs.  The order of RRs in a set is not significant and need not be preserved by nameservers, resolvers, or other parts of the DNS. However, sorting of multiple RRs is permitted for optimization purposes, for example, to specify that a particular nearby server be tried first. See 
+ 
+A domain name identifies a node.  Each node has a set of resource information, which may be empty.  The set of resource information associated with a particular name is composed of separate RRs.  The order of RRs in a set is not significant and need not be preserved by nameservers, resolvers, or other parts of the DNS. However, sorting of multiple RRs is permitted for optimization purposes, for example, to specify that a particular nearby server be tried first. See 
 The sortlist Statement
- and 
+ and 
 RRset Ordering
  for details.
      
 
      
 
-
+ 
 The components of a RR are
      
 
@@ -4374,13 +4638,13 @@ the domain name where the RR is found.
      
@@ -4388,13 +4652,13 @@ an encoded 16 bit value that specifies the type of the resource in this resource
 
@@ -4402,13 +4666,13 @@ the time to live of the RR. This field is a 32 bit integer in units of seconds,
 
@@ -4416,20 +4680,20 @@ an encoded 16 bit value that identifies a protocol family or instance of a proto
 
      
 
      
 
 
      
 
-
+ 
 owner name
      
       		
 
 
      
 
-
+ 
 the domain name where the RR is found.
      
       		
 
      
 
      
 
      
 
-
+ 
 type
      
       		
 
 
      
 
-
+ 
 an encoded 16 bit value that specifies the type of the resource in this resource record. Types refer to abstract resources.
      
       		
 
      
 
      
 
-
+ 
 TTL
      
       		
 
 
      
 
-
+ 
 the time to live of the RR. This field is a 32 bit integer in units of seconds, and is primarily used by resolvers when they cache RRs. The TTL describes how long a RR can be cached before it should be discarded.
      
       		
 
      
 
      
 
-
+ 
 class
      
       		
 
 
      
 
-
+ 
 an encoded 16 bit value that identifies a protocol family or instance of a protocol.
      
       		
 
      
 
      
 
-
+ 
 RDATA
      
       		
 
 
      
 
-
+ 
 the type and sometimes class-dependent data that describes the resource.
      
       		
 
      
 
      
 
      
 
-
+ 
 The following are 
 types
  of valid RRs (some of these listed, although not obsolete, are experimental (x) or historical (h) and no longer in general use):
      
@@ -4438,13 +4702,13 @@ types
 
      		
 
      
 
-
+ 
 A
      
       		
 
 
      
 
-
+ 
 a host address.
      
       		
 
      
 
      
 
-
+ 
 A6
      
       		
 
 
      
 
-
+ 
 an IPv6 address.
      
       		
 
      
 
      
 
-
+ 
 AAAA
      
       		
 
 
      
 
-
+ 
 Obsolete format of IPv6 address
      
       		
 
      
 
      
 
-
+ 
 AFSDB
      
       		
 
 
      
 
-
+ 
 (x) location of AFS database servers. Experimental.
      
       		
 
      
 
      
 
-
+ 
 CNAME
      
       		
 
 
      
 
-
+ 
 identifies the canonical name of an alias.
      
       		
 
      
 
      
 
-
+ 
 DNAME
      
       		
 
 
      
 
-
+ 
 for delegation of reverse addresses. Replaces the domain name specified with another name to be looked up. Described in RFC 2672.
      
       		
 
      
 
      
 
-
+ 
 HINFO
      
       		
 
 
      
 
-
+ 
 identifies the CPU and OS used by a host.
      
       		
 
      
 
      
 
-
+ 
 ISDN
      
       		
 
 
      
 
-
+ 
 (x) representation of ISDN addresses. Experimental.
      
       		
 
      
 
      
 
-
+ 
 KEY
      
       		
 
 
      
 
-
+ 
 stores a public key associated with a DNS name.
      
       		
 
      
 
      
 
-
+ 
 LOC
      
       		
 
 
      
 
-
+ 
 (x) for storing GPS info. See RFC 1876. Experimental.
      
       		
 
      
 
      
 
-
+ 
 MX
      
       		
 
 
      
 
-
+ 
 identifies a mail exchange for the domain.  See RFC 974 for details.
      
       		
 
      
 
      
 
-
+ 
 NS
      
       		
 
 
      
 
-
+ 
 the authoritative nameserver for the domain.
      
       		
 
      
 
      
 
-
+ 
 NXT
      
       		
 
 
      
 
-
+ 
 used in DNSSEC to securely indicate that RRs with an owner name in a certain name interval do not exist in a zone and indicate what RR types are present for an existing name. See RFC 2535 for details.
      
       		
 
      
 
      
 
-
+ 
 PTR
      
       		
 
 
      
 
-
+ 
 a pointer to another part of the domain name space.
      
       		
 
      
 
      
 
-
+ 
 RP
      
       		
 
 
      
 
-
+ 
 (x) information on persons responsible for the domain. Experimental.
      
       		
 
      
 
      
 
-
+ 
 RT
      
       		
 
 
      
 
-
+ 
 (x) route-through binding for hosts that do not have their own direct wide area network addresses. Experimental.
      
       		
 
      
 
      
 
-
+ 
 SIG
      
       		
 
 
      
 
-
+ 
 ("signature") contains data authenticated in the secure DNS. See RFC 2535 for details.
      
       		
 
      
 
      
 
-
+ 
 SOA
      
       		
 
 
      
 
-
+ 
 identifies the start of a zone of authority.
      
       		
 
      
 
      
 
-
+ 
 SRV
      
       		
 
 
      
 
-
+ 
 information about well known network services (replaces WKS).
      
       		
 
      
 
      
 
-
+ 
 WKS
      
       		
 
 
      
 
-
+ 
 (h) information about which well known network services, such as SMTP, that a domain supports. Historical, replaced by newer RR SRV.
      
       		
 
      
 
      
 
-
+ 
 X25
      
       		
 
 
      
 
-
+ 
 (x) representation of X.25 network addresses. Experimental.
      
       		
 
      
 
      
 
      
 
-
+ 
 The following 
 classes
  of resource records are currently valid in the DNS:
      
@@ -4740,30 +5004,30 @@ classes
 

 

 
-
+ 
 IN

 		
 
 

 
-
+ 
 the Internet system.

 		
 

 

 
 

-
-
-For information about other, older classes of RRs, 
-See Historical DNS Information.
-.

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

 		
 

 

 

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

@@ -4772,13 +5036,13 @@ RDATA

- + A

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

- + A6

- + maps a domain name to an IPv6 address, with a provision for indirection for leading "prefix" bits.

- + CNAME

- + a domain name

- + DNAME

- + provides alternate naming to an entire subtree of the domain name space, rather than to a single node. It causes some suffix of a queried name to be substituted with a name from the DNAME record's RDATA.

- + MX

- + a 16 bit preference value (lower is better) followed by a host name willing to act as a mail exchange for the owner domain.

- + NS

- + a fully qualified domain name.

- + PTR

- + a fully qualified doman name.

- + SOA

- + several fields.

- + The owner name is often implicit, rather than forming an integral part of the RR. For example, many nameservers internally form tree or hash structures for the name space, and chain RRs off nodes. The remaining RR parts are the fixed header (type, class, TTL) which is consistent for all RRs, and a variable part (RDATA) that fits the needs of the resource being described.

- + The meaning of the TTL field is a time limit on how long an RR can be kept in a cache. This limit does not apply to authoritative data in zones; it is also timed out, but by the refreshing policies for the zone. The TTL is assigned by the administrator for the zone where the data originates. While short TTLs can be used to minimize caching, and a zero TTL prohibits caching, the realities of Internet performance suggest that these times should be on the order of days for the typical host. If a change can be anticipated, the TTL can be reduced prior to the change to minimize inconsistency during the change, and then increased back to its former value following the change.

- + The data in the RDATA section of RRs is carried as a combination of binary strings and domain names. The domain names are frequently used as "pointers" to other data in the DNS.

    - + 5.3.1.2 Textual expression of RRs

- + RRs are represented in binary form in the packets of the DNS protocol, and are usually represented in highly encoded form when stored in a nameserver or resolver. In the examples provided in RFC 1034, a style similar to that used in master files was employed in order to show the contents of RRs. In this format, most RRs are shown on a single line, although continuation lines are possible using parentheses.

- + The start of the line gives the owner of the RR. If a line begins with a blank, then the owner is assumed to be the same as that of the previous RR. Blank lines are often included for readability.

- + Following the owner, we list the TTL, type, and class of the RR. Class and type use the mnemonics defined above, and TTL is an integer before the type field. In order to avoid ambiguity in parsing, type and class mnemonics are disjoint, TTLs are integers, and the type mnemonic is always last. The IN class and TTL values are often omitted from examples in the interests of clarity.

- + The resource data or RDATA section of the RR are given using knowledge of the typical representation for the data.

- + For example, we might show the RRs carried in a message as:

@@ -4946,19 +5210,19 @@ MX

@@ -4966,19 +5230,19 @@ MX

@@ -4986,19 +5250,19 @@ A

@@ -5006,19 +5270,19 @@ A

@@ -5026,53 +5290,53 @@ A

- + ISI.EDU.

- + MX

- + 10 VENERA.ISI.EDU.

- +  

- + MX

- + 10 VAXA.ISI.EDU

- + VENERA.ISI.EDU

- + A

- + 128.9.0.32

- +  

- + A

- + 10.1.0.52

- + VAXA.ISI.EDU

- + A

- + 10.2.0.27

- +  

- + A

- + 128.9.0.33

- + The MX RRs have an RDATA section which consists of a 16 bit number followed by a domain name. The address RRs use a standard IP address format to contain a 32 bit internet address.

- + This example shows six RRs, with two RRs at each of three domain names.

- + Similarly we might see:

@@ -5080,27 +5344,27 @@ A

- + XX.LCS.MIT.EDU. IN

- + A

- + 10.0.0.44

- + CH

- + A

- + MIT.EDU. 2420

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

@@ -5109,57 +5373,57 @@ XX.LCS.MIT.EDU

    - + 5.3.2 Discussion of MX Records

- + As described above, domain servers store information as a series of resource records, each of which contains a particular piece of information about a given domain name (which is usually, but not always, a host). The simplest way to think of a RR is as a typed pair of datum, a domain name matched with relevant data, and stored with some additional type information to help systems determine when the RR is relevant.

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

- + For a given domain, if there is both a CNAME record and an MX record, the MX record is in error, and will be ignored. Instead, the mail will be delivered to the server specified in the MX record pointed to by the CNAME.

- + For example:

@@ -5167,31 +5431,31 @@ mail.foo.com.

@@ -5199,31 +5463,31 @@ mail2.foo.com.

@@ -5231,31 +5495,31 @@ mail.backup.org.

@@ -5263,71 +5527,73 @@ A

- + example.com.

- + IN

- + MX

- + 10

- + mail.foo.com.

- +  

- + IN

- + MX

- + 10

- + mail2.foo.com.

- +  

- + IN

- + MX

- + 20

- + mail.backup.org.

- + mail.example.com.

- + IN

- + A

- + 10.0.0.1

- +  

- + mail2.example.com.

- + IN

- + A

- + 10.0.0.2

- +  

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

    - -5.3.3 Setting TTLs

    + +5.3.3 + +Setting TTLs

- + The time to live of the RR field is a 32 bit integer represented in units of seconds, and is primarily used by resolvers when they cache RRs. The TTL describes how long a RR can be cached before it should be discarded. The following three types of TTL are currently used in a zone file.

- +  

@@ -5335,13 +5601,13 @@ The maximum time for negative caching is 3 hours (3h).

@@ -5349,20 +5615,20 @@ The $TTL directive at the top of the zone file (before the SOA) gives a default

- + SOA

- + The last field in the SOA is the negative caching TTL. This controls how long other servers will cache no-such-domain (NXDOMAIN) responses from you.

- + The maximum time for negative caching is 3 hours (3h).

- + $TTL

- + The $TTL directive at the top of the zone file (before the SOA) gives a default TTL for every RR without a specific TTL set.

- + RR TTLs

- + Each RR can have a TTL as the second field in the RR, which will control how long other servers can cache the it.

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

@@ -5371,12 +5637,12 @@ All of these TTLs default to units of seconds, though units can be explicitly sp

    - + 5.3.4 Inverse Mapping in IPv4

- + Reverse name resolution (i.e., translation from IP address to name) is achieved by means of the in-addr.arpa domain and PTR records. Entries in the in-addr.arpa domain are made in least-to-most significant order, read left to right. This is the opposite order to the way IP addresses are usually written. Thus, a machine with an IP address of 10.1.2.3 would have a corresponding in-addr.arpa name of
3.2.1.10.in-addr.arpa. This name should have a PTR resource record whose data field is the name of the machine or, optionally, multiple PTR records if the machine has more than one name. For example, in the example.com @@ -5386,7 +5652,7 @@ $ORIGIN 2.1.10.in-addr.arpa 3 IN PTR foo.example.com.

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

@@ -5395,16 +5661,16 @@ $ORIGIN

    - + 5.3.5 Other Zone File Directives

- + The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format itself is class independent all records in a Master File must be of the same class.

- + Master File Directives include $ORIGIN , @@ -5424,8 +5690,7 @@ $ORIGIN

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

@@ -5434,22 +5699,29 @@ $ORIGIN <domain-name> [<comment>] $ORIGIN sets the domain name that will be appended to any unqualified records. When a zone is first read in there is an implicit $ORIGIN -<zone-name> +< +zone-name +> . The current $ORIGIN is appended to the domain specified in the $ORIGIN argument if it is not absolute.

-

-$ORIGIN EXAMPLE.COM
-WWW     CNAME   MAIN-SERVER
+ +
+$ORIGIN example.com
+WWW     CNAME   MAIN-SERVER
+

is equivalent to

-

-WWW.EXAMPLE.COM CNAME MAIN-SERVER.EXAMPLE.COM.
+ +
+WWW.EXAMPLE.COM CNAME MAIN-SERVER.EXAMPLE.COM.
+
+
    @@ -5463,14 +5735,15 @@ $INCLUDE

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

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

    -Read and process the file -filename +Read and process the file +filename as if it were included into the file at this point. If origin is specified the file is processed with @@ -5481,9 +5754,9 @@ $ORIGIN

    - -NOTE -: The behavior when + +NOTE: + The behavior when origin is specified differs from that described in RFC 1035. The origin and current domain revert to the values they were prior to the $INCLUDE @@ -5501,8 +5774,10 @@ $TTL

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

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

    @@ -5531,7 +5806,33 @@ $GENERATE Syntax: -$GENERATE <range> <lhs> <type> <rhs> [<comment>] +$GENERATE < + +range + +> < + +lhs + +> < + +type + +> < + +rhs + +> + +[ + +< + +comment + +> + +]

    @@ -5566,12 +5867,12 @@ is equivalent to

    -
    +

    range -

    +

    @@ -5582,12 +5883,12 @@ This can be one of two forms: start-stop or start-stop/step. If the first form i

    -
    +

    lhs -

    +

    @@ -5612,12 +5913,12 @@ is appended to the name.

    -
    +

    type -

    +

    @@ -5628,12 +5929,12 @@ At present the only supported types are PTR, CNAME and NS.

    -
    +

    rhs -

    +

    @@ -5665,23 +5966,23 @@ It is not yet implemented in BINDv9. Certain UNIX signals cause the name server to take specific actions, as described in the following table. These signals can be sent using the kill command.

    -

    - +

    + -  

    + 

    -
    - +

    + SIGHUP -

    +

    - + Causes the server to read named.conf @@ -5690,51 +5991,55 @@ named.conf

    -
    - +

    + SIGTERM -

    +

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

    + + + +SIGINT +

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

    + -SIGQUIT

    + +SIGQUIT +

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

    Return to BINDv9 Administrator Reference Manual table of contents.

    +

    Return to BINDv9 Administrator Reference Manual diff --git a/doc/arm/BV9ARM.6.html b/doc/arm/Bv9ARM.6.html similarity index 76% rename from doc/arm/BV9ARM.6.html rename to doc/arm/Bv9ARM.6.html index 1e0348a35b..a9d4e81478 100644 --- a/doc/arm/BV9ARM.6.html +++ b/doc/arm/Bv9ARM.6.html @@ -2,27 +2,27 @@ - + Section 6. Security Considerations

      - + 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 , @@ -34,58 +34,63 @@ 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; };
    + +
    +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; };
    -
    
+ 
+// 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 {
   ...
   ...
-  allow-query { our-nets; };
-  allow-recursion { our-nets; };
+  allow-query { our-nets; };
+  allow-recursion { our-nets; };
   ...
   blackhole { bogusnets; };
   ...
-};
    
-
    
-zone "example.com" {
-  type master;
-  file "m/example.com";
-  allow-query { any; };
-};
    
+};
+
+zone "example.com" {
+  type master;
+  file "m/example.com";
+  allow-query { any; };
+};    
+
    +

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

    - + For more information on how to use ACLs to protect your server, see the AUSCERT advisory at
    - + ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos

    @@ -93,7 +98,7 @@ ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos

      - + 6.2 chroot and @@ -102,7 +107,7 @@ setuid

    - + On UNIX servers, it is possible to run BIND in a chrooted environment ( @@ -112,15 +117,17 @@ 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> ). We suggest running as a nonprivileged user when using the + < +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,
    @@ -131,35 +138,36 @@ named     setuid to user 202:

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

      - + 6.2.1 The chroot - environment

      + Environment

    - + In order for a chroot() - environment to work properly in a particular directory (e.g. + 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 +, 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 + +If you are running an operating system that supports static binaries, you can also compile BIND statically and avoid the need to copy system libraries over to your chroot() sandbox.

    @@ -167,14 +175,14 @@ chroot()

      - -6.2.2 Using + +6.2.2 Using the setuid -

      + Function

    - + Prior to running the named daemon, use the @@ -188,18 +196,18 @@ chown

      - -6.3 Dynamic updates

      + +6.3 Dynamic Updates

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

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

    -

    Return to BINDv9 Administrator Reference Manual table of contents.

    +

    Return to BINDv9 Administrator Reference Manual diff --git a/doc/arm/BV9ARM.7.html b/doc/arm/Bv9ARM.7.html similarity index 60% rename from doc/arm/BV9ARM.7.html rename to doc/arm/Bv9ARM.7.html index 322ee56001..1ffdba6bff 100644 --- a/doc/arm/BV9ARM.7.html +++ b/doc/arm/Bv9ARM.7.html @@ -2,177 +2,225 @@ - + Section 7. Troubleshooting

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

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

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

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

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

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

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

      - + no root nameserver for class
    -
    
-findns: No root nameservers for class IN?
    +
     
+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.

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

      - + address already in use
    -
    
-ctl_server: bind: 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.

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

      - + 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,49 +229,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, 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 -info@isc.org -or visit the ISC web page at -the ISC web site + +To discuss arrangements for support, contact +info@isc.org + + +or visit the ISC web page at
    + +http://www.isc.org/services/support/ to read more.

    -

    - - - 

    - +
    -

    Return to BINDv9 Administrator Reference Manual table of contents.

    diff --git a/doc/arm/BV9ARM.8.html b/doc/arm/Bv9ARM.8.html similarity index 81% rename from doc/arm/BV9ARM.8.html rename to doc/arm/Bv9ARM.8.html index e6fc8cdfe9..2b90ab3114 100644 --- a/doc/arm/BV9ARM.8.html +++ b/doc/arm/Bv9ARM.8.html @@ -2,121 +2,135 @@ - + Appendices -
      -

      - - -Appendices

      -
    -
    -

    +

    + + +Appendices
    +
    +
    - -Appendix A. Acknowledgements
    + +Appendix A. Acknowledgements
    -

    +

    - -A Brief History of the DNS and BIND
    + +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
    + +Appendix B. Historical DNS Information
    -

    +

    - -Classes of resource records
    + +Classes of resource records
    - - + + HS = hesiod
    +

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

    - - + + CH = chaos
    +

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

    -

    Return to BINDv9 Administrator Reference Manual table of contents.

    -

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

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

    +

    - -Request for Comments (RFCs)
    + + + +C.1 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

    -

    +. January 1986.

    +

    - + 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 +138,37 @@ 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,31 +176,29 @@ 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 -for current versions.) -

    -

    + the following list of RFCs are undergoing major revision by the IETF. (See the Internet Drafts section, below, 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 +206,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,53 +230,47 @@ 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 - + +RFC2163. Allocchio, A. U sing the Internet DNS to Distribute MIXER Conformant Global Address Mapping - -. - -January 1998. -

    -

    +.January 1998.

    +

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

    @@ -270,29 +278,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 +308,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,86 +338,90 @@ 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.

    -

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

    -
    - + Obsolete and Unimplemented Experimental RRs
    -

    +

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

    -
    - + - -Internet Drafts
    + +C.2 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
    @@ -448,17 +460,17 @@ draft-skwan-utf8-dns-02.txt

    - -Electronic Mail Communication
    + +C.3 Electronic Mail Communication

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

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

    @@ -466,16 +478,17 @@ TSIG guide for BIND 8.2+
    - -Other BIND Documents
    + +C.4 Other BIND Documents

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

    -

    Return to BINDv9 Administrator Reference Manual table of contents.

    +

    Return to BINDv9 Administrator Reference Manual table of contents.

    +
    diff --git a/doc/arm/BV9ARM.css b/doc/arm/Bv9ARM.css similarity index 80% rename from doc/arm/BV9ARM.css rename to doc/arm/Bv9ARM.css index 0b2bed3931..7b74b2ac41 100644 --- a/doc/arm/BV9ARM.css +++ b/doc/arm/Bv9ARM.css @@ -24,7 +24,7 @@ H1.1Level, H2.1Level, H3.1Level, H4.1Level, H5.1Level, H6.1Level { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } P.1LevelContinued { text-align: left; @@ -40,23 +40,7 @@ P.1LevelContinued { 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; + font-family: Times; } H1.2Level, H2.2Level, H3.2Level, H4.2Level, H5.2Level, H6.2Level { text-align: left; @@ -72,7 +56,7 @@ H1.2Level, H2.2Level, H3.2Level, H4.2Level, H5.2Level, H6.2Level { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } LI.2Level-bullet1 { text-align: left; @@ -106,37 +90,21 @@ LI.2Level-bullet2 { text-transform: none; font-family: Times; } -PRE.2Level-fixed { +P.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-size: 11.000000pt; + font-weight: medium; 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; + font-family: Courier New; } LI.2Level-numList1 { text-align: left; @@ -184,54 +152,6 @@ P.2LevelContinued { 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 { @@ -248,39 +168,39 @@ H1.3Level, H2.3Level, H3.3Level, H4.3Level, H5.3Level, H6.3Level { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } -PRE.3Level-fixed { +P.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-size: 9.000000pt; + font-weight: medium; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -P.3Level-fixed1 { +P.3Level-fixed-special { 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-size: 9.000000pt; font-weight: medium; font-style: Regular; - color: #ff00ff; + color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } P.3LevelContinued { text-align: left; @@ -296,9 +216,9 @@ P.3LevelContinued { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times New Roman; + font-family: Times; } -P.3LevelContinued1 { +H1.3LevelContinued1, H2.3LevelContinued1, H3.3LevelContinued1, H4.3LevelContinued1, H5.3LevelContinued1, H6.3LevelContinued1 { text-align: left; text-indent: 0.000000pt; margin-top: 13.000000pt; @@ -312,55 +232,7 @@ P.3LevelContinued1 { 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; + font-family: Times New Roman; } H1.4Level, H2.4Level, H3.4Level, H4.4Level, H5.4Level, H6.4Level { text-align: left; @@ -376,9 +248,9 @@ H1.4Level, H2.4Level, H3.4Level, H4.4Level, H5.4Level, H6.4Level { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } -LI.4Level-bullet1 { +H1.4Level-bullet1, H2.4Level-bullet1, H3.4Level-bullet1, H4.4Level-bullet1, H5.4Level-bullet1, H6.4Level-bullet1 { text-align: left; text-indent: 72.000000pt; margin-top: 13.000000pt; @@ -410,53 +282,37 @@ LI.4Level-bullet2 { 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 { +P.4Level-fixed { 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-size: 9.000000pt; + font-weight: medium; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; +} +P.4Level-fixedSmall { + text-align: left; + text-indent: 0.000000pt; + margin-top: 2.000000pt; + margin-bottom: 0.000000pt; + margin-right: 0.000000pt; + margin-left: 126.000000pt; + font-size: 9.000000pt; + font-weight: medium; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; } P.4LevelContinued { text-align: left; @@ -472,25 +328,9 @@ P.4LevelContinued { 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 { +P.ActiveTOC { text-align: justify; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -504,7 +344,7 @@ THROW AWAY.ActiveTOC { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times New Roman; + font-family: Times; } H1.AppendixLevel1, H2.AppendixLevel1, H3.AppendixLevel1, H4.AppendixLevel1, H5.AppendixLevel1, H6.AppendixLevel1 { text-align: left; @@ -522,7 +362,7 @@ H1.AppendixLevel1, H2.AppendixLevel1, H3.AppendixLevel1, H4.AppendixLevel1, H5.A text-transform: none; font-family: Arial; } -THROW AWAY.AppendixLevel1TOC { +P.AppendixLevel1TOC { text-align: left; text-indent: 0.000000pt; margin-top: 14.000000pt; @@ -554,7 +394,7 @@ H1.AppendixLevel2, H2.AppendixLevel2, H3.AppendixLevel2, H4.AppendixLevel2, H5.A text-transform: none; font-family: Arial; } -THROW AWAY.AppendixLevel2TOC { +P.AppendixLevel2TOC { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -586,7 +426,7 @@ H1.AppendixLevel3, H2.AppendixLevel3, H3.AppendixLevel3, H4.AppendixLevel3, H5.A text-transform: none; font-family: Arial; } -THROW AWAY.AppendixLevel3TOC { +P.AppendixLevel3TOC { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -618,7 +458,7 @@ P.Bib2 { text-transform: none; font-family: Times New Roman; } -P.Bib3 { +P.Bib31 { text-align: left; text-indent: -9.000000pt; margin-top: 4.000000pt; @@ -634,7 +474,7 @@ P.Bib3 { text-transform: none; font-family: Times New Roman; } -P.Bib31 { +P.Biblio { text-align: left; text-indent: -9.000000pt; margin-top: 4.000000pt; @@ -648,7 +488,7 @@ P.Bib31 { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times; + font-family: Times New Roman; } P.Body { text-align: left; @@ -667,6 +507,22 @@ P.Body { font-family: Times; } P.Body1 { + 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 New; +} +P.Body11 { text-align: left; text-indent: 0.000000pt; margin-top: 6.000000pt; @@ -696,7 +552,7 @@ P.CellBody { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times New Roman; + font-family: Times; } P.CellBody-fixedfont { text-align: left; @@ -705,14 +561,14 @@ P.CellBody-fixedfont { margin-bottom: 0.000000pt; margin-right: 0.000000pt; margin-left: 0.000000pt; - font-size: 10.000000pt; - font-weight: Medium; + font-size: 6.000000pt; + font-weight: Bold; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } P.CellBody-fixedfontLG { text-align: left; @@ -721,32 +577,48 @@ P.CellBody-fixedfontLG { margin-bottom: 0.000000pt; margin-right: 0.000000pt; margin-left: 0.000000pt; - font-size: 10.000000pt; - font-weight: Medium; + font-size: 8.000000pt; + font-weight: medium; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -P.CellBody-fixedfontLG1 { +H1.CellBody1, H2.CellBody1, H3.CellBody1, H4.CellBody1, H5.CellBody1, H6.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: 10.000000pt; - font-weight: Medium; + font-size: 9.000000pt; + font-weight: medium; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -P.CellBody1 { +H1.CellBody2, H2.CellBody2, H3.CellBody2, H4.CellBody2, H5.CellBody2, H6.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: medium; + font-style: Italic; + color: #ff00ff; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Times; +} +H1.CellBody3, H2.CellBody3, H3.CellBody3, H4.CellBody3, H5.CellBody3, H6.CellBody3 { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -762,167 +634,119 @@ P.CellBody1 { text-transform: none; font-family: Times; } -P.CellBody11 { +H1.CellBody4, H2.CellBody4, H3.CellBody4, H4.CellBody4, H5.CellBody4, H6.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: 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-size: 9.000000pt; font-weight: Bold; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -H1.CellBody21, H2.CellBody21, H3.CellBody21, H4.CellBody21, H5.CellBody21, H6.CellBody21 { +H1.CellBody5, H2.CellBody5, H3.CellBody5, H4.CellBody5, H5.CellBody5, H6.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: 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-size: 9.000000pt; font-weight: medium; - font-style: Oblique; + font-style: Italic; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -P.CellBody4 { +H1.CellBody6, H2.CellBody6, H3.CellBody6, H4.CellBody6, H5.CellBody6, H6.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: 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-size: 9.000000pt; font-weight: Bold; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } -P.CellBody6 { +P.CellBody7 { 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-size: 9.000000pt; font-weight: medium; - font-style: Oblique; + font-style: Italic; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } -P.comment { +P.CellBody8 { text-align: left; text-indent: 0.000000pt; - margin-top: 13.000000pt; + margin-top: 0.000000pt; margin-bottom: 0.000000pt; margin-right: 0.000000pt; - margin-left: 144.000000pt; + margin-left: 0.000000pt; font-size: 11.000000pt; font-weight: medium; font-style: Regular; color: #000000; - text-decoration: none; + text-decoration: underline ; 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; + font-family: Times; } THROW AWAY.Footer { - text-align: justify; + 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-size: 9.000000pt; font-weight: medium; font-style: Regular; - color: #ffffff; + color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times New Roman; + font-family: Arial; } -THROW AWAY.Footer1 { +P.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: 9.000000pt; + font-weight: medium; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Helvetica; +} +P.Header { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -936,39 +760,7 @@ THROW AWAY.Footer1 { 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; + font-family: Arial; } P.Mapping-Table-Cell { text-align: left; @@ -1002,104 +794,8 @@ P.Mapping-Table-Cell1 { 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-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; margin-bottom: 0.000000pt; @@ -1108,7 +804,7 @@ P.Mapping-Table-Cell16 { font-size: 18.000000pt; font-weight: Bold; font-style: Regular; - color: #ffffff; + color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; @@ -1156,13 +852,29 @@ P.Mapping-Table-Cell31 { font-size: 14.000000pt; font-weight: Bold; font-style: Regular; - color: #000000; + color: #ffffff; text-decoration: none; vertical-align: baseline; text-transform: none; font-family: Helvetica; } -P.Mapping-Table-Cell32 { +P.Mapping-Table-Cell310 { + text-align: left; + text-indent: 0.000000pt; + margin-top: 0.000000pt; + margin-bottom: 0.000000pt; + margin-right: 0.000000pt; + margin-left: 0.000000pt; + font-size: 9.000000pt; + font-weight: Bold; + font-style: Regular; + color: #ffffff; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier; +} +P.Mapping-Table-Cell311 { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -1170,15 +882,15 @@ P.Mapping-Table-Cell32 { margin-right: 0.000000pt; margin-left: 0.000000pt; font-size: 11.000000pt; - font-weight: Bold; + font-weight: medium; font-style: Regular; - color: #000000; + color: #ffffff; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Times; } -P.Mapping-Table-Cell33 { +P.Mapping-Table-Cell312 { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -1194,7 +906,7 @@ P.Mapping-Table-Cell33 { text-transform: none; font-family: Helvetica; } -P.Mapping-Table-Cell4 { +P.Mapping-Table-Cell313 { text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; @@ -1204,14 +916,14 @@ P.Mapping-Table-Cell4 { font-size: 10.000000pt; font-weight: Bold; font-style: Regular; - color: #ffffff; + color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Times; } -P.Mapping-Table-Cell5 { - text-align: justify; +P.Mapping-Table-Cell314 { + text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; margin-bottom: 0.000000pt; @@ -1220,14 +932,46 @@ P.Mapping-Table-Cell5 { font-size: 14.000000pt; font-weight: Bold; font-style: Regular; - color: #ffffff; + color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; font-family: Arial; } -P.Mapping-Table-Cell6 { - text-align: justify; +P.Mapping-Table-Cell315 { + 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: Arial; +} +P.Mapping-Table-Cell316 { + text-align: left; + text-indent: 0.000000pt; + margin-top: 0.000000pt; + margin-bottom: 0.000000pt; + margin-right: 0.000000pt; + margin-left: 0.000000pt; + font-size: 9.000000pt; + font-weight: Bold; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; +} +P.Mapping-Table-Cell32 { + text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; margin-bottom: 0.000000pt; @@ -1240,10 +984,74 @@ P.Mapping-Table-Cell6 { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Arial; + font-family: Helvetica; } -P.Mapping-Table-Cell7 { - text-align: justify; +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: 11.000000pt; + font-weight: medium; + font-style: Italic; + color: #ffffff; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Times; +} +P.Mapping-Table-Cell34 { + 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: Helvetica; +} +P.Mapping-Table-Cell35 { + 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: #ffffff; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier; +} +P.Mapping-Table-Cell36 { + 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: #ffffff; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier; +} +P.Mapping-Table-Cell37 { + text-align: left; text-indent: 0.000000pt; margin-top: 0.000000pt; margin-bottom: 0.000000pt; @@ -1256,26 +1064,42 @@ P.Mapping-Table-Cell7 { text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Times New Roman; + font-family: Courier; } -P.Mapping-Table-Cell8 { - text-align: justify; +P.Mapping-Table-Cell38 { + 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-size: 11.000000pt; font-weight: Bold; - font-style: Italic; + font-style: Regular; color: #ffffff; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Helvetica; } -P.Mapping-Table-Cell9 { - text-align: justify; +P.Mapping-Table-Cell39 { + text-align: left; + text-indent: 0.000000pt; + margin-top: 0.000000pt; + margin-bottom: 0.000000pt; + margin-right: 0.000000pt; + margin-left: 0.000000pt; + font-size: 9.000000pt; + font-weight: medium; + font-style: Oblique; + color: #ffffff; + 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; @@ -1306,7 +1130,7 @@ P.Mapping-Table-Title { text-transform: none; font-family: Times; } -H1.Subhead2, H2.Subhead2, H3.Subhead2, H4.Subhead2, H5.Subhead2, H6.Subhead2 { +LI.Subhead2 { text-align: left; text-indent: 63.000000pt; margin-top: 12.000000pt; @@ -1320,39 +1144,7 @@ H1.Subhead2, H2.Subhead2, H3.Subhead2, H4.Subhead2, H5.Subhead2, H6.Subhead2 { 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; + font-family: Arial; } H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title { text-align: center; @@ -1370,15 +1162,17 @@ H1.Title, H2.Title, H3.Title, H4.Title, H5.Title, H6.Title { 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; + font-size: 9.000000pt; + font-weight: medium; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; } EM.Comment { font-size: 11.000000pt; @@ -1390,71 +1184,103 @@ EM.Comment { text-transform: none; font-family: Times; } -EM.Comment21 { - font-size: 10.000000pt; - font-style: Italic; - color: #ff00ff; - font-family: Arial; -} EM.doc-title { + font-size: 10.000000pt; + font-weight: medium; font-style: Italic; -} -EM.doc-title1 { - font-style: Italic; - font-family: Times New Roman; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Times; } EM.Emphasis { font-style: Italic; } +EM.Emphasis-underline { + font-size: 11.000000pt; + font-weight: medium; + font-style: Regular; + color: #000000; + text-decoration: underline ; + vertical-align: baseline; + text-transform: none; + font-family: Times; +} +EM.EquationVariables { + font-style: Italic; +} EM.grammar_literal { - font-size: 10.000000pt; + font-size: 9.000000pt; font-weight: Bold; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Courier; + font-family: Courier New; } -KBD.Literal-user-input { +TT.Literal-user-input { + font-size: 9.000000pt; + font-weight: Bold; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; } EM.Optional-meta-syntax { - font-size: 11.000000pt; + font-size: 9.000000pt; font-weight: medium; font-style: Italic; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; } EM.pathname { font-size: 10.000000pt; font-style: Italic; } EM.production_target { - font-size: 10.000000pt; + font-size: 9.000000pt; font-weight: Bold; font-style: Regular; color: #000000; text-decoration: none; vertical-align: baseline; text-transform: none; - font-family: Helvetica; + font-family: Arial; } CODE.Program-Process { - font-size: 12.000000pt; + font-size: 9.000000pt; font-weight: Bold; - font-family: Courier; + font-style: Regular; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Courier New; } 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; + font-family: Times; +} +EM.variable { + font-size: 9.000000pt; + font-weight: medium; + font-style: Italic; + color: #000000; + text-decoration: none; + vertical-align: baseline; + text-transform: none; + font-family: Arial; } diff --git a/doc/arm/BV9ARM.html b/doc/arm/Bv9ARM.html similarity index 57% rename from doc/arm/BV9ARM.html rename to doc/arm/Bv9ARM.html index c16274a72b..e2296cb59b 100644 --- a/doc/arm/BV9ARM.html +++ b/doc/arm/Bv9ARM.html @@ -2,19 +2,19 @@ - - + +BINDv9 Administrator Reference Manual +
    -ISC logo +ISC logo
    -

    BIND version 9
    Administrator Reference Manual

    DRAFT
    -March 19, 2000

    +May, 2000
    @@ -22,39 +22,46 @@ March 19, 2000

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

    + +
    + + +Table of Contents
    +

      - + Section 1. Introduction

      - + Section 2. BIND Resource Requirements

      - + Section 3. Nameserver Configuration

      - + Section 4. Advanced Concepts

      - + Section 5. BINDv9 Configuration Reference

      - + Section 6. Security Considerations

      - + Section 7. Troubleshooting

      - + Appendices -

      -
    + +
    + diff --git a/doc/arm/Bv9ARM.pdf b/doc/arm/Bv9ARM.pdf new file mode 100755 index 0000000000..6ccd799352 Binary files /dev/null and b/doc/arm/Bv9ARM.pdf differ