diff --git a/CHANGES b/CHANGES index 35f351af4e..4f89b3ea9d 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,6 @@ +4237. [doc] Upgraded documentation toolchain to use DocBook 5 + and dblatex. [RT #40766] + 4236. [func] On machines with 2 or more processors (CPU), the default value for the number of UDP listeners has been changed to the number of detected diff --git a/FAQ.xml b/FAQ.xml index 9c56f8123f..e06c82eebd 100644 --- a/FAQ.xml +++ b/FAQ.xml @@ -1,5 +1,3 @@ - - - - -
- Frequently Asked Questions about BIND 9 - + +
+ + 2004 2005 @@ -41,10 +37,10 @@ 2003 Internet Software Consortium. - - + + - Compilation and Installation Questions + @@ -96,7 +92,7 @@ - Configuration and Setup Questions + @@ -501,7 +497,7 @@ Master 10.0.1.1: You are running chrooted (-t) and have not supplied local timezone information in the chroot area. - + FreeBSD: /etc/localtime Solaris: /etc/TIMEZONE and /usr/share/lib/zoneinfo OSF: /etc/zoneinfo/localtime @@ -697,7 +693,7 @@ server ::/0 { bogus yes; }; - Operations Questions + @@ -767,7 +763,7 @@ server ::/0 { bogus yes; }; - General Questions + @@ -807,9 +803,8 @@ server ::/0 { bogus yes; }; of sending dynamic update requests to DNS servers without being specifically configured to do so. If the update requests are coming from a Windows 2000 machine, see - - <http://support.microsoft.com/support/kb/articles/q246/8/04.asp> + + <http://support.microsoft.com/support/kb/articles/q246/8/04.asp> for information about how to turn them off. @@ -959,7 +954,7 @@ serial-query-rate 5; // default 20 usage rules and are leaking queries to the Internet. You should establish your own zones for these addresses to prevent you querying the Internet's name servers for these addresses. - Please see <http://as112.net/> + Please see <http://as112.net/> for details of the problems you are causing and the counter measures that have had to be deployed. @@ -1084,9 +1079,9 @@ empty: - Operating-System Specific Questions + - HPUX + @@ -1112,7 +1107,7 @@ configure: error: need either working unistd.h or sys/select.h - Linux + @@ -1129,7 +1124,7 @@ client: UDP client handler shutting down due to fatal receive error: unexpected See: - <http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2> + <http://marc.theaimsgroup.com/?l=linux-netdev&m=113081708031466&w=2> @@ -1146,9 +1141,9 @@ client: UDP client handler shutting down due to fatal receive error: unexpected non-blocking is ignored. It is reported that setting xfrm_larval_drop to 1 helps but this may have negative side effects. See: -<https://bugzilla.redhat.com/show_bug.cgi?id=427629> +<https://bugzilla.redhat.com/show_bug.cgi?id=427629> and -<http://lkml.org/lkml/2007/12/4/260>. +<http://lkml.org/lkml/2007/12/4/260>. xfrm_larval_drop can be set to 1 by the following procedure: @@ -1244,8 +1239,7 @@ modprobe capability Red Hat have adopted the National Security Agency's - SELinux security policy (see <http://www.nsa.gov/selinux>) + SELinux security policy (see <http://www.nsa.gov/selinux>) and recommendations for BIND security , which are more secure than running named in a chroot and make use of the bind-chroot environment unnecessary . @@ -1403,8 +1397,8 @@ named_cache_t: for files modifiable by named - $ROOTDIR/var/{tmp,named/{slaves,d - Ubuntu uses AppArmor - <http://en.wikipedia.org/wiki/AppArmor> in + Ubuntu uses AppArmor + <http://en.wikipedia.org/wiki/AppArmor> in addition to normal file system permissions to protect the system. @@ -1441,7 +1435,7 @@ proc /var/named/proc proc defaults 0 0 - Windows + @@ -1492,7 +1486,7 @@ options { - FreeBSD + @@ -1513,15 +1507,15 @@ rand_irqs="3 14 15" See also - - <http://people.freebsd.org/~dougb/randomness.html>. + + <http://people.freebsd.org/~dougb/randomness.html>. - Solaris + @@ -1534,17 +1528,16 @@ rand_irqs="3 14 15" Sun has a blog entry describing how to do this. - + <http://blogs.sun.com/roller/page/anay/Weblog?catname=%2FSolaris> - + - Apple Mac OS X + @@ -1558,7 +1551,7 @@ rand_irqs="3 14 15" -% sudo rndc-confgen > /etc/rndc.conf +% sudo rndc-confgen > /etc/rndc.conf Copy the key statement from /etc/rndc.conf into /etc/rndc.key, e.g.: diff --git a/bin/check/named-checkconf.docbook b/bin/check/named-checkconf.docbook index 895e28fad6..fcfea88ea9 100644 --- a/bin/check/named-checkconf.docbook +++ b/bin/check/named-checkconf.docbook @@ -1,6 +1,5 @@ -]> +]> - - + + + + 2014-01-10 + - January 10, 2014 + ISC + Internet Systems Consortium, Inc. @@ -53,21 +56,21 @@ - + named-checkconf - - - - - filename - - - + + + + + filename + + + - - DESCRIPTION + DESCRIPTION + named-checkconf checks the syntax, but not the semantics, of a named configuration file. The file is parsed @@ -85,10 +88,10 @@ successful. named-checkconf can be run on these files explicitly, however. - + - - OPTIONS + OPTIONS + @@ -177,18 +180,18 @@ - + - - RETURN VALUES + RETURN VALUES + named-checkconf returns an exit status of 1 if errors were detected and 0 otherwise. - + - - SEE ALSO + SEE ALSO + named8 , @@ -197,16 +200,5 @@ , BIND 9 Administrator Reference Manual. - - - - AUTHOR - Internet Systems Consortium - - - - + + diff --git a/bin/check/named-checkzone.docbook b/bin/check/named-checkzone.docbook index 491064df46..f0ad4b3dfd 100644 --- a/bin/check/named-checkzone.docbook +++ b/bin/check/named-checkzone.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-19 + - February 19, 2014 + ISC + Internet Systems Consortium, Inc. @@ -59,68 +60,68 @@ - + named-checkzone - - - - - - - - - - - - - - - - - - - - - - - - - - zonename - filename + + + + + + + + + + + + + + + + + + + + + + + + + + zonename + filename - + named-compilezone - - - - - - - - - - - - - - - - - - - - - - - - zonename - filename + + + + + + + + + + + + + + + + + + + + + + + + zonename + filename - - DESCRIPTION + DESCRIPTION + named-checkzone checks the syntax and integrity of a zone file. It performs the same checks as named does when loading a @@ -138,10 +139,10 @@ least be as strict as those specified in the named configuration file. - + - - OPTIONS + OPTIONS + @@ -506,18 +507,18 @@ - + - - RETURN VALUES + RETURN VALUES + named-checkzone returns an exit status of 1 if errors were detected and 0 otherwise. - + - - SEE ALSO + SEE ALSO + named8 , @@ -527,16 +528,6 @@ RFC 1035, BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/confgen/ddns-confgen.docbook b/bin/confgen/ddns-confgen.docbook index 2c27b77c13..a4b0c90b78 100644 --- a/bin/confgen/ddns-confgen.docbook +++ b/bin/confgen/ddns-confgen.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-03-06 + - March 6, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,29 +43,29 @@ - + tsig-keygen - - - - name + + + + name - + ddns-confgen - - - - - - - -s name - -z zone + + + + + + + -s name + -z zone - - DESCRIPTION + DESCRIPTION + tsig-keygen and ddns-confgen are invocation methods for a utility that generates keys for use @@ -101,10 +102,10 @@ if nsupdate is to be used from a remote system. - + - - OPTIONS + OPTIONS + @@ -209,10 +210,10 @@ - + - - SEE ALSO + SEE ALSO + nsupdate1 , @@ -224,16 +225,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/confgen/rndc-confgen.docbook b/bin/confgen/rndc-confgen.docbook index e169c83bd1..f125a9f550 100644 --- a/bin/confgen/rndc-confgen.docbook +++ b/bin/confgen/rndc-confgen.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2013-03-14 + - March 14, 2013 + ISC + Internet Systems Consortium, Inc. @@ -52,24 +53,24 @@ - + rndc-confgen - - - - - - - - - - - + + + + + + + + + + + - - DESCRIPTION + DESCRIPTION + rndc-confgen generates configuration files for rndc. It can be used as a @@ -84,10 +85,10 @@ and a controls statement altogether. - + - - OPTIONS + OPTIONS + @@ -253,10 +254,10 @@ - + - - EXAMPLES + EXAMPLES + To allow rndc to be used with no manual configuration, run @@ -271,10 +272,10 @@ rndc-confgen - + - - SEE ALSO + SEE ALSO + rndc8 , @@ -286,16 +287,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/delv/delv.docbook b/bin/delv/delv.docbook index 4bd6e8ad6d..1c4abf2bdb 100644 --- a/bin/delv/delv.docbook +++ b/bin/delv/delv.docbook @@ -1,6 +1,5 @@ -]> +]> - - - + + + + 2014-04-23 + - April 23, 2014 + ISC + Internet Systems Consortium, Inc. @@ -43,46 +45,46 @@ - + delv - @server - - - - - - - - - - - - - name - type - class + @server + + + + + + + + + + + + + name + type + class queryopt - + delv - + - + delv - + - + delv queryopt query - - DESCRIPTION + DESCRIPTION + delv (Domain Entity Lookup & Validation) is a tool for sending DNS queries and validating the results, using the same internal @@ -123,10 +125,10 @@ delv will perform an NS query for "." (the root zone). - + - - SIMPLE USAGE + SIMPLE USAGE + A typical invocation of delv looks like: @@ -190,10 +192,10 @@ - + - - OPTIONS + OPTIONS + @@ -392,10 +394,10 @@ - + - - QUERY OPTIONS + QUERY OPTIONS + delv provides a number of query options which affect the way results are @@ -662,16 +664,16 @@ - + - - FILES + FILES + /etc/bind.keys /etc/resolv.conf - + - - SEE ALSO + SEE ALSO + dig1 , @@ -684,9 +686,6 @@ RFC5074, RFC5155. - - + + + diff --git a/bin/dig/dig.docbook b/bin/dig/dig.docbook index 699afe5a5d..3177abaaa2 100644 --- a/bin/dig/dig.docbook +++ b/bin/dig/dig.docbook @@ -1,6 +1,5 @@ -]> +]> - - - + + + + 2014-02-19 + - February 19, 2014 + ISC + Internet Systems Consortium, Inc. @@ -60,42 +62,42 @@ - + dig - @server - - - - - - - - - - - - - - name - type - class + @server + + + + + + + + + + + + + + name + type + class queryopt - + dig - + - + dig global-queryopt query - - DESCRIPTION + DESCRIPTION + dig (domain information groper) is a flexible tool for interrogating DNS name servers. It performs DNS lookups and @@ -146,10 +148,10 @@ use "IN." and "CH." when looking up these top level domains. - + - - SIMPLE USAGE + SIMPLE USAGE + A typical invocation of dig looks like: @@ -212,10 +214,10 @@ - + - - OPTIONS + OPTIONS + @@ -415,10 +417,10 @@ - + - - QUERY OPTIONS + QUERY OPTIONS + dig provides a number of query options which affect @@ -1154,10 +1156,10 @@ - + - - MULTIPLE QUERIES + MULTIPLE QUERIES + The BIND 9 implementation of dig @@ -1203,10 +1205,10 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr isc.org. - + - - IDN SUPPORT + IDN SUPPORT + If dig has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. @@ -1218,18 +1220,18 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr The IDN support is disabled if the variable is set when dig runs. - + - - FILES + FILES + /etc/resolv.conf ${HOME}/.digrc - + - - SEE ALSO + SEE ALSO + host1 , @@ -1241,16 +1243,13 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr , RFC1035. - + - - BUGS + BUGS + There are probably too many query options. - - + + + diff --git a/bin/dig/host.docbook b/bin/dig/host.docbook index 430a1c6f37..a831f31c7a 100644 --- a/bin/dig/host.docbook +++ b/bin/dig/host.docbook @@ -1,6 +1,5 @@ -]> +]> - - - + + + + 2009-01-20 + - January 20, 2009 + ISC + Internet Systems Consortium, Inc. @@ -54,26 +56,26 @@ - + host - - - - - - - - - - - - name - server + + + + + + + + + + + + name + server - - DESCRIPTION + DESCRIPTION + host is a simple utility for performing DNS lookups. @@ -253,10 +255,10 @@ The option causes host to print the version number and exit. - + - - IDN SUPPORT + IDN SUPPORT + If host has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. @@ -268,16 +270,16 @@ The IDN support is disabled if the variable is set when host runs. - + + + FILES - - FILES /etc/resolv.conf - + + + SEE ALSO - - SEE ALSO dig1 , @@ -285,10 +287,6 @@ named8 . + - - + diff --git a/bin/dig/nslookup.docbook b/bin/dig/nslookup.docbook index 022de672b8..aded8b9446 100644 --- a/bin/dig/nslookup.docbook +++ b/bin/dig/nslookup.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-24 + - January 24, 2014 + ISC + Internet Systems Consortium, Inc. @@ -76,16 +77,16 @@ - + nslookup - - name | - - server + + name | - + server - - DESCRIPTION + DESCRIPTION + Nslookup is a program to query Internet domain name servers. Nslookup has two modes: interactive and non-interactive. Interactive mode allows @@ -95,13 +96,13 @@ used to print just the name and requested information for a host or domain. - + - - ARGUMENTS + ARGUMENTS + Interactive mode is entered in the following cases: - + when no arguments are given (the default name server will be used) @@ -139,10 +140,10 @@ nslookup -query=hinfo -timeout=10 number and immediately exits. - + - - INTERACTIVE COMMANDS + INTERACTIVE COMMANDS + host server @@ -475,16 +476,16 @@ nslookup -query=hinfo -timeout=10 - + - - FILES + FILES + /etc/resolv.conf - + - - SEE ALSO + SEE ALSO + dig1 , @@ -495,16 +496,5 @@ nslookup -query=hinfo -timeout=10 named8 . - - - - Author - - Andrew Cherenson - - - + + diff --git a/bin/dnssec/dnssec-dsfromkey.docbook b/bin/dnssec/dnssec-dsfromkey.docbook index 7917e5c00a..a75d2054ad 100644 --- a/bin/dnssec/dnssec-dsfromkey.docbook +++ b/bin/dnssec/dnssec-dsfromkey.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2012-05-02 + - May 02, 2012 + ISC + Internet Systems Consortium, Inc. @@ -47,50 +48,50 @@ - + dnssec-dsfromkey - - - - - - - - keyfile + + + + + + + + keyfile - + dnssec-dsfromkey - -s - - - - - - - - - - - - dnsname + -s + + + + + + + + + + + + dnsname - + dnssec-dsfromkey - - + + - - DESCRIPTION + DESCRIPTION + dnssec-dsfromkey outputs the Delegation Signer (DS) resource record (RR), as defined in RFC 3658 and RFC 4509, for the given key(s). - + - - OPTIONS + OPTIONS + @@ -247,10 +248,10 @@ - + - - EXAMPLE + EXAMPLE + To build the SHA-256 DS RR from the Kexample.com.+003+26160 @@ -263,10 +264,10 @@ example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94 - + - - FILES + FILES + The keyfile can be designed by the key identification Knnnn.+aaa+iiiii or the full file name @@ -278,17 +279,17 @@ the string keyset- and the . - + - - CAVEAT + CAVEAT + A keyfile error can give a "file not found" even if the file exists. - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , @@ -300,16 +301,6 @@ RFC 4431. RFC 4509. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-importkey.docbook b/bin/dnssec/dnssec-importkey.docbook index c60cca72a2..b6dbb069ae 100644 --- a/bin/dnssec/dnssec-importkey.docbook +++ b/bin/dnssec/dnssec-importkey.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-20 + - February 20, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,33 +43,33 @@ - + dnssec-importkey - - - - - - - - + + + + + + + + - + dnssec-importkey - - - - - - - - - + + + + + + + + + - - DESCRIPTION + DESCRIPTION + dnssec-importkey reads a public DNSKEY record and generates a pair of .key/.private files. The DNSKEY record may be read from an @@ -86,10 +87,10 @@ public key can be added to and removed from the DNSKEY RRset on schedule even if the true private key is stored offline. - + - - OPTIONS + OPTIONS + @@ -159,10 +160,10 @@ - + - - TIMING OPTIONS + TIMING OPTIONS + Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as @@ -199,20 +200,20 @@ - + - - FILES + FILES + A keyfile can be designed by the key identification Knnnn.+aaa+iiiii or the full file name Knnnn.+aaa+iiiii.key as generated by dnssec-keygen8. - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , @@ -222,16 +223,6 @@ BIND 9 Administrator Reference Manual, RFC 5011. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-keyfromlabel.docbook b/bin/dnssec/dnssec-keyfromlabel.docbook index a74074e726..6944930d4c 100644 --- a/bin/dnssec/dnssec-keyfromlabel.docbook +++ b/bin/dnssec/dnssec-keyfromlabel.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-27 + - February 27, 2014 + ISC + Internet Systems Consortium, Inc. @@ -46,37 +47,37 @@ - + dnssec-keyfromlabel - -l label - - - - - - - - - - - - - - - - - - - - - - - name + -l label + + + + + + + + + + + + + + + + + + + + + + + name - - DESCRIPTION + DESCRIPTION + dnssec-keyfromlabel generates a key pair of files that referencing a key object stored in a cryptographic hardware service module (HSM). The private key @@ -90,10 +91,10 @@ line. This must match the name of the zone for which the key is being generated. - + - - OPTIONS + OPTIONS + @@ -358,10 +359,10 @@ - + - - TIMING OPTIONS + TIMING OPTIONS + Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. @@ -461,10 +462,10 @@ - + - - GENERATED KEY FILES + GENERATED KEY FILES + When dnssec-keyfromlabel completes successfully, @@ -507,10 +508,10 @@ fields. For obvious security reasons, this file does not have general read permission. - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , @@ -521,16 +522,6 @@ RFC 4034, The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13). - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-keygen.docbook b/bin/dnssec/dnssec-keygen.docbook index b4770fb926..c751e43e0b 100644 --- a/bin/dnssec/dnssec-keygen.docbook +++ b/bin/dnssec/dnssec-keygen.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-06 + - February 06, 2014 + ISC + Internet Systems Consortium, Inc. @@ -58,43 +59,43 @@ - + dnssec-keygen - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - name + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + name - - DESCRIPTION + DESCRIPTION + dnssec-keygen generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034. It can also generate keys for use with @@ -106,10 +107,10 @@ line. For DNSSEC keys, this must match the name of the zone for which the key is being generated. - + - - OPTIONS + OPTIONS + @@ -436,10 +437,10 @@ - + - - TIMING OPTIONS + TIMING OPTIONS + Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. @@ -541,11 +542,11 @@ - + - - GENERATED KEYS + GENERATED KEYS + When dnssec-keygen completes successfully, @@ -595,10 +596,10 @@ files are generated for symmetric encryption algorithms such as HMAC-MD5, even though the public and private key are equivalent. - + - - EXAMPLE + EXAMPLE + To generate a 768-bit DSA key for the domain example.com, the following command would be @@ -617,10 +618,10 @@ and Kexample.com.+003+26160.private. - + - - SEE ALSO + SEE ALSO + dnssec-signzone8 , @@ -629,16 +630,6 @@ RFC 2845, RFC 4034. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-revoke.docbook b/bin/dnssec/dnssec-revoke.docbook index 64efbd9fee..b058725a1d 100644 --- a/bin/dnssec/dnssec-revoke.docbook +++ b/bin/dnssec/dnssec-revoke.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-15 + - January 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -43,30 +44,30 @@ - + dnssec-revoke - - - - - - - - keyfile + + + + + + + + keyfile - - DESCRIPTION + DESCRIPTION + dnssec-revoke reads a DNSSEC key file, sets the REVOKED bit on the key as defined in RFC 5011, and creates a new pair of key files containing the now-revoked key. - + - - OPTIONS + OPTIONS + @@ -153,26 +154,16 @@ - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , BIND 9 Administrator Reference Manual, RFC 5011. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-settime.docbook b/bin/dnssec/dnssec-settime.docbook index 6314677acc..44933aa0ed 100644 --- a/bin/dnssec/dnssec-settime.docbook +++ b/bin/dnssec/dnssec-settime.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-06 + - February 06, 2014 + ISC + Internet Systems Consortium, Inc. @@ -45,26 +46,26 @@ - + dnssec-settime - - - - - - - - - - - - - keyfile + + + + + + + + + + + + + keyfile - - DESCRIPTION + DESCRIPTION + dnssec-settime reads a DNSSEC private key file and sets the key timing metadata as specified by the , , @@ -88,10 +89,10 @@ file. The private file's permissions are always set to be inaccessible to anyone other than the owner (mode 0600). - + - - OPTIONS + OPTIONS + @@ -179,10 +180,10 @@ - + - - TIMING OPTIONS + TIMING OPTIONS + Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as @@ -292,10 +293,10 @@ - + - - PRINTING OPTIONS + PRINTING OPTIONS + dnssec-settime can also be used to print the timing metadata associated with a key. @@ -330,10 +331,10 @@ - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , @@ -343,16 +344,6 @@ BIND 9 Administrator Reference Manual, RFC 5011. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-signzone.docbook b/bin/dnssec/dnssec-signzone.docbook index 0a18242223..81159f4570 100644 --- a/bin/dnssec/dnssec-signzone.docbook +++ b/bin/dnssec/dnssec-signzone.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-18 + - February 18, 2014 + ISC + Internet Systems Consortium, Inc. @@ -58,53 +59,53 @@ - + dnssec-signzone - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - zonefile - key + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + zonefile + key - - DESCRIPTION + DESCRIPTION + dnssec-signzone signs a zone. It generates NSEC and RRSIG records and produces a signed version of the @@ -113,10 +114,10 @@ determined by the presence or absence of a keyset file for each child zone. - + - - OPTIONS + OPTIONS + @@ -794,10 +795,10 @@ - + - - EXAMPLE + EXAMPLE + The following command signs the example.com zone with the DSA key generated by dnssec-keygen @@ -825,26 +826,16 @@ db.example.com.signed % dnssec-signzone -o example.com db.example.com db.example.com.signed % - + - - SEE ALSO + SEE ALSO + dnssec-keygen8 , BIND 9 Administrator Reference Manual, RFC 4033, RFC 4641. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/dnssec/dnssec-verify.docbook b/bin/dnssec/dnssec-verify.docbook index fddb8ebb05..08754f0b92 100644 --- a/bin/dnssec/dnssec-verify.docbook +++ b/bin/dnssec/dnssec-verify.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-15 + - January 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,31 +43,31 @@ - + dnssec-verify - - - - - - - - - zonefile + + + + + + + + + zonefile - - DESCRIPTION + DESCRIPTION + dnssec-verify verifies that a zone is fully signed for each algorithm found in the DNSKEY RRset for the zone, and that the NSEC / NSEC3 chains are complete. - + - - OPTIONS + OPTIONS + @@ -186,10 +187,10 @@ - + - - SEE ALSO + SEE ALSO + dnssec-signzone8 @@ -197,16 +198,6 @@ BIND 9 Administrator Reference Manual, RFC 4033. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/named/lwresd.docbook b/bin/named/lwresd.docbook index e45ce859b7..2a8273b0ef 100644 --- a/bin/named/lwresd.docbook +++ b/bin/named/lwresd.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2009-01-20 + - January 20, 2009 + ISC + Internet Systems Consortium, Inc. @@ -53,29 +54,29 @@ - + lwresd - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + - - DESCRIPTION + DESCRIPTION + lwresd is the daemon providing name lookup @@ -110,10 +111,10 @@ queries autonomously starting at the root name servers, using a built-in list of root server hints. - + - - OPTIONS + OPTIONS + @@ -319,10 +320,10 @@ - + - - FILES + FILES + @@ -346,10 +347,10 @@ - + - - SEE ALSO + SEE ALSO + named8 , @@ -360,16 +361,6 @@ resolver5 . - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/named/named.conf.docbook b/bin/named/named.conf.docbook index b0fede1f54..afaece268b 100644 --- a/bin/named/named.conf.docbook +++ b/bin/named/named.conf.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-08 + - January 08, 2014 + ISC + Internet Systems Consortium, Inc. @@ -52,13 +53,13 @@ - + named.conf - - DESCRIPTION + DESCRIPTION + named.conf is the configuration file for named. Statements are enclosed @@ -75,39 +76,39 @@ Unix style: # to end of line - + - - ACL - + ACL + + acl string { address_match_element; ... }; - + - - KEY - + KEY + + key domain_name { algorithm string; secret string; }; - + - - MASTERS - + MASTERS + + masters string port integer { ( masters | ipv4_address port integer | ipv6_address port integer ) key string ; ... }; - + - - SERVER - + SERVER + + server ( ipv4_address/prefixlen | ipv6_address/prefixlen ) { bogus boolean; edns boolean; @@ -127,29 +128,29 @@ server ( ipv4_address/prefixlen support-ixfr boolean; // obsolete }; - + - - TRUSTED-KEYS - + TRUSTED-KEYS + + trusted-keys { domain_name flags protocol algorithm key; ... }; - + - - MANAGED-KEYS - + MANAGED-KEYS + + managed-keys { domain_name initial-key flags protocol algorithm key; ... }; - + - - CONTROLS - + CONTROLS + + controls { inet ( ipv4_address | ipv6_address | * ) port ( integer | * ) @@ -158,11 +159,11 @@ controls { unix unsupported; // not implemented }; - + - - LOGGING - + LOGGING + + logging { channel string { file log_file; @@ -177,11 +178,11 @@ logging { category string { string; ... }; }; - + - - LWRES - + LWRES + + lwres { listen-on port integer { ( ipv4_address | ipv6_address ) port integer ; ... @@ -193,11 +194,11 @@ lwres { lwres-clients integer; }; - + - - OPTIONS - + OPTIONS + + options { avoid-v4-udp-ports { port; ... }; avoid-v6-udp-ports { port; ... }; @@ -408,11 +409,11 @@ options { use-id-pool boolean; // obsolete }; - + - - VIEW - + VIEW + + view string optional_class { match-clients { address_match_element; ... }; match-destinations { address_match_element; ... }; @@ -578,11 +579,11 @@ view string optional_class max-ixfr-log-size size; // obsolete }; - + - - ZONE - + ZONE + + zone string optional_class { type ( master | slave | stub | hint | redirect | forward | delegation-only ); @@ -676,16 +677,16 @@ zone string optional_class pubkey integer integer integer quoted_string; // obsolete }; - + - - FILES + FILES + /etc/named.conf - + - - SEE ALSO + SEE ALSO + named8 , @@ -697,10 +698,6 @@ zone string optional_class , BIND 9 Administrator Reference Manual. - + - + diff --git a/bin/named/named.docbook b/bin/named/named.docbook index 34cbeb83a6..fb10190e3a 100644 --- a/bin/named/named.docbook +++ b/bin/named/named.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-02-19 + - February 19, 2014 + ISC + Internet Systems Consortium, Inc. @@ -57,35 +58,35 @@ - + named - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + - - DESCRIPTION + DESCRIPTION + named is a Domain Name System (DNS) server, part of the BIND 9 distribution from ISC. For more @@ -98,10 +99,10 @@ /etc/named.conf, read any initial data, and listen for queries. - + - - OPTIONS + OPTIONS + @@ -158,10 +159,10 @@ -D string - Specifies a string that is used to identify a instance of - named in a process listing. The contents - of string are - not examined. + Specifies a string that is used to identify a instance of + named in a process listing. The contents + of string are + not examined. @@ -218,11 +219,11 @@ -M option - Sets the default memory context options. Currently - the only supported option is - external, - which causes the internal memory manager to be bypassed - in favor of system-provided memory allocation functions. + Sets the default memory context options. Currently + the only supported option is + external, + which causes the internal memory manager to be bypassed + in favor of system-provided memory allocation functions. @@ -231,14 +232,14 @@ -m flag - Turn on memory usage debugging flags. Possible flags are - usage, - trace, - record, - size, and - mctx. - These correspond to the ISC_MEM_DEBUGXXXX flags described in - <isc/mem.h>. + Turn on memory usage debugging flags. Possible flags are + usage, + trace, + record, + size, and + mctx. + These correspond to the ISC_MEM_DEBUGXXXX flags described in + <isc/mem.h>. @@ -285,38 +286,38 @@ -S #max-socks - - Allow named to use up to - #max-socks sockets. + + Allow named to use up to + #max-socks sockets. The default value is 4096 on systems built with default configuration options, and 21000 on systems built with "configure --with-tuning=large". - + This option should be unnecessary for the vast majority of users. - The use of this option could even be harmful because the + The use of this option could even be harmful because the specified value may exceed the limitation of the underlying system API. - It is therefore set only when the default configuration + It is therefore set only when the default configuration causes exhaustion of file descriptors and the operational environment is known to support the specified number of sockets. - Note also that the actual maximum number is normally a little + Note also that the actual maximum number is normally a little fewer than the specified value because - named reserves some file descriptors - for its internal use. + named reserves some file descriptors + for its internal use. - + -t directory Chroot - to directory after + to directory after processing the command line arguments, but before reading the configuration file. @@ -357,14 +358,14 @@ -u user Setuid - to user after completing + to user after completing privileged operations, such as creating sockets that listen on privileged ports. On Linux, named uses the kernel's - capability mechanism to drop all root privileges + capability mechanism to drop all root privileges except the ability to bind(2) to a privileged port and set process resource limits. @@ -431,10 +432,10 @@ - + - - SIGNALS + SIGNALS + In routine operation, signals should not be used to control the nameserver; rndc should be used @@ -467,10 +468,10 @@ The result of sending any other signals to the server is undefined. - + - - CONFIGURATION + CONFIGURATION + The named configuration file is too complex to describe in detail here. A complete description is provided @@ -487,10 +488,10 @@ named process. - + - - FILES + FILES + @@ -514,45 +515,35 @@ - + - - SEE ALSO + SEE ALSO + RFC 1033, RFC 1034, RFC 1035, named-checkconf - 8 + 8 , named-checkzone - 8 + 8 , rndc - 8 + 8 , lwresd - 8 + 8 , - named.conf - 5 + named.conf + 5 , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/nsupdate/nsupdate.docbook b/bin/nsupdate/nsupdate.docbook index daa6d7e2fd..058ea215f4 100644 --- a/bin/nsupdate/nsupdate.docbook +++ b/bin/nsupdate/nsupdate.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-04-18 + - April 18, 2014 + ISC + Internet Systems Consortium, Inc. + nsupdate 1 @@ -57,32 +59,32 @@ - + nsupdate - - - - - - - - - + + + + + + + + + - - - - - - - - - filename + + + + + + + + + filename - - DESCRIPTION + DESCRIPTION + nsupdate is used to submit Dynamic DNS Update requests as defined in RFC 2136 to a name server. @@ -138,10 +140,10 @@ non-standards-compliant variant of GSS-TSIG used by Windows 2000 can be switched on with the flag. - + - - OPTIONS + OPTIONS + @@ -347,10 +349,10 @@ - + - - INPUT FORMAT + INPUT FORMAT + nsupdate reads input from filename @@ -382,8 +384,8 @@ server - servername - port + servername + port @@ -409,8 +411,8 @@ local - address - port + address + port @@ -432,7 +434,7 @@ zone - zonename + zonename @@ -451,7 +453,7 @@ class - classname + classname @@ -466,7 +468,7 @@ ttl - seconds + seconds @@ -480,8 +482,8 @@ key - hmac:keyname - secret + hmac:keyname + secret @@ -524,7 +526,7 @@ realm - realm_name + realm_name @@ -538,7 +540,7 @@ check-names - yes_or_no + yes_or_no @@ -554,7 +556,7 @@ prereq nxdomain - domain-name + domain-name @@ -568,7 +570,7 @@ prereq yxdomain - domain-name + domain-name @@ -582,9 +584,9 @@ prereq nxrrset - domain-name - class - type + domain-name + class + type @@ -604,9 +606,9 @@ prereq yxrrset - domain-name - class - type + domain-name + class + type @@ -626,9 +628,9 @@ prereq yxrrset - domain-name - class - type + domain-name + class + type data @@ -660,10 +662,10 @@ update delete - domain-name - ttl - class - type data + domain-name + ttl + class + type data @@ -686,10 +688,10 @@ update add - domain-name - ttl - class - type + domain-name + ttl + class + type data @@ -779,10 +781,10 @@ Lines beginning with a semicolon are comments and are ignored. - + - - EXAMPLES + EXAMPLES + The examples below show how nsupdate @@ -830,10 +832,10 @@ (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have RRSIG, DNSKEY and NSEC records.) - + - - FILES + FILES + @@ -879,10 +881,10 @@ - + - - SEE ALSO + SEE ALSO + RFC 2136, RFC 3007, @@ -901,19 +903,16 @@ dnssec-keygen8 . - + - - BUGS + BUGS + The TSIG key is redundantly stored in two separate files. This is a consequence of nsupdate using the DST library for its cryptographic operations, and may change in future releases. - - + + + diff --git a/bin/pkcs11/pkcs11-destroy.docbook b/bin/pkcs11/pkcs11-destroy.docbook index 1cf5e2c763..aad8b55066 100644 --- a/bin/pkcs11/pkcs11-destroy.docbook +++ b/bin/pkcs11/pkcs11-destroy.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-15 + - January 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,21 +43,21 @@ - + pkcs11-destroy - - - - -i ID - -l label + + + + -i ID + -l label - - + + - - DESCRIPTION + DESCRIPTION + pkcs11-destroy destroys keys stored in a PKCS#11 device, identified by their or @@ -67,10 +68,10 @@ there is a five second delay to allow the user to interrupt the process before the destruction takes place. - + - - ARGUMENTS + ARGUMENTS + -m module @@ -132,10 +133,10 @@ - + - - SEE ALSO + SEE ALSO + pkcs11-keygen8 @@ -147,16 +148,6 @@ pkcs11-tokens8 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/pkcs11/pkcs11-keygen.docbook b/bin/pkcs11/pkcs11-keygen.docbook index dd1e32c75a..ada18dd531 100644 --- a/bin/pkcs11/pkcs11-keygen.docbook +++ b/bin/pkcs11/pkcs11-keygen.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-15 + - January 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,33 +43,33 @@ - + pkcs11-keygen - -a algorithm - - - - - - - - - - label + -a algorithm + + + + + + + + + + label - - DESCRIPTION + DESCRIPTION + pkcs11-keygen causes a PKCS#11 device to generate a new key pair with the given (which must be unique) and with bits of prime. - + - - ARGUMENTS + ARGUMENTS + -a algorithm @@ -179,10 +180,10 @@ - + - - SEE ALSO + SEE ALSO + pkcs11-destroy8 @@ -197,16 +198,6 @@ dnssec-keyfromlabel8 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/pkcs11/pkcs11-list.docbook b/bin/pkcs11/pkcs11-list.docbook index c5b6f7847b..4123d0c372 100644 --- a/bin/pkcs11/pkcs11-list.docbook +++ b/bin/pkcs11/pkcs11-list.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2009-10-05 + - October 05, 2009 + ISC + Internet Systems Consortium, Inc. @@ -42,28 +43,28 @@ - + pkcs11-list - - - - -i ID - -l label - + + + + -i ID + -l label + - - DESCRIPTION + DESCRIPTION + pkcs11-list lists the PKCS#11 objects with or or by default all objects. - + - - ARGUMENTS + ARGUMENTS + -P @@ -124,10 +125,10 @@ - + - - SEE ALSO + SEE ALSO + pkcs11-destroy8 @@ -139,16 +140,6 @@ pkcs11-tokens8 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/pkcs11/pkcs11-tokens.docbook b/bin/pkcs11/pkcs11-tokens.docbook index de3b658ca0..4f16c188eb 100644 --- a/bin/pkcs11/pkcs11-tokens.docbook +++ b/bin/pkcs11/pkcs11-tokens.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-15 + - January 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -41,23 +42,23 @@ - + pkcs11-tokens - + - - DESCRIPTION + DESCRIPTION + pkcs11-tokens lists the PKCS#11 available tokens with defaults from the slot/token scan performed at application initialization. - + - - ARGUMENTS + ARGUMENTS + -m module @@ -70,10 +71,10 @@ - + - - SEE ALSO + SEE ALSO + pkcs11-destroy8 @@ -85,16 +86,6 @@ pkcs11-list8 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/python/dnssec-checkds.docbook b/bin/python/dnssec-checkds.docbook index 8c528502e6..7a7f866a13 100644 --- a/bin/python/dnssec-checkds.docbook +++ b/bin/python/dnssec-checkds.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2013-01-01 + - January 01, 2013 + ISC + Internet Systems Consortium, Inc. @@ -43,35 +44,35 @@ - + dnssec-checkds - - - - - zone + + + + + zone - + dnssec-dsfromkey - - - - - zone + + + + + zone - - DESCRIPTION + DESCRIPTION + dnssec-checkds verifies the correctness of Delegation Signer (DS) or DNSSEC Lookaside Validation (DLV) resource records for keys in a specified zone. - + - - OPTIONS + OPTIONS + @@ -118,10 +119,10 @@ - + - - SEE ALSO + SEE ALSO + dnssec-dsfromkey8 , @@ -132,16 +133,6 @@ dnssec-signzone8 , - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/python/dnssec-coverage.docbook b/bin/python/dnssec-coverage.docbook index 7f335f3247..e5d902584f 100644 --- a/bin/python/dnssec-coverage.docbook +++ b/bin/python/dnssec-coverage.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-01-11 + - January 11, 2014 + ISC + Internet Systems Consortium, Inc. @@ -42,23 +43,23 @@ - + dnssec-coverage - - - - - - - - - - zone + + + + + + + + + + zone - - DESCRIPTION + DESCRIPTION + dnssec-coverage verifies that the DNSSEC keys for a given zone or a set of zones have timing metadata set properly to ensure no future lapses in DNSSEC @@ -84,10 +85,10 @@ accurate if all the zones that have keys in a given repository share the same TTL parameters.) - + - - OPTIONS + OPTIONS + @@ -237,10 +238,10 @@ - + - - SEE ALSO + SEE ALSO + dnssec-checkds8 @@ -255,16 +256,6 @@ dnssec-signzone8 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/rndc/rndc.conf.docbook b/bin/rndc/rndc.conf.docbook index 4bb858f261..83ed4f35e6 100644 --- a/bin/rndc/rndc.conf.docbook +++ b/bin/rndc/rndc.conf.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2013-03-14 + - March 14, 2013 + ISC + Internet Systems Consortium, Inc. @@ -51,13 +52,13 @@ - + rndc.conf - - DESCRIPTION + DESCRIPTION + rndc.conf is the configuration file for rndc, the BIND 9 name server control utility. This file has a similar structure and syntax to @@ -141,10 +142,10 @@ ship with BIND 9 but is available on many systems. See the EXAMPLE section for sample command lines for each. - + - - EXAMPLE + EXAMPLE + options { @@ -213,10 +214,10 @@ echo "known plaintext for a secret" | mmencode - + - - NAME SERVER CONFIGURATION + NAME SERVER CONFIGURATION + The name server must be configured to accept rndc connections and to recognize the key specified in the rndc.conf @@ -224,10 +225,10 @@ See the sections on the statement in the BIND 9 Administrator Reference Manual for details. - + - - SEE ALSO + SEE ALSO + rndc8 , @@ -239,16 +240,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/rndc/rndc.docbook b/bin/rndc/rndc.docbook index 586a39ea13..d8846369d5 100644 --- a/bin/rndc/rndc.docbook +++ b/bin/rndc/rndc.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2014-08-15 + - August 15, 2014 + ISC + Internet Systems Consortium, Inc. @@ -52,23 +53,23 @@ - + rndc - - - - - - - - - - command + + + + + + + + + + command - - DESCRIPTION + DESCRIPTION + rndc controls the operation of a name server. It supersedes the ndc utility @@ -97,10 +98,10 @@ determine how to contact the name server and decide what algorithm and key it should use. - + - - OPTIONS + OPTIONS + @@ -221,10 +222,10 @@ - + - - COMMANDS + COMMANDS + A list of commands supported by rndc can be seen by running rndc without arguments. @@ -959,10 +960,10 @@ - + - - LIMITATIONS + LIMITATIONS + There is currently no way to provide the shared secret for a without using the configuration file. @@ -970,10 +971,10 @@ Several error messages could be clearer. - + - - SEE ALSO + SEE ALSO + rndc.conf5 , @@ -991,16 +992,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/arpaname.docbook b/bin/tools/arpaname.docbook index 04fd54aec5..77b430e39a 100644 --- a/bin/tools/arpaname.docbook +++ b/bin/tools/arpaname.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2009-03-03 + - March 03, 2009 + ISC + Internet Systems Consortium, Inc. - arpaname 1 @@ -42,35 +42,25 @@ - + arpaname ipaddress - - DESCRIPTION + DESCRIPTION + arpaname translates IP addresses (IPv4 and IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names. - + - - SEE ALSO + SEE ALSO + BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/dnstap-read.docbook b/bin/tools/dnstap-read.docbook index 58d01751f0..2b80d7d074 100644 --- a/bin/tools/dnstap-read.docbook +++ b/bin/tools/dnstap-read.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2015-09-13 + - September 13, 2015 + ISC + Internet Systems Consortium, Inc. @@ -41,17 +42,17 @@ - + dnstap-read - - - - file + + + + file - - DESCRIPTION + DESCRIPTION + dnstap-read reads dnstap data from a specified file @@ -60,10 +61,10 @@ format, but if the option is specified, then a longer and more detailed YAML format is used instead. - + - - OPTIONS + OPTIONS + @@ -97,10 +98,10 @@ - + - - SEE ALSO + SEE ALSO + named8 @@ -110,16 +111,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/genrandom.docbook b/bin/tools/genrandom.docbook index ecc206a549..a53cd90b50 100644 --- a/bin/tools/genrandom.docbook +++ b/bin/tools/genrandom.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2011-08-08 + - August 08, 2011 + ISC + Internet Systems Consortium, Inc. @@ -44,26 +45,26 @@ - + genrandom - - size - filename + + size + filename - - DESCRIPTION + DESCRIPTION + genrandom generates a file or a set of files containing a specified quantity of pseudo-random data, which can be used as a source of entropy for other commands on systems with no random device. - + - - ARGUMENTS + ARGUMENTS + -n number @@ -93,10 +94,10 @@ - + - - SEE ALSO + SEE ALSO + rand3 @@ -105,16 +106,6 @@ arc4random3 - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/isc-hmac-fixup.docbook b/bin/tools/isc-hmac-fixup.docbook index 986c30b855..2d2774a2ae 100644 --- a/bin/tools/isc-hmac-fixup.docbook +++ b/bin/tools/isc-hmac-fixup.docbook @@ -1,8 +1,6 @@ -]> + - - + + + 2013-04-28 + - April 28, 2013 + ISC + Internet Systems Consortium, Inc. @@ -43,15 +44,15 @@ - + isc-hmac-fixup - algorithm - secret + algorithm + secret - - DESCRIPTION + DESCRIPTION + Versions of BIND 9 up to and including BIND 9.6 had a bug causing HMAC-SHA* TSIG keys which were longer than the digest length of the @@ -75,10 +76,10 @@ secret. (If the secret did not require conversion, then it will be printed without modification.) - + - - SECURITY CONSIDERATIONS + SECURITY CONSIDERATIONS + Secrets that have been converted by isc-hmac-fixup are shortened, but as this is how the HMAC protocol works in @@ -87,24 +88,14 @@ extra length would not significantly increase the function strength." - + - - SEE ALSO + SEE ALSO + BIND 9 Administrator Reference Manual, RFC 2104. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/mdig.docbook b/bin/tools/mdig.docbook index 6f8e3107d9..145a5f87e9 100644 --- a/bin/tools/mdig.docbook +++ b/bin/tools/mdig.docbook @@ -1,8 +1,7 @@ -]> +]> - - + + + + 2015-01-05 + - January 5, 2015 + ISC + Internet Systems Consortium, Inc. mdig @@ -39,41 +42,41 @@ - + mdig - @server - - - - - - - - - - - + @server + + + + + + + + + + + plusopt - + mdig - -h + -h - + mdig - @server + @server global-opt local-opt - query + query - - DESCRIPTION + DESCRIPTION + mdig is a multiple/pipelined query version of dig: instead of waiting for a response after sending each query, @@ -92,7 +95,7 @@ - The @server option is a mandatory global + The @server option is a mandatory global option. It is the name or IP address of the name server to query. (Unlike dig, this value is not retrieved from /etc/resolv.conf.) It can be an IPv4 address @@ -119,10 +122,10 @@ values to options like the timeout interval. They have the form . - + - - ANYWHERE OPTIONS + ANYWHERE OPTIONS + The option makes mdig @@ -142,10 +145,10 @@ The causes mdig to print the version number and exit. - + - - GLOBAL OPTIONS + GLOBAL OPTIONS + The option forces mdig to @@ -383,10 +386,10 @@ - + - - LOCAL OPTIONS + LOCAL OPTIONS + The option sets the query class to @@ -646,18 +649,14 @@ - + - - SEE ALSO + SEE ALSO + dig1 , RFC1035. - - + + diff --git a/bin/tools/named-journalprint.docbook b/bin/tools/named-journalprint.docbook index 8d65c8e300..b985254f95 100644 --- a/bin/tools/named-journalprint.docbook +++ b/bin/tools/named-journalprint.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2009-12-04 + - December 04, 2009 + ISC + Internet Systems Consortium, Inc. @@ -42,14 +43,14 @@ - + named-journalprint - journal + journal - - DESCRIPTION + DESCRIPTION + named-journalprint prints the contents of a zone journal file in a human-readable @@ -73,10 +74,10 @@ deleted, and continues with the resource record in master-file format. - + - - SEE ALSO + SEE ALSO + named8 @@ -86,16 +87,6 @@ , BIND 9 Administrator Reference Manual. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/bin/tools/named-rrchecker.docbook b/bin/tools/named-rrchecker.docbook index c0916cb89d..705d0da406 100644 --- a/bin/tools/named-rrchecker.docbook +++ b/bin/tools/named-rrchecker.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2013-11-12 + - November 12, 2013 + ISC + Internet Systems Consortium, Inc. named-rrchecker @@ -40,20 +41,20 @@ - + named-rrchecker - - - - - - - + + + + + + + - - DESCRIPTION + DESCRIPTION + named-rrchecker read a individual DNS resource record from standard input and checks if it is syntactically correct. @@ -79,10 +80,10 @@ print out the known class, standard type and private type mnemonics respectively. - + - - SEE ALSO + SEE ALSO + RFC 1034, RFC 1035, @@ -90,10 +91,6 @@ named8 - + - + diff --git a/bin/tools/nsec3hash.docbook b/bin/tools/nsec3hash.docbook index 618e53a1aa..6125fb44c0 100644 --- a/bin/tools/nsec3hash.docbook +++ b/bin/tools/nsec3hash.docbook @@ -1,6 +1,3 @@ -]> - - + + + + 2009-03-02 + - March 02, 2009 + ISC + Internet Systems Consortium, Inc. @@ -42,26 +43,26 @@ - + nsec3hash - salt - algorithm - iterations - domain + salt + algorithm + iterations + domain - - DESCRIPTION + DESCRIPTION + nsec3hash generates an NSEC3 hash based on a set of NSEC3 parameters. This can be used to check the validity of NSEC3 records in a signed zone. - + - - ARGUMENTS + ARGUMENTS + salt @@ -102,24 +103,14 @@ - + - - SEE ALSO + SEE ALSO + BIND 9 Administrator Reference Manual, RFC 5155. - + - - AUTHOR - Internet Systems Consortium - - - - + diff --git a/configure b/configure index 859bebb897..1fd18e98e5 100755 --- a/configure +++ b/configure @@ -667,6 +667,7 @@ SO_CFLAGS SO BIND9_CONFIGARGS BIND9_SRCID +BIND9_VERSIONSHORT BIND9_VERSIONSTRING BIND9_MAJOR BIND9_VERSION @@ -685,8 +686,8 @@ ATFLIBS ATFBIN ATFBUILD IDNLIBS -XSLT_DB2LATEX_ADMONITIONS -XSLT_DB2LATEX_STYLE +XSLT_DBLATEX_FASTBOOK +XSLT_DBLATEX_STYLE XSLT_DOCBOOK_MAKETOC_XHTML XSLT_DOCBOOK_MAKETOC_HTML XSLT_DOCBOOK_CHUNKTOC_XHTML @@ -701,6 +702,7 @@ DOXYGEN XMLLINT XSLTPROC W3M +DBLATEX PDFLATEX LATEX DNSTAPHTML @@ -20331,6 +20333,54 @@ test -n "$PDFLATEX" || PDFLATEX="pdflatex" +for ac_prog in dblatex +do + # Extract the first word of "$ac_prog", so it can be a program name with args. +set dummy $ac_prog; ac_word=$2 +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5 +$as_echo_n "checking for $ac_word... " >&6; } +if ${ac_cv_path_DBLATEX+:} false; then : + $as_echo_n "(cached) " >&6 +else + case $DBLATEX in + [\\/]* | ?:[\\/]*) + ac_cv_path_DBLATEX="$DBLATEX" # Let the user override the test with a path. + ;; + *) + as_save_IFS=$IFS; IFS=$PATH_SEPARATOR +for as_dir in $PATH +do + IFS=$as_save_IFS + test -z "$as_dir" && as_dir=. + for ac_exec_ext in '' $ac_executable_extensions; do + if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then + ac_cv_path_DBLATEX="$as_dir/$ac_word$ac_exec_ext" + $as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5 + break 2 + fi +done + done +IFS=$as_save_IFS + + ;; +esac +fi +DBLATEX=$ac_cv_path_DBLATEX +if test -n "$DBLATEX"; then + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $DBLATEX" >&5 +$as_echo "$DBLATEX" >&6; } +else + { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5 +$as_echo "no" >&6; } +fi + + + test -n "$DBLATEX" && break +done +test -n "$DBLATEX" || DBLATEX="dblatex" + + + # # Look for w3m # @@ -20828,64 +20878,56 @@ fi # -# Same dance for db2latex +# Same dance for dblatex # +dblatex_xsl_trees="/usr/local/share/xml/docbook/stylesheet/dblatex /usr/pkg/share/xml/docbook/stylesheet/dblatex /usr/share/xml/docbook/stylesheet/dblatex" -db2latex_xsl_trees="/usr/local/share/db2latex/xsl /usr/pkg/share/xsl/db2latex" - -# -# Look for stylesheets we need. -# - - -XSLT_DB2LATEX_STYLE="" -{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for docbook.xsl" >&5 -$as_echo_n "checking for docbook.xsl... " >&6; } -for d in $db2latex_xsl_trees +XSLT_DBLATEX_STYLE="" +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for xsl/docbook.xsl" >&5 +$as_echo_n "checking for xsl/docbook.xsl... " >&6; } +for d in $dblatex_xsl_trees do - f=$d/docbook.xsl + f=$d/xsl/docbook.xsl if test -f $f then - XSLT_DB2LATEX_STYLE=$f + XSLT_DBLATEX_STYLE=$f { $as_echo "$as_me:${as_lineno-$LINENO}: result: $f" >&5 $as_echo "$f" >&6; } break fi done -if test "X$XSLT_DB2LATEX_STYLE" = "X" +if test "X$XSLT_DBLATEX_STYLE" = "X" then { $as_echo "$as_me:${as_lineno-$LINENO}: result: \"not found\"" >&5 $as_echo "\"not found\"" >&6; }; - XSLT_DB2LATEX_STYLE=docbook.xsl + XSLT_DBLATEX_STYLE=xsl/docbook.xsl fi -# -# Look for "admonition" image directory. Can't use NOM_PATH_FILE() -# because it's a directory, so just do the same things, inline. -# - -{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for db2latex xsl figures" >&5 -$as_echo_n "checking for db2latex xsl figures... " >&6; } -for d in $db2latex_xsl_trees +XSLT_DBLATEX_FASTBOOK="" +{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for xsl/latex_book_fast.xsl" >&5 +$as_echo_n "checking for xsl/latex_book_fast.xsl... " >&6; } +for d in $dblatex_xsl_trees do - if test -d $d/figures + f=$d/xsl/latex_book_fast.xsl + if test -f $f then - XSLT_DB2LATEX_ADMONITIONS=$d/figures - { $as_echo "$as_me:${as_lineno-$LINENO}: result: $d/figures" >&5 -$as_echo "$d/figures" >&6; } + XSLT_DBLATEX_FASTBOOK=$f + { $as_echo "$as_me:${as_lineno-$LINENO}: result: $f" >&5 +$as_echo "$f" >&6; } break fi done -if test "X$XSLT_DB2LATEX_ADMONITIONS" = "X" +if test "X$XSLT_DBLATEX_FASTBOOK" = "X" then - { $as_echo "$as_me:${as_lineno-$LINENO}: result: not found" >&5 -$as_echo "not found" >&6; } - XSLT_DB2LATEX_ADMONITIONS=db2latex/xsl/figures + { $as_echo "$as_me:${as_lineno-$LINENO}: result: \"not found\"" >&5 +$as_echo "\"not found\"" >&6; }; + XSLT_DBLATEX_FASTBOOK=xsl/latex_book_fast.xsl fi + # # IDN support # @@ -21191,6 +21233,8 @@ BIND9_MAJOR="MAJOR=${MAJORVER}.${MINORVER}" BIND9_VERSIONSTRING="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}${DESCRIPTION:+ }${DESCRIPTION}" +BIND9_VERSIONSHORT="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}" + BIND9_SRCID="SRCID=unset" if test -f "${srcdir}/srcid"; then @@ -22411,7 +22455,7 @@ ac_config_commands="$ac_config_commands chmod" # elsewhere if there's a good reason for doing so. # -ac_config_files="$ac_config_files make/Makefile make/mkdep Makefile bin/Makefile bin/check/Makefile bin/confgen/Makefile bin/confgen/unix/Makefile bin/delv/Makefile bin/dig/Makefile bin/dnssec/Makefile bin/named/Makefile bin/named/unix/Makefile bin/nsupdate/Makefile bin/pkcs11/Makefile bin/python/Makefile bin/python/dnssec-checkds.py bin/python/dnssec-coverage.py bin/rndc/Makefile bin/tests/Makefile bin/tests/atomic/Makefile bin/tests/db/Makefile bin/tests/dst/Makefile bin/tests/dst/Kdh.+002+18602.key bin/tests/dst/Kdh.+002+18602.private bin/tests/dst/Kdh.+002+48957.key bin/tests/dst/Kdh.+002+48957.private bin/tests/dst/Ktest.+001+00002.key bin/tests/dst/Ktest.+001+54622.key bin/tests/dst/Ktest.+001+54622.private bin/tests/dst/Ktest.+003+23616.key bin/tests/dst/Ktest.+003+23616.private bin/tests/dst/Ktest.+003+49667.key bin/tests/dst/dst_2_data bin/tests/dst/t2_data_1 bin/tests/dst/t2_data_2 bin/tests/dst/t2_dsasig bin/tests/dst/t2_rsasig bin/tests/hashes/Makefile bin/tests/headerdep_test.sh bin/tests/master/Makefile bin/tests/mem/Makefile bin/tests/names/Makefile bin/tests/net/Makefile bin/tests/pkcs11/Makefile bin/tests/pkcs11/benchmarks/Makefile bin/tests/rbt/Makefile bin/tests/resolver/Makefile bin/tests/sockaddr/Makefile bin/tests/system/Makefile bin/tests/system/builtin/Makefile bin/tests/system/conf.sh bin/tests/system/dlz/prereq.sh bin/tests/system/dlzexternal/Makefile bin/tests/system/dlzexternal/ns1/named.conf bin/tests/system/dyndb/Makefile bin/tests/system/dyndb/driver/Makefile bin/tests/system/filter-aaaa/Makefile bin/tests/system/geoip/Makefile bin/tests/system/inline/checkdsa.sh bin/tests/system/lwresd/Makefile bin/tests/system/pipelined/Makefile bin/tests/system/resolver/Makefile bin/tests/system/rndc/Makefile bin/tests/system/rpz/Makefile bin/tests/system/rsabigexponent/Makefile bin/tests/system/statistics/Makefile bin/tests/system/tkey/Makefile bin/tests/system/tsiggss/Makefile bin/tests/tasks/Makefile bin/tests/timers/Makefile bin/tests/virtual-time/Makefile bin/tests/virtual-time/conf.sh bin/tools/Makefile contrib/scripts/check-secure-delegation.pl contrib/scripts/zone-edit.sh doc/Makefile doc/arm/Makefile doc/doxygen/Doxyfile doc/doxygen/Makefile doc/doxygen/doxygen-input-filter doc/misc/Makefile doc/xsl/Makefile doc/xsl/isc-docbook-chunk.xsl doc/xsl/isc-docbook-html.xsl doc/xsl/isc-docbook-latex.xsl doc/xsl/isc-manpage.xsl doc/xsl/isc-notes-html.xsl doc/xsl/isc-notes-latex.xsl isc-config.sh lib/Makefile lib/bind9/Makefile lib/bind9/include/Makefile lib/bind9/include/bind9/Makefile lib/dns/Makefile lib/dns/include/Makefile lib/dns/include/dns/Makefile lib/dns/include/dst/Makefile lib/dns/tests/Makefile lib/irs/Makefile lib/irs/include/Makefile lib/irs/include/irs/Makefile lib/irs/include/irs/netdb.h lib/irs/include/irs/platform.h lib/isc/$arch/Makefile lib/isc/$arch/include/Makefile lib/isc/$arch/include/isc/Makefile lib/isc/$thread_dir/Makefile lib/isc/$thread_dir/include/Makefile lib/isc/$thread_dir/include/isc/Makefile lib/isc/Makefile lib/isc/include/Makefile lib/isc/include/isc/Makefile lib/isc/include/isc/platform.h lib/isc/include/pk11/Makefile lib/isc/include/pkcs11/Makefile lib/isc/tests/Makefile lib/isc/nls/Makefile lib/isc/unix/Makefile lib/isc/unix/include/Makefile lib/isc/unix/include/isc/Makefile lib/isc/unix/include/pkcs11/Makefile lib/isccc/Makefile lib/isccc/include/Makefile lib/isccc/include/isccc/Makefile lib/isccfg/Makefile lib/isccfg/include/Makefile lib/isccfg/include/isccfg/Makefile lib/lwres/Makefile lib/lwres/include/Makefile lib/lwres/include/lwres/Makefile lib/lwres/include/lwres/netdb.h lib/lwres/include/lwres/platform.h lib/lwres/man/Makefile lib/lwres/tests/Makefile lib/lwres/unix/Makefile lib/lwres/unix/include/Makefile lib/lwres/unix/include/lwres/Makefile lib/tests/Makefile lib/tests/include/Makefile lib/tests/include/tests/Makefile lib/samples/Makefile lib/samples/Makefile-postinstall unit/Makefile unit/unittest.sh" +ac_config_files="$ac_config_files make/Makefile make/mkdep Makefile bin/Makefile bin/check/Makefile bin/confgen/Makefile bin/confgen/unix/Makefile bin/delv/Makefile bin/dig/Makefile bin/dnssec/Makefile bin/named/Makefile bin/named/unix/Makefile bin/nsupdate/Makefile bin/pkcs11/Makefile bin/python/Makefile bin/python/dnssec-checkds.py bin/python/dnssec-coverage.py bin/rndc/Makefile bin/tests/Makefile bin/tests/atomic/Makefile bin/tests/db/Makefile bin/tests/dst/Makefile bin/tests/dst/Kdh.+002+18602.key bin/tests/dst/Kdh.+002+18602.private bin/tests/dst/Kdh.+002+48957.key bin/tests/dst/Kdh.+002+48957.private bin/tests/dst/Ktest.+001+00002.key bin/tests/dst/Ktest.+001+54622.key bin/tests/dst/Ktest.+001+54622.private bin/tests/dst/Ktest.+003+23616.key bin/tests/dst/Ktest.+003+23616.private bin/tests/dst/Ktest.+003+49667.key bin/tests/dst/dst_2_data bin/tests/dst/t2_data_1 bin/tests/dst/t2_data_2 bin/tests/dst/t2_dsasig bin/tests/dst/t2_rsasig bin/tests/hashes/Makefile bin/tests/headerdep_test.sh bin/tests/master/Makefile bin/tests/mem/Makefile bin/tests/names/Makefile bin/tests/net/Makefile bin/tests/pkcs11/Makefile bin/tests/pkcs11/benchmarks/Makefile bin/tests/rbt/Makefile bin/tests/resolver/Makefile bin/tests/sockaddr/Makefile bin/tests/system/Makefile bin/tests/system/builtin/Makefile bin/tests/system/conf.sh bin/tests/system/dlz/prereq.sh bin/tests/system/dlzexternal/Makefile bin/tests/system/dlzexternal/ns1/named.conf bin/tests/system/dyndb/Makefile bin/tests/system/dyndb/driver/Makefile bin/tests/system/filter-aaaa/Makefile bin/tests/system/geoip/Makefile bin/tests/system/inline/checkdsa.sh bin/tests/system/lwresd/Makefile bin/tests/system/pipelined/Makefile bin/tests/system/resolver/Makefile bin/tests/system/rndc/Makefile bin/tests/system/rpz/Makefile bin/tests/system/rsabigexponent/Makefile bin/tests/system/statistics/Makefile bin/tests/system/tkey/Makefile bin/tests/system/tsiggss/Makefile bin/tests/tasks/Makefile bin/tests/timers/Makefile bin/tests/virtual-time/Makefile bin/tests/virtual-time/conf.sh bin/tools/Makefile contrib/scripts/check-secure-delegation.pl contrib/scripts/zone-edit.sh doc/Makefile doc/arm/Makefile doc/doxygen/Doxyfile doc/doxygen/Makefile doc/doxygen/doxygen-input-filter doc/misc/Makefile doc/tex/Makefile doc/tex/armstyle.sty doc/xsl/Makefile doc/xsl/isc-docbook-chunk.xsl doc/xsl/isc-docbook-html.xsl doc/xsl/isc-manpage.xsl doc/xsl/isc-notes-html.xsl isc-config.sh lib/Makefile lib/bind9/Makefile lib/bind9/include/Makefile lib/bind9/include/bind9/Makefile lib/dns/Makefile lib/dns/include/Makefile lib/dns/include/dns/Makefile lib/dns/include/dst/Makefile lib/dns/tests/Makefile lib/irs/Makefile lib/irs/include/Makefile lib/irs/include/irs/Makefile lib/irs/include/irs/netdb.h lib/irs/include/irs/platform.h lib/isc/$arch/Makefile lib/isc/$arch/include/Makefile lib/isc/$arch/include/isc/Makefile lib/isc/$thread_dir/Makefile lib/isc/$thread_dir/include/Makefile lib/isc/$thread_dir/include/isc/Makefile lib/isc/Makefile lib/isc/include/Makefile lib/isc/include/isc/Makefile lib/isc/include/isc/platform.h lib/isc/include/pk11/Makefile lib/isc/include/pkcs11/Makefile lib/isc/tests/Makefile lib/isc/nls/Makefile lib/isc/unix/Makefile lib/isc/unix/include/Makefile lib/isc/unix/include/isc/Makefile lib/isc/unix/include/pkcs11/Makefile lib/isccc/Makefile lib/isccc/include/Makefile lib/isccc/include/isccc/Makefile lib/isccfg/Makefile lib/isccfg/include/Makefile lib/isccfg/include/isccfg/Makefile lib/lwres/Makefile lib/lwres/include/Makefile lib/lwres/include/lwres/Makefile lib/lwres/include/lwres/netdb.h lib/lwres/include/lwres/platform.h lib/lwres/man/Makefile lib/lwres/tests/Makefile lib/lwres/unix/Makefile lib/lwres/unix/include/Makefile lib/lwres/unix/include/lwres/Makefile lib/tests/Makefile lib/tests/include/Makefile lib/tests/include/tests/Makefile lib/samples/Makefile lib/samples/Makefile-postinstall unit/Makefile unit/unittest.sh" # @@ -23486,13 +23530,13 @@ do "doc/doxygen/Makefile") CONFIG_FILES="$CONFIG_FILES doc/doxygen/Makefile" ;; "doc/doxygen/doxygen-input-filter") CONFIG_FILES="$CONFIG_FILES doc/doxygen/doxygen-input-filter" ;; "doc/misc/Makefile") CONFIG_FILES="$CONFIG_FILES doc/misc/Makefile" ;; + "doc/tex/Makefile") CONFIG_FILES="$CONFIG_FILES doc/tex/Makefile" ;; + "doc/tex/armstyle.sty") CONFIG_FILES="$CONFIG_FILES doc/tex/armstyle.sty" ;; "doc/xsl/Makefile") CONFIG_FILES="$CONFIG_FILES doc/xsl/Makefile" ;; "doc/xsl/isc-docbook-chunk.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-chunk.xsl" ;; "doc/xsl/isc-docbook-html.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-html.xsl" ;; - "doc/xsl/isc-docbook-latex.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-docbook-latex.xsl" ;; "doc/xsl/isc-manpage.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-manpage.xsl" ;; "doc/xsl/isc-notes-html.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-notes-html.xsl" ;; - "doc/xsl/isc-notes-latex.xsl") CONFIG_FILES="$CONFIG_FILES doc/xsl/isc-notes-latex.xsl" ;; "isc-config.sh") CONFIG_FILES="$CONFIG_FILES isc-config.sh" ;; "lib/Makefile") CONFIG_FILES="$CONFIG_FILES lib/Makefile" ;; "lib/bind9/Makefile") CONFIG_FILES="$CONFIG_FILES lib/bind9/Makefile" ;; diff --git a/configure.in b/configure.in index 946f0240da..94d8db383a 100644 --- a/configure.in +++ b/configure.in @@ -4045,6 +4045,9 @@ AC_SUBST(LATEX) AC_PATH_PROGS(PDFLATEX, pdflatex, pdflatex) AC_SUBST(PDFLATEX) +AC_PATH_PROGS(DBLATEX, dblatex, dblatex) +AC_SUBST(DBLATEX) + # # Look for w3m # @@ -4150,38 +4153,11 @@ NOM_PATH_FILE(XSLT_DOCBOOK_MAKETOC_HTML, html/maketoc.xsl, $docbook_xsl_trees) NOM_PATH_FILE(XSLT_DOCBOOK_MAKETOC_XHTML, xhtml/maketoc.xsl, $docbook_xsl_trees) # -# Same dance for db2latex +# Same dance for dblatex # - -db2latex_xsl_trees="/usr/local/share/db2latex/xsl /usr/pkg/share/xsl/db2latex" - -# -# Look for stylesheets we need. -# - -NOM_PATH_FILE(XSLT_DB2LATEX_STYLE, docbook.xsl, $db2latex_xsl_trees) - -# -# Look for "admonition" image directory. Can't use NOM_PATH_FILE() -# because it's a directory, so just do the same things, inline. -# - -AC_MSG_CHECKING(for db2latex xsl figures) -for d in $db2latex_xsl_trees -do - if test -d $d/figures - then - XSLT_DB2LATEX_ADMONITIONS=$d/figures - AC_MSG_RESULT($d/figures) - break - fi -done -if test "X$XSLT_DB2LATEX_ADMONITIONS" = "X" -then - AC_MSG_RESULT(not found) - XSLT_DB2LATEX_ADMONITIONS=db2latex/xsl/figures -fi -AC_SUBST(XSLT_DB2LATEX_ADMONITIONS) +dblatex_xsl_trees="/usr/local/share/xml/docbook/stylesheet/dblatex /usr/pkg/share/xml/docbook/stylesheet/dblatex /usr/share/xml/docbook/stylesheet/dblatex" +NOM_PATH_FILE(XSLT_DBLATEX_STYLE, xsl/docbook.xsl, $dblatex_xsl_trees) +NOM_PATH_FILE(XSLT_DBLATEX_FASTBOOK, xsl/latex_book_fast.xsl, $dblatex_xsl_trees) # # IDN support @@ -4390,6 +4366,8 @@ BIND9_MAJOR="MAJOR=${MAJORVER}.${MINORVER}" AC_SUBST(BIND9_MAJOR) BIND9_VERSIONSTRING="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}${DESCRIPTION:+ }${DESCRIPTION}" AC_SUBST(BIND9_VERSIONSTRING) +BIND9_VERSIONSHORT="${PRODUCT} ${MAJORVER}.${MINORVER}${PATCHVER:+.}${PATCHVER}${RELEASETYPE}${RELEASEVER}${EXTENSIONS}" +AC_SUBST(BIND9_VERSIONSHORT) BIND9_SRCID="SRCID=unset" if test -f "${srcdir}/srcid"; then @@ -4823,13 +4801,13 @@ AC_CONFIG_FILES([ doc/doxygen/Makefile doc/doxygen/doxygen-input-filter doc/misc/Makefile + doc/tex/Makefile + doc/tex/armstyle.sty doc/xsl/Makefile doc/xsl/isc-docbook-chunk.xsl doc/xsl/isc-docbook-html.xsl - doc/xsl/isc-docbook-latex.xsl doc/xsl/isc-manpage.xsl doc/xsl/isc-notes-html.xsl - doc/xsl/isc-notes-latex.xsl isc-config.sh lib/Makefile lib/bind9/Makefile diff --git a/doc/Makefile.in b/doc/Makefile.in index 29074b53fb..bc9b3a432c 100644 --- a/doc/Makefile.in +++ b/doc/Makefile.in @@ -13,8 +13,6 @@ # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR # PERFORMANCE OF THIS SOFTWARE. -# $Id: Makefile.in,v 1.11 2007/06/19 23:47:13 tbox Exp $ - # This Makefile is a placeholder. It exists merely to make # sure that its directory gets created in the object directory # tree when doing a build using separate object directories. @@ -23,7 +21,7 @@ srcdir = @srcdir@ VPATH = @srcdir@ top_srcdir = @top_srcdir@ -SUBDIRS = arm misc xsl doxygen +SUBDIRS = arm misc xsl doxygen tex TARGETS = @BIND9_MAKE_RULES@ diff --git a/doc/arm/.gitignore b/doc/arm/.gitignore new file mode 100644 index 0000000000..05964d527b --- /dev/null +++ b/doc/arm/.gitignore @@ -0,0 +1,3 @@ +noteversion.xml +pkgversion.xml +releaseinfo.xml diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index e4ee23ec49..02885f6e63 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -1,6 +1,3 @@ -]> - - - BIND 9 Administrator Reference Manual - - + + + + BIND 9 Administrator Reference Manual 2004 2005 @@ -44,11 +40,11 @@ 2003 Internet Software Consortium. - - + + - - Introduction + Introduction + The Internet Domain Name System (DNS) consists of the syntax @@ -60,8 +56,8 @@ hierarchical databases. - - Scope of Document +
Scope of Document + The Berkeley Internet Name Domain @@ -72,11 +68,11 @@ BIND version 9 software package for system administrators. - - + +
- - Organization of This Document +
Organization of This Document + In this document, Chapter 1 introduces the basic DNS and BIND concepts. Chapter 2 @@ -102,9 +98,9 @@ and the Domain Name System. - - - Conventions Used in This Document +
+
Conventions Used in This Document + In this document, we use the following general typographic @@ -229,9 +225,9 @@ - - - The Domain Name System (<acronym>DNS</acronym>) +
+
The Domain Name System (<acronym>DNS</acronym>) + The purpose of this document is to explain the installation and upkeep of the BIND (Berkeley Internet @@ -240,8 +236,8 @@ (DNS) as they relate to BIND. - - DNS Fundamentals +
DNS Fundamentals + The Domain Name System (DNS) is a hierarchical, distributed @@ -263,8 +259,8 @@ from ISC as a separate download. - - Domains and Domain Names +
Domains and Domain Names + The data stored in the DNS is identified by domain names that are organized as a tree according to @@ -312,10 +308,10 @@ the DNS protocol, please refer to the standards documents listed in . - +
- - Zones +
Zones + To properly operate a name server, it is important to understand the difference between a zone @@ -368,10 +364,10 @@ be a slave server for your domain, you are actually asking for slave service for some collection of zones. - +
- - Authoritative Name Servers +
Authoritative Name Servers + Each zone is served by at least @@ -389,8 +385,8 @@ dig (). - - The Primary Master +
The Primary Master + The authoritative server where the master copy of the zone @@ -409,10 +405,10 @@ by humans at all, but may instead be the result of dynamic update operations. - +
- - Slave Servers +
Slave Servers + The other authoritative servers, the slave servers (also known as secondary servers) @@ -425,10 +421,10 @@ to transfer it from another slave. In other words, a slave server may itself act as a master to a subordinate slave server. - +
- - Stealth Servers +
Stealth Servers + Usually all of the zone's authoritative servers are listed in @@ -463,12 +459,12 @@ with the outside world. - +
- - +
+
Caching Name Servers - Caching Name Servers + - +
- - Name Server Intensive Environment Issues +
Name Server Intensive Environment Issues + For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and @@ -639,10 +635,10 @@ this has the disadvantage of making many more external queries, as none of the name servers share their cached data. - +
- - Supported Operating Systems +
Supported Operating Systems + ISC BIND 9 compiles and runs on a large number @@ -653,21 +649,21 @@ directory of the BIND 9 source distribution. - +
- - Name Server Configuration + Name Server Configuration + In this chapter we provide some suggested configurations along with guidelines for their use. We suggest reasonable values for certain option settings. - - Sample Configurations - - A Caching-only Name Server +
Sample Configurations + +
A Caching-only Name Server + The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All @@ -696,10 +692,10 @@ zone "0.0.127.in-addr.arpa" { }; - +
- - An Authoritative-only Name Server +
An Authoritative-only Name Server + This sample configuration is for an authoritative-only server that is the master server for "example.com" @@ -745,11 +741,11 @@ zone "eng.example.com" { }; - - +
+
- - Load Balancing +
Load Balancing + @@ -11990,10 +11955,10 @@ zone zone_name class - +
- - Class +
Class + The zone's name may optionally be followed by a class. If a class is not specified, class IN (for Internet), @@ -12012,10 +11977,10 @@ zone zone_name classCHAOS class. - +
- - Zone Options +
Zone Options + @@ -12768,9 +12733,9 @@ example.com. NS ns2.example.net. - - - Dynamic Update Policies +
+
Dynamic Update Policies + BIND 9 supports two alternative methods of granting clients the right to perform dynamic updates to a zone, configured by the @@ -13174,10 +13139,10 @@ example.com. NS ns2.example.net. all records associated with a name, the rules are checked for each existing record type. - +
- - Multiple views +
Multiple views + When multiple views are in use, a zone may be referenced by more than one of them. Often, the views @@ -13234,14 +13199,14 @@ view external { An in-view zone is not intended to reference a forward zone. - +
- - - - Zone File - - Types of Resource Records and When to Use Them +
+ +
Zone File + +
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. @@ -13249,8 +13214,8 @@ view external { identified and implemented in the DNS. These are also included. - - Resource Records +
Resource Records + A domain name identifies a node. Each node has a set of @@ -14426,9 +14391,9 @@ view external { frequently used as "pointers" to other data in the DNS. - - - Textual expression of RRs +
+
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 @@ -14625,11 +14590,11 @@ view external { This example shows two addresses for XX.LCS.MIT.EDU, each of a different class. - - +
+
- - Discussion of MX Records +
Discussion of MX Records + As described above, domain servers store information as a @@ -14650,13 +14615,13 @@ view external { 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 + 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 address record - (A or AAAA) — CNAME is not sufficient. + (A or AAAA) — CNAME is not sufficient. For a given domain, if there is both a CNAME record and an @@ -14810,9 +14775,9 @@ view external { any order), and if neither of those succeed, delivery to mail.backup.org will be attempted. - - - Setting TTLs +
+
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 @@ -14881,9 +14846,9 @@ view external { All of these TTLs default to units of seconds, though units can be explicitly specified, for example, 1h30m. - - - Inverse Mapping in IPv4 +
+
Inverse Mapping in IPv4 + Reverse name resolution (that is, translation from IP address to name) is achieved by means of the in-addr.arpa domain @@ -14934,15 +14899,15 @@ view external { The $ORIGIN lines in the examples - are for providing context to the examples only — they do not + 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. - - - Other Zone File Directives +
+
Other Zone File Directives + The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format @@ -14955,8 +14920,8 @@ view external { Master File Directives include $ORIGIN, $INCLUDE, and $TTL. - - The <command>@</command> (at-sign) +
The <command>@</command> (at-sign) + When used in the label (or name) field, the asperand or at-sign (@) symbol represents the current origin. @@ -14964,9 +14929,9 @@ view external { <zone_name> (followed by trailing dot). - - - The <command>$ORIGIN</command> Directive +
+
The <command>$ORIGIN</command> Directive + Syntax: $ORIGIN domain-name @@ -14996,9 +14961,9 @@ WWW CNAME MAIN-SERVER WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. - - - The <command>$INCLUDE</command> Directive +
+
The <command>$INCLUDE</command> Directive + Syntax: $INCLUDE filename @@ -15030,9 +14995,9 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. feature, or both. - - - The <command>$TTL</command> Directive +
+
The <command>$TTL</command> Directive + Syntax: $TTL default-ttl @@ -15047,10 +15012,10 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. $TTL is defined in RFC 2308. - - - - <acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive +
+
+
<acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive + Syntax: $GENERATE range @@ -15248,10 +15213,10 @@ HOST-127.EXAMPLE. MX 0 . BIND 8 does not support the optional TTL and CLASS fields. - +
- - Additional File Formats +
Additional File Formats + In addition to the standard textual format, BIND 9 supports the ability to read or dump to zone files in @@ -15307,11 +15272,11 @@ HOST-127.EXAMPLE. MX 0 . portable backup of such a file, conversion to text format is recommended. - - +
+
- - BIND9 Statistics +
BIND9 Statistics + BIND 9 maintains lots of statistics information and provides several interfaces for users to @@ -15463,8 +15428,8 @@ HOST-127.EXAMPLE. MX 0 . (see .) - - The Statistics File +
The Statistics File + The text format statistics dump begins with a line, like: @@ -15500,10 +15465,10 @@ HOST-127.EXAMPLE. MX 0 . --- Statistics Dump --- (973798949) - +
- - Statistics Counters +
Statistics Counters + The following tables summarize statistics counters that BIND 9 provides. @@ -15521,8 +15486,8 @@ HOST-127.EXAMPLE. MX 0 . BIND 8 statistics, if applicable. - - Name Server Statistics Counters +
Name Server Statistics Counters + @@ -15581,7 +15546,7 @@ HOST-127.EXAMPLE. MX 0 . ReqEdns0 - + @@ -15594,7 +15559,7 @@ HOST-127.EXAMPLE. MX 0 . ReqBadEDNSVer - + @@ -15607,7 +15572,7 @@ HOST-127.EXAMPLE. MX 0 . ReqTSIG - + @@ -15620,7 +15585,7 @@ HOST-127.EXAMPLE. MX 0 . ReqSIG0 - + @@ -15633,7 +15598,7 @@ HOST-127.EXAMPLE. MX 0 . ReqBadSIG - + @@ -15724,7 +15689,7 @@ HOST-127.EXAMPLE. MX 0 . RespTruncated - + @@ -15737,7 +15702,7 @@ HOST-127.EXAMPLE. MX 0 . RespEDNS0 - + @@ -15750,7 +15715,7 @@ HOST-127.EXAMPLE. MX 0 . RespTSIG - + @@ -15763,7 +15728,7 @@ HOST-127.EXAMPLE. MX 0 . RespSIG0 - + @@ -15776,7 +15741,7 @@ HOST-127.EXAMPLE. MX 0 . QrySuccess - + @@ -15795,7 +15760,7 @@ HOST-127.EXAMPLE. MX 0 . QryAuthAns - + @@ -15821,7 +15786,7 @@ HOST-127.EXAMPLE. MX 0 . QryReferral - + @@ -15838,7 +15803,7 @@ HOST-127.EXAMPLE. MX 0 . QryNxrrset - + @@ -15936,7 +15901,7 @@ HOST-127.EXAMPLE. MX 0 . QryDropped - + @@ -15964,7 +15929,7 @@ HOST-127.EXAMPLE. MX 0 . QryFailure - + @@ -15989,7 +15954,7 @@ HOST-127.EXAMPLE. MX 0 . QryNXRedir - + @@ -16002,7 +15967,7 @@ HOST-127.EXAMPLE. MX 0 . QryNXRedirRLookup - + @@ -16016,7 +15981,7 @@ HOST-127.EXAMPLE. MX 0 . XfrReqDone - + @@ -16029,7 +15994,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateReqFwd - + @@ -16042,7 +16007,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateRespFwd - + @@ -16055,7 +16020,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateFwdFail - + @@ -16068,7 +16033,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateDone - + @@ -16081,7 +16046,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateFail - + @@ -16094,7 +16059,7 @@ HOST-127.EXAMPLE. MX 0 . UpdateBadPrereq - + @@ -16107,7 +16072,7 @@ HOST-127.EXAMPLE. MX 0 . RateDropped - + @@ -16120,7 +16085,7 @@ HOST-127.EXAMPLE. MX 0 . RateSlipped - + @@ -16133,7 +16098,7 @@ HOST-127.EXAMPLE. MX 0 . RPZRewrites - + @@ -16144,10 +16109,10 @@ HOST-127.EXAMPLE. MX 0 . - +
- - Zone Maintenance Statistics Counters +
Zone Maintenance Statistics Counters + @@ -16300,10 +16265,10 @@ HOST-127.EXAMPLE. MX 0 . - +
- - Resolver Statistics Counters +
Resolver Statistics Counters + @@ -16438,7 +16403,7 @@ HOST-127.EXAMPLE. MX 0 . EDNS0Fail - + @@ -16471,7 +16436,7 @@ HOST-127.EXAMPLE. MX 0 . Truncated - + @@ -16510,7 +16475,7 @@ HOST-127.EXAMPLE. MX 0 . QueryAbort - + @@ -16523,7 +16488,7 @@ HOST-127.EXAMPLE. MX 0 . QuerySockFail - + @@ -16539,7 +16504,7 @@ HOST-127.EXAMPLE. MX 0 . QueryTimeout - + @@ -16578,7 +16543,7 @@ HOST-127.EXAMPLE. MX 0 . GlueFetchv4Fail - + @@ -16591,7 +16556,7 @@ HOST-127.EXAMPLE. MX 0 . GlueFetchv6Fail - + @@ -16604,7 +16569,7 @@ HOST-127.EXAMPLE. MX 0 . ValAttempt - + @@ -16617,7 +16582,7 @@ HOST-127.EXAMPLE. MX 0 . ValOk - + @@ -16630,7 +16595,7 @@ HOST-127.EXAMPLE. MX 0 . ValNegOk - + @@ -16643,7 +16608,7 @@ HOST-127.EXAMPLE. MX 0 . ValFail - + @@ -16656,7 +16621,7 @@ HOST-127.EXAMPLE. MX 0 . QryRTTnn - + @@ -16686,10 +16651,10 @@ HOST-127.EXAMPLE. MX 0 . - +
- - Socket I/O Statistics Counters +
Socket I/O Statistics Counters + Socket I/O statistics counters are defined per socket @@ -16844,9 +16809,9 @@ HOST-127.EXAMPLE. MX 0 . - - - Compatibility with <emphasis>BIND</emphasis> 8 Counters +
+
Compatibility with <emphasis>BIND</emphasis> 8 Counters + Most statistics counters that were available in BIND 8 are also supported in @@ -16897,15 +16862,15 @@ HOST-127.EXAMPLE. MX 0 . - - - +
+
+
- - <acronym>BIND</acronym> 9 Security Considerations - - Access Control Lists + <acronym>BIND</acronym> 9 Security Considerations + +
Access Control Lists + Access Control Lists (ACLs) are address match lists that you can set up and nickname for future use in @@ -17094,10 +17059,10 @@ allow-query { !{ !10/8; any; }; key example; }; will only matches when both conditions are true. - +
- - <command>Chroot</command> and <command>Setuid</command> +
<command>Chroot</command> and <command>Setuid</command> + On UNIX servers, it is possible to run BIND in a chrooted environment (using @@ -17121,8 +17086,8 @@ allow-query { !{ !10/8; any; }; key example; }; /usr/local/sbin/named -u 202 -t /var/named - - The <command>chroot</command> Environment +
The <command>chroot</command> Environment + In order for a chroot environment @@ -17148,10 +17113,10 @@ allow-query { !{ !10/8; any; }; key example; }; /dev/log, and /etc/localtime. - +
- - Using the <command>setuid</command> Function +
Using the <command>setuid</command> Function + Prior to running the named daemon, @@ -17169,11 +17134,11 @@ allow-query { !{ !10/8; any; }; key example; }; unprivileged user, it will not be able to bind to new restricted ports if the server is reloaded. - - +
+
- - Dynamic Update Security +
Dynamic Update Security + Access to the dynamic @@ -17215,15 +17180,15 @@ allow-query { !{ !10/8; any; }; key example; }; all. - +
- - Troubleshooting - - Common Problems - - It's not working; how can I figure out what's wrong? + Troubleshooting + +
Common Problems + +
It's not working; how can I figure out what's wrong? + The best solution to solving installation and @@ -17233,13 +17198,13 @@ allow-query { !{ !10/8; any; }; key example; }; what went wrong and how to fix the problem. - - - - Incrementing and Changing the Serial Number +
+
+
Incrementing and Changing the Serial Number + - Zone serial numbers are just numbers — they aren't + 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. Occasionally they will make a mistake and set them to a @@ -17264,9 +17229,9 @@ allow-query { !{ !10/8; any; }; key example; }; it to be, and reload the zone again. - - - Where Can I Get Help? +
+
Where Can I Get Help? + The Internet Systems Consortium @@ -17284,23 +17249,23 @@ allow-query { !{ !10/8; any; }; key example; }; To discuss arrangements for support, contact - info@isc.org or visit the + info@isc.org or visit the ISC web page at - http://www.isc.org/services/support/ + http://www.isc.org/services/support/ to read more. - +
- - Release Notes - + Release Notes + + - - A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym> - + A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym> + +
DNS + 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 @@ -17334,6 +17299,9 @@ allow-query { !{ !10/8; any; }; key example; }; Administration (DARPA). +
+ +
BIND Versions of BIND through 4.8.3 were maintained by the Computer @@ -17347,7 +17315,7 @@ allow-query { !{ !10/8; any; }; key example; }; 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 Øivind Kure. + handled by Mike Karels and Øivind Kure. BIND versions 4.9 and 4.9.1 were @@ -17395,12 +17363,13 @@ allow-query { !{ !10/8; any; }; key example; }; of several corporations, and by the tireless work efforts of numerous individuals. +
- - General <acronym>DNS</acronym> Reference Information - - IPv6 addresses (AAAA) + General <acronym>DNS</acronym> Reference Information + +
IPv6 addresses (AAAA) + IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the DNS to facilitate @@ -17455,11 +17424,11 @@ allow-query { !{ !10/8; any; }; key example; }; string of zeros that can fit, and can be used only once in an address. - - - Bibliography (and Suggested Reading) - - Request for Comments (RFCs) +
+
Bibliography (and Suggested Reading) + +
Request for Comments (RFCs) + Specification documents for the Internet protocol suite, including the DNS, are published as part of @@ -17469,886 +17438,538 @@ allow-query { !{ !10/8; any; }; key example; }; Engineering Steering Group (IESG). RFCs can be obtained online via FTP at: - + ftp://www.isi.edu/in-notes/RFCxxxx.txt - + (where xxxx 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 - Standards + RFC974 - - Partridge - C. - - Mail Routing and the Domain System + PartridgeC. + Mail Routing and the Domain System January 1986 RFC1034 - - Mockapetris - P.V. - - Domain Names — Concepts and Facilities + MockapetrisP.V. + Domain Names — Concepts and Facilities November 1987 RFC1035 - - Mockapetris - P. V. - Domain Names — Implementation and - Specification + MockapetrisP. V. Domain Names — Implementation and + Specification November 1987 - + Proposed Standards - Proposed Standards + RFC2181 - - Elz - R., R. Bush - - Clarifications to the <acronym>DNS</acronym> - Specification + ElzR., R. Bush + Clarifications to the DNS + Specification July 1997 RFC2308 - - Andrews - M. - - Negative Caching of <acronym>DNS</acronym> - Queries + AndrewsM. + Negative Caching of DNS + Queries March 1998 RFC1995 - - Ohta - M. - - Incremental Zone Transfer in <acronym>DNS</acronym> + OhtaM. + Incremental Zone Transfer in DNS August 1996 RFC1996 - - Vixie - P. - - A Mechanism for Prompt Notification of Zone Changes + VixieP. + A Mechanism for Prompt Notification of Zone Changes August 1996 RFC2136 - - Vixie - P. - - - S. - Thomson - - - Y. - Rekhter - - - J. - Bound - + VixieP. + S.Thomson + Y.Rekhter + J.Bound - Dynamic Updates in the Domain Name System + Dynamic Updates in the Domain Name System April 1997 RFC2671 - - P. - Vixie - + P.Vixie - Extension Mechanisms for DNS (EDNS0) + Extension Mechanisms for DNS (EDNS0) August 1997 RFC2672 - - M. - Crawford - + M.Crawford - Non-Terminal DNS Name Redirection + Non-Terminal DNS Name Redirection August 1999 RFC2845 - - Vixie - P. - - - O. - Gudmundsson - - - D. - Eastlake - 3rd - - - B. - Wellington - + VixieP. + O.Gudmundsson + D.Eastlake3rd + B.Wellington - Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG) + Secret Key Transaction Authentication for DNS (TSIG) May 2000 RFC2930 - - D. - Eastlake - 3rd - + D.Eastlake3rd - Secret Key Establishment for DNS (TKEY RR) + Secret Key Establishment for DNS (TKEY RR) September 2000 RFC2931 - - D. - Eastlake - 3rd - + D.Eastlake3rd - DNS Request and Transaction Signatures (SIG(0)s) + DNS Request and Transaction Signatures (SIG(0)s) September 2000 RFC3007 - - B. - Wellington - + B.Wellington - Secure Domain Name System (DNS) Dynamic Update + Secure Domain Name System (DNS) Dynamic Update November 2000 RFC3645 - - S. - Kwan - - - P. - Garg - - - J. - Gilroy - - - L. - Esibov - - - J. - Westhead - - - R. - Hall - + S.Kwan + P.Garg + J.Gilroy + L.Esibov + J.Westhead + R.Hall - Generic Security Service Algorithm for Secret + <citetitle>Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS - (GSS-TSIG) + (GSS-TSIG) October 2003 - - <acronym>DNS</acronym> Security Proposed Standards + <acronym>DNS</acronym> Security Proposed Standards + RFC3225 - - D. - Conrad - + D.Conrad - Indicating Resolver Support of DNSSEC + Indicating Resolver Support of DNSSEC December 2001 RFC3833 - - D. - Atkins - - - R. - Austein - + D.Atkins + R.Austein - Threat Analysis of the Domain Name System (DNS) + Threat Analysis of the Domain Name System (DNS) August 2004 RFC4033 - - R. - Arends - - - R. - Austein - - - M. - Larson - - - D. - Massey - - - S. - Rose - + R.Arends + R.Austein + M.Larson + D.Massey + S.Rose - DNS Security Introduction and Requirements + DNS Security Introduction and Requirements March 2005 RFC4034 - - R. - Arends - - - R. - Austein - - - M. - Larson - - - D. - Massey - - - S. - Rose - + R.Arends + R.Austein + M.Larson + D.Massey + S.Rose - Resource Records for the DNS Security Extensions + Resource Records for the DNS Security Extensions March 2005 RFC4035 - - R. - Arends - - - R. - Austein - - - M. - Larson - - - D. - Massey - - - S. - Rose - + R.Arends + R.Austein + M.Larson + D.Massey + S.Rose - Protocol Modifications for the DNS - Security Extensions + Protocol Modifications for the DNS + Security Extensions March 2005 - - Other Important RFCs About <acronym>DNS</acronym> - Implementation + Other Important RFCs About <acronym>DNS</acronym> + Implementation + RFC1535 - - Gavron - E. - - A Security Problem and Proposed Correction With Widely - Deployed <acronym>DNS</acronym> Software + GavronE. + A Security Problem and Proposed Correction With Widely + Deployed DNS Software October 1993 RFC1536 - - Kumar - A. - - - J. - Postel - - - C. - Neuman - - - P. - Danzig - - - S. - Miller - + KumarA. + J.Postel + C.Neuman + P.Danzig + S.Miller - Common <acronym>DNS</acronym> Implementation - Errors and Suggested Fixes + Common DNS Implementation + Errors and Suggested Fixes October 1993 RFC1982 - - Elz - R. - - - R. - Bush - + ElzR. + R.Bush - Serial Number Arithmetic + Serial Number Arithmetic August 1996 RFC4074 - - Morishita - Y. - - - T. - Jinmei - + MorishitaY. + T.Jinmei - Common Misbehaviour Against <acronym>DNS</acronym> - Queries for IPv6 Addresses + Common Misbehaviour Against DNS + Queries for IPv6 Addresses May 2005 - - Resource Record Types + Resource Record Types + RFC1183 - - Everhart - C.F. - - - L. A. - Mamakos - - - R. - Ullmann - - - P. - Mockapetris - + EverhartC.F. + L. A.Mamakos + R.Ullmann + P.Mockapetris - New <acronym>DNS</acronym> RR Definitions + New DNS RR Definitions October 1990 RFC1706 - - Manning - B. - - - R. - Colella - + ManningB. + R.Colella - <acronym>DNS</acronym> NSAP Resource Records + DNS NSAP Resource Records October 1994 RFC2168 - - Daniel - R. - - - M. - Mealling - + DanielR. + M.Mealling - Resolution of Uniform Resource Identifiers using - the Domain Name System + Resolution of Uniform Resource Identifiers using + the Domain Name System June 1997 RFC1876 - - Davis - C. - - - P. - Vixie - - - T. - Goodwin - - - I. - Dickinson - + DavisC. + P.Vixie + T.Goodwin + I.Dickinson - A Means for Expressing Location Information in the + <citetitle>A Means for Expressing Location Information in the Domain - Name System + Name System January 1996 RFC2052 - - Gulbrandsen - A. - - - P. - Vixie - + GulbrandsenA. + P.Vixie - A <acronym>DNS</acronym> RR for Specifying the + <citetitle>A <acronym>DNS</acronym> RR for Specifying the Location of - Services + Services October 1996 RFC2163 - - Allocchio - A. - - Using the Internet <acronym>DNS</acronym> to + <author><personname><surname>Allocchio</surname><firstname>A.</firstname></personname></author> + <citetitle>Using the Internet <acronym>DNS</acronym> to Distribute MIXER - Conformant Global Address Mapping + Conformant Global Address Mapping January 1998 RFC2230 - - Atkinson - R. - - Key Exchange Delegation Record for the <acronym>DNS</acronym> + AtkinsonR. + Key Exchange Delegation Record for the DNS October 1997 RFC2536 - - Eastlake - D. - 3rd - - DSA KEYs and SIGs in the Domain Name System (DNS) + EastlakeD.3rd + DSA KEYs and SIGs in the Domain Name System (DNS) March 1999 RFC2537 - - Eastlake - D. - 3rd - - RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) + EastlakeD.3rd + RSA/MD5 KEYs and SIGs in the Domain Name System (DNS) March 1999 RFC2538 - - Eastlake - D. - 3rd - - - Gudmundsson - O. - + EastlakeD.3rd + GudmundssonO. - Storing Certificates in the Domain Name System (DNS) + Storing Certificates in the Domain Name System (DNS) March 1999 RFC2539 - - Eastlake - D. - 3rd - + EastlakeD.3rd - Storage of Diffie-Hellman Keys in the Domain Name System (DNS) + Storage of Diffie-Hellman Keys in the Domain Name System (DNS) March 1999 RFC2540 - - Eastlake - D. - 3rd - + EastlakeD.3rd - Detached Domain Name System (DNS) Information + Detached Domain Name System (DNS) Information March 1999 RFC2782 - - Gulbrandsen - A. - - - Vixie - P. - - - Esibov - L. - - A DNS RR for specifying the location of services (DNS SRV) + GulbrandsenA. + VixieP. + EsibovL. + A DNS RR for specifying the location of services (DNS SRV) February 2000 RFC2915 - - Mealling - M. - - - Daniel - R. - - The Naming Authority Pointer (NAPTR) DNS Resource Record + MeallingM. + DanielR. + The Naming Authority Pointer (NAPTR) DNS Resource Record September 2000 RFC3110 - - Eastlake - D. - 3rd - - RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) + EastlakeD.3rd + RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS) May 2001 RFC3123 - - Koch - P. - - A DNS RR Type for Lists of Address Prefixes (APL RR) + KochP. + A DNS RR Type for Lists of Address Prefixes (APL RR) June 2001 RFC3596 - - Thomson - S. - - - C. - Huitema - - - V. - Ksinant - - - M. - Souissi - + ThomsonS. + C.Huitema + V.Ksinant + M.Souissi - <acronym>DNS</acronym> Extensions to support IP - version 6 + DNS Extensions to support IP + version 6 October 2003 RFC3597 - - Gustafsson - A. - - Handling of Unknown DNS Resource Record (RR) Types + GustafssonA. + Handling of Unknown DNS Resource Record (RR) Types September 2003 - - <acronym>DNS</acronym> and the Internet + <acronym>DNS</acronym> and the Internet + RFC1101 - - Mockapetris - P. V. - - <acronym>DNS</acronym> Encoding of Network Names - and Other Types + MockapetrisP. V. + DNS Encoding of Network Names + and Other Types April 1989 RFC1123 - - Braden - R. - - Requirements for Internet Hosts - Application and - Support + BradenR. + Requirements for Internet Hosts - Application and + Support October 1989 RFC1591 - - Postel - J. - - Domain Name System Structure and Delegation + PostelJ. + Domain Name System Structure and Delegation March 1994 RFC2317 - - Eidnes - H. - - - G. - de Groot - - - P. - Vixie - + EidnesH. + G.de Groot + P.Vixie - Classless IN-ADDR.ARPA Delegation + Classless IN-ADDR.ARPA Delegation March 1998 RFC2826 - - Internet Architecture Board - + Internet Architecture Board - IAB Technical Comment on the Unique DNS Root + IAB Technical Comment on the Unique DNS Root May 2000 RFC2929 - - Eastlake - D. - 3rd - - - Brunner-Williams - E. - - - Manning - B. - + EastlakeD.3rd + Brunner-WilliamsE. + ManningB. - Domain Name System (DNS) IANA Considerations + Domain Name System (DNS) IANA Considerations September 2000 - - <acronym>DNS</acronym> Operations + <acronym>DNS</acronym> Operations + RFC1033 - - Lottor - M. - - Domain administrators operations guide + LottorM. + Domain administrators operations guide November 1987 RFC1537 - - Beertema - P. - - Common <acronym>DNS</acronym> Data File - Configuration Errors + BeertemaP. + Common DNS Data File + Configuration Errors October 1993 RFC1912 - - Barr - D. - - Common <acronym>DNS</acronym> Operational and - Configuration Errors + BarrD. + Common DNS Operational and + Configuration Errors February 1996 RFC2010 - - Manning - B. - - - P. - Vixie - + ManningB. + P.Vixie - Operational Criteria for Root Name Servers + Operational Criteria for Root Name Servers October 1996 RFC2219 - - Hamilton - M. - - - R. - Wright - + HamiltonM. + R.Wright - Use of <acronym>DNS</acronym> Aliases for - Network Services + Use of DNS Aliases for + Network Services October 1997 - - Internationalized Domain Names + Internationalized Domain Names + RFC2825 - - IAB - - - Daigle - R. - + IAB + DaigleR. - A Tangled Web: Issues of I18N, Domain Names, - and the Other Internet protocols + A Tangled Web: Issues of I18N, Domain Names, + and the Other Internet protocols May 2000 RFC3490 - - Faltstrom - P. - - - Hoffman - P. - - - Costello - A. - + FaltstromP. + HoffmanP. + CostelloA. - Internationalizing Domain Names in Applications (IDNA) + Internationalizing Domain Names in Applications (IDNA) March 2003 RFC3491 - - Hoffman - P. - - - Blanchet - M. - + HoffmanP. + BlanchetM. - Nameprep: A Stringprep Profile for Internationalized Domain Names + Nameprep: A Stringprep Profile for Internationalized Domain Names March 2003 RFC3492 - - Costello - A. - + CostelloA. - Punycode: A Bootstring encoding of Unicode + <citetitle>Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in - Applications (IDNA) + Applications (IDNA) March 2003 - - Other <acronym>DNS</acronym>-related RFCs + Other <acronym>DNS</acronym>-related RFCs + Note: the following list of RFCs, although @@ -18358,165 +17979,108 @@ allow-query { !{ !10/8; any; }; key example; }; RFC1464 - - Rosenbaum - R. - - Using the Domain Name System To Store Arbitrary String - Attributes + RosenbaumR. + Using the Domain Name System To Store Arbitrary String + Attributes May 1993 RFC1713 - - Romao - A. - - Tools for <acronym>DNS</acronym> Debugging + RomaoA. + Tools for DNS Debugging November 1994 RFC1794 - - Brisco - T. - - <acronym>DNS</acronym> Support for Load - Balancing + BriscoT. + DNS Support for Load + Balancing April 1995 RFC2240 - - Vaughan - O. - - A Legal Basis for Domain Name Allocation + VaughanO. + A Legal Basis for Domain Name Allocation November 1997 RFC2345 - - Klensin - J. - - - T. - Wolf - - - G. - Oglesby - + KlensinJ. + T.Wolf + G.Oglesby - Domain Names and Company Name Retrieval + Domain Names and Company Name Retrieval May 1998 RFC2352 - - Vaughan - O. - - A Convention For Using Legal Names as Domain Names + VaughanO. + A Convention For Using Legal Names as Domain Names May 1998 RFC3071 - - Klensin - J. - + KlensinJ. - Reflections on the DNS, RFC 1591, and Categories of Domains + Reflections on the DNS, RFC 1591, and Categories of Domains February 2001 RFC3258 - - Hardie - T. - + HardieT. - Distributing Authoritative Name Servers via - Shared Unicast Addresses + Distributing Authoritative Name Servers via + Shared Unicast Addresses April 2002 RFC3901 - - Durand - A. - - - J. - Ihren - + DurandA. + J.Ihren - DNS IPv6 Transport Operational Guidelines + DNS IPv6 Transport Operational Guidelines September 2004 - - Obsolete and Unimplemented Experimental RFC + Obsolete and Unimplemented Experimental RFC + RFC1712 - - Farrell - C. - - - M. - Schulze - - - S. - Pleitner - - - D. - Baldoni - + FarrellC. + M.Schulze + S.Pleitner + D.Baldoni - <acronym>DNS</acronym> Encoding of Geographical - Location + DNS Encoding of Geographical + Location November 1994 RFC2673 - - Crawford - M. - + CrawfordM. - Binary Labels in the Domain Name System + Binary Labels in the Domain Name System August 1999 RFC2874 - - Crawford - M. - - - Huitema - C. - + CrawfordM. + HuitemaC. - DNS Extensions to Support IPv6 Address Aggregation - and Renumbering + DNS Extensions to Support IPv6 Address Aggregation + and Renumbering July 2000 - - Obsoleted DNS Security RFCs + Obsoleted DNS Security RFCs + Most of these have been consolidated into RFC4033, @@ -18526,152 +18090,101 @@ allow-query { !{ !10/8; any; }; key example; }; RFC2065 - - Eastlake - 3rd - D. - - - C. - Kaufman - + Eastlake3rdD. + C.Kaufman - Domain Name System Security Extensions + Domain Name System Security Extensions January 1997 RFC2137 - - Eastlake - 3rd - D. - - Secure Domain Name System Dynamic Update + Eastlake3rdD. + Secure Domain Name System Dynamic Update April 1997 RFC2535 - - Eastlake - 3rd - D. - + Eastlake3rdD. - Domain Name System Security Extensions + Domain Name System Security Extensions March 1999 RFC3008 - - Wellington - B. - + WellingtonB. - Domain Name System Security (DNSSEC) - Signing Authority + Domain Name System Security (DNSSEC) + Signing Authority November 2000 RFC3090 - - Lewis - E. - + LewisE. - DNS Security Extension Clarification on Zone Status + DNS Security Extension Clarification on Zone Status March 2001 RFC3445 - - Massey - D. - - - Rose - S. - + MasseyD. + RoseS. - Limiting the Scope of the KEY Resource Record (RR) + Limiting the Scope of the KEY Resource Record (RR) December 2002 RFC3655 - - Wellington - B. - - - Gudmundsson - O. - + WellingtonB. + GudmundssonO. - Redefinition of DNS Authenticated Data (AD) bit + Redefinition of DNS Authenticated Data (AD) bit November 2003 RFC3658 - - Gudmundsson - O. - + GudmundssonO. - Delegation Signer (DS) Resource Record (RR) + Delegation Signer (DS) Resource Record (RR) December 2003 RFC3755 - - Weiler - S. - + WeilerS. - Legacy Resolver Compatibility for Delegation Signer (DS) + Legacy Resolver Compatibility for Delegation Signer (DS) May 2004 RFC3757 - - Kolkman - O. - - - Schlyter - J. - - - Lewis - E. - + KolkmanO. + SchlyterJ. + LewisE. - Domain Name System KEY (DNSKEY) Resource Record - (RR) Secure Entry Point (SEP) Flag + Domain Name System KEY (DNSKEY) Resource Record + (RR) Secure Entry Point (SEP) Flag April 2004 RFC3845 - - Schlyter - J. - + SchlyterJ. - DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format + DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format August 2004 - - - Internet Drafts +
+
Internet Drafts + Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs @@ -18682,78 +18195,64 @@ allow-query { !{ !10/8; any; }; key example; }; they are "works in progress." IDs have a lifespan of six months after which they are deleted unless updated by their authors. - - - Other Documents About <acronym>BIND</acronym> +
+
Other Documents About <acronym>BIND</acronym> + - - Albitz - Paul - - - Cricket - Liu - + AlbitzPaul + CricketLiu - <acronym>DNS</acronym> and <acronym>BIND</acronym> + DNS and BIND 1998 Sebastopol, CA: O'Reilly and Associates - - +
+
- - BIND 9 DNS Library Support - + BIND 9 DNS Library Support + + - - Manual pages - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Manual pages + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index b71619d41f..288705f158 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -14,13 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - Chapter 1. Introduction - - + + @@ -39,27 +38,28 @@
-
-

-Chapter 1. Introduction

+
+

+Chapter 1. Introduction

Table of Contents

-
-
Scope of Document
-
Organization of This Document
-
Conventions Used in This Document
-
The Domain Name System (DNS)
+
+
Scope of Document
+
Organization of This Document
+
Conventions Used in This Document
+
The Domain Name System (DNS)
-
DNS Fundamentals
-
Domains and Domain Names
-
Zones
-
Authoritative Name Servers
-
Caching Name Servers
-
Name Servers in Multiple Roles
+
DNS Fundamentals
+
Domains and Domain Names
+
Zones
+
Authoritative Name Servers
+
Caching Name Servers
+
Name Servers in Multiple Roles
-

+ +

The Internet Domain Name System (DNS) consists of the syntax to specify the names of entities in the Internet in a hierarchical @@ -69,10 +69,13 @@ group of distributed hierarchical databases.

-
+ +

-Scope of Document

-

+Scope of Document

+ + +

The Berkeley Internet Name Domain (BIND) implements a domain name server for a number of operating systems. This @@ -81,12 +84,14 @@ BIND version 9 software package for system administrators.

-

This version of the manual corresponds to BIND version 9.11.

-
-
+

This version of the manual corresponds to BIND version 9.11.

+
+ +

-Organization of This Document

-

+Organization of This Document

+ +

In this document, Chapter 1 introduces the basic DNS and BIND concepts. Chapter 2 describes resource requirements for running BIND in various @@ -111,18 +116,22 @@ and the Domain Name System.

- -
+
+

-Conventions Used in This Document

-

+Conventions Used in This Document

+ + +

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

-
+ +
+
--++ @@ -176,14 +185,17 @@ -
-

+ + + +

The following conventions are used in descriptions of the BIND configuration file:

-
+
+
--++ @@ -235,46 +247,55 @@ -
+ +

- -
+
+

-The Domain Name System (DNS)

-

+The Domain Name System (DNS)

+ +

The purpose of this document is to explain the installation and upkeep of the BIND (Berkeley Internet Name Domain) software package, and we begin by reviewing the fundamentals of the Domain Name System (DNS) as they relate to BIND.

-
+ +

-DNS Fundamentals

-

+DNS Fundamentals

+ + +

The Domain Name System (DNS) is a hierarchical, distributed database. It stores information for mapping Internet host names to IP addresses and vice versa, mail routing information, and other data used by Internet applications.

-

+ +

Clients look up information in the DNS by calling a resolver library, which sends queries to one or more name servers and interprets the responses. The BIND 9 software distribution contains a - name server, named, and a resolver - library, liblwres. The older - libbind resolver library is also available + name server, named, and a resolver + library, liblwres. The older + libbind resolver library is also available from ISC as a separate download.

- -
+ +
+

-Domains and Domain Names

-

+Domains and Domain Names

+ + +

The data stored in the DNS is identified by domain names that are organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The domain @@ -285,7 +306,8 @@ separated by dots. A label need only be unique within its parent domain.

-

+ +

For example, a domain name for a host at the company Example, Inc. could be ourhost.example.com, @@ -297,7 +319,8 @@ ourhost is the name of the host.

-

+ +

For administrative purposes, the name space is partitioned into areas called zones, each starting at a node and extending down to the leaf nodes or to nodes where other zones @@ -305,27 +328,32 @@ The data for each zone is stored in a name server, which answers queries about the zone using the DNS protocol.

-

+ +

The data associated with each domain name is stored in the form of resource records (RRs). Some of the supported resource record types are described in - the section called “Types of Resource Records and When to Use Them”. + the section called “Types of Resource Records and When to Use Them”.

-

+ +

For more detailed information about the design of the DNS and the DNS protocol, please refer to the standards documents listed in - the section called “Request for Comments (RFCs)”. + the section called “Request for Comments (RFCs)”.

- -
+
+ +

-Zones

-

+Zones

+ +

To properly operate a name server, it is important to understand the difference between a zone and a domain.

-

+ +

As stated previously, a zone is a point of delegation in the DNS tree. A zone consists of those contiguous parts of the domain @@ -337,7 +365,8 @@ parent zone, which should be matched by equivalent NS records at the root of the delegated zone.

-

+ +

For instance, consider the example.com domain which includes names such as host.aaa.example.com and @@ -359,7 +388,8 @@ gain a complete understanding of this difficult and subtle topic.

-

+ +

Though BIND is called a "domain name server", it deals primarily in terms of zones. The master and slave @@ -369,11 +399,14 @@ be a slave server for your domain, you are actually asking for slave service for some collection of zones.

- -
+
+ +

-Authoritative Name Servers

-

+Authoritative Name Servers

+ + +

Each zone is served by at least one authoritative name server, which contains the complete data for the zone. @@ -381,16 +414,20 @@ most zones have two or more authoritative servers, on different networks.

-

+ +

Responses from authoritative servers have the "authoritative answer" (AA) bit set in the response packets. This makes them easy to identify when debugging DNS configurations using tools like - dig (the section called “Diagnostic Tools”). + dig (the section called “Diagnostic Tools”).

-
+ +

-The Primary Master

-

+The Primary Master

+ + +

The authoritative server where the master copy of the zone data is maintained is called the primary master server, or simply the @@ -401,16 +438,19 @@ zone file or master file.

-

+ +

In some cases, however, the master file may not be edited by humans at all, but may instead be the result of dynamic update operations.

- -
+
+ +

-Slave Servers

-

+Slave Servers

+ +

The other authoritative servers, the slave servers (also known as secondary servers) load @@ -422,11 +462,14 @@ to transfer it from another slave. In other words, a slave server may itself act as a master to a subordinate slave server.

- -
+
+ +

-Stealth Servers

-

+Stealth Servers

+ + +

Usually all of the zone's authoritative servers are listed in NS records in the parent zone. These NS records constitute a delegation of the zone from the parent. @@ -437,7 +480,8 @@ list servers in the parent's delegation that are not present at the zone's top level.

-

+ +

A stealth server is a server that is authoritative for a zone but is not listed in that zone's NS records. Stealth servers can be used for keeping a local copy of @@ -448,7 +492,8 @@ are inaccessible.

-

+ +

A configuration where the primary master server itself is a stealth server is often referred to as a "hidden primary" configuration. One use for this configuration is when the primary @@ -456,12 +501,19 @@ is behind a firewall and therefore unable to communicate directly with the outside world.

- - -
+ +
+ + +

-Caching Name Servers

-

+Caching Name Servers

+ + + + + +

The resolver libraries provided by most operating systems are stub resolvers, meaning that they are not capable of @@ -473,22 +525,27 @@ is called a recursive name server; it performs recursive lookups for local clients.

-

+ +

To improve performance, recursive servers cache the results of the lookups they perform. Since the processes of recursion and caching are intimately connected, the terms recursive server and caching server are often used synonymously.

-

+ +

The length of time for which a record may be retained in the cache of a caching name server is controlled by the Time To Live (TTL) field associated with each resource record.

-
+ +

-Forwarding

-

+Forwarding

+ + +

Even a caching name server does not necessarily perform the complete recursive lookup itself. Instead, it can forward some or all of the queries @@ -496,7 +553,8 @@ server, commonly referred to as a forwarder.

-

+ +

There may be one or more forwarders, and they are queried in turn until the list is exhausted or an answer @@ -510,18 +568,23 @@ that can do it, and that server would query the Internet DNS servers on the internal server's behalf.

- - -
+
+ + + +

-Name Servers in Multiple Roles

-

+Name Servers in Multiple Roles

+ + +

The BIND name server can simultaneously act as a master for some zones, a slave for other zones, and as a caching (recursive) server for a set of local clients.

-

+ +

However, since the functions of authoritative name service and caching/recursive name service are logically separate, it is often advantageous to run them on separate server machines. @@ -536,9 +599,11 @@ does not need to be reachable from the Internet at large and can be placed inside a firewall.

- - - + + + + +
@@ -556,6 +621,6 @@
-

BIND 9.11.0pre-alpha

+

BIND 9.11.0pre-alpha

diff --git a/doc/arm/Bv9ARM.ch02.html b/doc/arm/Bv9ARM.ch02.html index 9d713cf13f..9e7ce8cb91 100644 --- a/doc/arm/Bv9ARM.ch02.html +++ b/doc/arm/Bv9ARM.ch02.html @@ -14,13 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - Chapter 2. BIND Resource Requirements - - + + @@ -39,29 +38,33 @@
-
-

-Chapter 2. BIND Resource Requirements

+
+

+Chapter 2. BIND Resource Requirements

Table of Contents

-
-
Hardware requirements
-
CPU Requirements
-
Memory Requirements
-
Name Server Intensive Environment Issues
-
Supported Operating Systems
+
+
Hardware requirements
+
CPU Requirements
+
Memory Requirements
+
Name Server Intensive Environment Issues
+
Supported Operating Systems
-
+ + +

-Hardware requirements

-

+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 features of BIND 9 may prove to be quite CPU intensive however, so organizations that make heavy use of these @@ -70,30 +73,33 @@ full utilization of multiprocessor systems for installations that need it.

-
-
+
+

-CPU Requirements

-

+CPU Requirements

+ +

CPU requirements for BIND 9 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.

- -
+
+ +

-Memory Requirements

-

+Memory Requirements

+ +

The memory of the server has to be large enough to fit the - cache and zones loaded off disk. The max-cache-size + cache and zones loaded off disk. The max-cache-size option can be used to limit the amount of memory used by the cache, at the expense of reducing cache hit rates and causing more DNS traffic. Additionally, if additional section caching - (the section called “Additional Section Caching”) is enabled, - the max-acache-size option can be used to + (the section called “Additional Section Caching”) is enabled, + the max-acache-size option can be used to limit the amount of memory used by the mechanism. It is still good practice to have enough memory to load @@ -104,11 +110,14 @@ a relatively stable size where entries are expiring from the cache as fast as they are being inserted.

- -
+ +
+ +

-Name Server Intensive Environment Issues

-

+Name Server Intensive Environment Issues

+ +

For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal name servers query a main name server, which @@ -121,11 +130,13 @@ this has the disadvantage of making many more external queries, as none of the name servers share their cached data.

- -
+
+ +

-Supported Operating Systems

-

+Supported Operating Systems

+ +

ISC BIND 9 compiles and runs on a large number of Unix-like operating systems and on @@ -135,8 +146,8 @@ directory of the BIND 9 source distribution.

- - + +
@@ -154,6 +165,6 @@
-

BIND 9.11.0pre-alpha

+

BIND 9.11.0pre-alpha

diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index e5f95de5a9..1d4b7590f6 100644 --- a/doc/arm/Bv9ARM.ch03.html +++ b/doc/arm/Bv9ARM.ch03.html @@ -14,13 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - Chapter 3. Name Server Configuration - - + + @@ -39,45 +38,50 @@
-
-

-Chapter 3. Name Server Configuration

+
+

+Chapter 3. Name Server Configuration

Table of Contents

-
-
Sample Configurations
+
+
Sample Configurations
-
A Caching-only Name Server
-
An Authoritative-only Name Server
+
A Caching-only Name Server
+
An Authoritative-only Name Server
-
Load Balancing
-
Name Server Operations
+
Load Balancing
+
Name Server Operations
-
Tools for Use With the Name Server Daemon
-
Signals
+
Tools for Use With the Name Server Daemon
+
Signals
-

+ +

In this chapter we provide some suggested configurations along with guidelines for their use. We suggest reasonable values for certain option settings.

-
+ +

Sample Configurations

-
+ +

-A Caching-only Name Server

-

+A Caching-only Name Server

+ +

The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All queries - from outside clients are refused using the allow-query + from outside clients are refused using the allow-query option. Alternatively, the same effect could be achieved using suitable firewall rules.

+ 
 // Two corporate subnets we wish to allow queries from.
 acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
@@ -95,15 +99,19 @@ zone "0.0.127.in-addr.arpa" {
      notify no;
 };
-
-
+ +
+ +

-An Authoritative-only Name Server

-

+An Authoritative-only Name Server

+ +

This sample configuration is for an authoritative-only server that is the master server for "example.com" and a slave for the subdomain "eng.example.com".

+ 
 options {
      // Working directory
@@ -142,29 +150,37 @@ zone "eng.example.com" {
      masters { 192.168.4.12; };
 };
- - -
+ +
+ + +

-Load Balancing

-

+Load Balancing

+ + + +

A primitive form of load balancing can be achieved in the DNS by using multiple records (such as 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 set of records such as the following means that clients will connect to each machine one third of the time:

-
+ +
+
-----+++++ @@ -272,48 +288,56 @@ zone "eng.example.com" { -
-

+ + +

When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. In the example above, clients will randomly receive records in the order 1, 2, 3; 2, 3, 1; and 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 sub-statement in the - options statement, see - RRset Ordering. + rrset-order sub-statement in the + options statement, see + RRset Ordering.

- -
+ +
+ +

-Name Server Operations

-
+Name Server Operations
+ + +

-Tools for Use With the Name Server Daemon

-

+Tools for Use With the Name Server Daemon

+ +

This section describes several indispensable diagnostic, administrative and monitoring tools available to the system administrator for controlling and debugging the name server daemon.

-
+

Diagnostic Tools

-

- The dig, host, and - nslookup programs are all command + +

+ The dig, host, and + nslookup programs are all command line tools for manually querying name servers. They differ in style and output format.

-
-
dig
+ +
+
dig
-

- The domain information groper (dig) +

+ The domain information groper (dig) is the most versatile and complete of these lookup tools. It has two modes: simple interactive mode for a single query, and batch mode which executes a @@ -322,39 +346,61 @@ zone "eng.example.com" { accessible from the command line.

-

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] + [+query-option] + [-dig-option] + [%comment] +

+

+ The usual simple use of dig will take the form

-

- dig @server domain query-type query-class +

+ dig @server domain query-type query-class

-

+

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

-
-
host
+ +
host
-

- The host utility emphasizes +

+ The host utility emphasizes simplicity and ease of use. By default, it converts between host names and Internet addresses, but its functionality can be extended with the use of options.

-

host [-aCdlnrsTwv] [-c class] [-N ndots] [-t type] [-W timeout] [-R retries] [-m flag] [-4] [-6] hostname [server]

-

+

+ host + [-aCdlnrsTwv] + [-c class] + [-N ndots] + [-t type] + [-W timeout] + [-R retries] + [-m flag] + [-4] + [-6] + hostname + [server] +

+

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

-
-
nslookup
+ +
nslookup
-

nslookup +

nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query name servers for information about various @@ -363,8 +409,15 @@ zone "eng.example.com" { the name and requested information for a host or domain.

-

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

-

+

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

+

Interactive mode is entered when no arguments are given (the default name server will be used) or when the first argument is a @@ -372,7 +425,7 @@ zone "eng.example.com" { Internet address of a name server.

-

+

Non-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument. @@ -380,146 +433,179 @@ zone "eng.example.com" { optional second argument specifies the host name or address of a name server.

-

+

Due to its arcane user interface and frequently inconsistent - behavior, we do not recommend the use of nslookup. - Use dig instead. + behavior, we do not recommend the use of nslookup. + Use dig instead.

-
+
-
-
+
+ +

Administrative Tools

-

+ +

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

-
+
-named-checkconf +named-checkconf
-

- The named-checkconf program +

+ The named-checkconf program checks the syntax of a named.conf file.

-

named-checkconf [-jvz] [-t directory] [filename]

-
+

+ named-checkconf + [-jvz] + [-t directory] + [filename] +

+
-named-checkzone +named-checkzone
-

- The named-checkzone program +

+ The named-checkzone program checks a master file for syntax and consistency.

-

named-checkzone [-djqvD] [-c class] [-o output] [-t directory] [-w directory] [-k (ignore|warn|fail)] [-n (ignore|warn|fail)] [-W (ignore|warn)] zone [filename]

-
+

+ named-checkzone + [-djqvD] + [-c class] + [-o output] + [-t directory] + [-w directory] + [-k (ignore|warn|fail)] + [-n (ignore|warn|fail)] + [-W (ignore|warn)] + zone + [filename] +

+
-named-compilezone -
-

- Similar to named-checkzone, but - it always dumps the zone content to a specified file - (typically in a different format). -

-
-rndc +named-compilezone
-

+

+ Similar to named-checkzone, but + it always dumps the zone content to a specified file + (typically in a different format). +

+
+
+rndc +
+
+

The remote name daemon control - (rndc) program allows the + (rndc) program allows the system administrator to control the operation of a name server. - Since BIND 9.2, rndc - supports all the commands of the BIND 8 ndc - utility except ndc start and - ndc restart, which were also - not supported in ndc's + Since BIND 9.2, rndc + supports all the commands of the BIND 8 ndc + utility except ndc start and + ndc restart, which were also + not supported in ndc's channel mode. - If you run rndc without any + If you run rndc without any options it will display a usage message as follows:

-

rndc [-c config] [-s server] [-p port] [-y key] command [command...]

-

See rndc(8) for details of - the available rndc commands. +

+ rndc + [-c config] + [-s server] + [-p port] + [-y key] + command + [command...] +

+ +

See rndc(8) for details of + the available rndc commands.

-

- rndc requires a configuration file, + +

+ rndc requires a configuration file, since all communication with the server is authenticated with digital signatures that rely on a shared secret, and there is no way to provide that secret other than with a configuration file. The default location for the - rndc configuration file is + rndc configuration file is /etc/rndc.conf, but an alternate location can be specified with the -c option. If the configuration file is not found, - rndc will also look in + rndc will also look in /etc/rndc.key (or whatever sysconfdir was defined when the BIND build was configured). The rndc.key file is generated by - running rndc-confgen -a as + running rndc-confgen -a as described in - the section called “controls Statement Definition and + the section called “controls Statement Definition and Usage”.

-

+ +

The format of the configuration file is similar to that of named.conf, but limited to - only four statements, the options, - key, server and - include + only four statements, the options, + key, server and + include statements. These statements are what associate the secret keys to the servers with which they are meant to be shared. The order of statements is not significant.

-

- The options statement has + +

+ The options statement has three clauses: - default-server, default-key, - and default-port. - default-server takes a + default-server, default-key, + and default-port. + default-server takes a host name or address argument and represents the server that will be contacted if no -s option is provided on the command line. - default-key takes - the name of a key as its argument, as defined by a key statement. - default-port specifies the + default-key takes + the name of a key as its argument, as defined by a key statement. + default-port specifies the port to which - rndc should connect if no + rndc should connect if no port is given on the command line or in a - server statement. + server statement.

-

- The key statement defines a + +

+ The key statement defines a key to be used - by rndc when authenticating + by rndc when authenticating with - named. Its syntax is + named. Its syntax is identical to the - key statement in named.conf. + key statement in named.conf. The keyword key is followed by a key name, which must be a valid domain name, though it need not actually be hierarchical; thus, a string like "rndc_key" is a valid name. - The key statement has two + The key statement has two clauses: - algorithm and secret. + algorithm and secret. While the configuration parser will accept any string as the argument to algorithm, currently only the strings @@ -532,25 +618,28 @@ zone "eng.example.com" { have any meaning. The secret is a base-64 encoded string as specified in RFC 3548.

-

- The server statement + +

+ The server statement associates a key - defined using the key + defined using the key statement with a server. The keyword server is followed by a - host name or address. The server statement - has two clauses: key and port. - The key clause specifies the + host name or address. The server statement + has two clauses: key and port. + The key clause specifies the name of the key to be used when communicating with this server, and the - port clause can be used to - specify the port rndc should + port clause can be used to + specify the port rndc should connect to on the server.

-

+ +

A sample minimal configuration file is as follows:

+ 
 key rndc_key {
      algorithm "hmac-sha256";
@@ -562,65 +651,76 @@ options {
      default-key    rndc_key;
 };
-

+ +

This file, if installed as /etc/rndc.conf, would allow the command:

-

+ +

$ rndc reload

-

+ +

to connect to 127.0.0.1 port 953 and cause the name server to reload, if a name server on the local machine were running with following controls statements:

+ 
 controls {
         inet 127.0.0.1
             allow { localhost; } keys { rndc_key; };
 };
-

+ +

and it had an identical key statement for rndc_key.

-

- Running the rndc-confgen + +

+ Running the rndc-confgen program will conveniently create a rndc.conf file for you, and also display the - corresponding controls + corresponding controls statement that you need to add to named.conf. Alternatively, - you can run rndc-confgen -a + you can run rndc-confgen -a to set up a rndc.key file and not modify named.conf at all.

-
+ +
-
-
-
+ +
+
+

-Signals

-

+Signals

+ + +

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

-
+
+
--++ -
-

SIGHUP

+

SIGHUP

@@ -631,7 +731,7 @@ controls {

-

SIGTERM

+

SIGTERM

@@ -641,7 +741,7 @@ controls {

-

SIGINT

+

SIGINT

@@ -650,10 +750,11 @@ controls {

- - - + + + + +
@@ -671,6 +772,6 @@ controls {
-

BIND 9.11.0pre-alpha

+

BIND 9.11.0pre-alpha

diff --git a/doc/arm/Bv9ARM.ch04.html b/doc/arm/Bv9ARM.ch04.html index 3ab01ba7f5..ca7b94acaa 100644 --- a/doc/arm/Bv9ARM.ch04.html +++ b/doc/arm/Bv9ARM.ch04.html @@ -14,13 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> - Chapter 4. Advanced DNS Features - - + + @@ -39,152 +38,169 @@
-
-

-Chapter 4. Advanced DNS Features

+
+

+Chapter 4. Advanced DNS Features

Table of Contents

-
-
Notify
-
Dynamic Update
-
The journal file
-
Incremental Zone Transfers (IXFR)
-
Split DNS
-
Example split DNS setup
-
TSIG
+
+
Notify
+
Dynamic Update
+
The journal file
+
Incremental Zone Transfers (IXFR)
+
Split DNS
+
Example split DNS setup
+
TSIG
-
Generate Shared Keys for Each Pair of Hosts
-
Copying the Shared Secret to Both Machines
-
Informing the Servers of the Key's Existence
-
Instructing the Server to Use the Key
-
TSIG Key Based Access Control
-
Errors
+
Generate Shared Keys for Each Pair of Hosts
+
Copying the Shared Secret to Both Machines
+
Informing the Servers of the Key's Existence
+
Instructing the Server to Use the Key
+
TSIG Key Based Access Control
+
Errors
-
TKEY
-
SIG(0)
-
DNSSEC
+
TKEY
+
SIG(0)
+
DNSSEC
-
Generating Keys
-
Signing the Zone
-
Configuring Servers
+
Generating Keys
+
Signing the Zone
+
Configuring Servers
-
DNSSEC, Dynamic Zones, and Automatic Signing
+
DNSSEC, Dynamic Zones, and Automatic Signing
-
Converting from insecure to secure
-
Dynamic DNS update method
-
Fully automatic zone signing
-
Private-type records
-
DNSKEY rollovers
-
Dynamic DNS update method
-
Automatic key rollovers
-
NSEC3PARAM rollovers via UPDATE
-
Converting from NSEC to NSEC3
-
Converting from NSEC3 to NSEC
-
Converting from secure to insecure
-
Periodic re-signing
-
NSEC3 and OPTOUT
+
Converting from insecure to secure
+
Dynamic DNS update method
+
Fully automatic zone signing
+
Private-type records
+
DNSKEY rollovers
+
Dynamic DNS update method
+
Automatic key rollovers
+
NSEC3PARAM rollovers via UPDATE
+
Converting from NSEC to NSEC3
+
Converting from NSEC3 to NSEC
+
Converting from secure to insecure
+
Periodic re-signing
+
NSEC3 and OPTOUT
-
Dynamic Trust Anchor Management
+
Dynamic Trust Anchor Management
-
Validating Resolver
-
Authoritative Server
+
Validating Resolver
+
Authoritative Server
-
PKCS#11 (Cryptoki) support
+
PKCS#11 (Cryptoki) support
-
Prerequisites
-
Native PKCS#11
-
OpenSSL-based PKCS#11
-
PKCS#11 Tools
-
Using the HSM
-
Specifying the engine on the command line
-
Running named with automatic zone re-signing
+
Prerequisites
+
Native PKCS#11
+
OpenSSL-based PKCS#11
+
PKCS#11 Tools
+
Using the HSM
+
Specifying the engine on the command line
+
Running named with automatic zone re-signing
-
DLZ (Dynamically Loadable Zones)
+
DLZ (Dynamically Loadable Zones)
-
Configuring DLZ
-
Sample DLZ Driver
+
Configuring DLZ
+
Sample DLZ Driver
-
DynDB (Dynamic Database)
+
DynDB (Dynamic Database)
-
Configuring DynDB
-
Sample DynDB Module
+
Configuring DynDB
+
Sample DynDB Module
-
IPv6 Support in BIND 9
+
IPv6 Support in BIND 9
-
Address Lookups Using AAAA Records
-
Address to Name Lookups Using Nibble Format
+
Address Lookups Using AAAA Records
+
Address to Name Lookups Using Nibble Format
-
+ + +

Notify

-

+ + +

DNS NOTIFY is a mechanism that allows master servers to notify their slave servers of changes to a zone's data. In - response to a NOTIFY from a master server, the + response to a NOTIFY from a master server, the slave will check to see that its version of the zone is the current version and, if not, initiate a zone transfer.

-

+ +

For more information about DNS - NOTIFY, see the description of the - notify option in the section called “Boolean Options” and - the description of the zone option also-notify in - the section called “Zone Transfers”. The NOTIFY + NOTIFY, see the description of the + notify option in the section called “Boolean Options” and + the description of the zone option also-notify in + the section called “Zone Transfers”. The NOTIFY protocol is specified in RFC 1996.

-
+ +

Note

- As a slave zone can also be a master to other slaves, named, - by default, sends NOTIFY messages for every zone - it loads. Specifying notify master-only; will - cause named to only send NOTIFY for master + As a slave zone can also be a master to other slaves, named, + by default, sends NOTIFY messages for every zone + it loads. Specifying notify master-only; will + cause named to only send NOTIFY for master zones that it loads.
-
-
+ +
+ +

Dynamic Update

-

+ + +

Dynamic Update is a method for adding, replacing or deleting records in a master server by sending it a special form of DNS messages. The format and meaning of these messages is specified in RFC 2136.

-

+ +

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

-

- If the zone's update-policy is set to + +

+ If the zone's update-policy is set to local, updates to the zone will be permitted for the key local-ddns, - which will be generated by named at startup. - See the section called “Dynamic Update Policies” for more details. + which will be generated by named at startup. + See the section called “Dynamic Update Policies” for more details.

-

+ +

Dynamic updates using Kerberos signed requests can be made using the TKEY/GSS protocol by setting either the - tkey-gssapi-keytab option, or alternatively - by setting both the tkey-gssapi-credential - and tkey-domain options. Once enabled, + tkey-gssapi-keytab option, or alternatively + by setting both the tkey-gssapi-credential + and tkey-domain options. Once enabled, Kerberos signed requests will be matched against the update policies for the zone, using the Kerberos principal as the signer for the request.

-

+ +

Updating of secure zones (zones using DNSSEC) follows RFC 3007: RRSIG, NSEC and NSEC3 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 journal file

-

+ + +

All changes made to a zone using dynamic update are stored in the zone's journal file. This file is automatically created by the server when the first dynamic update takes place. @@ -194,7 +210,8 @@ file unless specifically overridden. The journal file is in a binary format and should not be edited manually.

-

+ +

The server will also occasionally write ("dump") the complete contents of the updated zone to its zone file. This is not done immediately after @@ -207,55 +224,66 @@ will be removed when the dump is complete, and can be safely ignored.

-

+ +

When a server is restarted after a shutdown or crash, it will replay the journal file to incorporate into the zone any updates that took place after the last zone dump.

-

+ +

Changes that result from incoming incremental zone transfers are also journalled in a similar way.

-

+ +

The zone files of dynamic zones cannot normally be edited by hand because they are not guaranteed to contain the most recent dynamic changes — those are only in the journal file. The only way to ensure that the zone file of a dynamic zone - is up to date is to run rndc stop. + is up to date is to run rndc stop.

-

+ +

If you have to make changes to a dynamic zone manually, the following procedure will work: Disable dynamic updates to the zone using - rndc freeze zone. + rndc freeze zone. This will update the zone's master file with the changes stored in its .jnl file. Edit the zone file. Run - rndc thaw zone + rndc thaw zone to reload the changed zone and re-enable dynamic updates.

-

- rndc sync zone + +

+ rndc sync zone will update the zone file with changes from the journal file without stopping dynamic updates; this may be useful for viewing the current zone state. To remove the .jnl file after updating the zone file, use - rndc sync -clean. + rndc sync -clean.

-
-
-
+ +
+ +
+ +

Incremental Zone Transfers (IXFR)

-

+ + +

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

-

+ +

When acting as a master, BIND 9 supports IXFR for those zones where the necessary change history information is available. These @@ -263,27 +291,30 @@ whose data was obtained by IXFR. For manually maintained master zones, and for slave zones obtained by performing a full zone transfer (AXFR), IXFR is supported only if the option - ixfr-from-differences is set + ixfr-from-differences is set to yes.

-

+ +

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

-
-
+
+ +

-Split DNS

-

+Split DNS

+ +

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

-

+

One common reason for setting up a DNS system this way is to hide "internal" DNS information from "external" clients on the Internet. There is some debate as to whether or not this is actually @@ -297,17 +328,18 @@ choose to use a Split DNS to present a consistent view of itself to the outside world.

-

+

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

-
+

-Example split DNS setup

-

+Example split DNS setup

+ +

Let's say a company named Example, Inc. (example.com) has several corporate sites that have an internal network with @@ -315,14 +347,14 @@ Internet Protocol (IP) space and an external demilitarized zone (DMZ), 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 name servers. One set will be on the inside network (in the reserved @@ -330,7 +362,7 @@ "proxy" hosts that can talk to both sides of its network, in the DMZ.

-

+

The internal servers will be configured to forward all queries, except queries for site1.internal, site2.internal, site1.example.com, and site2.example.com, to the servers @@ -339,20 +371,20 @@ for site1.example.com, site2.example.com, site1.internal, and site2.internal.

-

+

To protect the site1.internal and site2.internal domains, the internal name servers must be configured to disallow all queries to these domains from any external hosts, including the bastion hosts.

-

+

The external servers, which are on the bastion hosts, will be configured to serve the "public" version of the site1 and site2.example.com zones. This could include things such as the host records for public servers (www.example.com and ftp.example.com), and mail exchange (MX) records (a.mx.example.com and b.mx.example.com).

-

+

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 @@ -361,11 +393,11 @@ be delivered to the bastion host, which can then forward it on to internal hosts.

-

+

Here's an example of a wildcard MX record:

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

+ 

*   IN MX 10 external1.example.com.
+

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 @@ -373,57 +405,72 @@ the bastion hosts will need to be configured to point to the internal name servers 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 name servers for DNS queries. This could also be enforced via selective filtering on the network.

-

+

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

-
    -
  • +
      +
    • + Look up any hostnames in the site1 and site2.example.com zones. -
      • -
    • + +
      • +
    • + Look up any hostnames in the site1.internal and site2.internal domains. -
      • -
    • Look up any hostnames on the Internet.
      • -
    • Exchange mail with both internal and external people.
      • + + +
    • + Look up any hostnames on the Internet. +
      • +
    • + Exchange mail with both internal and external people. +
    -

    +

    Hosts on the Internet will be able to:

    -
      -
    • +
        +
      • + Look up any hostnames in the site1 and site2.example.com zones. -
        • -
      • + +
        • +
      • + Exchange mail with anyone in the site1 and site2.example.com zones. -
        • + +
      -

      + +

      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 the section called “Sample Configurations”. + for information on how to configure your zone files, see the section called “Sample Configurations”.

      -

      + +

      Internal DNS server config:

      + 
       
 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
@@ -485,9 +532,11 @@ zone "site2.internal" {
   allow-transfer { internals; }
 };
      -

      + +

      External (bastion host) DNS server config:

      + 
       acl internals { 172.16.72.0/24; 192.168.1.0/24; };
 
@@ -522,190 +571,214 @@ zone "site2.example.com" {
   allow-transfer { internals; externals; }
 };
      -

      + +

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

      + 
       search ...
 nameserver 172.16.72.2
 nameserver 172.16.72.3
 nameserver 172.16.72.4
      -
    -
-
+ +
+
+

TSIG

-

+ +

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

-

+

BIND primarily supports TSIG for server to server communication. This includes zone transfer, notify, and recursive query messages. Resolvers based on newer versions of BIND 8 have limited support for TSIG.

-

+ +

TSIG can also be useful for dynamic update. A primary server for a dynamic zone should control access to the dynamic update service, but IP-based access control is insufficient. The cryptographic access control provided by TSIG - is far superior. The nsupdate + is far superior. The nsupdate program supports TSIG via the -k and -y command line options or inline by use - of the key. + of the key.

-
+ +

-Generate Shared Keys for Each Pair of Hosts

-

+Generate Shared Keys for Each Pair of Hosts

+ +

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

-
+

-Automatic Generation

-

+Automatic Generation

+ +

The following command will generate a 128-bit (16 byte) HMAC-SHA256 key as described above. Longer keys are better, but shorter keys are easier to read. Note that the maximum key length is the digest length, here 256 bits.

-

+

dnssec-keygen -a hmac-sha256 -b 128 -n HOST host1-host2.

-

+

The key is in the file Khost1-host2.+163+00000.private. Nothing directly uses this file, but the base-64 encoded string following "Key:" can be extracted from the file and used as a shared secret:

-
Key: La/E5CjG9O+os1jq0a2jdA==
-

+ 

Key: La/E5CjG9O+os1jq0a2jdA==
+

The string "La/E5CjG9O+os1jq0a2jdA==" can be used as the shared secret.

- -
+
+

-Manual Generation

-

+Manual Generation

+ +

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

-

- Also, a known string can be run through mmencode or +

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

- - -
+
+ +

-Copying the Shared Secret to Both Machines

-

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

- -
+
+

-Informing the Servers of the Key's Existence

-

+Informing the Servers of the Key's Existence

+ +

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

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

+ +

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 is included by named.conf.

-

+

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

- -
+
+ +

-Instructing the Server to Use the Key

-

+Instructing the Server to Use the Key

+ +

Since keys are shared between two hosts only, the server must be told when keys are to be used. The following is added to the named.conf file for 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 request 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 request messages to host1.

- -
+
+

-TSIG Key Based Access Control

-

+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. + be denoted key host1-host2.

-

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

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

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

+ +

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

-

- See the section called “Dynamic Update Policies” for a discussion of - the more flexible update-policy statement. + +

+ See the section called “Dynamic Update Policies” for a discussion of + the more flexible update-policy statement.

- -
+ +
+

-Errors

-

+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 (format error) will be returned, since the server will not @@ -713,7 +786,8 @@ allow-update { key host1-host2. ;}; 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 @@ -726,48 +800,55 @@ allow-update { key host1-host2. ;}; verified. In any of these cases, the message's rcode (response code) is set to NOTAUTH (not authenticated).

- - -
+ +
+ +

-TKEY

-

TKEY +TKEY

+ + +

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 + TKEY that specify how the key is generated or assigned. BIND 9 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, + 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 + 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 TKEY process is initiated by a + +

+ The TKEY process is initiated by a client - or server by sending a signed TKEY + 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. + 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 + TKEY mode. When using the Diffie-Hellman - TKEY mode, Diffie-Hellman keys are + TKEY mode, Diffie-Hellman keys are exchanged, and the shared secret is derived by both participants.

- -
+ +
+

-SIG(0)

-

+SIG(0)

+ + +

BIND 9 partially supports DNSSEC SIG(0) transaction signatures as specified in RFC 2535 and RFC 2931. SIG(0) @@ -775,30 +856,37 @@ allow-update { key host1-host2. ;}; is performed in the same manner as TSIG keys; privileges can be granted or denied based on the key name.

-

+ +

When a SIG(0) signed message is received, it will only be verified if the key is known and trusted by the server; the server will not attempt to locate and/or validate the key.

-

+ +

SIG(0) signing of multiple-message TCP streams is not supported.

-

+ +

The only tool shipped with BIND 9 that - generates SIG(0) signed messages is nsupdate. + generates SIG(0) signed messages is nsupdate.

- -
+ +
+

DNSSEC

-

+ + +

Cryptographic authentication of DNS information is possible through the DNS Security (DNSSEC-bis) extensions, defined in RFC 4033, RFC 4034, and RFC 4035. This section describes the creation and use of DNSSEC signed zones.

-

+ +

In order to set up a DNSSEC secure zone, there are a series of steps which must be followed. BIND 9 ships @@ -811,7 +899,8 @@ allow-update { key host1-host2. ;}; that the tools shipped with BIND 9.2.x and earlier are not compatible with the current ones.

-

+ +

There must also be communication with the administrators of the parent and/or child zone to transmit keys. A zone's security status must be indicated by the parent zone for a DNSSEC capable @@ -820,37 +909,45 @@ allow-update { key host1-host2. ;}; delegation point.

-

+ +

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.

-
+ +

-Generating Keys

-

- The dnssec-keygen program is used to +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 + ZONE, and must be usable for authentication. It is recommended that zone keys use a cryptographic algorithm designated as "mandatory to implement" by the IETF; currently the only one is RSASHA1.

-

+ +

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

-

+ +

dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.

-

+ +

Two output files will be produced: Kchild.example.+005+12345.key and Kchild.example.+005+12345.private @@ -866,29 +963,36 @@ allow-update { key host1-host2. ;}; .key file) is used for signature verification.

-

+ +

To generate another key with the same properties (but with a different key tag), repeat the above command.

-

- The dnssec-keyfromlabel program is used + +

+ The dnssec-keyfromlabel program is used to get a key pair from a crypto hardware and build the key - files. Its usage is similar to dnssec-keygen. + files. Its usage is similar to dnssec-keygen.

-

+ +

The public keys should be inserted into the zone file by including the .key files using - $INCLUDE statements. + $INCLUDE statements.

- -
+ +
+

-Signing the Zone

-

- The dnssec-signzone program is used +Signing the Zone

+ + +

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

-

+ +

Any keyset files corresponding to secure subzones should be present. The zone signer will generate NSEC, NSEC3 @@ -898,16 +1002,19 @@ allow-update { key host1-host2. ;}; is not specified, then DS RRsets for the secure child zones need to be added manually.

-

+ +

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 @@ -915,76 +1022,89 @@ allow-update { key host1-host2. ;}; as the input file for the zone.

-

dnssec-signzone + +

dnssec-signzone will also produce a keyset and dsset files and optionally a dlvset file. These are used to provide the parent zone administrators with the DNSKEYs (or their corresponding DS records) that are the secure entry point to the zone.

- -
+ +
+ +

-Configuring Servers

-

- To enable named to respond appropriately +Configuring Servers

+ + +

+ To enable named to respond appropriately to DNS requests from DNSSEC aware clients, - dnssec-enable must be set to yes. + dnssec-enable must be set to yes. (This is the default setting.)

-

- To enable named to validate answers from - other servers, the dnssec-enable option + +

+ To enable named to validate answers from + other servers, the dnssec-enable option must be set to yes, and the - dnssec-validation options must be set to + dnssec-validation options must be set to yes or auto.

-

- If dnssec-validation is set to + +

+ If dnssec-validation is set to auto, then a default trust anchor for the DNS root zone will be used. If it is set to yes, however, then at least one trust anchor must be configured - with a trusted-keys or - managed-keys statement in + with a trusted-keys or + managed-keys statement in named.conf, or DNSSEC validation will not occur. The default setting is yes.

-

- trusted-keys are copies of DNSKEY RRs + +

+ trusted-keys are copies of DNSKEY RRs for zones that are used to form the first link in the cryptographic chain of trust. All keys listed in - trusted-keys (and corresponding zones) + trusted-keys (and corresponding zones) are deemed to exist and only the listed keys will be used to validated the DNSKEY RRset that they are from.

-

- managed-keys are trusted keys which are + +

+ managed-keys are trusted keys which are automatically kept up to date via RFC 5011 trust anchor maintenance.

-

- trusted-keys and - managed-keys are described in more detail + +

+ trusted-keys and + managed-keys are described in more detail later in this document.

-

+ +

Unlike BIND 8, BIND 9 does not verify signatures on load, so zone keys for authoritative zones do not need to be specified in the configuration file.

-

+ +

After DNSSEC gets established, a typical DNSSEC configuration will look something like the following. It has one or more public keys for the root. This allows answers from outside the organization to be validated. It will also have several keys for parts of the namespace the organization - controls. These are here to ensure that named + controls. These are here to ensure that named is immune to compromises in the DNSSEC components of the security of parent zones.

+ 
 managed-keys {
         /* Root Key */
@@ -1037,162 +1157,177 @@ options {
         dnssec-validation yes;
 };
-
+ +

Note

None of the keys listed in this example are valid. In particular, the root key is not valid.
-

+ +

When DNSSEC validation is enabled and properly configured, the resolver will reject any answers from signed, secure zones which fail to validate, and will return SERVFAIL to the client.

-

+ +

Responses may fail to validate for any of several reasons, including missing, expired, or invalid signatures, a key which does not match the DS RRset in the parent zone, or an insecure response from a zone which, according to its parent, should have been secure.

-
+ +

Note

-

+

When the validator receives a response from an unsigned zone that has a signed parent, it must confirm with the parent that the zone was intentionally left unsigned. It does this by verifying, via signed and validated NSEC/NSEC3 records, that the parent zone contains no DS records for the child.

-

+

If the validator can prove that the zone is insecure, then the response is accepted. However, if it cannot, then it must assume an insecure response to be a forgery; it rejects the response and logs an error.

-

+

The logged error reads "insecurity proof failed" and "got insecure response; parent indicates it should be secure". (Prior to BIND 9.7, the logged error was "not insecure". This referred to the zone, not the response.)

-
-
-
-
+
+ + + +

DNSSEC, Dynamic Zones, and Automatic Signing

-

As of BIND 9.7.0 it is possible to change a dynamic zone + +

As of BIND 9.7.0 it is possible to change a dynamic zone from insecure to signed and back again. A secure zone can use either NSEC or NSEC3 chains.

-

-Converting from insecure to secure

-

Changing a zone from insecure to secure can be done in two +

+

+Converting from insecure to secure

+ +
+

Changing a zone from insecure to secure can be done in two ways: using a dynamic DNS update, or the - auto-dnssec zone option.

-

For either method, you need to configure - named so that it can see the + auto-dnssec zone option.

+

For either method, you need to configure + named so that it can see the K* files which contain the public and private parts of the keys that will be used to sign the zone. These files will have been generated by - dnssec-keygen. You can do this by placing them + dnssec-keygen. You can do this by placing them in the key-directory, as specified in named.conf:

-
-        zone example.net {
-                type master;
-                update-policy local;
-                file "dynamic/example.net/example.net";
-                key-directory "dynamic/example.net";
-        };
+  
+	zone example.net {
+		type master;
+		update-policy local;
+		file "dynamic/example.net/example.net";
+		key-directory "dynamic/example.net";
+	};
 

-
If one KSK and one ZSK DNSKEY key have been generated, this
+  
If one KSK and one ZSK DNSKEY key have been generated, this
   configuration will cause all records in the zone to be signed
   with the ZSK, and the DNSKEY RRset to be signed with the KSK as
   well. An NSEC chain will be generated as part of the initial
   signing process.

-

-Dynamic DNS update method

-
To insert the keys via dynamic update:

-
-        % nsupdate
-        > ttl 3600
-        > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
-        > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
-        > send
+  

+

+Dynamic DNS update method

+    
+  

+  
To insert the keys via dynamic update:

+  
+	% nsupdate
+	> ttl 3600
+	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+	> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+	> send
 

-
While the update request will complete almost immediately,
+  
While the update request will complete almost immediately,
   the zone will not be completely signed until 
-  named has had time to walk the zone and
+  named has had time to walk the zone and
   generate the NSEC and RRSIG records. The NSEC record at the apex
   will be added last, to signal that there is a complete NSEC
   chain.

-
If you wish to sign using NSEC3 instead of NSEC, you should
+  
If you wish to sign using NSEC3 instead of NSEC, you should
   add an NSEC3PARAM record to the initial update request. If you
   wish the NSEC3 chain to have the OPTOUT bit set, set it in the
   flags field of the NSEC3PARAM record.

-
-        % nsupdate
-        > ttl 3600
-        > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
-        > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
-        > update add example.net NSEC3PARAM 1 1 100 1234567890
-        > send
+  
+	% nsupdate
+	> ttl 3600
+	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+	> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+	> update add example.net NSEC3PARAM 1 1 100 1234567890
+	> send
 

-
Again, this update request will complete almost
+  
Again, this update request will complete almost
   immediately; however, the record won't show up until 
-  named has had a chance to build/remove the
+  named has had a chance to build/remove the
   relevant chain. A private type record will be created to record
   the state of the operation (see below for more details), and will
   be removed once the operation completes.

-
While the initial signing and NSEC/NSEC3 chain generation
+  
While the initial signing and NSEC/NSEC3 chain generation
   is happening, other updates are possible as well.

-

-Fully automatic zone signing

-
To enable automatic signing, add the 
-  auto-dnssec option to the zone statement in 
+  

+

+Fully automatic zone signing

+    
+  

+  
To enable automatic signing, add the 
+  auto-dnssec option to the zone statement in 
   named.conf. 
-  auto-dnssec has two possible arguments: 
+  auto-dnssec has two possible arguments: 
   allow or 
   maintain.

-
With 
-  auto-dnssec allow, 
-  named can search the key directory for keys
+  
With 
+  auto-dnssec allow, 
+  named can search the key directory for keys
   matching the zone, insert them into the zone, and use them to
   sign the zone. It will do so only when it receives an 
-  rndc sign <zonename>.

-

+  rndc sign <zonename>.

+  

   
-  auto-dnssec maintain includes the above
+  auto-dnssec maintain includes the above
   functionality, but will also automatically adjust the zone's
   DNSKEY records on schedule according to the keys' timing metadata.
-  (See dnssec-keygen(8) and
-  dnssec-settime(8) for more information.) 
+  (See dnssec-keygen(8) and
+  dnssec-settime(8) for more information.) 
   

-

-  named will periodically search the key directory
+  

+  named will periodically search the key directory
   for keys matching the zone, and if the keys' metadata indicates
   that any change should be made the zone, such as adding, removing,
   or revoking a key, then that action will be carried out.  By default,
   the key directory is checked for changes every 60 minutes; this period
   can be adjusted with the dnssec-loadkeys-interval, up
-  to a maximum of 24 hours.  The rndc loadkeys forces
-  named to check for key updates immediately.
+  to a maximum of 24 hours.  The rndc loadkeys forces
+  named to check for key updates immediately.
   

-

+  

   If keys are present in the key directory the first time the zone
   is loaded, the zone will be signed immediately, without waiting for an 
-  rndc sign or rndc loadkeys
+  rndc sign or rndc loadkeys
   command. (Those commands can still be used when there are unscheduled
   key changes, however.)
   

-

+  

   When new keys are added to a zone, the TTL is set to match that
   of any existing DNSKEY RRset. If there is no existing DNSKEY RRset,
   then the TTL will be set to the TTL specified when the key was
-  created (using the dnssec-keygen -L option), if
+  created (using the dnssec-keygen -L option), if
   any, or to the SOA TTL.
   

-

+  

   If you wish the zone to be signed using NSEC3 instead of NSEC,
   submit an NSEC3PARAM record via dynamic update prior to the
   scheduled publication and activation of the keys.  If you wish the
@@ -1202,25 +1337,28 @@ options {
   the zone is signed and the NSEC3 chain is completed, the NSEC3PARAM
   record will appear in the zone.
   

-
Using the 
-  auto-dnssec option requires the zone to be
+  
Using the 
+  auto-dnssec option requires the zone to be
   configured to allow dynamic updates, by adding an 
-  allow-update or 
-  update-policy statement to the zone
+  allow-update or 
+  update-policy statement to the zone
   configuration. If this has not been done, the configuration will
   fail.

-

-Private-type records

-
The state of the signing process is signaled by
+  

+

+Private-type records

+    
+  

+  
The state of the signing process is signaled by
   private-type records (with a default type value of 65534). When
   signing is complete, these records will have a nonzero value for
   the final octet (for those records which have a nonzero initial
   octet).

-
The private type record format: If the first octet is
+  
The private type record format: If the first octet is
   non-zero then the record indicates that the zone needs to be
   signed with the key matching the record, or that all signatures
   that match the record should be removed.

-

+  

     

 


 

@@ -1231,15 +1369,15 @@ options {
 

 

   

-
Only records flagged as "complete" can be removed via
+  
Only records flagged as "complete" can be removed via
   dynamic update. Attempts to remove other private type records
   will be silently ignored.

-
If the first octet is zero (this is a reserved algorithm
+  
If the first octet is zero (this is a reserved algorithm
   number that should never appear in a DNSKEY record) then the
   record indicates changes to the NSEC3 chains are in progress. The
   rest of the record contains an NSEC3PARAM record. The flag field
   tells what operation to perform based on the flag bits.

-

+  

     

 


 

@@ -1250,39 +1388,48 @@ options {
 

 

   

-

-DNSKEY rollovers

-
As with insecure-to-secure conversions, rolling DNSSEC
+  

+

+DNSKEY rollovers

+    
+  

+  
As with insecure-to-secure conversions, rolling DNSSEC
   keys can be done in two ways: using a dynamic DNS update, or the 
-  auto-dnssec zone option.

-

-Dynamic DNS update method

-
 To perform key rollovers via dynamic update, you need to add
+  auto-dnssec zone option.

+  

+

+Dynamic DNS update method

+    
+  

+  
 To perform key rollovers via dynamic update, you need to add
   the K* files for the new keys so that 
-  named can find them. You can then add the new
+  named can find them. You can then add the new
   DNSKEY RRs via dynamic update. 
-  named will then cause the zone to be signed
+  named will then cause the zone to be signed
   with the new keys. When the signing is complete the private type
   records will be updated so that the last octet is non
   zero.

-
If this is for a KSK you need to inform the parent and any
+  
If this is for a KSK you need to inform the parent and any
   trust anchor repositories of the new KSK.

-
You should then wait for the maximum TTL in the zone before
+  
You should then wait for the maximum TTL in the zone before
   removing the old DNSKEY. If it is a KSK that is being updated,
   you also need to wait for the DS RRset in the parent to be
   updated and its TTL to expire. This ensures that all clients will
   be able to verify at least one signature when you remove the old
   DNSKEY.

-
The old DNSKEY can be removed via UPDATE. Take care to
+  
The old DNSKEY can be removed via UPDATE. Take care to
   specify the correct key. 
-  named will clean out any signatures generated
+  named will clean out any signatures generated
   by the old key after the update completes.

-

-Automatic key rollovers

-
When a new key reaches its activation date (as set by
-  dnssec-keygen or dnssec-settime),
-  if the auto-dnssec zone option is set to 
-  maintain, named will
+  

+

+Automatic key rollovers

+    
+  

+  
When a new key reaches its activation date (as set by
+  dnssec-keygen or dnssec-settime),
+  if the auto-dnssec zone option is set to 
+  maintain, named will
   automatically carry out the key rollover.  If the key's algorithm
   has not previously been used to sign the zone, then the zone will
   be fully signed as quickly as possible.  However, if the new key
@@ -1292,89 +1439,112 @@ options {
   signature validity periods expire.  By default, this rollover
   completes in 30 days, after which it will be safe to remove the
   old key from the DNSKEY RRset.

-

-NSEC3PARAM rollovers via UPDATE

-
Add the new NSEC3PARAM record via dynamic update. When the
+  

+

+NSEC3PARAM rollovers via UPDATE

+    
+  

+  
Add the new NSEC3PARAM record via dynamic update. When the
   new NSEC3 chain has been generated, the NSEC3PARAM flag field
   will be zero. At this point you can remove the old NSEC3PARAM
   record. The old chain will be removed after the update request
   completes.

-

-Converting from NSEC to NSEC3

-
To do this, you just need to add an NSEC3PARAM record. When
+  

+

+Converting from NSEC to NSEC3

+    
+  

+  
To do this, you just need to add an NSEC3PARAM record. When
   the conversion is complete, the NSEC chain will have been removed
   and the NSEC3PARAM record will have a zero flag field. The NSEC3
   chain will be generated before the NSEC chain is
   destroyed.

-

-Converting from NSEC3 to NSEC

-
To do this, use nsupdate to
+  

+

+Converting from NSEC3 to NSEC

+    
+  

+  
To do this, use nsupdate to
   remove all NSEC3PARAM records with a zero flag
   field. The NSEC chain will be generated before the NSEC3 chain is
   removed.

-

-Converting from secure to insecure

-
To convert a signed zone to unsigned using dynamic DNS,
+  

+

+Converting from secure to insecure

+    
+  

+  
To convert a signed zone to unsigned using dynamic DNS,
   delete all the DNSKEY records from the zone apex using
-  nsupdate. All signatures, NSEC or NSEC3 chains,
+  nsupdate. All signatures, NSEC or NSEC3 chains,
   and associated NSEC3PARAM records will be removed automatically.
   This will take place after the update request completes.

-
 This requires the 
-  dnssec-secure-to-insecure option to be set to 
+  
 This requires the 
+  dnssec-secure-to-insecure option to be set to 
   yes in 
   named.conf.

-
In addition, if the auto-dnssec maintain
+  
In addition, if the auto-dnssec maintain
   zone statement is used, it should be removed or changed to
-  allow instead (or it will re-sign).
+  allow instead (or it will re-sign).
   

-

-Periodic re-signing

-
In any secure zone which supports dynamic updates, named
+  

+

+Periodic re-signing

+    
+  

+  
In any secure zone which supports dynamic updates, named
   will periodically re-sign RRsets which have not been re-signed as
   a result of some update action. The signature lifetimes will be
   adjusted so as to spread the re-sign load over time rather than
   all at once.

-

-NSEC3 and OPTOUT

-

-  named only supports creating new NSEC3 chains
+  

+

+NSEC3 and OPTOUT

+    
+  

+  

+  named only supports creating new NSEC3 chains
   where all the NSEC3 records in the zone have the same OPTOUT
   state. 
-  named supports UPDATES to zones where the NSEC3
+  named supports UPDATES to zones where the NSEC3
   records in the chain have mixed OPTOUT state. 
-  named does not support changing the OPTOUT
+  named does not support changing the OPTOUT
   state of an individual NSEC3 record, the entire chain needs to be
   changed if the OPTOUT state of an individual NSEC3 needs to be
   changed.
-
+ +

Dynamic Trust Anchor Management

-

BIND 9.7.0 introduces support for RFC 5011, dynamic trust + +

BIND 9.7.0 introduces support for RFC 5011, dynamic trust anchor management. Using this feature allows - named to keep track of changes to critical + named to keep track of changes to critical DNSSEC keys without any need for the operator to make changes to configuration files.

-
+

-Validating Resolver

-

To configure a validating resolver to use RFC 5011 to +Validating Resolver

+ + +

To configure a validating resolver to use RFC 5011 to maintain a trust anchor, configure the trust anchor using a - managed-keys statement. Information about + managed-keys statement. Information about this can be found in - the section called “managed-keys Statement Definition + the section called “managed-keys Statement Definition and Usage”.

-
-
+ +
+

-Authoritative Server

-

To set up an authoritative zone for RFC 5011 trust anchor +Authoritative Server

+ +

To set up an authoritative zone for RFC 5011 trust anchor maintenance, generate two (or more) key signing keys (KSKs) for the zone. Sign the zone with one of them; this is the "active" KSK. All KSKs which do not sign the zone are "stand-by" keys.

-

Any validating resolver which is configured to use the +

Any validating resolver which is configured to use the active KSK as an RFC 5011-managed trust anchor will take note of the stand-by KSKs in the zone's DNSKEY RRset, and store them for future reference. The resolver will recheck the zone @@ -1383,62 +1553,64 @@ options { anchor for the zone. Any time after this 30-day acceptance timer has completed, the active KSK can be revoked, and the zone can be "rolled over" to the newly accepted key.

-

The easiest way to place a stand-by key in a zone is to +

The easiest way to place a stand-by key in a zone is to use the "smart signing" features of - dnssec-keygen and - dnssec-signzone. If a key with a publication + dnssec-keygen and + dnssec-signzone. If a key with a publication date in the past, but an activation date which is unset or in the future, " - dnssec-signzone -S" will include the DNSKEY + dnssec-signzone -S" will include the DNSKEY record in the zone, but will not sign with it:

-
+    
 $ dnssec-keygen -K keys -f KSK -P now -A now+2y example.net
 $ dnssec-signzone -S -K keys example.net
 

-
To revoke a key, the new command 
-    dnssec-revoke has been added. This adds the
+    
To revoke a key, the new command 
+    dnssec-revoke has been added. This adds the
     REVOKED bit to the key flags and re-generates the 
     K*.key and 
     K*.private files.

-
After revoking the active key, the zone must be signed
+    
After revoking the active key, the zone must be signed
     with both the revoked KSK and the new active KSK. (Smart
     signing takes care of this automatically.)

-
Once a key has been revoked and used to sign the DNSKEY
+    
Once a key has been revoked and used to sign the DNSKEY
     RRset in which it appears, that key will never again be
     accepted as a valid trust anchor by the resolver. However,
     validation can proceed using the new active key (which had been
     accepted by the resolver when it was a stand-by key).

-
See RFC 5011 for more details on key rollover
+    
See RFC 5011 for more details on key rollover
     scenarios.

-
When a key has been revoked, its key ID changes,
+    
When a key has been revoked, its key ID changes,
     increasing by 128, and wrapping around at 65535. So, for
     example, the key "Kexample.com.+005+10000" becomes
     "Kexample.com.+005+10128".

-
If two keys have IDs exactly 128 apart, and one is
+    
If two keys have IDs exactly 128 apart, and one is
     revoked, then the two key IDs will collide, causing several
     problems. To prevent this, 
-    dnssec-keygen will not generate a new key if
+    dnssec-keygen will not generate a new key if
     another key is present which may collide. This checking will
     only occur if the new keys are written to the same directory
     which holds all other keys in use for that zone.

-
Older versions of BIND 9 did not have this precaution.
+    
Older versions of BIND 9 did not have this precaution.
     Exercise caution if using key revocation on keys that were
     generated by previous releases, or if using keys stored in
     multiple directories or on multiple machines.

-
It is expected that a future release of BIND 9 will
+    
It is expected that a future release of BIND 9 will
     address this problem in a different way, by storing revoked
     keys with their original unrevoked key IDs.

+  
 
-
-

+
+    

 

 PKCS#11 (Cryptoki) support

-

+  
+  

     PKCS#11 (Public Key Cryptography Standard #11) defines a
     platform-independent API for the control of hardware security
     modules (HSMs) and other cryptographic support devices.
   

-

+  

     BIND 9 is known to work with three HSMs: The AEP Keyper, which has
     been tested with Debian Linux, Solaris x86 and Windows Server 2003;
     the Thales nShield, tested with Debian Linux; and the Sun SCA 6000
@@ -1447,13 +1619,13 @@ $ dnssec-signzone -S -K keys example.net<
     a software-based HSM simulator library produced by the OpenDNSSEC
     project.
   

-

+  

     PKCS#11 makes use of a "provider library": a dynamically loadable
     library which provides a low-level PKCS#11 interface to drive the HSM
     hardware.  The PKCS#11 provider library comes from the HSM vendor, and
     it is specific to the HSM to be controlled.
   

-

+  

     There are two available mechanisms for PKCS#11 support in BIND 9:
     OpenSSL-based PKCS#11 and native PKCS#11.  When using the first
     mechanism, BIND uses a modified version of OpenSSL, which loads
@@ -1463,19 +1635,21 @@ $ dnssec-signzone -S -K keys example.net<
     OpenSSL completely; BIND loads the provider library itself, and uses
     the PKCS#11 API to drive the HSM directly.
   

-

+  

 

-Prerequisites

-

+Prerequisites

+    
+    

       See the documentation provided by your HSM vendor for
       information about installing, initializing, testing and
       troubleshooting the HSM.
     

-

-

+  

+  

 

-Native PKCS#11

-

+Native PKCS#11

+    
+    

       Native PKCS#11 mode will only work with an HSM capable of carrying
       out every cryptographic operation BIND 9 may
       need. The HSM's provider library must have a complete implementation
@@ -1487,35 +1661,36 @@ $ dnssec-signzone -S -K keys example.net<
       native PKCS#11, it is expected that OpenSSL-based PKCS#11 will
       be deprecated.)
     

-

+    

       To build BIND with native PKCS#11, configure as follows:
     

-
+    
 $ cd bind9
 $ ./configure --enable-native-pkcs11 \
     --with-pkcs11=provider-library-path
     

-

-      This will cause all BIND tools, including named
-      and the dnssec-* and pkcs11-*
+    

+      This will cause all BIND tools, including named
+      and the dnssec-* and pkcs11-*
       tools, to use the PKCS#11 provider library specified in
       provider-library-path for cryptography.
       (The provider library path can be overridden using the
-      -E in named and the
-      dnssec-* tools, or the -m in
-      the pkcs11-* tools.)
+      -E in named and the
+      dnssec-* tools, or the -m in
+      the pkcs11-* tools.)
     

-

+    

 

-Building SoftHSMv2

-

+Building SoftHSMv2

+      
+      

 	SoftHSMv2, the latest development version of SoftHSM, is available
 	from
-	
+	
 	  https://github.com/opendnssec/SoftHSMv2
 	.
 	It is a software library developed by the OpenDNSSEC project
-	(
+	(
 	  http://www.opendnssec.org
 	)
 	which provides a PKCS#11 interface to a virtual HSM, implemented in
@@ -1526,7 +1701,7 @@ $ ./configure --enable-native-pkcs11 \
 	cryptographic functions, but when using it for native PKCS#11 in
 	BIND, OpenSSL is required.
       

-

+      

 	By default, the SoftHSMv2 configuration file is
 	prefix/etc/softhsm2.conf (where
 	prefix is configured at compile time).
@@ -1534,19 +1709,20 @@ $ ./configure --enable-native-pkcs11 \
 	variable.  The SoftHSMv2 cryptographic store must be installed and
 	initialized before using it with BIND.
       

-
+      
 $  cd SoftHSMv2 
 $  configure --with-crypto-backend=openssl --prefix=/opt/pkcs11/usr --enable-gost 
 $  make 
 $  make install 
 $  /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 
       

-
-
-

+    

+  
+  

 

-OpenSSL-based PKCS#11

-

+OpenSSL-based PKCS#11

+    
+    

       OpenSSL-based PKCS#11 mode uses a modified version of the
       OpenSSL library; stock OpenSSL does not fully support PKCS#11.
       ISC provides a patch to OpenSSL to correct this.  This patch is
@@ -1554,20 +1730,23 @@ $  /opt/pkcs11/usr/bin/softhsm-util --init-token
       modified by ISC to provide new features such as PIN management and
       key-by-reference.
     

-

+    

       There are two "flavors" of PKCS#11 support provided by
       the patched OpenSSL, one of which must be chosen at
       configuration time. The correct choice depends on the HSM
       hardware:
     

-
    
-
  • 
+    
      
+
    • 
+	
      
 	  Use 'crypto-accelerator' with HSMs that have hardware
 	  cryptographic acceleration features, such as the SCA 6000
 	  board. This causes OpenSSL to run all supported
 	  cryptographic operations in the HSM.
-	
      • 
-
    • 
+	
      
+      
      • 
+
    • 
+	
      
 	  Use 'sign-only' with HSMs that are designed to
 	  function primarily as secure key storage devices, but lack
 	  hardware acceleration. These devices are highly secure, but
@@ -1578,9 +1757,10 @@ $  /opt/pkcs11/usr/bin/softhsm-util --init-token
 	  such as zone signing, and to use the system CPU for all
 	  other computationally-intensive operations. The AEP Keyper
 	  is an example of such a device.
-	
      • 
+	
      
+      
 
    
-
    
+    
    
       The modified OpenSSL code is included in the BIND 9 release,
       in the form of a context diff against the latest versions of
       OpenSSL.  OpenSSL 0.9.8, 1.0.0, and 1.0.1 are supported; there are
@@ -1588,7 +1768,7 @@ $  /opt/pkcs11/usr/bin/softhsm-util --init-token
       we use OpenSSL 0.9.8, but the same methods work with OpenSSL
       1.0.0 and 1.0.1.
     
    
-
    
+    
    
 
    Note
    
       The latest OpenSSL versions as of this writing (January 2015)
       are 0.9.8zc, 1.0.0o, and 1.0.1j.
@@ -1596,122 +1776,129 @@ $  /opt/pkcs11/usr/bin/softhsm-util --init-token
       are released. The version number in the following examples
       is expected to change.
     
    
-
    
+    
    
       Before building BIND 9 with PKCS#11 support, it will be
       necessary to build OpenSSL with the patch in place, and configure
       it with the path to your HSM's PKCS#11 provider library.
     
    
-
    
+    
    
 
    
-Patching OpenSSL
    
-
    -$ wget http://www.openssl.org/source/openssl-0.9.8zc.tar.gz
+Patching OpenSSL
    
+      
+      
    +$ wget http://www.openssl.org/source/openssl-0.9.8zc.tar.gz
   
    
-
    Extract the tarball:
    
-
    +      
    Extract the tarball:
    
+      
     $ tar zxf openssl-0.9.8zc.tar.gz
 
    
-
    Apply the patch from the BIND 9 release:
    
-
    +      
    Apply the patch from the BIND 9 release:
    
+      
     $ patch -p1 -d openssl-0.9.8zc \
 	      < bind9/bin/pkcs11/openssl-0.9.8zc-patch
 
    
-
    
+      
    
 
    Note
    
 	Note that the patch file may not be compatible with the
 	"patch" utility on all operating systems. You may need to
 	install GNU patch.
       
    
-
    
+      
    
 	When building OpenSSL, place it in a non-standard
 	location so that it does not interfere with OpenSSL libraries
 	elsewhere on the system. In the following examples, we choose
 	to install into "/opt/pkcs11/usr". We will use this location
 	when we configure BIND 9.
       
    
-
    
+      
    
 	Later, when building BIND 9, the location of the custom-built
 	OpenSSL library will need to be specified via configure.
       
    
-
    
-
    
+    
    
+    
    
 
    
-Building OpenSSL for the AEP Keyper on Linux
    
-
    
+Building OpenSSL for the AEP Keyper on Linux

+      
+      
+      

 	The AEP Keyper is a highly secure key storage device,
 	but does not provide hardware cryptographic acceleration. It
 	can carry out cryptographic operations, but it is probably
 	slower than your system's CPU. Therefore, we choose the
 	'sign-only' flavor when building OpenSSL.
       

-

+      

 	The Keyper-specific PKCS#11 provider library is
 	delivered with the Keyper software. In this example, we place
 	it /opt/pkcs11/usr/lib:
       

-
+      
 $ cp pkcs11.GCC4.0.2.so.4.05 /opt/pkcs11/usr/lib/libpkcs11.so
 

-

+      

 	This library is only available for Linux as a 32-bit
 	binary. If we are compiling on a 64-bit Linux system, it is
 	necessary to force a 32-bit build, by specifying -m32 in the
 	build options.
       

-

+      

 	Finally, the Keyper library requires threads, so we
 	must specify -pthread.
       

-
+      
 $ cd openssl-0.9.8zc
 $ ./Configure linux-generic32 -m32 -pthread \
 	    --pk11-libname=/opt/pkcs11/usr/lib/libpkcs11.so \
 	    --pk11-flavor=sign-only \
 	    --prefix=/opt/pkcs11/usr
 

-

-	After configuring, run "make"
-	and "make test". If "make
+      

+	After configuring, run "make"
+	and "make test". If "make
 	test" fails with "pthread_atfork() not found", you forgot to
 	add the -pthread above.
       

-
-

+    

+    

 

-Building OpenSSL for the SCA 6000 on Solaris

-

+Building OpenSSL for the SCA 6000 on Solaris

+      
+      
+      

 	The SCA-6000 PKCS#11 provider is installed as a system
 	library, libpkcs11. It is a true crypto accelerator, up to 4
 	times faster than any CPU, so the flavor shall be
 	'crypto-accelerator'.
       

-

+      

 	In this example, we are building on Solaris x86 on an
 	AMD64 system.
       

-
+      
 $ cd openssl-0.9.8zc
 $ ./Configure solaris64-x86_64-cc \
 	    --pk11-libname=/usr/lib/64/libpkcs11.so \
 	    --pk11-flavor=crypto-accelerator \
 	    --prefix=/opt/pkcs11/usr
 

-

+      

 	(For a 32-bit build, use "solaris-x86-cc" and /usr/lib/libpkcs11.so.)
       

-

+      

 	After configuring, run 
-	make and 
-	make test.
+	make and 
+	make test.
       

-
-

+    

+    

 

-Building OpenSSL for SoftHSM

-

+Building OpenSSL for SoftHSM

+      
+      
+      

 	SoftHSM (version 1) is a software library developed by the
 	OpenDNSSEC project
-	(
+	(
 	  http://www.opendnssec.org
 	)
 	which provides a
@@ -1721,13 +1908,13 @@ $ ./Configure solaris64-x86_64-cc \
 	less secure than a true HSM, it can allow you to experiment
 	with PKCS#11 when an HSM is not available.
       

-

+      

 	The SoftHSM cryptographic store must be installed and
 	initialized before using it with OpenSSL, and the SOFTHSM_CONF
 	environment variable must always point to the SoftHSM configuration
 	file:
       

-
+      
 $  cd softhsm-1.3.7 
 $  configure --prefix=/opt/pkcs11/usr 
 $  make 
@@ -1736,127 +1923,134 @@ $  export SOFTHSM_CONF=/opt/pkcs11/softhsm.conf
 $  echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF 
 $  /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm 
 

-

+      

 	SoftHSM can perform all cryptographic operations, but
 	since it only uses your system CPU, there is no advantage to using
 	it for anything but signing.  Therefore, we choose the 'sign-only'
 	flavor when building OpenSSL.
       

-
+      
 $ cd openssl-0.9.8zc
 $ ./Configure linux-x86_64 -pthread \
 	    --pk11-libname=/opt/pkcs11/usr/lib/libsofthsm.so \
 	    --pk11-flavor=sign-only \
 	    --prefix=/opt/pkcs11/usr
 

-

-	After configuring, run "make"
-	and "make test".
+      

+	After configuring, run "make"
+	and "make test".
       

-
-

+    
+    

       Once you have built OpenSSL, run
-      "apps/openssl engine pkcs11" to confirm
+      "apps/openssl engine pkcs11" to confirm
       that PKCS#11 support was compiled in correctly. The output
       should be one of the following lines, depending on the flavor
       selected:
     

-
+    
 	(pkcs11) PKCS #11 engine support (sign only)
 

-
Or:

-
+    
Or:

+    
 	(pkcs11) PKCS #11 engine support (crypto accelerator)
 

-

+    

       Next, run
-      "apps/openssl engine pkcs11 -t". This will
+      "apps/openssl engine pkcs11 -t". This will
       attempt to initialize the PKCS#11 engine. If it is able to
       do so successfully, it will report
-      “[ available ]”.
+      “[ available ]”.
     

-

+    

       If the output is correct, run
-      "make install" which will install the
+      "make install" which will install the
       modified OpenSSL suite to /opt/pkcs11/usr.
     

-

+    

 

-Configuring BIND 9 for Linux with the AEP Keyper

-

+Configuring BIND 9 for Linux with the AEP Keyper

+      
+      
+      

 	To link with the PKCS#11 provider, threads must be
 	enabled in the BIND 9 build.
       

-

+      

 	The PKCS#11 library for the AEP Keyper is currently
 	only available as a 32-bit binary. If we are building on a
 	64-bit host, we must force a 32-bit build by adding "-m32" to
 	the CC options on the "configure" command line.
       

-
+      
 $ cd ../bind9
 $ ./configure CC="gcc -m32" --enable-threads \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libpkcs11.so
 

-
-

+    

+    

 

-Configuring BIND 9 for Solaris with the SCA 6000

-

+Configuring BIND 9 for Solaris with the SCA 6000

+      
+      
+      

 	To link with the PKCS#11 provider, threads must be
 	enabled in the BIND 9 build.
       

-
+      
 $ cd ../bind9
 $ ./configure CC="cc -xarch=amd64" --enable-threads \
 	    --with-openssl=/opt/pkcs11/usr \
 	    --with-pkcs11=/usr/lib/64/libpkcs11.so
 

-
(For a 32-bit build, omit CC="cc -xarch=amd64".)

-

+      
(For a 32-bit build, omit CC="cc -xarch=amd64".)

+      

 	If configure complains about OpenSSL not working, you
 	may have a 32/64-bit architecture mismatch. Or, you may have
 	incorrectly specified the path to OpenSSL (it should be the
 	same as the --prefix argument to the OpenSSL
 	Configure).
       

-
-

+    

+    

 

-Configuring BIND 9 for SoftHSM

-
+Configuring BIND 9 for SoftHSM

+      
+      
+      
 $ cd ../bind9
 $ ./configure --enable-threads \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libsofthsm.so
 

-
-

+    
+    

       After configuring, run
-      "make",
-      "make test" and
-      "make install".
+      "make",
+      "make test" and
+      "make install".
     

-

+    

       (Note: If "make test" fails in the "pkcs11" system test, you may
       have forgotten to set the SOFTHSM_CONF environment variable.)
     

-
-

+  

+  

 

-PKCS#11 Tools

-

+PKCS#11 Tools

+    
+    

       BIND 9 includes a minimal set of tools to operate the
       HSM, including 
-      pkcs11-keygen to generate a new key pair
+      pkcs11-keygen to generate a new key pair
       within the HSM, 
-      pkcs11-list to list objects currently
+      pkcs11-list to list objects currently
       available,
-      pkcs11-destroy to remove objects, and
-      pkcs11-tokens to list available tokens.
+      pkcs11-destroy to remove objects, and
+      pkcs11-tokens to list available tokens.
     

-

+    

       In UNIX/Linux builds, these tools are built only if BIND
       9 is configured with the --with-pkcs11 option. (Note: If
       --with-pkcs11 is set to "yes", rather than to the path of the
@@ -1865,24 +2059,25 @@ $ ./configure --enable-threads \
       PKCS11_PROVIDER environment variable to specify the path to the
       provider.)
     

-
-

+  

+  

 

-Using the HSM

-

+Using the HSM

+    
+    

       For OpenSSL-based PKCS#11, we must first set up the runtime
       environment so the OpenSSL and PKCS#11 libraries can be loaded:
     

-
+    
 $ export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${LD_LIBRARY_PATH}
 

-

-      This causes named and other binaries to load
+    

+      This causes named and other binaries to load
       the OpenSSL library from /opt/pkcs11/usr/lib
       rather than from the default location.  This step is not necessary
       when using native PKCS#11.
     

-

+    

       Some HSMs require other environment variables to be set.
       For example, when operating an AEP Keyper, it is necessary to
       specify the location of the "machine" file, which stores
@@ -1891,45 +2086,45 @@ $ export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${L
       /opt/Keyper/PKCS11Provider/machine,
       use:
     

-
+    
 $ export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11Provider
 

-

+    

       Such environment variables must be set whenever running
       any tool that uses the HSM, including 
-      pkcs11-keygen, 
-      pkcs11-list, 
-      pkcs11-destroy, 
-      dnssec-keyfromlabel, 
-      dnssec-signzone, 
-      dnssec-keygen, and
-      named.
+      pkcs11-keygen, 
+      pkcs11-list, 
+      pkcs11-destroy, 
+      dnssec-keyfromlabel, 
+      dnssec-signzone, 
+      dnssec-keygen, and
+      named.
     

-

+    

       We can now create and use keys in the HSM. In this case,
       we will create a 2048 bit key and give it the label
       "sample-ksk":
     

-
+    
 $ pkcs11-keygen -b 2048 -l sample-ksk
 

-
To confirm that the key exists:

-
+    
To confirm that the key exists:

+    
 $ pkcs11-list
 Enter PIN:
 object[0]: handle 2147483658 class 3 label[8] 'sample-ksk' id[0]
 object[1]: handle 2147483657 class 2 label[8] 'sample-ksk' id[0]
 

-

+    

       Before using this key to sign a zone, we must create a
       pair of BIND 9 key files. The "dnssec-keyfromlabel" utility
       does this. In this case, we will be using the HSM key
       "sample-ksk" as the key-signing key for "example.net":
     

-
+    
 $ dnssec-keyfromlabel -l sample-ksk -f KSK example.net
 

-

+    

       The resulting K*.key and K*.private files can now be used
       to sign the zone. Unlike normal K* files, which contain both
       public and private key data, these files will contain only the
@@ -1937,31 +2132,31 @@ $ dnssec-keyfromlabel -l sample-ksk -f KSK examp
       remains stored within the HSM. Signing with the private key takes
       place inside the HSM.
     

-

+    

       If you wish to generate a second key in the HSM for use
       as a zone-signing key, follow the same procedure above, using a
       different keylabel, a smaller key size, and omitting "-f KSK"
       from the dnssec-keyfromlabel arguments:
     

-

+    

       (Note: When using OpenSSL-based PKCS#11 the label is an arbitrary
       string which identifies the key.  With native PKCS#11, the label is
       a PKCS#11 URI string which may include other details about the key
       and the HSM, including its PIN. See
-      dnssec-keyfromlabel(8) for details.)
+      dnssec-keyfromlabel(8) for details.)
     

-
+    
 $ pkcs11-keygen -b 1024 -l sample-zsk
 $ dnssec-keyfromlabel -l sample-zsk example.net
 

-

+    

       Alternatively, you may prefer to generate a conventional
       on-disk key, using dnssec-keygen:
     

-
+    
 $ dnssec-keygen example.net
 

-

+    

       This provides less security than an HSM key, but since
       HSMs can be slow or cumbersome to use for security reasons, it
       may be more efficient to reserve HSM keys for use in the less
@@ -1971,13 +2166,13 @@ $ dnssec-keygen example.net
       there is no speed advantage to using on-disk keys, as cryptographic
       operations will be done by the HSM regardless.)
     

-

+    

       Now you can sign the zone. (Note: If not using the -S
-      option to dnssec-signzone, it will be
+      option to dnssec-signzone, it will be
       necessary to add the contents of both K*.key
       files to the zone master file before signing it.)
     

-
+    
 $ dnssec-signzone -S example.net
 Enter PIN:
 Verifying the zone using the following algorithms:
@@ -1986,57 +2181,59 @@ Zone signing complete:
 Algorithm: NSEC3RSASHA1: ZSKs: 1, KSKs: 1 active, 0 revoked, 0 stand-by
 example.net.signed
 

-
-

+  

+  

 

-Specifying the engine on the command line

-

+Specifying the engine on the command line

+    
+    

       When using OpenSSL-based PKCS#11, the "engine" to be used by
-      OpenSSL can be specified in named and all of
-      the BIND dnssec-* tools by using the "-E
+      OpenSSL can be specified in named and all of
+      the BIND dnssec-* tools by using the "-E
       <engine>" command line option. If BIND 9 is built with
       the --with-pkcs11 option, this option defaults to "pkcs11".
       Specifying the engine will generally not be necessary unless
       for some reason you wish to use a different OpenSSL
       engine.
     

-

+    

       If you wish to disable use of the "pkcs11" engine —
       for troubleshooting purposes, or because the HSM is unavailable
       — set the engine to the empty string. For example:
     

-
+    
 $ dnssec-signzone -E '' -S example.net
 

-

+    

       This causes 
-      dnssec-signzone to run as if it were compiled
+      dnssec-signzone to run as if it were compiled
       without the --with-pkcs11 option.
     

-

+    

       When built with native PKCS#11 mode, the "engine" option has a
       different meaning: it specifies the path to the PKCS#11 provider
       library.  This may be useful when testing a new provider library.
     

-
-

+  

+  

 

-Running named with automatic zone re-signing

-

-      If you want named to dynamically re-sign zones
+Running named with automatic zone re-signing

+    
+    

+      If you want named to dynamically re-sign zones
       using HSM keys, and/or to to sign new records inserted via nsupdate,
-      then named must have access to the HSM PIN. In OpenSSL-based PKCS#11,
+      then named must have access to the HSM PIN. In OpenSSL-based PKCS#11,
       this is accomplished by placing the PIN into the openssl.cnf file
       (in the above examples, 
       /opt/pkcs11/usr/ssl/openssl.cnf).
     

-

+    

       The location of the openssl.cnf file can be overridden by
       setting the OPENSSL_CONF environment variable before running
-      named.
+      named.
     

-
Sample openssl.cnf:

-
+    
Sample openssl.cnf:

+    
 	openssl_conf = openssl_def
 	[ openssl_def ]
 	engines = engine_section
@@ -2045,59 +2242,62 @@ $ dnssec-signzone -E '' -S example.net<PLACE PIN HERE>
 

-

+    

       This will also allow the dnssec-* tools to access the HSM
       without PIN entry. (The pkcs11-* tools access the HSM directly,
       not via OpenSSL, so a PIN will still be required to use
       them.)
     

-

+    

       In native PKCS#11 mode, the PIN can be provided in a file specified
       as an attribute of the key's label.  For example, if a key had the label
       pkcs11:object=local-zsk;pin-source=/etc/hsmpin,
       then the PIN would be read from the file
       /etc/hsmpin.
     

-

+    

 
Warning

-

+      

 	Placing the HSM's PIN in a text file in this manner may reduce the
 	security advantage of using an HSM. Be sure this is what you want to
 	do before configuring the system in this way.
       

+    

+  

 
-
-
-

+
+    

 

 DLZ (Dynamically Loadable Zones)

-

+  
+  

     DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows
     zone data to be retrieved directly from an external database.  There is
     no required format or schema.  DLZ drivers exist for several different
     database backends including PostgreSQL, MySQL, and LDAP and can be
     written for any other.
   

-

-    Historically, DLZ drivers had to be statically linked with the named
+  

+    Historically, DLZ drivers had to be statically linked with the named
     binary and were turned on via a configure option at compile time (for
     example, "configure --with-dlz-ldap").
     Currently, the drivers provided in the BIND 9 tarball in
     contrib/dlz/drivers are still linked this
     way.
   

-

+  

     In BIND 9.8 and higher, it is possible to link some DLZ modules
     dynamically at runtime, via the DLZ "dlopen" driver, which acts as a
     generic wrapper around a shared object implementing the DLZ API.  The
-    "dlopen" driver is linked into named by default, so configure options
+    "dlopen" driver is linked into named by default, so configure options
     are no longer necessary when using these dynamically linkable drivers,
     but are still needed for the older drivers in
     contrib/dlz/drivers.
   

-

-    When the DLZ module provides data to named, it does so in text format.
-    The response is converted to DNS wire format by named.  This
+
+  

+    When the DLZ module provides data to named, it does so in text format.
+    The response is converted to DNS wire format by named.  This
     conversion, and the lack of any internal caching, places significant
     limits on the query performance of DLZ modules.  Consequently, DLZ is
     not recommended for use on high-volume servers.  However, it can be
@@ -2106,34 +2306,36 @@ $ dnssec-signzone -E '' -S example.net
-

+
+  

 

-Configuring DLZ

-

-      A DLZ database is configured with a dlz
+Configuring DLZ

+    
+    

+      A DLZ database is configured with a dlz
       statement in named.conf:
     

-
+    
     dlz example {
-        database "dlopen driver.so args";
-        search yes;
+	database "dlopen driver.so args";
+	search yes;
     };
     

-

+    

       This specifies a DLZ module to search when answering queries; the
       module is implemented in driver.so and is
       loaded at runtime by the dlopen DLZ driver.  Multiple
-      dlz statements can be specified; when
+      dlz statements can be specified; when
       answering a query, all DLZ modules with search
       set to yes will be queried to find out if
       they contain an answer for the query name; the best available
       answer will be returned to the client.
     

-

+    

       The search option in the above example can be
       omitted, because yes is the default value.
     

-

+    

       If search is set to no, then
       this DLZ module is not searched for the best
       match when a query is received.  Instead, zones in this DLZ must be
@@ -2143,49 +2345,50 @@ $ dnssec-signzone -E '' -S example.net
-
+    
     dlz other {
-        database "dlopen driver.so args";
-        search no;
+	database "dlopen driver.so args";
+	search no;
     };
 
     zone "." {
-        type redirect;
-        dlz other;
+	type redirect;
+	dlz other;
     };
     

-

-

+  

+  

 

-Sample DLZ Driver

-

+Sample DLZ Driver

+    
+    

       For guidance in implementation of DLZ modules, the directory
       contrib/dlz/example contains a basic
       dynamically-linkable DLZ module--i.e., one which can be
       loaded at runtime by the "dlopen" DLZ driver.
       The example sets up a single zone, whose name is passed
-      to the module as an argument in the dlz
+      to the module as an argument in the dlz
       statement:
     

-
+    
     dlz other {
-        database "dlopen driver.so example.nil";
+	database "dlopen driver.so example.nil";
     };
     

-

+    

       In the above example, the module is configured to create a zone
       "example.nil", which can answer queries and AXFR requests, and
       accept DDNS updates.  At runtime, prior to any updates, the zone
       contains an SOA, NS, and a single A record at the apex:
     

-
+    
  example.nil.  3600    IN      SOA     example.nil. hostmaster.example.nil. (
-                                               123 900 600 86400 3600
-                                       )
+					       123 900 600 86400 3600
+				       )
  example.nil.  3600    IN      NS      example.nil.
  example.nil.  1800    IN      A       10.53.0.1
     

-

+    

       The sample driver is capable of retrieving information about the
       querying client, and altering its response on the basis of this
       information.  To demonstrate this feature, the example driver
@@ -2196,21 +2399,23 @@ $ dnssec-signzone -E '' -S example.net
-

+    

       Documentation of the DLZ module API can be found in
       contrib/dlz/example/README.  This directory also
       contains the header file dlz_minimal.h, which
       defines the API and should be included by any dynamically-linkable
       DLZ module.
     

+  
 
-
-

+
+    

 

 DynDB (Dynamic Database)

-

+  
+  

     DynDB is an extension to BIND 9 which, like DLZ
-    (see the section called “DLZ (Dynamically Loadable Zones)”), allows zone data to be
+    (see the section called “DLZ (Dynamically Loadable Zones)”), allows zone data to be
     retrieved from an external database.  Unlike DLZ, a DynDB module
     provides a full-featured BIND zone database interface.  Where
     DLZ translates DNS queries into real-time database lookups,
@@ -2220,90 +2425,95 @@ $ dnssec-signzone -E '' -S example.net
-

+  

     A DynDB module supporting LDAP has been created by Red Hat
     and is available from
-    https://fedorahosted.org/bind-dyndb-ldap/.
+    https://fedorahosted.org/bind-dyndb-ldap/.
   

-

+  

     A sample DynDB module for testing and developer guidance
     is included with the BIND source code, in the directory
     bin/tests/system/dyndb/driver.
   

-

+
+  

 

-Configuring DynDB

-

-      A DynDB database is configured with a dyndb
+Configuring DynDB

+    
+    

+      A DynDB database is configured with a dyndb
       statement in named.conf:
     

-
+    
     dyndb example "driver.so" {
         parameters
     };
     

-

+    

       The file driver.so is a DynDB module which
       implements the full DNS database API.  Multiple
-      dyndb statements can be specified, to load
+      dyndb statements can be specified, to load
       different drivers or multiple instances of the same driver.
       Zones provided by a DynDB module are added to the view's zone
       table, and are treated as normal authoritative zones when BIND
       is responding to queries.  Zone configuration is handled internally
       by the DynDB module.
     

-

+    

       The parameters are passed as an opaque
       string to the DynDB module's initialization routine. Configuration
       syntax will differ depending on the driver.
     

-

-

+  

+  

 

-Sample DynDB Module

-

+Sample DynDB Module

+    
+    

       For guidance in implementation of DynDB modules, the directory
       bin/tests/system/dyndb/driver.
       contains a basic DynDB module.
       The example sets up two zones, whose names are passed
-      to the module as arguments in the dyndb
+      to the module as arguments in the dyndb
       statement:
     

-
+    
     dyndb sample "sample.so" { example.nil. arpa. };
     

-

+    

       In the above example, the module is configured to create a zone
       "example.nil", which can answer queries and AXFR requests, and
       accept DDNS updates.  At runtime, prior to any updates, the zone
       contains an SOA, NS, and a single A record at the apex:
     

-
+    
  example.nil.  86400    IN      SOA     example.nil. example.nil. (
                                                0 28800 7200 604800 86400
                                        )
  example.nil.  86400    IN      NS      example.nil.
  example.nil.  86400    IN      A       127.0.0.1
     

-

+    

       When the zone is updated dynamically, the DynDB module will determine
       whether the updated RR is an address (i.e., type A or AAAA) and if
       so, it will automatically update the corresponding PTR record in a
       reverse zone.  (Updates are not stored permanently; all updates are
       lost when the server is restarted.)
     

+  
 
-
-

+
+    

 

-IPv6 Support in BIND 9

-

+IPv6 Support in BIND 9

+      

         BIND 9 fully supports all currently
         defined forms of IPv6 name to address and address to name
         lookups.  It will also use IPv6 addresses to make queries when
         running on an IPv6 capable system.
       

-

+
+      

         For forward lookups, BIND 9 supports
         only AAAA records.  RFC 3363 deprecated the use of A6 records,
         and client-side support for A6 records was accordingly removed
@@ -2313,7 +2523,8 @@ $ dnssec-signzone -E '' -S example.net
-

+
+      

         For IPv6 reverse lookups, BIND 9 supports
         the traditional "nibble" format used in the
         ip6.arpa domain, as well as the older, deprecated
@@ -2328,33 +2539,41 @@ $ dnssec-signzone -E '' -S example.netBIND 9
         name server will not load a zone file containing binary labels.
       

-

+
+      

         For an overview of the format and structure of IPv6 addresses,
-        see the section called “IPv6 addresses (AAAA)”.
+        see the section called “IPv6 addresses (AAAA)”.
       

-

+
+      

 

-Address Lookups Using AAAA Records

-

+Address Lookups Using AAAA Records

+        
+
+        

           The IPv6 AAAA record is a parallel to the IPv4 A record,
           and, unlike the deprecated A6 record, specifies the entire
           IPv6 address in a single record.  For example,
         

+
 
 $ORIGIN example.com.
 host            3600    IN      AAAA    2001:db8::1
 

-

+
+        

           Use of IPv4-in-IPv6 mapped addresses is not recommended.
           If a host has an IPv4 address, use an A record, not
           a AAAA, with ::ffff:192.168.42.1 as
           the address.
         

-
-

+      

+      

 

-Address to Name Lookups Using Nibble Format

-

+Address to Name Lookups Using Nibble Format

+        
+
+        

           When looking up an address in nibble format, the address
           components are simply reversed, just as in IPv4, and
           ip6.arpa. is appended to the
@@ -2363,14 +2582,16 @@ host            3600    IN      AAAA    2001:db8::1
           a host with address
           2001:db8::1.
         

+
 
 $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0  14400   IN    PTR    (
                                     host.example.com. )
 

-
-
-
+
+      
+    
+  
 

 

 
@@ -2388,6 +2609,6 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch05.html b/doc/arm/Bv9ARM.ch05.html
index 688d0b4085..8fca93ea55 100644
--- a/doc/arm/Bv9ARM.ch05.html
+++ b/doc/arm/Bv9ARM.ch05.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Chapter 5. The BIND 9 Lightweight Resolver
-
-
+
+
 
 
 
@@ -39,32 +38,34 @@
 
 

 
-

-

-Chapter 5. The BIND 9 Lightweight Resolver

+

+

+Chapter 5. The BIND 9 Lightweight Resolver

 

 
Table of Contents

-

-
The Lightweight Resolver Library

-
Running a Resolver Daemon

+

+
The Lightweight Resolver Library

+
Running a Resolver Daemon

 

 

-

+    
+    

 

-The Lightweight Resolver Library

-

+The Lightweight Resolver Library

+      
+      

         Traditionally applications have been linked with a stub resolver
         library that sends recursive DNS queries to a local caching name
         server.
       

-

+      

         IPv6 once introduced new complexity into the resolution process,
         such as following A6 chains and DNAME records, and simultaneous
         lookup of IPv4 and IPv6 addresses.  Though most of the complexity was
         then removed, these are hard or impossible
         to implement in a traditional stub resolver.
       

-

+      

         BIND 9 therefore can also provide resolution
         services to local clients
         using a combination of a lightweight resolver library and a resolver
@@ -72,62 +73,67 @@
         a simple UDP-based protocol, the "lightweight resolver protocol"
         that is distinct from and simpler than the full DNS protocol.
       

-

-

+    

+    

 

 Running a Resolver Daemon

-

+      
+
+      

         To use the lightweight resolver interface, the system must
-        run the resolver daemon lwresd or a
+        run the resolver daemon lwresd or a
         local
-        name server configured with a lwres
+        name server configured with a lwres
         statement.
       

-

+
+      

         By default, applications using the lightweight resolver library will
         make
         UDP requests to the IPv4 loopback address (127.0.0.1) on port 921.
         The
-        address can be overridden by lwserver
+        address can be overridden by lwserver
         lines in
         /etc/resolv.conf.
       

-

+
+      

         The daemon currently only looks in the DNS, but in the future
         it may use other sources such as /etc/hosts,
         NIS, etc.
       

-

-        The lwresd daemon is essentially a
+
+      

+        The lwresd daemon is essentially a
         caching-only name server that responds to requests using the
         lightweight
         resolver protocol rather than the DNS protocol.  Because it needs
         to run on each host, it is designed to require no or minimal
         configuration.
         Unless configured otherwise, it uses the name servers listed on
-        nameserver lines in /etc/resolv.conf
+        nameserver lines in /etc/resolv.conf
         as forwarders, but is also capable of doing the resolution
         autonomously if
         none are specified.
       

-

-        The lwresd daemon may also be
+      

+        The lwresd daemon may also be
         configured with a
         named.conf style configuration file,
         in
         /etc/lwresd.conf by default.  A name
         server may also
         be configured to act as a lightweight resolver daemon using the
-        lwres statement in named.conf.
+        lwres statement in named.conf.
       

-

-        The number of client queries that the lwresd
+      

+        The number of client queries that the lwresd
         daemon is able to serve can be set using the
         lwres-tasks and lwres-clients
         statements in the configuration.
       

-

-
+    
+  
 

 

 
@@ -145,6 +151,6 @@
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index 8fec69ec6d..25cb9f05fb 100644
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Chapter 6. BIND 9 Configuration Reference
-
-
+
+
 
 
 
@@ -39,74 +38,79 @@
 
 

 
-

-

-Chapter 6. BIND 9 Configuration Reference

+

+

+Chapter 6. BIND 9 Configuration Reference

 

 
Table of Contents

-

-
Configuration File Elements

+

+
Configuration File Elements

 

-
Address Match Lists

-
Comment Syntax

+
Address Match Lists

+
Comment Syntax

 

-
Configuration File Grammar

+
Configuration File Grammar

 

-
acl Statement Grammar

-
acl Statement Definition and
+
acl Statement Grammar

+
acl Statement Definition and
           Usage

-
controls Statement Grammar

-
controls Statement Definition and
+
controls Statement Grammar

+
controls Statement Definition and
           Usage

-
include Statement Grammar

-
include Statement Definition and
+
include Statement Grammar

+
include Statement Definition and
           Usage

-
key Statement Grammar

-
key Statement Definition and Usage

-
logging Statement Grammar

-
logging Statement Definition and
+
key Statement Grammar

+
key Statement Definition and Usage

+
logging Statement Grammar

+
logging Statement Definition and
           Usage

-
lwres Statement Grammar

-
lwres Statement Definition and Usage

-
masters Statement Grammar

-
masters Statement Definition and
+
lwres Statement Grammar

+
lwres Statement Definition and Usage

+
masters Statement Grammar

+
masters Statement Definition and
           Usage

-
options Statement Grammar

-
options Statement Definition and
+
options Statement Grammar

+
options Statement Definition and
           Usage

-
server Statement Grammar

-
server Statement Definition and
+
server Statement Grammar

+
server Statement Definition and
             Usage

-
statistics-channels Statement Grammar

-
statistics-channels Statement Definition and
+
statistics-channels Statement Grammar

+
statistics-channels Statement Definition and
             Usage

-
trusted-keys Statement Grammar

-
trusted-keys Statement Definition
+
trusted-keys Statement Grammar

+
trusted-keys Statement Definition
             and Usage

-
managed-keys Statement Grammar

-
managed-keys Statement Definition
+
managed-keys Statement Grammar

+
managed-keys Statement Definition
             and Usage

-
view Statement Grammar

-
view Statement Definition and Usage

-
zone
+
view Statement Grammar

+
view Statement Definition and Usage

+
zone
             Statement Grammar

-
zone Statement Definition and Usage

+
zone Statement Definition and Usage

 

-
Zone File

+
Zone File

 

-
Types of Resource Records and When to Use Them

-
Discussion of MX Records

-
Setting TTLs

-
Inverse Mapping in IPv4

-
Other Zone File Directives

-
BIND Master File Extension: the  $GENERATE Directive

-
Additional File Formats

+
Types of Resource Records and When to Use Them

+
Discussion of MX Records

+
Setting TTLs

+
Inverse Mapping in IPv4

+
Other Zone File Directives

+
BIND Master File Extension: the  $GENERATE Directive

+
Additional File Formats

+

+
BIND9 Statistics

+

+
The Statistics File

+
Statistics Counters

 

-
BIND9 Statistics

-
Statistics Counters

 

 

-

+    
+
+    

       BIND 9 configuration is broadly similar
       to BIND 8; however, there are a few new
       areas
@@ -116,23 +120,26 @@
       if they can be more efficiently implemented using the new features
       found in BIND 9.
     

-

+
+    

       BIND 4 configuration files can be
       converted to the new format
       using the shell script
       contrib/named-bootconf/named-bootconf.sh.
     

-

+    

 

 Configuration File Elements

-

+      
+      

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

-

+      

+        
--++
@@ -144,7 +151,7 @@
 
@@ -160,7 +167,7 @@
                   ip_addr,
                   ip_prefix, key_id,
                   or acl_name elements, see
-                  the section called “Address Match Lists”.
+                  the section called “Address Match Lists”.
                 

@@ -215,8 +222,8 @@
 
@@ -241,7 +248,7 @@
               
-

 




 
 
 

                 

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

               		
 

               
 

                 

                   One to four integers valued 0 through
-                  255 separated by dots (`.'), such as 123,
-                  45.67 or 89.123.45.67.
+                  255 separated by dots (`.'), such as 123,
+                  45.67 or 89.123.45.67.
                 

               		
 

 

                 

-                  An IPv6 address, such as 2001:db8::1234.
+                  An IPv6 address, such as 2001:db8::1234.
                   IPv6 scoped addresses that have ambiguity on their
                   scope zones must be disambiguated by an appropriate
                   zone ID with the percent character (`%') as
@@ -253,9 +260,9 @@
                   currently only interface names as link identifiers
                   are supported, assuming one-to-one mapping between
                   interfaces and links.  For example, a link-local
-                  address fe80::1 on the link
-                  attached to the interface ne0
-                  can be specified as fe80::1%ne0.
+                  address fe80::1 on the link
+                  attached to the interface ne0
+                  can be specified as fe80::1%ne0.
                   Note that on most systems link-local addresses
                   always have the ambiguity, and need to be
                   disambiguated.
@@ -321,10 +328,10 @@
                   netmask.
                   Trailing zeros in a ip_addr
                   may omitted.
-                  For example, 127/8 is the
-                  network 127.0.0.0 with
-                  netmask 255.0.0.0 and 1.2.3.0/28 is
-                  network 1.2.3.0 with netmask 255.255.255.240.
+                  For example, 127/8 is the
+                  network 127.0.0.0 with
+                  netmask 255.0.0.0 and 1.2.3.0/28 is
+                  network 1.2.3.0 with netmask 255.255.255.240.
                 

                 

                   When specifying a prefix involving a IPv6 scoped address
@@ -432,7 +439,7 @@
                   Integers may take values
                   0 <= value <= 18446744073709551615, though
                   certain parameters
-                  (such as max-journal-size) may
+                  (such as max-journal-size) may
                   use a more limited range within these extremes.
                   In most cases, setting a value to 0 does not
                   literally mean zero; it means "undefined" or
@@ -517,87 +524,109 @@
               

 

 

-

+
+      

+      

 

 Address Match Lists

-

+        
+        

 

-Syntax

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

-

-

+
+        

+        

 

-Definition and Usage

-

+Definition and Usage

+          
+          

             Address match lists are primarily used to determine access
             control for various server operations. They are also used in
-            the listen-on and sortlist
+            the listen-on and sortlist
             statements. The elements which constitute an address match
             list can be any of the following:
           

-
    
-
  • an IP address (IPv4 or IPv6)
    • 
-
  • an IP prefix (in `/' notation)
    • 
-
  • 
-                a key ID, as defined by the key
+          
      
+
    • 
+              an IP address (IPv4 or IPv6)
+            
      • 
+
    • 
+              an IP prefix (in `/' notation)
+            
      • 
+
    • 
+              
+                a key ID, as defined by the key
                 statement
-              
      • 
-
    • the name of an address match list defined with
-                the acl statement
-              
      • 
-
    • a nested address match list enclosed in braces
      • 
+              
+            
+
    • 
+              the name of an address match list defined with
+                the acl statement
+              
+            
      • 
+
    • 
+              a nested address match list enclosed in braces
+            
      • 
 
    
-
    
+
+          
    
             Elements can be negated with a leading exclamation mark (`!'),
             and the match list names "any", "none", "localhost", and
             "localnets" are predefined. More information on those names
             can be found in the description of the acl statement.
           
    
-
    
+
+          
    
             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 comparison takes place in approximately O(1)
             time.  However, key comparisons require that the list of keys
             be traversed until a matching key is found, and therefore may
             be somewhat slower.
           
    
-
    
+
+          
    
             The interpretation of a match depends on whether the list is being
-            used for access control, defining listen-on ports, or in a
-            sortlist, and whether the element was negated.
+            used for access control, defining listen-on ports, or in a
+            sortlist, 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-notify,
-            allow-recursion,
-            allow-recursion-on,
-            allow-query,
-            allow-query-on,
-            allow-query-cache,
-            allow-query-cache-on,
-            allow-transfer,
-            allow-update,
-            allow-update-forwarding,
-            blackhole, and
-            keep-response-order all use address match
-            lists.  Similarly, the listen-on option will cause the
+            allow-notify,
+            allow-recursion,
+            allow-recursion-on,
+            allow-query,
+            allow-query-on,
+            allow-query-cache,
+            allow-query-cache-on,
+            allow-transfer,
+            allow-update,
+            allow-update-forwarding,
+            blackhole, and
+            keep-response-order all use address match
+            lists.  Similarly, the listen-on option will cause the
             server to refuse queries on any of the machine's
             addresses which do not match the list.
           
    
-
    
+
+          
    
             Order of insertion is significant.  If more than one element
             in an ACL is found to match a given IP address or prefix,
             preference will be given to the one that came
@@ -606,29 +635,35 @@
             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;
+            1.2.3/24; ! 1.2.3.13;
             the 1.2.3.13 element is completely useless because the
             algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
-            element.  Using ! 1.2.3.13; 1.2.3/24 fixes
+            element.  Using ! 1.2.3.13; 1.2.3/24 fixes
             that problem by having 1.2.3.13 blocked by the negation, but
             all other 1.2.3.* hosts fall through.
           
    
-

-

-

+        

+      
+
+      

 

-Comment Syntax

-

+Comment Syntax

+        
+
+        

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

-

+
+        

 

-Syntax

-

+Syntax

+          
+
+          

             

 
/* This is a BIND comment as in C */

 

@@ -640,25 +675,26 @@
 # and perl

 

           

-
-

+        

+        

 

-Definition and Usage

-

+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.
@@ -669,14 +705,15 @@
 

 
           

-

+
+          

             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
@@ -686,14 +723,15 @@
 

 
           

-

+          

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

-

+
+          

 
 

 
# This is the start of a comment.  The next line
@@ -703,22 +741,26 @@
 

 
           

-

+
+          

 
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.
             

-

-

-
-
-

+          

+        
+      
+    
+
+    

 

 Configuration File Grammar

-

+      
+
+      

         A BIND 9 configuration consists of
         statements and comments.
         Statements end with a semicolon. Statements and comments are the
@@ -726,18 +768,21 @@
         statements contain a block of sub-statements, which are also
         terminated with a semicolon.
       

-

+
+      

         The following statements are supported:
       

-

+
+      

+        
--++
-

 




 
 
 

 
-                
acl

+                
acl

               		
 
                 

@@ -748,18 +793,18 @@
 

 

 
-                
controls

+                
controls

               		
 
                 

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

               		
 

 

 
-                
include

+                
include

               		
 
                 

@@ -769,7 +814,7 @@
 

 

 
-                
key

+                
key

               		
 
                 

@@ -780,7 +825,7 @@
 

 

 
-                
logging

+                
logging

               		
 
                 

@@ -791,31 +836,31 @@
 

 

 
-                
lwres

+                
lwres

               		
 
                 

-                  configures named to
-                  also act as a light-weight resolver daemon (lwresd).
+                  configures named to
+                  also act as a light-weight resolver daemon (lwresd).
                 

               		
 

 

 
-                
masters

+                
masters

               		
 
                 

                   defines a named masters list for
                   inclusion in stub and slave zones'
-                  masters or
-                  also-notify lists.
+                  masters or
+                  also-notify lists.
                 

               		
 

 

 
-                
options

+                
options

               		
 
                 

@@ -826,7 +871,7 @@
 

 

 
-                
server

+                
server

               		
 
                 

@@ -837,18 +882,18 @@
 

 

 
-                
statistics-channels

+                
statistics-channels

               		
 
                 

                   declares communication channels to get access to
-                  named statistics.
+                  named statistics.
                 

               		
 

 

 
-                
trusted-keys

+                
trusted-keys

               		
 
                 

@@ -858,7 +903,7 @@
 

 

 
-                
managed-keys

+                
managed-keys

               		
 
                 

@@ -869,7 +914,7 @@
 

 

 
-                
view

+                
view

               		
 
                 

@@ -879,7 +924,7 @@
 

 

 
-                
zone

+                
zone

               		
 
                 

@@ -888,42 +933,53 @@
               

 

 

-

-        The logging and
-        options statements may only occur once
+
+      

+
+      

+        The logging and
+        options statements may only occur once
         per
         configuration.
       

-

+
+      

 

-acl Statement Grammar

-
acl acl-name {
+acl Statement Grammar

+        
+
+
acl acl-name {
     address_match_list
 };
 

-
-

+
+      

+      

 

-acl Statement Definition and
+acl Statement Definition and
           Usage

-

-          The acl statement assigns a symbolic
+        
+
+        

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

-

+
+        

           The following ACLs are built-in:
         

-

+
+        

+          
--++
-

 




 
 
 

 
-                  
any

+                  
any

                 		
 
                   

@@ -933,7 +989,7 @@
 

 

 
-                  
none

+                  
none

                 		
 
                   

@@ -943,44 +999,47 @@
 

 

 
-                  
localhost

+                  
localhost

                 		
 
                   

                     Matches the IPv4 and IPv6 addresses of all network
                     interfaces on the system.  When addresses are
-                    added or removed, the localhost
+                    added or removed, the localhost
                     ACL element is updated to reflect the changes.
                   

                 		
 

 

 
-                  
localnets

+                  
localnets

                 		
 
                   

                     Matches any host on an IPv4 or IPv6 network
                     for which the system has an interface.
                     When addresses are added or removed,
-                    the localnets
+                    the localnets
                     ACL element is updated to reflect the changes.
                     Some systems do not provide a way to determine the prefix
                     lengths of
                     local IPv6 addresses.
-                    In such a case, localnets
+                    In such a case, localnets
                     only matches the local
-                    IPv6 addresses, just like localhost.
+                    IPv6 addresses, just like localhost.
                   

                 		
 

 

-

-

+
+        

+      
+      

 

-controls Statement Grammar

-
controls {
+controls Statement Grammar

+        
+
+
controls {
    [ inet ( ip_addr | * ) [ port ip_port ]
                 allow {  address_match_list  }
                 keys { key_list }; ]
@@ -990,91 +1049,103 @@
    [ unix ...; ]
 };
 

-
-

+
+      

+
+      

 

-controls Statement Definition and
+controls Statement Definition and
           Usage

-

-          The controls statement declares control
+        
+
+        

+          The controls statement declares control
           channels to be used by system administrators to control the
           operation of the name server. These control channels are
-          used by the rndc utility to send
+          used by the rndc utility to send
           commands to and retrieve non-DNS results from a name server.
         

-

-          An inet control channel is a TCP socket
-          listening at the specified ip_port on the
-          specified ip_addr, which can be an IPv4 or IPv6
-          address.  An ip_addr of * (asterisk) is
+
+        

+          An inet control channel is a TCP socket
+          listening at the specified ip_port on the
+          specified ip_addr, which can be an IPv4 or IPv6
+          address.  An ip_addr of * (asterisk) is
           interpreted as the IPv4 wildcard address; connections will be
           accepted on any of the system's IPv4 addresses.
           To listen on the IPv6 wildcard address,
-          use an ip_addr of ::.
-          If you will only use rndc on the local host,
+          use an ip_addr of ::.
+          If you will only use rndc on the local host,
           using the loopback address (127.0.0.1
           or ::1) is recommended for maximum security.
         

-

+
+        

           If no port is specified, port 953 is used. The asterisk
-          "*" cannot be used for ip_port.
+          "*" cannot be used for ip_port.
         

-

+
+        

           The ability to issue commands over the control channel is
-          restricted by the allow and
-          keys clauses.
+          restricted by the allow and
+          keys clauses.
           Connections to the control channel are permitted based on the
-          address_match_list.  This is for simple
-          IP address based filtering only; any key_id
-          elements of the address_match_list
+          address_match_list.  This is for simple
+          IP address based filtering only; any key_id
+          elements of the address_match_list
           are ignored.
         

-

-          A unix control channel is a UNIX domain
+
+        

+          A unix control channel is a UNIX domain
           socket listening at the specified path in the file system.
-          Access to the socket is specified by the perm,
-          owner and group clauses.
+          Access to the socket is specified by the perm,
+          owner and group clauses.
           Note on some platforms (SunOS and Solaris) the permissions
-          (perm) are applied to the parent directory
+          (perm) are applied to the parent directory
           as the permissions on the socket itself are ignored.
         

-

+
+        

           The primary authorization mechanism of the command
-          channel is the key_list, which
-          contains a list of key_ids.
-          Each key_id in the key_list
+          channel is the key_list, which
+          contains a list of key_ids.
+          Each key_id in the key_list
           is authorized to execute commands over the control channel.
-          See Remote Name Daemon Control application in the section called “Administrative Tools”)
-          for information about configuring keys in rndc.
+          See Remote Name Daemon Control application in the section called “Administrative Tools”)
+          for information about configuring keys in rndc.
         

-

-          If no controls statement is present,
-          named will set up a default
+
+        

+          If no controls statement is present,
+          named will set up a default
           control channel listening on the loopback address 127.0.0.1
           and its IPv6 counterpart ::1.
-          In this case, and also when the controls statement
-          is present but does not have a keys clause,
-          named will attempt to load the command channel key
+          In this case, and also when the controls statement
+          is present but does not have a keys clause,
+          named will attempt to load the command channel key
           from the file rndc.key in
           /etc (or whatever sysconfdir
           was specified as when BIND was built).
           To create a rndc.key file, run
           rndc-confgen -a.
         

-

+
+        

           The rndc.key feature was created to
           ease the transition of systems from BIND 8,
           which did not have digital signatures on its command channel
-          messages and thus did not have a keys clause.
+          messages and thus did not have a keys clause.
 
           It makes it possible to use an existing BIND 8
           configuration file in BIND 9 unchanged,
-          and still have rndc work the same way
-          ndc worked in BIND 8, simply by executing the
+          and still have rndc work the same way
+          ndc worked in BIND 8, simply by executing the
           command rndc-confgen -a after BIND 9 is
           installed.
         

-

+
+        

           Since the rndc.key feature
           is only intended to allow the backward-compatible usage of
           BIND 8 configuration files, this
@@ -1086,86 +1157,99 @@
           those things.  The rndc.key file
           also has its
           permissions set such that only the owner of the file (the user that
-          named is running as) can access it.
+          named is running as) can access it.
           If you
           desire greater flexibility in allowing other users to access
-          rndc commands, then you need to create
+          rndc commands, then you need to create
           a
           rndc.conf file and make it group
           readable by a group
           that contains the users who should have access.
         

-

+
+        

           To disable the command channel, use an empty
-          controls statement:
-          controls { };.
+          controls statement:
+          controls { };.
         

-

-

+
+      

+      

 

-include Statement Grammar

-
include filename;

-

-

+include Statement Grammar

+        
+        
include filename;

+      
+      

 

-include Statement Definition and
+include Statement Definition and
           Usage

-

-          The include statement inserts the
-          specified file at the point where the include
-          statement is encountered. The include
+        
+
+        

+          The include statement inserts the
+          specified file at the point where the include
+          statement is encountered. The include
                 statement facilitates the administration of configuration
           files
           by permitting the reading or writing of some things but not
           others. For example, the statement could include private keys
           that are readable only by the name server.
         

-

-

+
+      

+      

 

-key Statement Grammar

-
key key_id {
+key Statement Grammar

+        
+
+
key key_id {
     algorithm algorithm_id;
     secret secret_string;
 };
 

-
-

+
+      

+
+      

 

-key Statement Definition and Usage

-

-          The key statement defines a shared
-          secret key for use with TSIG (see the section called “TSIG”)
+key Statement Definition and Usage

+        
+
+        

+          The key statement defines a shared
+          secret key for use with TSIG (see the section called “TSIG”)
           or the command channel
-          (see the section called “controls Statement Definition and
+          (see the section called “controls Statement Definition and
           Usage”).
         

-

-          The key statement can occur at the
+
+        

+          The key statement can occur at the
           top level
-          of the configuration file or inside a view
-          statement.  Keys defined in top-level key
+          of the configuration file or inside a view
+          statement.  Keys defined in top-level key
           statements can be used in all views.  Keys intended for use in
-          a controls statement
-          (see the section called “controls Statement Definition and
+          a controls statement
+          (see the section called “controls Statement Definition and
           Usage”)
           must be defined at the top level.
         

-

+
+        

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

-

+
+        

           The algorithm_id is a string
           that specifies a security/authentication algorithm.  The
-          named server supports hmac-md5,
+          named server supports hmac-md5,
           hmac-sha1, hmac-sha224,
           hmac-sha256, hmac-sha384
           and hmac-sha512 TSIG authentication.
@@ -1176,112 +1260,130 @@
           to be used by the algorithm, and is treated as a base-64
           encoded string.
         

-
-

+
+      

+      

 

-logging Statement Grammar

-
logging {
-   [ channel channel_name {
-     ( file path_name
-         [ versions ( number | unlimited ) ]
-         [ size size_spec ]
-       | syslog syslog_facility
-       | stderr
-       | null );
-     [ severity (critical | error | warning | notice |
+logging Statement Grammar

+        
+
+
logging {
+   [ channel channel_name {
+     ( file path_name
+         [ versions ( number | unlimited ) ]
+         [ size size_spec ]
+       | syslog syslog_facility
+       | stderr
+       | 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; ]
-     [ buffered yes or no; ]
+     [ print-category yes or no; ]
+     [ print-severity yes or no; ]
+     [ print-time yes or no; ]
+     [ buffered yes or no; ]
    }; ]
-   [ category category_name {
+   [ category category_name {
      channel_name ; [ channel_name ; ... ]
    }; ]
    ...
 };
 

-
-

+
+      

+
+      

 

-logging Statement Definition and
+logging Statement Definition and
           Usage

-

-          The logging statement configures a
+        
+
+        

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

-

-          Only one logging statement is used to
+        

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

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

-

-          If named is started with the
+
+        

+          If named is started with the
           -L option, it logs to the specified file
           at startup, instead of using syslog. In this case the logging
           configuration will be:
         

+
 
logging {
      category default { default_logfile; default_debug; };
      category unmatched { null; };
 };
 

-

+
+        

           In BIND 9, 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
+          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 -g option
           was specified.
         

-

+
+        

 

-The channel Phrase

-

+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 destination clause that
             says whether messages selected for the channel go to a file, to a
             particular syslog facility, to the standard error stream, 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
+            info), and whether to include a
+            named-generated time stamp, the
             category name
             and/or severity level (the default is not to include any).
           

-

-            The null destination clause
+
+          

+            The null destination clause
             causes all messages sent to the channel to be discarded;
             in that case, other options for the channel are meaningless.
           

-

-            The file destination clause directs
+
+          

+            The file destination clause directs
             the channel
             to a disk file.  It 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.
           

-

-            If you use the versions log file
+
+          

+            If you use the versions log file
             option, then
-            named will retain that many backup
+            named will retain that many backup
             versions of the file by
             renaming them when opening.  For example, if you choose to keep
             three old versions
@@ -1291,25 +1393,26 @@
             lamers.log.2, lamers.log.0 is renamed
             to lamers.log.1, and lamers.log is
             renamed to lamers.log.0.
-            You can say versions unlimited to
+            You can say versions unlimited to
             not limit
             the number of versions.
-            If a size option is associated with
+            If a size option is associated with
             the log file,
             then renaming is only done when the file being opened exceeds the
             indicated size.  No backup versions are kept by default; any
             existing
             log file is simply appended.
           

-

-            The size option for files is used
+
+          

+            The size option for files is used
             to limit log
-            growth. If the file ever exceeds the size, then named will
-            stop writing to the file unless it has a versions option
+            growth. If the file ever exceeds the size, then named will
+            stop writing to the file unless it has a versions option
             associated with it.  If backup versions are kept, the files are
             rolled as
             described above and a new one begun.  If there is no
-            versions option, no more data will
+            versions option, no more data will
             be written to the log
             until some out-of-band mechanism removes or truncates the log to
             less than the
@@ -1317,64 +1420,68 @@
             the
             file.
           

-

-            Example usage of the size and
-            versions options:
+
+          

+            Example usage of the size and
+            versions options:
           

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

-

-            The syslog destination clause
+
+          

+            The syslog destination clause
             directs the
             channel to the system log.  Its argument is a
-            syslog facility as described in the syslog man
-            page. Known facilities are kern, user,
-            mail, daemon, auth,
-            syslog, lpr, news,
-            uucp, cron, authpriv,
-            ftp, local0, local1,
-            local2, local3, local4,
-            local5, local6 and
-            local7, however not all facilities
+            syslog facility as described in the syslog man
+            page. Known facilities are kern, user,
+            mail, daemon, auth,
+            syslog, lpr, news,
+            uucp, cron, authpriv,
+            ftp, local0, local1,
+            local2, local3, local4,
+            local5, local6 and
+            local7, however not all facilities
             are supported on
             all operating systems.
-            How syslog will handle messages
+            How syslog will handle messages
             sent to
-            this facility is described in the syslog.conf man
-            page. If you have a system which uses a very old version of syslog that
-            only uses two arguments to the openlog() function,
+            this facility is described in the syslog.conf man
+            page. If you have a system which uses a very old version of syslog that
+            only uses two arguments to the openlog() function,
             then this clause is silently ignored.
           

-

+          

             On Windows machines syslog messages are directed to the EventViewer.
           

-

-            The severity clause works like syslog's
+          

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

-

-            If you are using syslog, then the syslog.conf priorities
+          

+            If you are using syslog, then the syslog.conf priorities
             will also determine what eventually passes through. For example,
-            defining a channel facility and severity as daemon and debug but
-            only logging daemon.warning via syslog.conf will
-            cause messages of severity info and
-            notice to
-            be dropped. If the situation were reversed, with named writing
-            messages of only warning or higher,
-            then syslogd would
+            defining a channel facility and severity as daemon and debug but
+            only logging daemon.warning via syslog.conf will
+            cause messages of severity info and
+            notice to
+            be dropped. If the situation were reversed, with named writing
+            messages of only warning or higher,
+            then syslogd would
             print all messages it received from the channel.
           

-

-            The stderr destination clause
+
+          

+            The stderr destination clause
             directs the
             channel to the server's standard error stream.  This is intended
             for
@@ -1382,67 +1489,74 @@
             example
             when debugging a configuration.
           

-

+
+          

             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
+            level is set either by starting the named server
             with the -d flag followed by a positive integer,
-            or by running rndc trace.
+            or by running rndc trace.
             The global debug level
-            can be set to zero, and debugging mode turned off, by running rndc
+            can be set to zero, and debugging mode turned off, by running rndc
 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, for example:
           

+
 
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
+            level. Channels with dynamic
             severity use the
             server's global debug level to determine what messages to print.
           

-

-            If print-time has been turned on,
+          

+            If print-time has been turned on,
             then
-            the date and time will be logged. print-time may
-            be specified for a syslog channel,
+            the date and time will be logged. print-time may
+            be specified for a syslog channel,
             but is usually
-            pointless since syslog also logs
+            pointless since syslog also logs
             the date and
-            time. If print-category is
+            time. If print-category is
             requested, then the
-            category of the message will be logged as well. Finally, if print-severity is
-            on, then the severity level of the message will be logged. The print- options may
+            category of the message will be logged as well. Finally, if print-severity is
+            on, then the severity level of the message will be logged. The print- options may
             be used in any combination, and will always be printed in the
             following
             order: time, category, severity. Here is an example where all
-            three print- options
+            three print- options
             are on:
           

-

+
+          

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

-

-            If buffered has been turned on the output
+
+          

+            If buffered has been turned on the output
             to files will not be flushed after each log entry.  By default
             all log messages are flushed.
           

-

+
+          

             There are four predefined channels that are used for
-            named's default logging as follows.
-            If named is started with the
+            named's default logging as follows.
+            If named is started with the
             -L then a
-            fifth channel default_logfile is added.
+            fifth channel default_logfile is added.
             How they are
-            used is described in the section called “The category Phrase”.
+            used is described in the section called “The category Phrase”.
           

+
 
channel default_syslog {
     // send to syslog's daemon facility
     syslog daemon;
@@ -1479,57 +1593,68 @@ channel default_logfile {
     severity dynamic;
 };
 

-

-            The default_debug channel has the
+
+          

+            The default_debug channel has the
             special
             property that it only produces output when the server's debug
             level is
             nonzero.  It normally writes to a file called 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
+            is created only after named has
             changed to the
-            new UID, and any debug output generated while named is
+            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 -L
             option to specify a default logfile, or the -g
             option to log to standard error which you can redirect 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.
           

-
-

+        

+
+        

 

-The category Phrase

-

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

-

-            If you start named with the
+
+          

+            If you start named with the
             -L option then the default category is:
           

+
 
category default { default_logfile; 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;
@@ -1539,26 +1664,30 @@ category security {
     default_syslog;
     default_debug;
 };

-

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

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

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

-

+
+          

             Following are the available categories and brief descriptions
             of the types of log information they contain. More
             categories may be added in future BIND releases.
           

-

+          

+  
--++
-

 




 
 
 

 
-	  
client

+	  
client

 			
 
 	  

@@ -1568,7 +1697,7 @@ category notify { null; };
 

 

 
-	  
cname

+	  
cname

 			
 
 	  

@@ -1579,7 +1708,7 @@ category notify { null; };
 

 

 
-	  
config

+	  
config

 			
 
 	  

@@ -1589,7 +1718,7 @@ category notify { null; };
 

 

 
-	  
database

+	  
database

 			
 
 	  

@@ -1601,7 +1730,7 @@ category notify { null; };
 

 

 
-	  
default

+	  
default

 			
 
 	  

@@ -1614,21 +1743,21 @@ category notify { null; };
 

 

 
-	  
delegation-only

+	  
delegation-only

 			
 
 	  

 	    Delegation only.  Logs queries that have been
 	    forced to NXDOMAIN as the result of a
 	    delegation-only zone or a
-	    delegation-only in a
+	    delegation-only in a
 	    forward, hint or stub zone declaration.
 	  

 			
 

 

 
-	  
dispatch

+	  
dispatch

 			
 
 	  

@@ -1639,7 +1768,7 @@ category notify { null; };
 

 

 
-	  
dnssec

+	  
dnssec

 			
 
 	  

@@ -1649,7 +1778,7 @@ category notify { null; };
 

 

 
-	  
dnssec

+	  
dnstap

 			
 
 	  

@@ -1659,7 +1788,7 @@ category notify { null; };
 

 

 
-	  
edns-disabled

+	  
edns-disabled

 			
 
 	  

@@ -1681,7 +1810,7 @@ category notify { null; };
 	    number of false-positive reports.
 	  

 	  

-	    Note: eventually named will have to stop
+	    Note: eventually named will have to stop
 	    treating such timeouts as due to RFC 1034 non
 	    compliance and start treating it as plain
 	    packet loss.  Falsely classifying packet
@@ -1693,7 +1822,7 @@ category notify { null; };
 

 

 
-	  
general

+	  
general

 			
 
 	  

@@ -1704,7 +1833,7 @@ category notify { null; };
 

 

 
-	  
lame-servers

+	  
lame-servers

 			
 
 	  

@@ -1716,7 +1845,7 @@ category notify { null; };
 

 

 
-	  
network

+	  
network

 			
 
 	  

@@ -1726,7 +1855,7 @@ category notify { null; };
 

 

 
-	  
notify

+	  
notify

 			
 
 	  

@@ -1736,15 +1865,15 @@ category notify { null; };
 

 

 
-	  
queries

+	  
queries

 			
 
 	  

 	    Specify where queries should be logged to.
 	  

 	  

-	    At startup, specifying the category queries will also
-	    enable query logging unless querylog option has been
+	    At startup, specifying the category queries will also
+	    enable query logging unless querylog option has been
 	    specified.
 	  

 
@@ -1780,7 +1909,7 @@ category notify { null; };
 

 

 
-	  
query-errors

+	  
query-errors

 			
 
 	  

@@ -1791,13 +1920,13 @@ category notify { null; };
 

 

 
-	  
rate-limit

+	  
rate-limit

 			
 
 	  

 	    The start, periodic, and final notices of the
 	    rate limiting of a stream of responses are logged at
-	    info severity in this category.
+	    info severity in this category.
 	    These messages include a hash value of the domain name
 	    of the response and the name itself,
 	    except when there is insufficient memory to record
@@ -1811,13 +1940,13 @@ category notify { null; };
 	  

 	  

 	    Rate limiting of individual requests
-	    is logged in the query-errors category.
+	    is logged in the query-errors category.
 	  

 			
 

 

 
-	  
resolver

+	  
resolver

 			
 
 	  

@@ -1829,20 +1958,20 @@ category notify { null; };
 

 

 
-	  
rpz

+	  
rpz

 			
 
 	  

 	    Information about errors in response policy zone files,
 	    rewritten responses, and at the highest
-	    debug levels, mere rewriting
+	    debug levels, mere rewriting
 	    attempts.
 	  

 			
 

 

 
-	  
security

+	  
security

 			
 
 	  

@@ -1852,7 +1981,7 @@ category notify { null; };
 

 

 
-	  
spill

+	  
spill

 			
 
 	  

@@ -1864,22 +1993,22 @@ category notify { null; };
 

 

 
-	  
unmatched

+	  
unmatched

 			
 
 	  

-	    Messages that named was unable to determine the
-	    class of or for which there was no matching view.
-	    A one line summary is also logged to the client category.
+	    Messages that named was unable to determine the
+	    class of or for which there was no matching view.
+	    A one line summary is also logged to the client category.
 	    This category is best sent to a file or stderr, by
 	    default it is sent to
-	    the null channel.
+	    the null channel.
 	  

 			
 

 

 
-	  
update

+	  
update

 			
 
 	  

@@ -1889,7 +2018,7 @@ category notify { null; };
 

 

 
-	  
update-security

+	  
update-security

 			
 
 	  

@@ -1899,7 +2028,7 @@ category notify { null; };
 

 

 
-	  
xfer-in

+	  
xfer-in

 			
 
 	  

@@ -1909,7 +2038,7 @@ category notify { null; };
 

 

 
-	  
xfer-out

+	  
xfer-out

 			
 
 	  

@@ -1918,27 +2047,29 @@ category notify { null; };
 	

 

 

+
 
-

+        

+        

 

-The query-errors Category

-

-            The query-errors category is
+The query-errors Category

+          

+            The query-errors category is
             specifically intended for debugging purposes: To identify
             why and how specific queries result in responses which
             indicate an error.
             Messages of this category are therefore only logged
-            with debug levels.
+            with debug levels.
           

-

+
+          

             At the debug levels of 1 or higher, each response with the
             rcode of SERVFAIL is logged as follows:
           

-

+          

             client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880
           

-

+          

             This means an error resulting in SERVFAIL was
             detected at line 3880 of source file
             query.c.
@@ -1946,13 +2077,13 @@ category notify { null; };
             help identify the cause of SERVFAIL for an
             authoritative server.
           

-

+          

             At the debug levels of 2 or higher, detailed context
             information of recursive resolutions that resulted in
             SERVFAIL is logged.
             The log message will look like as follows:
           

-

+          

 
             

 
@@ -1963,14 +2094,14 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             

 

           

-

+          

             The first part before the colon shows that a recursive
             resolution for AAAA records of www.example.com completed
             in 30.000183 seconds and the final result that led to the
             SERVFAIL was determined at line 2970 of source file
             resolver.c.
           

-

+          

             The following part shows the detected final result and the
             latest result of DNSSEC validation.
             The latter is always success when no validation attempt
@@ -1980,7 +2111,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             to a timeout in 30 seconds.
             DNSSEC validation was probably not attempted.
           

-

+          

             The last part enclosed in square brackets shows statistics
             information collected for this particular resolution
             attempt.
@@ -1990,10 +2121,12 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             The meaning of the other fields is summarized in the
             following table.
           

-

+
+          

+            
--++
@@ -2129,15 +2262,16 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   
-

 




 
 
 

 

 

-

+
+          
+          

             At the debug levels of 3 or higher, the same messages
             as those at the debug 1 level are logged for other errors
             than SERVFAIL.
             Note that negative responses such as NXDOMAIN are not
             regarded as errors here.
           

-

+          

             At the debug levels of 4 or higher, the same messages
             as those at the debug 2 level are logged for other errors
             than SERVFAIL.
@@ -2146,16 +2280,20 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             This is because any unexpected results can be difficult to
             debug in the recursion case.
           

-
-
-

+        

+      
+
+      

 

-lwres Statement Grammar

-

-           This is the grammar of the lwres
+lwres Statement Grammar

+        
+
+        

+           This is the grammar of the lwres
           statement in the named.conf file:
         

-
lwres {
+
+
lwres {
     [ listen-on { ip_addr [port ip_port] [dscp ip_dscp] ;
     [ ip_addr [port ip_port] [dscp ip_dscp] ; ... ] }; ]
     [ view view_name; ]
@@ -2165,20 +2303,24 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     [ lwres-clients number; ]
 };
 

-
-

+
+      

+      

 

-lwres Statement Definition and Usage

-

-          The lwres statement configures the
+lwres Statement Definition and Usage

+        
+
+        

+          The lwres statement configures the
           name
           server to also act as a lightweight resolver server. (See
-          the section called “Running a Resolver Daemon”.)  There may be multiple
-          lwres statements configuring
+          the section called “Running a Resolver Daemon”.)  There may be multiple
+          lwres statements configuring
           lightweight resolver servers with different properties.
         

-

-          The listen-on statement specifies a
+
+        

+          The listen-on statement specifies a
           list of
           IPv4 addresses (and ports) that this instance of a lightweight
           resolver daemon
@@ -2188,8 +2330,9 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           127.0.0.1,
           port 921.
         

-

-          The view statement binds this
+
+        

+          The view statement binds this
           instance of a
           lightweight resolver daemon to a view in the DNS namespace, so that
           the
@@ -2199,75 +2342,86 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           is
           used, and if there is no default view, an error is triggered.
         

-

-          The search statement is equivalent to
+
+        

+          The search statement is equivalent to
           the
-          search statement in
+          search statement in
           /etc/resolv.conf.  It provides a
           list of domains
           which are appended to relative names in queries.
         

-

-          The ndots statement is equivalent to
+
+        

+          The ndots statement is equivalent to
           the
-          ndots statement in
+          ndots statement in
           /etc/resolv.conf.  It indicates the
           minimum
           number of dots in a relative domain name that should result in an
           exact match lookup before search path elements are appended.
         

-

+        

           The lwres-tasks statement specifies the number
           of worker threads the lightweight resolver will dedicate to serving
           clients.  By default the number is the same as the number of CPUs on
           the system; this can be overridden using the -n
           command line option when starting the server.
         

-

+        

           The lwres-clients specifies
           the number of client objects per thread the lightweight
           resolver should create to serve client queries.
           By default, if the lightweight resolver runs as a part
-          of named, 256 client objects are
-          created for each task; if it runs as lwresd,
+          of named, 256 client objects are
+          created for each task; if it runs as lwresd,
           1024 client objects are created for each thread. The maximum
           value is 32768; higher values will be silently ignored and
           the maximum will be used instead.
           Note that setting too high a value may overconsume
           system resources.
         

-

+        

           The maximum number of client queries that the lightweight
           resolver can handle at any one time equals
           lwres-tasks times lwres-clients.
         

-
-

+      

+      

 

-masters Statement Grammar

+masters Statement Grammar

+        
+
 
-masters name [port ip_port] [dscp ip_dscp] { ( masters_list |
+masters name [port ip_port] [dscp ip_dscp] { ( masters_list |
       ip_addr [port ip_port] [key key] ) ; [...] };
 

-
-

+
+      

+
+      

 

-masters Statement Definition and
+masters Statement Definition and
           Usage

-
masters
+        
+        
masters
           lists allow for a common set of masters to be easily used by
-          multiple stub and slave zones in their masters
-          or also-notify lists.
+          multiple stub and slave zones in their masters
+          or also-notify lists.
         

-

-

+      

+
+      

 

-options Statement Grammar

-

-          This is the grammar of the options
+options Statement Grammar

+        
+
+        

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

-
options {
+
+
options {
     [ attach-cache cache_name; ]
     [ version version_string; ]
     [ hostname hostname_string; ]
@@ -2544,24 +2698,29 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     [v6-bias number ; ]
 };
 

-
-

+
+      

+
+      

 

-options Statement Definition and
+options Statement Definition and
           Usage

-

-          The options statement sets up global
+        
+
+        

+          The options statement sets up global
           options
           to be used by BIND. This statement
           may appear only
-          once in a configuration file. If there is no options
+          once in a configuration file. If there is no options
           statement, an options block with each option set to its default will
           be used.
         

-

-
attach-cache

+
+        

+
attach-cache

 

-

+                

                   Allows multiple views to share a single cache
                   database.
                   Each view has its own cache database by default, but
@@ -2570,38 +2729,43 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   share a single cache to save memory and possibly
                   improve resolution efficiency by using this option.
                 

-

-                  The attach-cache option
-                  may also be specified in view
+
+                

+                  The attach-cache option
+                  may also be specified in view
                   statements, in which case it overrides the
-                  global attach-cache option.
+                  global attach-cache option.
                 

-

+
+                

                   The cache_name specifies
                   the cache to be shared.
-                  When the named server configures
+                  When the named server configures
                   views which are supposed to share a cache, it
                   creates a cache with the specified name for the
                   first view of these sharing views.
                   The rest of the views will simply refer to the
                   already created cache.
                 

-

+
+                

                   One common configuration to share a cache would be to
                   allow all views to share a single cache.
                   This can be done by specifying
-                  the attach-cache as a global
+                  the attach-cache as a global
                   option with an arbitrary name.
                 

-

+
+                

                   Another possible operation is to allow a subset of
                   all views to share a cache while the others to
                   retain their own caches.
                   For example, if there are three views A, B, and C,
                   and only A and B should share a cache, specify the
-                  attach-cache option as a view A (or
+                  attach-cache option as a view A (or
                   B)'s option, referring to the other view name:
                 

+
 
   view "A" {
     // this view has its own cache
@@ -2616,22 +2780,24 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     ...
   };
 

-

+
+                

                   Views that share a cache must have the same policy
                   on configurable parameters that may affect caching.
                   The current implementation requires the following
                   configurable options be consistent among these
                   views:
-                  check-names,
-                  cleaning-interval,
-                  dnssec-accept-expired,
-                  dnssec-validation,
-                  max-cache-ttl,
-                  max-ncache-ttl,
-                  max-cache-size, and
-                  zero-no-soa-ttl.
+                  check-names,
+                  cleaning-interval,
+                  dnssec-accept-expired,
+                  dnssec-validation,
+                  max-cache-ttl,
+                  max-ncache-ttl,
+                  max-cache-size, and
+                  zero-no-soa-ttl.
                 

-

+
+                

                   Note that there may be other parameters that may
                   cause confusion if they are inconsistent for
                   different views that share a single cache.
@@ -2643,9 +2809,10 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   configuration differences in different views do
                   not cause disruption with a shared cache.
                 

-

-
directory

-

+              

+
directory

+

+              

                 The working directory of the server.
                 Any non-absolute pathnames in the configuration file will be
                 taken
@@ -2658,46 +2825,47 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 which the server
                 was started. The directory specified should be an absolute
                 path.
-              

-
dnstap

+              

+            
+
dnstap

 

-

-                dnstap is a fast, flexible method
+              

+                dnstap is a fast, flexible method
                 for capturing and logging DNS traffic. Developed by
                 Robert Edmonds at Farsight Security, Inc., and supported
-                by multiple DNS implementations, dnstap
+                by multiple DNS implementations, dnstap
                 uses
-                libfstrm (a lightweight high-speed
+                libfstrm (a lightweight high-speed
                 framing library, see
-                https://github.com/farsightsec/fstrm) to send
+                https://github.com/farsightsec/fstrm) to send
                 event payloads which are encoded using Protocol Buffers
-                (libprotobuf-c, a mechanism for
+                (libprotobuf-c, a mechanism for
                 serializing structured data developed
                 by Google, Inc.; see 
-                https://developers.google.com/protocol-buffers).
+                https://developers.google.com/protocol-buffers).
               

-

-                To enable dnstap at compile time, 
-                the fstrm and protobuf-c
+              

+                To enable dnstap at compile time, 
+                the fstrm and protobuf-c
                 libraries must be available, and BIND must be configured with
                 --enable-dnstap.
               

-

-                The dnstap option is a bracketed list
+              

+                The dnstap option is a bracketed list
                 of message types to be logged. These may be set differently
                 for each view. Supported types are client,
                 auth, resolver, and
                 forwarder.  Specifying type
-                all will cause all dnstap
+                all will cause all dnstap
                 messages to be logged, regardless of type.
               

-

+              

                 Each type may take an additional argument to indicate whether
                 to log query messages or
                 response messages; if not specified,
                 both queries and responses are logged.
               

-

+              

                 Example: To log all authoritative queries and responses,
                 recursive client responses, and upstream queries sent by
                 the resolver, use:
@@ -2710,72 +2878,78 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 

 

               

-

-                Logged dnstap messages can be parsed
-                using the dnstap-read utility (see
-                dnstap-read(1) for details).
+              

+                Logged dnstap messages can be parsed
+                using the dnstap-read utility (see
+                dnstap-read(1) for details).
               

-

-                For more information on dnstap, see
-                http://dnstap.info.
+              

+                For more information on dnstap, see
+                http://dnstap.info.
               

-
-
dnstap-output

+            
+
dnstap-output

 

-

-                Configures the path to which the dnstap
-                frame stream will be sent if dnstap
+              

+                Configures the path to which the dnstap
+                frame stream will be sent if dnstap
                 is enabled at compile time and active.
               

-

+              

                 The first argument is either file or
                 unix, indicating whether the destination
                 is a file or a UNIX domain socket.  The second argument
                 is the path of the file or socket.  (Note: when using a
-                socket, dnstap messages will
+                socket, dnstap messages will
                 only be sent if another process such as
-                fstrm_capture
-                (provided with libfstrm) is listening on
+                fstrm_capture
+                (provided with libfstrm) is listening on
                 the socket.)
               

-

-                dnstap-output can only be set globally
-                in options. Currently, it can only be
-                set once while named is running;
+              

+                dnstap-output can only be set globally
+                in options. Currently, it can only be
+                set once while named is running;
                 once set, it cannot be changed by
-                rndc reload or
-                rndc reconfig.
+                rndc reload or
+                rndc reconfig.
               

-

-
dnstap-identity

-

-                Specifies an identity string to send in
-                dnstap messages. If set to
+            

+
dnstap-identity

+

+              

+                Specifies an identity string to send in
+                dnstap messages. If set to
                 hostname, which is the default, the
                 server's hostname will be sent. If set to
                 none, no identity string will be sent.
-              

-
dnstap-version

-

-                Specifies a version string to send in
-                dnstap messages. The default is the
+              

+            

+
dnstap-version

+

+              

+                Specifies a version string to send in
+                dnstap messages. The default is the
                 version number of the BIND release. If set to
                 none, no version string will be sent.
-              

-
geoip-directory

-

+              

+            

+
geoip-directory

+

+              

                 Specifies the directory containing GeoIP
                 .dat database files for GeoIP
                 initialization.  By default, this option is unset
                 and the GeoIP support will use libGeoIP's
                 built-in directory.
-                (For details, see the section called “acl Statement Definition and
+                (For details, see the section called “acl Statement Definition and
           Usage” about the
-                geoip ACL.)
-              

-
key-directory

-

+                geoip ACL.)
+              

+            

+
key-directory

+

+              

                 When performing dynamic update of secure zones, the
                 directory where the public and private DNSSEC key files
                 should be found, if different than the current working
@@ -2784,16 +2958,17 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 bind.keys,
                 rndc.key or
                 session.key.)
-              

-
managed-keys-directory

+              

+            
+
managed-keys-directory

 

-

+              

                 Specifies the directory in which to store the files that
                 track managed DNSSEC keys.  By default, this is the working
                 directory.
               

-

-                If named is not configured to use views,
+              

+                If named is not configured to use views,
                 then managed keys for the server will be tracked in a single
                 file called managed-keys.bind.
                 Otherwise, managed keys will be tracked in separate files,
@@ -2803,32 +2978,37 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 followed by the extension
                 .mkeys.
               

-

+              

                 (Note: in previous releases, file names for views
                 always used the SHA256 hash of the view name. To ensure
                 compatibility after upgrade, if a file using the old
                 name format is found to exist, it will be used instead
                 of the new format.)
               

-

-
named-xfer

-

+            

+
named-xfer

+

+              

                 This option is obsolete. It
                 was used in BIND 8 to specify
-                the pathname to the named-xfer
+                the pathname to the named-xfer
                 program.  In BIND 9, no separate
-                named-xfer program is needed;
+                named-xfer program is needed;
                 its functionality is built into the name server.
-              

-
tkey-gssapi-keytab

-

+              

+            

+
tkey-gssapi-keytab

+

+              

                 The KRB5 keytab file to use for GSS-TSIG updates. If
                 this option is set and tkey-gssapi-credential is not
                 set, then updates will be allowed with any key
                 matching a principal in the specified keytab.
-              

-
tkey-gssapi-credential

-

+              

+            

+
tkey-gssapi-credential

+

+              

                 The security credential with which the server should
                 authenticate keys requested by the GSS-TSIG protocol.
                 Currently only Kerberos 5 authentication is available
@@ -2838,150 +3018,178 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 The location keytab file can be overridden using the
                 tkey-gssapi-keytab option. Normally this principal is
                 of the form "DNS/server.domain".
-                To use GSS-TSIG, tkey-domain must
+                To use GSS-TSIG, tkey-domain must
                 also be set if a specific keytab is not set with
                 tkey-gssapi-keytab.
-              

-
tkey-domain

-

+              

+            

+
tkey-domain

+

+              

                 The domain appended to the names of all shared keys
-                generated with TKEY.  When a
-                client requests a TKEY exchange,
+                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
+                In most cases, the domainname
                 should be the server's domain name, or an otherwise
                 non-existent subdomain like
                 "_tkey.domainname".  If you are
                 using GSS-TSIG, this variable must be defined, unless
                 you specify a specific keytab using tkey-gssapi-keytab.
-              

-
tkey-dhkey

-

+              

+            

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

-
cache-file

-

+              

+            

+
cache-file

+

+              

                 This is for testing only.  Do not use.
-              

-
dump-file

-

+              

+            

+
dump-file

+

+              

                 The pathname of the file the server dumps
                 the database to when instructed to do so with
-                rndc dumpdb.
+                rndc dumpdb.
                 If not specified, the default is named_dump.db.
-              

-
memstatistics-file

-

+              

+            

+
memstatistics-file

+

+              

                 The pathname of the file the server writes memory
                 usage statistics to on exit. If not specified,
                 the default is named.memstats.
-              

-
lock-file

+              

+            
+
lock-file

 

-

-                The pathname of a file on which named will
+              

+                The pathname of a file on which named will
                 attempt to acquire a file lock when starting up for
                 the first time; if unsuccessful, the server will
                 will terminate, under the assumption that another
                 server is already running.  If not specified, the default is
                 /var/run/named/named.lock.
               

-

-                Specifying lock-file none disables the
-                use of a lock file.  lock-file is
-                ignored if named was run using the -X
+              

+                Specifying lock-file none disables the
+                use of a lock file.  lock-file is
+                ignored if named was run using the -X
                 option, which overrides it.  Changes to
-                lock-file are ignored if
-                named is being reloaded or
+                lock-file are ignored if
+                named is being reloaded or
                 reconfigured; it is only effective when the server is
                 first started up.
               

-

-
pid-file

-

+            

+
pid-file

+

+              

                 The pathname of the file the server writes its process ID
                 in. If not specified, the default is
                 /var/run/named/named.pid.
                 The PID file is used by programs that want to send signals to
                 the running
-                name server. Specifying pid-file none disables the
+                name server. Specifying pid-file none disables the
                 use of a PID file — no file will be written and any
-                existing one will be removed.  Note that none
+                existing one will be removed.  Note that none
                 is a keyword, not a filename, and therefore is not enclosed
                 in
                 double quotes.
-              

-
recursing-file

-

+              

+            

+
recursing-file

+

+              

                 The pathname of the file the server dumps
                 the queries that are currently recursing when instructed
-                to do so with rndc recursing.
+                to do so with rndc recursing.
                 If not specified, the default is named.recursing.
-              

-
statistics-file

-

+              

+            

+
statistics-file

+

+              

                 The pathname of the file the server appends statistics
-                to when instructed to do so using rndc stats.
+                to when instructed to do so using rndc stats.
                 If not specified, the default is named.stats in the
                 server's current directory.  The format of the file is
                 described
-                in the section called “The Statistics File”.
-              

-
bindkeys-file

-

+                in the section called “The Statistics File”.
+              

+            

+
bindkeys-file

+

+              

                 The pathname of a file to override the built-in trusted
-                keys provided by named.
-                See the discussion of dnssec-lookaside
-                and dnssec-validation for details.
+                keys provided by named.
+                See the discussion of dnssec-lookaside
+                and dnssec-validation for details.
                 If not specified, the default is
                 /etc/bind.keys.
-              

-
secroots-file

-

+              

+            

+
secroots-file

+

+              

                 The pathname of the file the server dumps
                 security roots to when instructed to do so with
-                rndc secroots.
+                rndc secroots.
                 If not specified, the default is
                 named.secroots.
-              

-
session-keyfile

-

+              

+            

+
session-keyfile

+

+              

                 The pathname of the file into which to write a TSIG
-                session key generated by named for use by
-                nsupdate -l.  If not specified, the
+                session key generated by named for use by
+                nsupdate -l.  If not specified, the
                 default is /var/run/named/session.key.
-                (See the section called “Dynamic Update Policies”, and in
+                (See the section called “Dynamic Update Policies”, and in
                 particular the discussion of the
-                update-policy statement's
+                update-policy statement's
                 local option for more
                 information about this feature.)
-              

-
session-keyname

-

+              

+            

+
session-keyname

+

+              

                 The key name to use for the TSIG session key.
                 If not specified, the default is "local-ddns".
-              

-
session-keyalg

-

+              

+            

+
session-keyalg

+

+              

                 The algorithm to use for the TSIG session key.
                 Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
                 hmac-sha384, hmac-sha512 and hmac-md5.  If not
                 specified, the default is hmac-sha256.
-              

-
port

-

+              

+            

+
port

+

+              

                 The UDP/TCP port number the server uses for
                 receiving and sending DNS protocol traffic.
                 The default is 53.  This option is mainly intended for server
@@ -2989,16 +3197,20 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 a server using a port other than 53 will not be able to
                 communicate with
                 the global DNS.
-              

-
dscp

-

+              

+            

+
dscp

+

+              

                 The global Differentiated Services Code Point (DSCP)
                 value to classify outgoing DNS traffic on operating
                 systems that support DSCP. Valid values are 0 through 63.
                 It is not configured by default.
-              

-
random-device

-

+              

+            

+
random-device

+

+              

                 The source of entropy to be used by the server.  Entropy is
                 primarily needed
                 for DNSSEC operations, such as TKEY transactions and dynamic
@@ -3011,37 +3223,40 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 is
                 /dev/random
                 (or equivalent) when present, and none otherwise.  The
-                random-device option takes
+                random-device option takes
                 effect during
                 the initial configuration load at server startup time and
                 is ignored on subsequent reloads.
-              

-
preferred-glue

-

+              

+            

+
preferred-glue

+

+              

                 If specified, the listed type (A or AAAA) will be emitted
                 before other glue
                 in the additional section of a query response.
                 The default is to prefer A records when responding
                 to queries that arrived via IPv4 and AAAA when
                 responding to queries that arrived via IPv6.
-              

+              

+            
 

-root-delegation-only
+root-delegation-only
 

 

-

+              

                 Turn on enforcement of delegation-only in TLDs
                 (top level domains) and root zones with an optional
                 exclude list.
               

-

+              

                 DS queries are expected to be made to and be answered by
                 delegation only zones.  Such queries and responses are
                 treated as an exception to delegation-only processing
                 and are not converted to NXDOMAIN responses provided
                 a CNAME is not discovered at the query name.
               

-

+              

                 If a delegation only zone server also serves a child
                 zone it is not always possible to determine whether
                 an answer comes from the delegation only zone or the
@@ -3057,183 +3272,187 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 all these checks there is still a possibility of
                 false negatives when a child zone is being served.
               

-

+              

                 Similarly false positives can arise from empty nodes
                 (no records at the name) in the delegation only zone
                 when the query type is not ANY.
               

-

+              

                 Note some TLDs are not delegation only (e.g. "DE", "LV",
                 "US" and "MUSEUM").  This list is not exhaustive.
               

+
 
 options {
         root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
 };
 

-

-
disable-algorithms

+
+            
+
disable-algorithms

 

-

+              

                 Disable the specified DNSSEC algorithms at and below the
                 specified name.
-                Multiple disable-algorithms
+                Multiple disable-algorithms
                 statements are allowed.
-                Only the best match disable-algorithms
+                Only the best match disable-algorithms
                 clause will be used to determine which algorithms are used.
               

-

+              

                 If all supported algorithms are disabled, the zones covered
-                by the disable-algorithms will be treated
+                by the disable-algorithms will be treated
                 as insecure.
               

-

-
disable-ds-digests

+            
+
disable-ds-digests

 

-

+              

                 Disable the specified DS/DLV digest types at and below the
                 specified name.
-                Multiple disable-ds-digests
+                Multiple disable-ds-digests
                 statements are allowed.
-                Only the best match disable-ds-digests
+                Only the best match disable-ds-digests
                 clause will be used to determine which digest types are used.
               

-

+              

                 If all supported digest types are disabled, the zones covered
-                by the disable-ds-digests will be treated
+                by the disable-ds-digests will be treated
                 as insecure.
               

-

-
dnssec-lookaside

+            
+
dnssec-lookaside

 

-

-                When set, dnssec-lookaside provides the
+              

+                When set, dnssec-lookaside provides the
                 validator with an alternate method to validate DNSKEY
                 records at the top of a zone.  When a DNSKEY is at or
                 below a domain specified by the deepest
-                dnssec-lookaside, and the normal DNSSEC
+                dnssec-lookaside, and the normal DNSSEC
                 validation has left the key untrusted, the trust-anchor
                 will be appended to the key name and a DLV record will be
                 looked up to see if it can validate the key.  If the DLV
                 record validates a DNSKEY (similarly to the way a DS
                 record does) the DNSKEY RRset is deemed to be trusted.
               

-

-                If dnssec-lookaside is set to
+              

+                If dnssec-lookaside is set to
                 auto, then built-in default
                 values for the DLV domain and trust anchor will be
                 used, along with a built-in key for validation.
               

-

-                If dnssec-lookaside is set to
+              

+                If dnssec-lookaside is set to
                 no, then dnssec-lookaside
                 is not used.
               

-

+              

                 The default DLV key is stored in the file
                 bind.keys;
-                named will load that key at
-                startup if dnssec-lookaside is set to
+                named will load that key at
+                startup if dnssec-lookaside is set to
                 auto.  A copy of the file is
                 installed along with BIND 9, and is
                 current as of the release date.  If the DLV key expires, a
                 new copy of bind.keys can be downloaded
-                from https://www.isc.org/solutions/dlv/.
+                from https://www.isc.org/solutions/dlv/.
               

-

+              

                 (To prevent problems if bind.keys is
                 not found, the current key is also compiled in to
-                named.  Relying on this is not
-                recommended, however, as it requires named
+                named.  Relying on this is not
+                recommended, however, as it requires named
                 to be recompiled with a new key when the DLV key expires.)
               

-

-                NOTE: named only loads certain specific
+              

+                NOTE: named only loads certain specific
                 keys from bind.keys:  those for the
                 DLV zone and for the DNS root zone.  The file cannot be
                 used to store keys for other zones.
               

-

-
dnssec-must-be-secure

-

+            

+
dnssec-must-be-secure

+

+              

                 Specify hierarchies which must be or may not be secure
                 (signed and validated).  If yes,
-                then named will only accept answers if
+                then named will only accept answers if
                 they are secure.  If no, then normal
                 DNSSEC validation applies allowing for insecure answers to
                 be accepted.  The specified domain must be under a
-                trusted-keys or
-                managed-keys statement, or
-                dnssec-lookaside must be active.
-              

-
dns64

+                trusted-keys or
+                managed-keys statement, or
+                dnssec-lookaside must be active.
+              

+            
+
dns64

 

-

-                This directive instructs named to
+              

+                This directive instructs named to
                 return mapped IPv4 addresses to AAAA queries when
                 there are no AAAA records.  It is intended to be
                 used in conjunction with a NAT64.  Each
-                dns64 defines one DNS64 prefix.
+                dns64 defines one DNS64 prefix.
                 Multiple DNS64 prefixes can be defined.
               

-

+              

                 Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
                 64 and 96 as per RFC 6052.
               

-

+              

                 Additionally a reverse IP6.ARPA zone will be created for
                 the prefix to provide a mapping from the IP6.ARPA names
                 to the corresponding IN-ADDR.ARPA names using synthesized
-                CNAMEs.  dns64-server and
-                dns64-contact can be used to specify
+                CNAMEs.  dns64-server and
+                dns64-contact can be used to specify
                 the name of the server and contact for the zones. These
                 are settable at the view / options level.  These are
                 not settable on a per-prefix basis.
               

-

-                Each dns64 supports an optional
-                clients ACL that determines which
+              

+                Each dns64 supports an optional
+                clients ACL that determines which
                 clients are affected by this directive.  If not defined,
                 it defaults to any;.
               

-

-                Each dns64 supports an optional
-                mapped ACL that selects which
+              

+                Each dns64 supports an optional
+                mapped ACL that selects which
                 IPv4 addresses are to be mapped in the corresponding
                 A RRset.  If not defined it defaults to
                 any;.
               

-

+              

                 Normally, DNS64 won't apply to a domain name that
                 owns one or more AAAA records; these records will
                 simply be returned.  The optional
-                exclude ACL allows specification
+                exclude ACL allows specification
                 of a list of IPv6 addresses that will be ignored
                 if they appear in a domain name's AAAA records, and
                 DNS64 will be applied to any A records the domain
-                name owns.  If not defined, exclude
+                name owns.  If not defined, exclude
                 defaults to none.
               

-

-                A optional suffix can also
+              

+                A optional suffix can also
                 be defined to set the bits trailing the mapped
                 IPv4 address bits.  By default these bits are
                 set to ::.  The bits
                 matching the prefix and mapped IPv4 address
                 must be zero.
               

-

-                If recursive-only is set to
-                yes the DNS64 synthesis will
+              

+                If recursive-only is set to
+                yes the DNS64 synthesis will
                 only happen for recursive queries.  The default
-                is no.
+                is no.
               

-

-                If break-dnssec is set to
-                yes the DNS64 synthesis will
+              

+                If break-dnssec is set to
+                yes the DNS64 synthesis will
                 happen even if the result, if validated, would
                 cause a DNSSEC validation failure.  If this option
-                is set to no (the default), the DO
+                is set to no (the default), the DO
                 is set on the incoming query, and there are RRSIGs on
                 the applicable records, then synthesis will not happen.
               

@@ -3247,114 +3466,116 @@ options {
                 suffix ::;
         };
 

-
-
dnssec-loadkeys-interval

-

-                  When a zone is configured with auto-dnssec
+            

+
dnssec-loadkeys-interval

+

+                

+                  When a zone is configured with auto-dnssec
                   maintain; its key repository must be checked
                   periodically to see if any new keys have been added
                   or any existing keys' timing metadata has been updated
-                  (see dnssec-keygen(8) and
-                  dnssec-settime(8)).  The
-                  dnssec-loadkeys-interval option
+                  (see dnssec-keygen(8) and
+                  dnssec-settime(8)).  The
+                  dnssec-loadkeys-interval option
                   sets the frequency of automatic repository checks, in
                   minutes.  The default is 60 (1 hour),
                   the minimum is 1 (1 minute), and the
                   maximum is 1440 (24 hours); any higher
                   value is silently reduced.
-                

-
dnssec-update-mode

+                

+            
+
dnssec-update-mode

 

-

+                

                   If this option is set to its default value of
                   maintain in a zone of type
                   master which is DNSSEC-signed
                   and configured to allow dynamic updates (see
-                  the section called “Dynamic Update Policies”), and
-                  if named has access to the
+                  the section called “Dynamic Update Policies”), and
+                  if named has access to the
                   private signing key(s) for the zone, then
-                  named will automatically sign all new
+                  named will automatically sign all new
                   or changed records and maintain signatures for the zone
                   by regenerating RRSIG records whenever they approach
                   their expiration date.
                 

-

+                

                   If the option is changed to no-resign,
-                  then named will sign all new or
+                  then named will sign all new or
                   changed records, but scheduled maintenance of
                   signatures is disabled.
                 

-

-                  With either of these settings, named
+                

+                  With either of these settings, named
                   will reject updates to a DNSSEC-signed zone when the
                   signing keys are inactive or unavailable to
-                  named.  (A planned third option,
+                  named.  (A planned third option,
                   external, will disable all automatic
                   signing and allow DNSSEC data to be submitted into a zone
                   via dynamic update; this is not yet implemented.)
                 

-

-
nta-lifetime

+            
+
nta-lifetime

 

-

+                

                   Species the default lifetime, in seconds,
                   that will be used for negative trust anchors added
-                  via rndc nta.
+                  via rndc nta.
                 

-

+                

                   A negative trust anchor selectively disables
                   DNSSEC validation for zones that are known to be
                   failing because of misconfiguration rather than
                   an attack.  When data to be validated is
                   at or below an active NTA (and above any other
-                  configured trust anchors), named will
+                  configured trust anchors), named will
                   abort the DNSSEC validation process and treat the data as
                   insecure rather than bogus.  This continues until the
                   NTA's lifetime is elapsed. NTAs persist
-                  across named restarts.
+                  across named restarts.
                 

-

+                

                   For convenience, TTL-style time unit suffixes can be
                   used to specify the NTA lifetime in seconds, minutes
                   or hours.  nta-lifetime defaults to
                   one hour.  It cannot exceed one week.
                 

-

-
nta-recheck

+            
+
nta-recheck

 

-

+                

                   Species how often to check whether negative
-                  trust anchors added via rndc nta
+                  trust anchors added via rndc nta
                   are still necessary.
                 

-

+                

                   A negative trust anchor is normally used when a
                   domain has stopped validating due to operator error;
                   it temporarily disables DNSSEC validation for that
                   domain. In the interest of ensuring that DNSSEC
                   validation is turned back on as soon as possible,
-                  named will periodically send a
+                  named will periodically send a
                   query to the domain, ignoring negative trust anchors,
                   to find out whether it can now be validated.  If so,
                   the negative trust anchor is allowed to expire early.
                 

-

+                

                   Validity checks can be disabled for an individual
-                  NTA by using rndc nta -f, or
+                  NTA by using rndc nta -f, or
                   for all NTAs by setting nta-recheck
                   to zero.
                 

-

+                

                   For convenience, TTL-style time unit suffixes can be
                   used to specify the NTA recheck interval in seconds,
                   minutes or hours.  The default is five minutes.  It
                   cannot be longer than nta-lifetime
                   (which cannot be longer than a week).
                 

-

-
max-zone-ttl

+            
+
max-zone-ttl

 

-

+              

                 Specifies a maximum permissible TTL value in seconds.
                 For convenience, TTL-style time unit suffixes may be
                 used to specify the maximum value.
@@ -3365,7 +3586,7 @@ options {
                 max-zone-ttl will cause the zone to
                 be rejected.
               

-

+              

                 This is useful in DNSSEC-signed zones because when
                 rolling to a new DNSKEY, the old key needs to remain
                 available until RRSIG records have expired from
@@ -3373,73 +3594,73 @@ options {
                 that the largest TTL in the zone will be no higher
                 than the set value.
               

-

+              

                 (NOTE: Because map-format files
                 load directly into memory, this option cannot be
                 used with them.)
               

-

+              

                 The default value is unlimited.
                 A max-zone-ttl of zero is treated as
                 unlimited.
               

-

-
serial-update-method

+            
+
serial-update-method

 

-

+              

                 Zones configured for dynamic DNS may use this
                 option to set the update method that will be used for
                 the zone serial number in the SOA record.
               

-

+              

                 With the default setting of
-                serial-update-method increment;, the
+                serial-update-method increment;, the
                 SOA serial number will be incremented by one each time
                 the zone is updated.
               

-

+              

                 When set to
-                serial-update-method unixtime;, the
+                serial-update-method unixtime;, the
                 SOA serial number will be set to the number of seconds
                 since the UNIX epoch, unless the serial number is
                 already greater than or equal to that value, in which
                 case it is simply incremented by one.
               

-

+              

                 When set to
-                serial-update-method date;, the
+                serial-update-method date;, the
                 new SOA serial number will be the current date
                 in the form "YYYYMMDD", followed by two zeroes,
                 unless the existing serial number is already greater
                 than or equal to that value, in which case it is
                 incremented by one.
               

-

-
zone-statistics

+            
+
zone-statistics

 

-

+              

                 If full, the server will collect
                 statistical data on all zones (unless specifically
                 turned off on a per-zone basis by specifying
-                zone-statistics terse or
-                zone-statistics none
-                in the zone statement).
+                zone-statistics terse or
+                zone-statistics none
+                in the zone statement).
                 The default is terse, providing
                 minimal statistics on zones (including name and
                 current serial number, but not query type
                 counters).
               

-

+              

                 These statistics may be accessed via the
-                statistics-channel or
-                using rndc stats, which
+                statistics-channel or
+                using rndc stats, which
                 will dump them to the file listed
-                in the statistics-file.  See
-                also the section called “The Statistics File”.
+                in the statistics-file.  See
+                also the section called “The Statistics File”.
               

-

+              

                 For backward compatibility with earlier versions
-                of BIND 9, the zone-statistics
+                of BIND 9, the zone-statistics
                 option can also accept yes
                 or no; yes
                 has the same meaning as full.
@@ -3448,35 +3669,41 @@ options {
                 as none; previously, it
                 was the same as terse.
               

-

+            
 
-

+
+        

 

 Boolean Options

-

-
automatic-interface-scan

+          
+
+          

+
automatic-interface-scan

 

-

+                

                   If yes and supported by the OS,
                   automatically rescan network interfaces when the interface
                   addresses are added or removed.  The default is
                   yes.
                 

-

+                

                   Currently the OS needs to support routing sockets for
-                  automatic-interface-scan to be
+                  automatic-interface-scan to be
                   supported.
                 

-

-
allow-new-zones

-

+              

+
allow-new-zones

+

+                

                   If yes, then zones can be
-                  added at runtime via rndc addzone.
+                  added at runtime via rndc addzone.
                   The default is no.
-                

-
auth-nxdomain

-

-                  If yes, then the AA bit
+                

+              

+
auth-nxdomain

+

+                

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

-
deallocate-on-exit

-

+                

+              

+
deallocate-on-exit

+

+                

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

-
memstatistics

-

+                

+              

+
memstatistics

+

+                

                   Write memory statistics to the file specified by
-                  memstatistics-file at exit.
+                  memstatistics-file at exit.
                   The default is no unless
                   '-m record' is specified on the command line in
                   which case it is yes.
-                

-
dialup

+                

+              
+
dialup

 

-

+                

                   If yes, then the
                   server treats all zones as if they are doing zone transfers
                   across
@@ -3512,19 +3744,19 @@ options {
                   according
                   to zone type and concentrates the zone maintenance so that
                   it all
-                  happens in a short interval, once every heartbeat-interval and
+                  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.
                 

-

-                  The dialup option
-                  may also be specified in the view and
-                  zone statements,
-                  in which case it overrides the global dialup
+                

+                  The dialup option
+                  may also be specified in the view and
+                  zone statements,
+                  in which case it overrides the global dialup
                   option.
                 

-

+                

                   If the zone is a master zone, then the server will send out a
                   NOTIFY
                   request to all the slaves (default). This should trigger the
@@ -3534,19 +3766,19 @@ options {
                   to verify the zone while the connection is active.
                   The set of servers to which NOTIFY is sent can be controlled
                   by
-                  notify and also-notify.
+                  notify and also-notify.
                 

-

+                

                   If the
                   zone is a slave or stub zone, then the server will suppress
                   the regular
                   "zone up to date" (refresh) queries and only perform them
                   when the
-                  heartbeat-interval expires in
+                  heartbeat-interval expires in
                   addition to sending
                   NOTIFY requests.
                 

-

+                

                   Finer control can be achieved by using
                   notify which only sends NOTIFY
                   messages,
@@ -3555,18 +3787,20 @@ options {
                   suppresses the normal refresh queries, refresh
                   which suppresses normal refresh processing and sends refresh
                   queries
-                  when the heartbeat-interval
+                  when the heartbeat-interval
                   expires, and
                   passive which just disables normal
                   refresh
                   processing.
                 

-

+
+                

+                  
----++++
@@ -3593,7 +3827,7 @@ options {
 
-

 








 
 
 

 

 
-                          
no (default)

+                          
no (default)

                         		
 
                           

@@ -3613,7 +3847,7 @@ options {
 

 

 
-                          
yes

+                          
yes

                         		
 
                           

@@ -3633,7 +3867,7 @@ options {
 

 

 
-                          
notify

+                          
notify

                         		
 
                           

@@ -3653,7 +3887,7 @@ options {
 

 

 
-                          
refresh

+                          
refresh

                         		
 
                           

@@ -3673,7 +3907,7 @@ options {
 

 

 
-                          
passive

+                          
passive

                         		
 
                           

@@ -3693,7 +3927,7 @@ options {
 

 

 
-                          
notify-passive

+                          
notify-passive

                         		
 
                           

@@ -3712,21 +3946,27 @@ options {
                         

 

 

-

+
+                

+
+                

                   Note that normal NOTIFY processing is not affected by
-                  dialup.
+                  dialup.
                 

-
-
fake-iquery

-

+
+              

+
fake-iquery

+

+                

                   In BIND 8, this option
                   enabled simulating the obsolete DNS query type
                   IQUERY. BIND 9 never does
                   IQUERY simulation.
-                

-
fetch-glue

-

+                

+              

+
fetch-glue

+

+                

                   This option is obsolete.
                   In BIND 8, fetch-glue yes
                   caused the server to attempt to fetch glue resource records
@@ -3735,101 +3975,117 @@ options {
                   data section of a response.  This is now considered a bad
                   idea
                   and BIND 9 never does it.
-                

-
flush-zones-on-shutdown

-

+                

+              

+
flush-zones-on-shutdown

+

+                

                   When the nameserver exits due receiving SIGTERM,
                   flush or do not flush any pending zone writes.  The default
                   is
-                  flush-zones-on-shutdown no.
-                

-
geoip-use-ecs

-

+                  flush-zones-on-shutdown no.
+                

+              

+
geoip-use-ecs

+

+                

                   When BIND is compiled with GeoIP support and configured
                   with "geoip" ACL elements, this option indicates whether
                   the EDNS Client Subnet option, if present in a request,
                   should be used for matching against the GeoIP database.
                   The default is
-                  geoip-use-ecs yes.
-                

-
has-old-clients

-

+                  geoip-use-ecs yes.
+                

+              

+
has-old-clients

+

+                

                   This option was incorrectly implemented
                   in BIND 8, and is ignored by BIND 9.
                   To achieve the intended effect
                   of
-                  has-old-clients yes, specify
-                  the two separate options auth-nxdomain yes
-                  and rfc2308-type1 no instead.
-                

-
host-statistics

-

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

+              

+
host-statistics

+

+                

                   In BIND 8, this enables keeping of
                   statistics for every host that the name server interacts
                   with.
                   Not implemented in BIND 9.
-                

-
maintain-ixfr-base

-

+                

+              

+
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. BIND 9 maintains a transaction
                   log whenever possible.  If you need to disable outgoing
                   incremental zone
-                  transfers, use provide-ixfr no.
-                

-
minimal-responses

-

+                  transfers, use provide-ixfr no.
+                

+              

+
minimal-responses

+

+                

                   If yes, then when generating
                   responses the server will only add records to the authority
                   and additional data sections when they are required (e.g.
                   delegations, negative responses).  This may improve the
                   performance of the server.
                   The default is no.
-                

-
multiple-cnames

-

+                

+              

+
multiple-cnames

+

+                

                   This option was used in BIND 8 to allow
                   a domain name to have multiple CNAME records in violation of
                   the DNS standards.  BIND 9.2 onwards
                   always strictly enforces the CNAME rules both in master
                   files and dynamic updates.
-                

-
notify

+                

+              
+
notify

 

-

+                

                   If yes (the default),
                   DNS NOTIFY messages are sent when a zone the server is
                   authoritative for
-                  changes, see the section called “Notify”.  The messages are
+                  changes, see the section called “Notify”.  The messages are
                   sent to the
                   servers listed in the zone's NS records (except the master
                   server identified
                   in the SOA MNAME field), and to any servers listed in the
-                  also-notify option.
+                  also-notify option.
                 

-

+                

                   If master-only, notifies are only
                   sent
                   for master zones.
                   If explicit, notifies are sent only
                   to
-                  servers explicitly listed using also-notify.
+                  servers explicitly listed using also-notify.
                   If no, no notifies are sent.
                 

-

-                  The notify option may also be
-                  specified in the zone
+                

+                  The notify option may also be
+                  specified in the zone
                   statement,
-                  in which case it overrides the options notify statement.
+                  in which case it overrides the options notify statement.
                   It would only be necessary to turn off this option if it
                   caused slaves
                   to crash.
                 

-

-
notify-to-soa

-

+              

+
notify-to-soa

+

+                

                   If yes do not check the nameservers
                   in the NS RRset against the SOA MNAME.  Normally a NOTIFY
                   message is not sent to the SOA MNAME (SOA ORIGIN) as it is
@@ -3838,9 +4094,11 @@ options {
                   hidden master configurations and in that case you would
                   want the ultimate master to still send NOTIFY messages to
                   all the nameservers listed in the NS RRset.
-                

-
recursion

-

+                

+              

+
recursion

+

+                

                   If yes, and a
                   DNS query requests recursion, then the server will attempt
                   to do
@@ -3850,31 +4108,46 @@ options {
                   return a
                   referral response. The default is
                   yes.
-                  Note that setting recursion no does not prevent
+                  Note that setting recursion no does not prevent
                   clients from getting data from the server's cache; it only
                   prevents new data from being cached as an effect of client
                   queries.
                   Caching may still occur as an effect the server's internal
                   operation, such as NOTIFY address lookups.
-                  See also fetch-glue above.
-                

-
request-nsid

-

+                  See also fetch-glue above.
+                

+              

+
request-nsid

+

+                

                   If yes, then an empty EDNS(0)
                   NSID (Name Server Identifier) option is sent with all
                   queries to authoritative name servers during iterative
                   resolution. If the authoritative server returns an NSID
                   option in its response, then its contents are logged in
-                  the resolver category at level
-                  info.
+                  the resolver category at level
+                  info.
                   The default is no.
-                

-
request-sit

-

-
require-server-cookie

-

-
send-cookie

-

+                

+              

+
request-sit

+

+                

+                  This experimental option is obsolete.
+                

+              

+
require-server-cookie

+

+                

+                  Require a valid server cookie before sending a full
+                  response to a UDP request from a cookie aware client.
+                  BADCOOKIE is sent if there is a bad or no existent
+                  server cookie.
+                

+              

+
send-cookie

+

+                

                   If yes, then a COOKIE EDNS
                   option is sent along with the query.  If the
                   resolver has previously talked to the server, the
@@ -3889,29 +4162,37 @@ options {
                   response rate limiting (RRL).  Resolvers which
                   do not send a correct COOKIE option may be limited
                   to receiving smaller responses via the
-                  nocookie-udp-size option.
-                

-
nocookie-udp-size

-

+                  nocookie-udp-size option.
+                

+              

+
nocookie-udp-size

+

+                

                   Sets the maximum size of UDP responses that will be
                   sent to queries without a valid server COOKIE. A value
                   below 128 will be silently raised to 128. The default
-                  value is 4096, but the max-udp-size
+                  value is 4096, but the max-udp-size
                   option may further limit the response size.
-                

-
sit-secret

-

+                

+              

+
sit-secret

+

+                

                   This experimental option is obsolete.
-                

-
cookie-algorithm

-

+                

+              

+
cookie-algorithm

+

+                

                   Set the algorithm to be used when generating the
                   server cookie.  One of "aes", "sha1" or "sha256".
                   The default is "aes" if supported by the cryptographic
                   library or otherwise "sha256".
-                

-
cookie-secret

-

+                

+              

+
cookie-secret

+

+                

                   If set, this is a shared secret used for generating
                   and verifying Source Identity Token EDNS options
                   within an anycast cluster.  If not set, the system
@@ -3919,90 +4200,101 @@ options {
                   shared secret is encoded as a hex string and needs
                   to be 128 bits for AES128, 160 bits for SHA1 and
                   256 bits for SHA256.
-                

-
rfc2308-type1

+                

+              
+
rfc2308-type1

 

-

+                

                   Setting this to yes will
                   cause the server to send NS records along with the SOA
                   record for negative
                   answers. The default is no.
                 

-

+                

 
Note

-

+                  

                     Not yet implemented in BIND
                     9.
                   

-

-

-
use-id-pool

-

+                

+              
+
use-id-pool

+

+                

                   This option is obsolete.
                   BIND 9 always allocates query
                   IDs from a pool.
-                

-
use-ixfr

-

+                

+              

+
use-ixfr

+

+                

                   This option is obsolete.
                   If you need to disable IXFR to a particular server or
                   servers, see
-                  the information on the provide-ixfr option
-                  in the section called “server Statement Definition and
+                  the information on the provide-ixfr option
+                  in the section called “server Statement Definition and
             Usage”.
                   See also
-                  the section called “Incremental Zone Transfers (IXFR)”.
-                

-
provide-ixfr

-

+                  the section called “Incremental Zone Transfers (IXFR)”.
+                

+              

+
provide-ixfr

+

+                

                   See the description of
-                  provide-ixfr in
-                  the section called “server Statement Definition and
+                  provide-ixfr in
+                  the section called “server Statement Definition and
             Usage”.
-                

-
request-ixfr

-

+                

+              

+
request-ixfr

+

+                

                   See the description of
-                  request-ixfr in
-                  the section called “server Statement Definition and
+                  request-ixfr in
+                  the section called “server Statement Definition and
             Usage”.
-                

-
request-expire

-

+                

+              

+
request-expire

+

+                

                   See the description of
-                  request-expire in
-                  the section called “server Statement Definition and
+                  request-expire in
+                  the section called “server Statement Definition and
             Usage”.
-                

-
treat-cr-as-space

-

+                

+              

+
treat-cr-as-space

+

+                

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

+                

+              
 

-additional-from-auth, additional-from-cache
+additional-from-auth, additional-from-cache
 

 

-

+
+                

                   These options control the behavior of an authoritative
                   server when
                   answering queries which have additional data, or when
                   following CNAME
                   and DNAME chains.
                 

-

+
+                

                   When both of these options are set to yes
                   (the default) and a
                   query is being answered from authoritative data (a zone
@@ -4022,27 +4314,30 @@ options {
                   what would
                   otherwise be provided in the additional section.
                 

-

+
+                

                   For example, if a query asks for an MX record for host foo.example.com,
                   and the record found is "MX 10 mail.example.net", normally the address
                   records (A and AAAA) for mail.example.net will be provided as well,
                   if known, even though they are not in the example.com zone.
-                  Setting these options to no
+                  Setting these options to no
                   disables this behavior and makes
                   the server only search for additional data in the zone it
                   answers from.
                 

-

+
+                

                   These options are intended for use in authoritative-only
                   servers, or in authoritative-only views.  Attempts to set
-                  them to no without also
+                  them to no without also
                   specifying
-                  recursion no will cause the
+                  recursion no will cause the
                   server to
                   ignore the options and log a warning message.
                 

-

-                  Specifying additional-from-cache no actually
+
+                

+                  Specifying additional-from-cache no actually
                   disables the use of the cache not only for additional data
                   lookups
                   but also when looking up the answer.  This is usually the
@@ -4051,7 +4346,8 @@ options {
                   correctness of
                   the cached data is an issue.
                 

-

+
+                

                   When a name server is non-recursively queried for a name
                   that is not
                   below the apex of any served zone, it normally answers with
@@ -4062,34 +4358,35 @@ options {
                   upwards referral
                   comes from the cache, the server will not be able to provide
                   upwards
-                  referrals when additional-from-cache no
+                  referrals when additional-from-cache no
                   has been specified.  Instead, it will respond to such
                   queries
                   with REFUSED.  This should not cause any problems since
                   upwards referrals are not required for the resolution
                   process.
                 

-

-
match-mapped-addresses

+
+              
+
match-mapped-addresses

 

-

+                

                   If yes, then an
                   IPv4-mapped IPv6 address will match any address match
                   list entries that match the corresponding IPv4 address.
                 

-

+                

                   This option was introduced to work around a kernel quirk
                   in some operating systems that causes IPv4 TCP
                   connections, such as zone transfers, to be accepted on an
                   IPv6 socket using mapped addresses.  This caused address
                   match lists designed for IPv4 to fail to match.  However,
-                  named now solves this problem
+                  named now solves this problem
                   internally.  The use of this option is discouraged.
                 

-

-
filter-aaaa-on-v4

+              
+
filter-aaaa-on-v4

 

-

+                

                   This option is only available when
                   BIND 9 is compiled with the
                   --enable-filter-aaaa option on the
@@ -4098,26 +4395,26 @@ options {
                   to DNS clients unless they have connections to the IPv6
                   Internet.  This is not recommended unless absolutely
                   necessary.  The default is no.
-                  The filter-aaaa-on-v4 option
-                  may also be specified in view statements
-                  to override the global filter-aaaa-on-v4
+                  The filter-aaaa-on-v4 option
+                  may also be specified in view statements
+                  to override the global filter-aaaa-on-v4
                   option.
                 

-

+                

                   If yes,
-                  the DNS client is at an IPv4 address, in filter-aaaa,
+                  the DNS client is at an IPv4 address, in filter-aaaa,
                   and if the response does not include DNSSEC signatures,
                   then all AAAA records are deleted from the response.
                   This filtering applies to all responses and not only
                   authoritative responses.
                 

-

+                

                   If break-dnssec,
                   then AAAA records are deleted even when DNSSEC is enabled.
                   As suggested by the name, this makes the response not verify,
                   because the DNSSEC protocol is designed detect deletions.
                 

-

+                

                   This mechanism can erroneously cause other servers to
                   not give AAAA records to their clients.
                   A recursing server with both IPv6 and IPv4 network connections
@@ -4125,29 +4422,31 @@ options {
                   via IPv4 will be denied AAAA records even if its client is
                   using IPv6.
                 

-

+                

                   This mechanism is applied to authoritative as well as
                   non-authoritative records.
                   A client using IPv4 that is not allowed recursion can
                   erroneously be given AAAA records because the server is not
                   allowed to check for A records.
                 

-

+                

                   Some AAAA records are given to IPv4 clients in glue records.
                   IPv4 clients that are servers can then erroneously
                   answer requests for AAAA records received via IPv4.
                 

-

-
filter-aaaa-on-v6

-

-                  Identical to filter-aaaa-on-v4,
+              

+
filter-aaaa-on-v6

+

+                

+                  Identical to filter-aaaa-on-v4,
                   except it filters AAAA responses to queries from IPv6
                   clients instead of IPv4 clients.  To filter all
                   responses, set both options to yes.
-                

-
ixfr-from-differences

+                

+              
+
ixfr-from-differences

 

-

+                

                   When yes and the server loads a new
                   version of a master zone from its zone file or receives a
                   new version of a slave file via zone transfer, it will
@@ -4157,7 +4456,7 @@ options {
                   transmitted to downstream slaves as an incremental zone
                   transfer.
                 

-

+                

                   By allowing incremental zone transfers to be used for
                   non-dynamic zones, this option saves bandwidth at the
                   expense of increased CPU and memory consumption at the
@@ -4169,80 +4468,84 @@ options {
                   temporarily allocate memory to hold this complete
                   difference set.
                 

-
ixfr-from-differences
-                  also accepts master and
-                  slave at the view and options
+                
ixfr-from-differences
+                  also accepts master and
+                  slave at the view and options
                   levels which causes
-                  ixfr-from-differences to be enabled for
-                  all master or
-                  slave zones respectively.
+                  ixfr-from-differences to be enabled for
+                  all master or
+                  slave zones respectively.
                   It is off by default.
                 

-

-
multi-master

-

+              

+
multi-master

+

+                

                   This should be set when you have multiple masters for a zone
                   and the
-                  addresses refer to different machines.  If yes, named will
+                  addresses refer to different machines.  If yes, named will
                   not log
-                  when the serial number on the master is less than what named
+                  when the serial number on the master is less than what named
                   currently
                   has.  The default is no.
-                

-
auto-dnssec

+                

+              
+
auto-dnssec

 

-

+                

                   Zones configured for dynamic DNS may use this
                   option to allow varying levels of automatic DNSSEC key
                   management. There are three possible settings:
                 

-

-                  auto-dnssec allow; permits
+                

+                  auto-dnssec allow; permits
                   keys to be updated and the zone fully re-signed
-                  whenever the user issues the command rndc sign
+                  whenever the user issues the command rndc sign
                   zonename.
                 

-

-                  auto-dnssec maintain; includes the
+                

+                  auto-dnssec maintain; includes the
                   above, but also automatically adjusts the zone's DNSSEC
                   keys on schedule, according to the keys' timing metadata
-                  (see dnssec-keygen(8) and
-                  dnssec-settime(8)).  The command
-                  rndc sign
+                  (see dnssec-keygen(8) and
+                  dnssec-settime(8)).  The command
+                  rndc sign
                   zonename causes
-                  named to load keys from the key
+                  named to load keys from the key
                   repository and sign the zone with all keys that are
                   active.
-                  rndc loadkeys
+                  rndc loadkeys
                   zonename causes
-                  named to load keys from the key
+                  named to load keys from the key
                   repository and schedule key maintenance events to occur
                   in the future, but it does not sign the full zone
                   immediately.  Note: once keys have been loaded for a
                   zone the first time, the repository will be searched
                   for changes periodically, regardless of whether
-                  rndc loadkeys is used.  The recheck
+                  rndc loadkeys is used.  The recheck
                   interval is defined by
-                  dnssec-loadkeys-interval.)
+                  dnssec-loadkeys-interval.)
                 

-

-                  The default setting is auto-dnssec off.
+                

+                  The default setting is auto-dnssec off.
                 

-

-
dnssec-enable

-

+              

+
dnssec-enable

+

+                

                   This indicates whether DNSSEC-related resource
-                  records are to be returned by named.
+                  records are to be returned by named.
                   If set to no,
-                  named will not return DNSSEC-related
+                  named will not return DNSSEC-related
                   resource records unless specifically queried for.
                   The default is yes.
-                

-
dnssec-validation

+                

+              
+
dnssec-validation

 

-

-                  Enable DNSSEC validation in named.
-                  Note dnssec-enable also needs to be
+                

+                  Enable DNSSEC validation in named.
+                  Note dnssec-enable also needs to be
                   set to yes to be effective.
                   If set to no, DNSSEC validation
                   is disabled.  If set to auto,
@@ -4250,56 +4553,60 @@ options {
                   trust-anchor for the DNS root zone is used.  If set to
                   yes, DNSSEC validation is enabled,
                   but a trust anchor must be manually configured using
-                  a trusted-keys or
-                  managed-keys statement.  The default
+                  a trusted-keys or
+                  managed-keys statement.  The default
                   is yes.
                 

-

+                

 
Note

-

+                  

                     Whenever the resolver sends out queries to an
                     EDNS-compliant server, it always sets the DO bit
                     indicating it can support DNSSEC responses even if
-                    dnssec-validation is off.
+                    dnssec-validation is off.
                   

-

-

-
dnssec-accept-expired

-

+                

+              
+
dnssec-accept-expired

+

+                

                   Accept expired signatures when verifying DNSSEC signatures.
                   The default is no.
                   Setting this option to yes
-                  leaves named vulnerable to
+                  leaves named vulnerable to
                   replay attacks.
-                

-
querylog

-

-                  Specify whether query logging should be started when named
-                  starts.
-                  If querylog is not specified,
-                  then the query logging
-                  is determined by the presence of the logging category queries.
-                

-
check-names

+                

+              
+
querylog

 

-

+                

+                  Specify whether query logging should be started when named
+                  starts.
+                  If querylog is not specified,
+                  then the query logging
+                  is determined by the presence of the logging category queries.
+                

+              

+
check-names

+

+                

                   This option is used to restrict the character set and syntax
                   of
                   certain domain names in master files and/or DNS responses
                   received
                   from the network.  The default varies according to usage
                   area.  For
-                  master zones the default is fail.
-                  For slave zones the default
-                  is warn.
-                  For answers received from the network (response)
-                  the default is ignore.
+                  master zones the default is fail.
+                  For slave zones the default
+                  is warn.
+                  For answers received from the network (response)
+                  the default is ignore.
                 

-

+                

                   The rules for legal hostnames and mail domains are derived
                   from RFC 952 and RFC 821 as modified by RFC 1123.
                 

-
check-names
+                
check-names
                   applies to the owner names of A, AAAA and MX records.
                   It also applies to the domain names in the RDATA of NS, SOA,
                   MX, and SRV records.
@@ -4307,48 +4614,54 @@ options {
                   name indicated that it is a reverse lookup of a hostname
                   (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
                 

-

-
check-dup-records

-

+              

+
check-dup-records

+

+                

                   Check master zones for records that are treated as different
                   by DNSSEC but are semantically equal in plain DNS.  The
-                  default is to warn.  Other possible
-                  values are fail and
-                  ignore.
-                

-
check-mx

-

+                  default is to warn.  Other possible
+                  values are fail and
+                  ignore.
+                

+              

+
check-mx

+

+                

                   Check whether the MX record appears to refer to a IP address.
-                  The default is to warn.  Other possible
-                  values are fail and
-                  ignore.
-                

-
check-wildcard

-

+                  The default is to warn.  Other possible
+                  values are fail and
+                  ignore.
+                

+              

+
check-wildcard

+

+                

                   This option is used to check for non-terminal wildcards.
                   The use of non-terminal wildcards is almost always as a
                   result of a failure
                   to understand the wildcard matching algorithm (RFC 1034).
                   This option
-                  affects master zones.  The default (yes) is to check
+                  affects master zones.  The default (yes) is to check
                   for non-terminal wildcards and issue a warning.
-                

-
check-integrity

+                

+              
+
check-integrity

 

-

+                

                   Perform post load zone integrity checks on master
                   zones.  This checks that MX and SRV records refer
                   to address (A or AAAA) records and that glue
                   address records exist for delegated zones.  For
                   MX and SRV records only in-zone hostnames are
                   checked (for out-of-zone hostnames use
-                  named-checkzone).
+                  named-checkzone).
                   For NS records only names below top of zone are
                   checked (for out-of-zone names and glue consistency
-                  checks use named-checkzone).
-                  The default is yes.
+                  checks use named-checkzone).
+                  The default is yes.
                 

-

+                

                   The use of the SPF record for publishing Sender
                   Policy Framework is deprecated as the migration
                   from using TXT records to SPF records was abandoned.
@@ -4356,55 +4669,67 @@ options {
                   Policy Framework record exists (starts with "v=spf1")
                   if there is an SPF record. Warnings are emitted if the
                   TXT record does not exist and can be suppressed with
-                  check-spf.
+                  check-spf.
                 

-

-
check-mx-cname

-

-                  If check-integrity is set then
+              

+
check-mx-cname

+

+                

+                  If check-integrity is set then
                   fail, warn or ignore MX records that refer
-                  to CNAMES.  The default is to warn.
-                

-
check-srv-cname

-

-                  If check-integrity is set then
+                  to CNAMES.  The default is to warn.
+                

+              

+
check-srv-cname

+

+                

+                  If check-integrity is set then
                   fail, warn or ignore SRV records that refer
-                  to CNAMES.  The default is to warn.
-                

-
check-sibling

-

+                  to CNAMES.  The default is to warn.
+                

+              

+
check-sibling

+

+                

                   When performing integrity checks, also check that
-                  sibling glue exists.  The default is yes.
-                

-
check-spf

-

-                  If check-integrity is set then
+                  sibling glue exists.  The default is yes.
+                

+              

+
check-spf

+

+                

+                  If check-integrity is set then
                   check that there is a TXT Sender Policy Framework
                   record present (starts with "v=spf1") if there is an
                   SPF record present. The default is
-                  warn.
-                

-
zero-no-soa-ttl

-

+                  warn.
+                

+              

+
zero-no-soa-ttl

+

+                

                   When returning authoritative negative responses to
                   SOA queries set the TTL of the SOA record returned in
                   the authority section to zero.
-                  The default is yes.
-                

-
zero-no-soa-ttl-cache

-

+                  The default is yes.
+                

+              

+
zero-no-soa-ttl-cache

+

+                

                   When caching a negative response to a SOA query
                   set the TTL to zero.
-                  The default is no.
-                

-
update-check-ksk

+                  The default is no.
+                

+              
+
update-check-ksk

 

-

+                

                   When set to the default value of yes,
                   check the KSK bit in each key to determine how the key
                   should be used when generating RRSIGs for a secure zone.
                 

-

+                

                   Ordinarily, zone-signing keys (that is, keys without the
                   KSK bit set) are used to sign the entire zone, while
                   key-signing keys (keys with the KSK bit set) are only
@@ -4412,10 +4737,10 @@ options {
                   However, if this option is set to no,
                   then the KSK bit is ignored; KSKs are treated as if they
                   were ZSKs and are used to sign the entire zone.  This is
-                  similar to the dnssec-signzone -z
+                  similar to the dnssec-signzone -z
                   command line option.
                 

-

+                

                   When this option is set to yes, there
                   must be at least two active keys for every algorithm
                   represented in the DNSKEY RRset: at least one KSK and one
@@ -4423,62 +4748,67 @@ options {
                   this requirement is not met, this option will be ignored
                   for that algorithm.
                 

-

-
dnssec-dnskey-kskonly

+              
+
dnssec-dnskey-kskonly

 

-

-                  When this option and update-check-ksk
+                

+                  When this option and update-check-ksk
                   are both set to yes, only key-signing
                   keys (that is, keys with the KSK bit set) will be used
                   to sign the DNSKEY RRset at the zone apex.  Zone-signing
                   keys (keys without the KSK bit set) will be used to sign
                   the remainder of the zone, but not the DNSKEY RRset.
                   This is similar to the
-                  dnssec-signzone -x command line option.
+                  dnssec-signzone -x command line option.
                 

-

-                  The default is no.  If
-                  update-check-ksk is set to
+                

+                  The default is no.  If
+                  update-check-ksk is set to
                   no, this option is ignored.
                 

-

-
try-tcp-refresh

-

+              

+
try-tcp-refresh

+

+                

                   Try to refresh the zone using TCP if UDP queries fail.
                   For BIND 8 compatibility, the default is
-                  yes.
-                

-
dnssec-secure-to-insecure

+                  yes.
+                

+              
+
dnssec-secure-to-insecure

 

-

+                

                   Allow a dynamic zone to transition from secure to
                   insecure (i.e., signed to unsigned) by deleting all
-                  of the DNSKEY records.  The default is no.
-                  If set to yes, and if the DNSKEY RRset
+                  of the DNSKEY records.  The default is no.
+                  If set to yes, and if the DNSKEY RRset
                   at the zone apex is deleted, all RRSIG and NSEC records
                   will be removed from the zone as well.
                 

-

+                

                   If the zone uses NSEC3, then it is also necessary to
                   delete the NSEC3PARAM RRset from the zone apex; this will
                   cause the removal of all corresponding NSEC3 records.
                   (It is expected that this requirement will be eliminated
                   in a future release.)
                 

-

+                

                   Note that if a zone has been configured with
-                  auto-dnssec maintain and the
+                  auto-dnssec maintain and the
                   private keys remain accessible in the key repository,
                   then the zone will be automatically signed again the
-                  next time named is started.
+                  next time named is started.
                 

-

+              
 

-
-

+
+        

+
+        

 

-Forwarding

-

+Forwarding

+          
+          

             The forwarding facility can be used to create a large site-wide
             cache on a few servers, reducing traffic over links to external
             name servers. It can also be used to allow queries by servers that
@@ -4488,9 +4818,11 @@ options {
             the server is not authoritative and does not have the answer in
             its cache.
           

-

-
forward

-

+
+          

+
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
@@ -4500,173 +4832,197 @@ options {
                   the answer itself. If only is
                   specified, the
                   server will only query the forwarders.
-                

-
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 a different forward only/first behavior,
-            or not forward at all, see the section called “zone
+            or have a different forward only/first behavior,
+            or not forward at all, see the section called “zone
             Statement Grammar”.
           

-
-

+        

+
+        

 

-Dual-stack Servers

-

+Dual-stack Servers

+          
+          

             Dual-stack servers are used as servers of last resort to work
             around
             problems in reachability due the lack of support for either IPv4
             or IPv6
             on the host machine.
           

-

-
dual-stack-servers

-

+
+          

+
dual-stack-servers

+

+                

                   Specifies host names or addresses of machines with access to
                   both IPv4 and IPv6 transports. If a hostname is used, the
                   server must be able
                   to resolve the name using only the transport it has.  If the
                   machine is dual
-                  stacked, then the dual-stack-servers have no effect unless
+                  stacked, then the dual-stack-servers have no effect unless
                   access to a transport has been disabled on the command line
-                  (e.g. named -4).
-                

+                  (e.g. named -4).
+                

+              

 

-
-

+        

+
+        

 

 Access Control

-

+          
+
+          

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

-

-
allow-notify

-

+
+          

+
allow-notify

+

+                

                   Specifies which hosts are allowed to
                   notify this server, a slave, of zone changes in addition
                   to the zone masters.
-                  allow-notify may also be
+                  allow-notify may also be
                   specified in the
-                  zone statement, in which case
+                  zone statement, in which case
                   it overrides the
-                  options allow-notify
+                  options allow-notify
                   statement.  It is only meaningful
                   for a slave zone.  If not specified, the default is to
                   process notify messages
                   only from a zone's master.
-                

-
allow-query

+                

+              

+
allow-query

 

-

+                

                   Specifies which hosts are allowed to ask ordinary
-                  DNS questions. allow-query may
-                  also be specified in the zone
+                  DNS questions. allow-query may
+                  also be specified in the zone
                   statement, in which case it overrides the
-                  options allow-query statement.
+                  options allow-query statement.
                   If not specified, the default is to allow queries
                   from all hosts.
                 

-

+                

 
Note

-

-                    allow-query-cache is now
+                  

+                    allow-query-cache is now
                     used to specify access to the cache.
                   

-

-

-
allow-query-on

+                

+              
+
allow-query-on

 

-

+                

                   Specifies which local addresses can accept ordinary
                   DNS questions. This makes it possible, for instance,
                   to allow queries on internal-facing interfaces but
                   disallow them on external-facing ones, without
                   necessarily knowing the internal network's addresses.
                 

-

-                  Note that allow-query-on is only
+                

+                  Note that allow-query-on is only
                   checked for queries that are permitted by
-                  allow-query.  A query must be
+                  allow-query.  A query must be
                   allowed by both ACLs, or it will be refused.
                 

-

-                  allow-query-on may
-                  also be specified in the zone
+                

+                  allow-query-on may
+                  also be specified in the zone
                   statement, in which case it overrides the
-                  options allow-query-on statement.
+                  options allow-query-on statement.
                 

-

+                

                   If not specified, the default is to allow queries
                   on all addresses.
                 

-

+                

 
Note

-

-                    allow-query-cache is
+                  

+                    allow-query-cache is
                     used to specify access to the cache.
                   

-

-

-
allow-query-cache

-

+                

+              
+
allow-query-cache

+

+                

                   Specifies which hosts are allowed to get answers
-                  from the cache.  If allow-query-cache
-                  is not set then allow-recursion
-                  is used if set, otherwise allow-query
-                  is used if set unless recursion no; is
-                  set in which case none; is used,
-                  otherwise the default (localnets;
-                  localhost;) is used.
-                

-
allow-query-cache-on

-

+                  from the cache.  If allow-query-cache
+                  is not set then allow-recursion
+                  is used if set, otherwise allow-query
+                  is used if set unless recursion no; is
+                  set in which case none; is used,
+                  otherwise the default (localnets;
+                  localhost;) is used.
+                

+              

+
allow-query-cache-on

+

+                

                   Specifies which local addresses can give answers
                   from the cache.  If not specified, the default is
                   to allow cache queries on any address,
-                  localnets and
-                  localhost.
-                

-
allow-recursion

-

+                  localnets and
+                  localhost.
+                

+              

+
allow-recursion

+

+                

                   Specifies which hosts are allowed to make recursive
                   queries through this server. If
-                  allow-recursion is not set
-                  then allow-query-cache is
-                  used if set, otherwise allow-query
+                  allow-recursion is not set
+                  then allow-query-cache is
+                  used if set, otherwise allow-query
                   is used if set, otherwise the default
-                  (localnets;
-                  localhost;) is used.
-                

-
allow-recursion-on

-

+                  (localnets;
+                  localhost;) is used.
+                

+              

+
allow-recursion-on

+

+                

                   Specifies which local addresses can accept recursive
                   queries.  If not specified, the default is to allow
                   recursive queries on all addresses.
-                

-
allow-update

-

+                

+              

+
allow-update

+

+                

                   Specifies which hosts are allowed to
                   submit Dynamic DNS updates for master zones. The default is
                   to deny
                   updates from all hosts.  Note that allowing updates based
                   on the requestor's IP address is insecure; see
-                  the section called “Dynamic Update Security” for details.
-                

-
allow-update-forwarding

+                  the section called “Dynamic Update Security” for details.
+                

+              
+
allow-update-forwarding

 

-

+                

                   Specifies which hosts are allowed to
                   submit Dynamic DNS updates to slave zones to be forwarded to
                   the
@@ -4683,17 +5039,18 @@ options {
                   with the
                   master server, not the slaves.
                 

-

+                

                   Note that enabling the update forwarding feature on a slave
                   server
                   may expose master servers relying on insecure IP address
                   based
-                  access control to attacks; see the section called “Dynamic Update Security”
+                  access control to attacks; see the section called “Dynamic Update Security”
                   for more details.
                 

-

-
allow-v6-synthesis

-

+              

+
allow-v6-synthesis

+

+                

                   This option was introduced for the smooth transition from
                   AAAA
                   to A6 and from "nibble labels" to binary labels.
@@ -4701,58 +5058,67 @@ options {
                   deprecated,
                   this option was also deprecated.
                   It is now ignored with some warning messages.
-                

-
allow-transfer

-

+                

+              

+
allow-transfer

+

+                

                   Specifies which hosts are allowed to
-                  receive zone transfers from the server. allow-transfer may
-                  also be specified in the zone
+                  receive zone transfers from the server. allow-transfer may
+                  also be specified in the zone
                   statement, in which
-                  case it overrides the options allow-transfer statement.
+                  case it overrides the options allow-transfer statement.
                   If not specified, the default is to allow transfers to all
                   hosts.
-                

-
blackhole

-

+                

+              

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

-
filter-aaaa

-

+                

+              

+
filter-aaaa

+

+                

                   Specifies a list of addresses to which
-                  filter-aaaa-on-v4
+                  filter-aaaa-on-v4
                   is applies.  The default is any.
-                

-
keep-response-order

-

+                

+              

+
keep-response-order

+

+                

                   Specifies a list of addresses to which the server
                   will send responses to TCP queries in the same order
                   in which they were received.  This disables the
                   processing of TCP queries in parallel. The default
                   is none.
-                

-
no-case-compress

+                

+              
+
no-case-compress

 

-

+                

                   Specifies a list of addresses which require responses
                   to use case-insensitive compression.  This ACL can be
-                  used when named needs to work with
+                  used when named needs to work with
                   clients that do not comply with the requirement in RFC
                   1034 to use case-insensitive name comparisons when
                   checking for matching domain names.
                 

-

+                

                   If left undefined, the ACL defaults to
-                  none: case-insensitive compression
+                  none: case-insensitive compression
                   will be used for all clients.  If the ACL is defined and
                   matches a client, then case will be ignored when
                   compressing domain names in DNS responses sent to that
                   client.
                 

-

+                

                   This can result in slightly smaller responses: if
                   a response contains the names "example.com" and
                   "example.COM", case-insensitive compression would treat
@@ -4764,13 +5130,13 @@ options {
                   match the query, which is required by some clients
                   due to incorrect use of case-sensitive comparisons.
                 

-

+                

                   Case-insensitive compression is always
                   used in AXFR and IXFR responses, regardless of whether
                   the client matches this ACL.
                 

-

-                  There are circumstances in which named
+                

+                  There are circumstances in which named
                   will not preserve the case of owner names of records:
                   if a zone file defines records of different types with
                   the same name, but the capitalization of the name is
@@ -4784,9 +5150,10 @@ options {
                   have their case preserved unless the client matches this
                   ACL.
                 

-

-
resolver-query-timeout

-

+              

+
resolver-query-timeout

+

+                

                   The amount of time in seconds that the resolver
                   will spend attempting to resolve a recursive
                   query before failing.  The default and minimum
@@ -4794,51 +5161,60 @@ options {
                   30.  Setting it to
                   0 will result in the default
                   being used.
-                

+                

+              
 
-
-

+
+        

+
+        

 

-Interfaces

-

+Interfaces

+          
+          

             The interfaces and ports that the server will answer queries
-            from may be specified using the listen-on option. listen-on takes
+            from may be specified using the listen-on option. listen-on takes
             an optional port and an address_match_list
             of IPv4 addresses.  (IPv6 addresses are ignored, with a
             logged warning.)
             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
+          

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

-

+
+          

             will enable the name server 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
+
+          

+            If no listen-on is specified, the
             server will listen on port 53 on all IPv4 interfaces.
           

-

-            The listen-on-v6 option is used to
+
+          

+            The listen-on-v6 option is used to
             specify the interfaces and the ports on which the server will
             listen for incoming queries sent using IPv6.  If not specified,
             the server will listen on port 53 on all IPv6 interfaces.
           

-

+
+          

             When 

 
{ any; }

 
 is
             specified
             as the address_match_list for the
-            listen-on-v6 option,
+            listen-on-v6 option,
             the server does not bind a separate socket to each IPv6 interface
             address as it does for IPv4 if the operating system has enough API
             support for IPv6 (specifically if it conforms to RFC 3493 and RFC
@@ -4847,100 +5223,116 @@ listen-on port 1234 { !1.2.3.4; 1.2/16; };
             If the system only has incomplete API support for IPv6, however,
             the behavior is the same as that for IPv4.
           

-

+
+          

             A list of particular IPv6 addresses can also be specified, in
             which case
             the server listens on a separate socket for each specified
             address,
             regardless of whether the desired API is supported by the system.
-            IPv4 addresses specified in listen-on-v6
+            IPv4 addresses specified in listen-on-v6
             will be ignored, with a logged warning.
           

-

-            Multiple listen-on-v6 options can
+
+          

+            Multiple listen-on-v6 options can
             be used.
             For example,
           

+
 
listen-on-v6 { any; };
 listen-on-v6 port 1234 { !2001:db8::/32; any; };
 

-

+
+          

             will enable the name server on port 53 for any IPv6 addresses
             (with a single wildcard socket),
             and on port 1234 of IPv6 addresses that is not in the prefix
             2001:db8::/32 (with separate sockets for each matched address.)
           

-

+
+          

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

+
 
listen-on-v6 { none; };
 

-
-

+
+        

+
+        

 

 Query Address

-

+          
+          

             If the server doesn't know the answer to a question, it will
-            query other name servers. query-source specifies
+            query other name servers. query-source specifies
             the address and port used for such queries. For queries sent over
-            IPv6, there is a separate query-source-v6 option.
-            If address is * (asterisk) or is omitted,
-            a wildcard IP address (INADDR_ANY)
+            IPv6, there is a separate query-source-v6 option.
+            If address is * (asterisk) or is omitted,
+            a wildcard IP address (INADDR_ANY)
             will be used.
           

-

-            If port is * or is omitted,
+
+          

+            If port is * or is omitted,
             a random port number from a pre-configured
             range is picked up and will be used for each query.
             The port range(s) is that specified in
-            the use-v4-udp-ports (for IPv4)
-            and use-v6-udp-ports (for IPv6)
+            the use-v4-udp-ports (for IPv4)
+            and use-v6-udp-ports (for IPv6)
             options, excluding the ranges specified in
-            the avoid-v4-udp-ports
-            and avoid-v6-udp-ports options, respectively.
+            the avoid-v4-udp-ports
+            and avoid-v6-udp-ports options, respectively.
           

-

-            The defaults of the query-source and
-            query-source-v6 options
+
+          

+            The defaults of the query-source and
+            query-source-v6 options
             are:
           

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

-

-            If use-v4-udp-ports or
-            use-v6-udp-ports is unspecified,
-            named will check if the operating
+
+          

+            If use-v4-udp-ports or
+            use-v6-udp-ports is unspecified,
+            named will check if the operating
             system provides a programming interface to retrieve the
             system's default range for ephemeral ports.
             If such an interface is available,
-            named will use the corresponding system
+            named will use the corresponding system
             default range; otherwise, it will use its own defaults:
          

+
 
use-v4-udp-ports { range 1024 65535; };
 use-v6-udp-ports { range 1024 65535; };
 

-

+
+          

             Note: make sure the ranges be sufficiently large for
             security.  A desirable size depends on various parameters,
             but we generally recommend it contain at least 16384 ports
             (14 bits of entropy).
             Note also that the system's default range when used may be
             too small for this purpose, and that the range may even be
-            changed while named is running; the new
-            range will automatically be applied when named
+            changed while named is running; the new
+            range will automatically be applied when named
             is reloaded.
             It is encouraged to
-            configure use-v4-udp-ports and
-            use-v6-udp-ports explicitly so that the
+            configure use-v4-udp-ports and
+            use-v6-udp-ports explicitly so that the
             ranges are sufficiently large and are reasonably
             independent from the ranges used by other applications.
           

-

+
+          

             Note: the operational configuration
-            where named runs may prohibit the use
+            where named runs may prohibit the use
             of some ports.  For example, UNIX systems will not allow
-            named running without a root privilege
+            named running without a root privilege
             to use ports less than 1024.
             If such ports are included in the specified (or detected)
             set of query ports, the corresponding query attempts will
@@ -4948,77 +5340,90 @@ use-v6-udp-ports { range 1024 65535; };
             It is therefore important to configure the set of ports
             that can be safely used in the expected operational environment.
           

-

-            The defaults of the avoid-v4-udp-ports and
-            avoid-v6-udp-ports options
+
+          

+            The defaults of the avoid-v4-udp-ports and
+            avoid-v6-udp-ports options
             are:
           

+
 
avoid-v4-udp-ports {};
 avoid-v6-udp-ports {};
 

-

+
+          

             Note: BIND 9.5.0 introduced
-            the use-queryport-pool
+            the use-queryport-pool
             option to support a pool of such random ports, but this
             option is now obsolete because reusing the same ports in
             the pool may not be sufficiently secure.
             For the same reason, it is generally strongly discouraged to
             specify a particular port for the
-            query-source or
-            query-source-v6 options;
+            query-source or
+            query-source-v6 options;
             it implicitly disables the use of randomized port numbers.
           

-

-
use-queryport-pool

-

+
+          

+
use-queryport-pool

+

+                

                   This option is obsolete.
-                

-
queryport-pool-ports

-

+                

+              

+
queryport-pool-ports

+

+                

                   This option is obsolete.
-                

-
queryport-pool-updateinterval

-

+                

+              

+
queryport-pool-updateinterval

+

+                

                   This option is obsolete.
-                

+                

+              

 

-

+          

 
Note

-

-              The address specified in the query-source option
+            

+              The address specified in the query-source option
               is used for both UDP and TCP queries, but the port applies only
               to UDP queries.  TCP queries always use a random
               unprivileged port.
             

-

-

+          

+          

 
Note

-

+            

               Solaris 2.5.1 and earlier does not support setting the source
               address for TCP sockets.
             

-

-

+          

+          

 
Note

-

-              See also transfer-source and
-              notify-source.
+            

+              See also transfer-source and
+              notify-source.
             

-

-

-

+          

+        

+
+        

 

 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.
           

-

-
also-notify

+
+          

+
also-notify

 

-

+                

                   Defines a global list of IP addresses of name servers
                   that are also sent NOTIFY messages whenever a fresh copy of
                   the
@@ -5027,59 +5432,68 @@ avoid-v6-udp-ports {};
                   This helps to ensure that copies of the zones will
                   quickly converge on stealth servers.
                   Optionally, a port may be specified with each
-                  also-notify address to send
+                  also-notify address to send
                   the notify messages to a port other than the
                   default of 53.
                   An optional TSIG key can also be specified with each
                   address to cause the notify messages to be signed; this
                   can be useful when sending notifies to multiple views.
                   In place of explicit addresses, one or more named
-                  masters lists can be used.
+                  masters lists can be used.
                 

-

-                  If an also-notify list
-                  is given in a zone statement,
+                

+                  If an also-notify list
+                  is given in a zone statement,
                   it will override
-                  the options also-notify
-                  statement. When a zone notify
+                  the options also-notify
+                  statement. When a zone notify
                   statement
-                  is set to no, the IP
-                  addresses in the global also-notify list will
+                  is set to no, the IP
+                  addresses in the global also-notify list will
                   not be sent NOTIFY messages for that zone. The default is
                   the empty
                   list (no global notification list).
                 

-

-
max-transfer-time-in

-

+              

+
max-transfer-time-in

+

+                

                   Inbound zone transfers running longer than
                   this many minutes will be terminated. The default is 120
                   minutes
                   (2 hours).  The maximum value is 28 days (40320 minutes).
-                

-
max-transfer-idle-in

-

+                

+              

+
max-transfer-idle-in

+

+                

                   Inbound zone transfers making no progress
                   in this many minutes will be terminated. The default is 60
                   minutes
                   (1 hour).  The maximum value is 28 days (40320 minutes).
-                

-
max-transfer-time-out

-

+                

+              

+
max-transfer-time-out

+

+                

                   Outbound zone transfers running longer than
                   this many minutes will be terminated. The default is 120
                   minutes
                   (2 hours).  The maximum value is 28 days (40320 minutes).
-                

-
max-transfer-idle-out

-

+                

+              

+
max-transfer-idle-out

+

+                

                   Outbound zone transfers making no progress
                   in this many minutes will be terminated.  The default is 60
                   minutes (1
                   hour).  The maximum value is 28 days (40320 minutes).
-                

-
notify-rate

-

+                

+              

+
notify-rate

+

+                

                   The rate at which NOTIFY requests will be sent
                   during normal zone maintenance operations. (NOTIFY
                   requests due to initial zone loading are subject
@@ -5087,96 +5501,113 @@ avoid-v6-udp-ports {};
                   20 per second.
                   The lowest possible rate is one per second; when set
                   to zero, it will be silently raised to one.
-                

-
startup-notify-rate

-

+                

+              

+
startup-notify-rate

+

+                

                   The rate at which NOTIFY requests will be sent
                   when the name server is first starting up, or when
                   zones have been newly added to the nameserver.
                   The default is 20 per second.
                   The lowest possible rate is one per second; when set
                   to zero, it will be silently raised to one.
-                

-
serial-query-rate

-

+                

+              

+
serial-query-rate

+

+                

                   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.  To limit
                   the amount of bandwidth used, BIND 9 limits the
                   rate at which queries are sent.  The value of the
-                  serial-query-rate option, an
+                  serial-query-rate option, an
                   integer, is the maximum number of queries sent
                   per second.  The default is 20 per second.
                   The lowest possible rate is one per second; when set
                   to zero, it will be silently raised to one.
-                

-
serial-queries

-

-                  In BIND 8, the serial-queries
+                

+              

+
serial-queries

+

+                

+                  In BIND 8, the serial-queries
                   option
                   set the maximum number of concurrent serial number queries
                   allowed to be outstanding at any given time.
                   BIND 9 does not limit the number of outstanding
-                  serial queries and ignores the serial-queries option.
+                  serial queries and ignores the serial-queries option.
                   Instead, it limits the rate at which the queries are sent
-                  as defined using the serial-query-rate option.
-                

-
transfer-format

-

+                  as defined using the serial-query-rate option.
+                

+              

+
transfer-format

+

+
+                

                   Zone transfers can be sent using two different formats,
-                  one-answer and
-                  many-answers.
-                  The transfer-format option is used
+                  one-answer and
+                  many-answers.
+                  The transfer-format option is used
                   on the master server to determine which format it sends.
-                  one-answer uses one DNS message per
+                  one-answer uses one DNS message per
                   resource record transferred.
-                  many-answers packs as many resource
+                  many-answers packs as many resource
                   records as possible into a message.
-                  many-answers is more efficient, but is
+                  many-answers is more efficient, but is
                   only supported by relatively new slave servers,
                   such as BIND 9, BIND
                   8.x and BIND 4.9.5 onwards.
-                  The many-answers format is also supported by
+                  The many-answers format is also supported by
                   recent Microsoft Windows nameservers.
-                  The default is many-answers.
-                  transfer-format may be overridden on a
-                  per-server basis by using the server
+                  The default is many-answers.
+                  transfer-format may be overridden on a
+                  per-server basis by using the server
                   statement.
-                

-
transfers-in

-

+                

+
+              

+
transfers-in

+

+                

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

-
transfers-out

-

+                

+              

+
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

-

+                

+              

+
transfers-per-ns

+

+                

                   The maximum number of inbound zone transfers
                   that can be concurrently transferring from a given remote
                   name server.
                   The default value is 2.
-                  Increasing transfers-per-ns
+                  Increasing transfers-per-ns
                   may
                   speed up the convergence of slave zones, but it also may
                   increase
-                  the load on the remote name server. transfers-per-ns may
-                  be overridden on a per-server basis by using the transfers phrase
-                  of the server statement.
-                

-
transfer-source

+                  the load on the remote name server. transfers-per-ns may
+                  be overridden on a per-server basis by using the transfers phrase
+                  of the server statement.
+                

+              
+
transfer-source

 

-
transfer-source
+                
transfer-source
                   determines which local address will be bound to IPv4
                   TCP connections used to fetch zones transferred
                   inbound by the server.  It also determines the
@@ -5186,122 +5617,136 @@ avoid-v6-udp-ports {};
                   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
+                  allow-transfer option for the
                   zone being transferred, if one is specified. This
                   statement sets the
-                  transfer-source for all zones,
+                  transfer-source for all zones,
                   but can be overridden on a per-view or per-zone
                   basis by including a
-                  transfer-source statement within
-                  the view or
-                  zone block in the configuration
+                  transfer-source statement within
+                  the view or
+                  zone block in the configuration
                   file.
                 

-

+                

 
Note

-

+                  

                     Solaris 2.5.1 and earlier does not support setting the
                     source address for TCP sockets.
                   

-

-

-
transfer-source-v6

-

-                  The same as transfer-source,
-                  except zone transfers are performed using IPv6.
-                

-
alt-transfer-source

+                

+              
+
transfer-source-v6

 

-

+                

+                  The same as transfer-source,
+                  except zone transfers are performed using IPv6.
+                

+              

+
alt-transfer-source

+

+                

                   An alternate transfer source if the one listed in
-                  transfer-source fails and
-                  use-alt-transfer-source is
+                  transfer-source fails and
+                  use-alt-transfer-source is
                   set.
                 

-

+                

 
Note

                   If you do not wish the alternate transfer source
                   to be used, you should set
-                  use-alt-transfer-source
+                  use-alt-transfer-source
                   appropriately and you should not depend upon
                   getting an answer back to the first refresh
                   query.
                 

-

-
alt-transfer-source-v6

-

-                  An alternate transfer source if the one listed in
-                  transfer-source-v6 fails and
-                  use-alt-transfer-source is
-                  set.
-                

-
use-alt-transfer-source

-

-                  Use the alternate transfer sources or not.  If views are
-                  specified this defaults to no
-                  otherwise it defaults to
-                  yes (for BIND 8
-                  compatibility).
-                

-
notify-source

+              
+
alt-transfer-source-v6

 

-
notify-source
+                

+                  An alternate transfer source if the one listed in
+                  transfer-source-v6 fails and
+                  use-alt-transfer-source is
+                  set.
+                

+              

+
use-alt-transfer-source

+

+                

+                  Use the alternate transfer sources or not.  If views are
+                  specified this defaults to no
+                  otherwise it defaults to
+                  yes (for BIND 8
+                  compatibility).
+                

+              

+
notify-source

+

+                
notify-source
                   determines which local source address, and
                   optionally UDP port, will be used to send NOTIFY
                   messages.  This address must appear in the slave
-                  server's masters zone clause or
-                  in an allow-notify clause.  This
-                  statement sets the notify-source
+                  server's masters zone clause or
+                  in an allow-notify clause.  This
+                  statement sets the notify-source
                   for all zones, but can be overridden on a per-zone or
                   per-view basis by including a
-                  notify-source statement within
-                  the zone or
-                  view block in the configuration
+                  notify-source statement within
+                  the zone or
+                  view block in the configuration
                   file.
                 

-

+                

 
Note

-

+                  

                     Solaris 2.5.1 and earlier does not support setting the
                     source address for TCP sockets.
                   

-

-

-
notify-source-v6

-

-                  Like notify-source,
+                

+              
+
notify-source-v6

+

+                

+                  Like notify-source,
                   but applies to notify messages sent to IPv6 addresses.
-                

+                

+              
 

-
-

+
+        

+
+        

 

-UDP Port Lists

-

-            use-v4-udp-ports,
-            avoid-v4-udp-ports,
-            use-v6-udp-ports, and
-            avoid-v6-udp-ports
+UDP Port Lists

+          
+          

+            use-v4-udp-ports,
+            avoid-v4-udp-ports,
+            use-v6-udp-ports, and
+            avoid-v6-udp-ports
             specify a list of IPv4 and IPv6 UDP ports that will be
             used or not used as source ports for UDP messages.
-            See the section called “Query Address” about how the
+            See the section called “Query Address” about how the
             available ports are determined.
             For example, with the following configuration
           

+
 
 use-v6-udp-ports { range 32768 65535; };
 avoid-v6-udp-ports { 40000; range 50000 60000; };
 

-

+
+           

              UDP ports of IPv6 messages sent
-             from named will be in one
+             from named will be in one
              of the following ranges: 32768 to 39999, 40001 to 49999,
              and 60001 to 65535.
            

-

-             avoid-v4-udp-ports and
-             avoid-v6-udp-ports can be used
-             to prevent named from choosing as its random source port a
+
+           

+             avoid-v4-udp-ports and
+             avoid-v6-udp-ports can be used
+             to prevent named from choosing as its random source port a
              port that is blocked by your firewall or a port that is
              used by other applications;
              if a query went out with a source port blocked by a
@@ -5309,30 +5754,34 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
              answer would not get by the firewall and the name server would
              have to query again.
              Note: the desired range can also be represented only with
-             use-v4-udp-ports and
-             use-v6-udp-ports, and the
-             avoid- options are redundant in that
+             use-v4-udp-ports and
+             use-v6-udp-ports, and the
+             avoid- options are redundant in that
              sense; they are provided for backward compatibility and
              to possibly simplify the port specification.
            

-
-

+        

+
+        

 

-Operating System Resource Limits

-

+Operating System Resource Limits

+          
+
+          

             The server's usage of many system resources can be limited.
             Scaled values are allowed when specifying resource limits.  For
-            example, 1G can be used instead of
-            1073741824 to specify a limit of
+            example, 1G can be used instead of
+            1073741824 to specify a limit of
             one
-            gigabyte. unlimited requests
+            gigabyte. unlimited requests
             unlimited use, or the
-            maximum available amount. default
+            maximum available amount. default
             uses the limit
             that was in force when the server was started. See the description
-            of size_spec in the section called “Configuration File Elements”.
+            of size_spec in the section called “Configuration File Elements”.
           

-

+
+          

             The following options set operating system resource limits for
             the name server process.  Some operating systems don't support
             some or
@@ -5340,14 +5789,18 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             the
             unsupported limit is used.
           

-

-
coresize

-

+
+          

+
coresize

+

+                

                   The maximum size of a core dump. The default
                   is default.
-                

-
datasize

-

+                

+              

+
datasize

+

+                

                   The maximum amount of data memory the server
                   may use. The default is default.
                   This is a hard limit on server memory usage.
@@ -5359,42 +5812,55 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   to raise an operating system data size limit that is
                   too small by default.  If you wish to limit the amount
                   of memory used by the server, use the
-                  max-cache-size and
-                  recursive-clients
+                  max-cache-size and
+                  recursive-clients
                   options instead.
-                

-
files

-

+                

+              

+
files

+

+                

                   The maximum number of files the server
                   may have open concurrently. The default is unlimited.
-                

-
stacksize

-

+                

+              

+
stacksize

+

+                

                   The maximum amount of stack memory the server
                   may use. The default is default.
-                

+                

+              

 

-
-

+
+        

+
+        

 

 Server  Resource Limits

-

+          
+
+          

             The following options set limits on the server's
             resource consumption that are enforced internally by the
             server rather than the operating system.
           

-

-
max-ixfr-log-size

-

+
+          

+
max-ixfr-log-size

+

+                

                   This option is obsolete; it is accepted
                   and ignored for BIND 8 compatibility.  The option
-                  max-journal-size performs a
+                  max-journal-size performs a
                   similar function in BIND 9.
-                

-
max-journal-size

-

+                

+              

+
max-journal-size

+

+                

                   Sets a maximum size for each journal file
-                  (see the section called “The journal file”).  When the journal file
+                  (see the section called “The journal file”).  When the journal file
                   approaches
                   the specified size, some of the oldest transactions in the
                   journal
@@ -5403,16 +5869,19 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   unlimited, which also
                   means 2 gigabytes.
                   This may also be set on a per-zone basis.
-                

-
host-statistics-max

-

+                

+              

+
host-statistics-max

+

+                

                   In BIND 8, specifies the maximum number of host statistics
                   entries to be kept.
                   Not implemented in BIND 9.
-                

-
recursive-clients

+                

+              

+
recursive-clients

 

-

+                

                   The maximum number ("hard quota") of simultaneous
                   recursive lookups the server will perform on behalf
                   of clients.  The default is
@@ -5420,17 +5889,17 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   client uses a fair
                   bit of memory (on the order of 20 kilobytes), the
                   value of the
-                  recursive-clients option may
+                  recursive-clients option may
                   have to be decreased on hosts with limited memory.
                 

-

+                

                   recursive-clients defines a "hard
                   quota" limit for pending recursive clients: when more
                   clients than this are pending, new incoming requests
                   will not be accepted, and for each incoming request
                   a previous pending request will also be dropped.
                 

-

+                

                   A "soft quota" is also set.  When this lower
                   quota is exceeded, incoming requests are accepted, but
                   for each one, a pending request will be dropped.
@@ -5440,51 +5909,53 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   otherwise it is set to 90% of
                   recursive-clients.
                 

-

-
tcp-clients

-

+              

+
tcp-clients

+

+                

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

+                

+              
 

-clients-per-query, max-clients-per-query
+clients-per-query, max-clients-per-query
 

 

-
These set the
+                
These set the
                   initial value (minimum) and maximum number of recursive
                   simultaneous clients for any given query
                   (<qname,qtype,qclass>) that the server will accept
-                  before dropping additional clients.  named will attempt to
+                  before dropping additional clients.  named will attempt to
                   self tune this value and changes will be logged.  The
                   default values are 10 and 100.
                 

-

+                

                   This value should reflect how many queries come in for
                   a given name in the time it takes to resolve that name.
-                  If the number of queries exceed this value, named will
+                  If the number of queries exceed this value, named will
                   assume that it is dealing with a non-responsive zone
                   and will drop additional queries.  If it gets a response
                   after dropping queries, it will raise the estimate.  The
                   estimate will then be lowered in 20 minutes if it has
                   remained unchanged.
                 

-

-                  If clients-per-query is set to zero,
+                

+                  If clients-per-query is set to zero,
                   then there is no limit on the number of clients per query
                   and no queries will be dropped.
                 

-

-                  If max-clients-per-query is set to zero,
+                

+                  If max-clients-per-query is set to zero,
                   then there is no upper bound other than imposed by
-                  recursive-clients.
+                  recursive-clients.
                 

-

+              
 

-fetches-per-zone
+fetches-per-zone
 

 

-

+                

                   The maximum number of simultaneous iterative
                   queries to any one domain that the server will
                   permit before blocking new queries for data
@@ -5494,7 +5965,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   would take to resolve them.  It should be smaller
                   than recursive-clients.
                 

-

+                

                   When many clients simultaneously query for the
                   same name and type, the clients will all be attached
                   to the same fetch, up to the
@@ -5506,7 +5977,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   max-clients-per-query is not
                   effective as a limit.
                 

-

+                

                   Optionally, this value may be followed by the keyword
                   drop or fail,
                   indicating whether queries which exceed the fetch
@@ -5514,14 +5985,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   or answered with SERVFAIL.  The default is
                   drop.
                 

-

-                  If fetches-per-zone is set to zero,
+                

+                  If fetches-per-zone is set to zero,
                   then there is no limit on the number of fetches per query
                   and no queries will be dropped.  The default is zero.
                 

-

+                

                   The current list of active fetches can be dumped by
-                  running rndc recursing.  The list
+                  running rndc recursing.  The list
                   includes the number of active fetches for each
                   domain and the number of queries that have been
                   passed or dropped as a result of the
@@ -5532,12 +6003,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   next time a fetch is sent to that domain, it is
                   recreated with the counters set to zero.)
                 

-

+              
 

-fetches-per-server
+fetches-per-server
 

 

-

+                

                   The maximum number of simultaneous iterative
                   queries that the server will allow to be sent to
                   a single upstream name server before blocking
@@ -5547,7 +6018,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   would take to resolve them.  It should be smaller
                   than recursive-clients.
                 

-

+                

                   Optionally, this value may be followed by the keyword
                   drop or fail,
                   indicating whether queries will be dropped with no
@@ -5556,36 +6027,36 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   exceeded the per-server quota.  The default is
                   fail.
                 

-

-                  If fetches-per-server is set to zero,
+                

+                  If fetches-per-server is set to zero,
                   then there is no limit on the number of fetches per query
                   and no queries will be dropped.  The default is zero.
                 

-

-                  The fetches-per-server quota is
+                

+                  The fetches-per-server quota is
                   dynamically adjusted in response to detected
                   congestion. As queries are sent to a server
                   and are either answered or time out, an
                   exponentially weighted moving average is calculated
                   of the ratio of timeouts to responses.  If the
                   current average timeout ratio rises above a "high"
-                  threshold, then fetches-per-server
+                  threshold, then fetches-per-server
                   is reduced for that server.  If the timeout ratio
                   drops below a "low" threshold, then
-                  fetches-per-server is increased.
-                  The fetch-quota-params options
+                  fetches-per-server is increased.
+                  The fetch-quota-params options
                   can be used to adjust the parameters for this
                   calculation.
                 

-

-
fetch-quota-params

+              
+
fetch-quota-params

 

-

+                

                   Sets the parameters to use for dynamic resizing of
                   the fetches-per-server quota in
                   response to detected congestion.
                 

-

+                

                   The first argument is an integer value indicating
                   how frequently to recalculate the moving average
                   of the ratio of timeouts to responses for each
@@ -5593,7 +6064,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   the average ratio after every 100 queries have either
                   been answered or timed out.
                 

-

+                

                   The remaining three arguments represent the "low"
                   threshold (defaulting to a timeout ratio of 0.1),
                   the "high" threshold (defaulting to a timeout
@@ -5608,25 +6079,26 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   precision of 1/100: at most two places after
                   the decimal point are significant.
                 

-

-
reserved-sockets

+              
+
reserved-sockets

 

-

+                

                   The number of file descriptors reserved for TCP, stdio,
                   etc.  This needs to be big enough to cover the number of
-                  interfaces named listens on, tcp-clients as well as
+                  interfaces named listens on, tcp-clients as well as
                   to provide room for outgoing TCP queries and incoming zone
                   transfers.  The default is 512.
                   The minimum value is 128 and the
                   maximum value is 128 less than
                   maxsockets (-S).  This option may be removed in the future.
                 

-

+                

                   This option has little effect on Windows.
                 

-

-
max-cache-size

-

+              

+
max-cache-size

+

+                

                   The maximum amount of memory to use for the
                   server's cache, in bytes or % of total physical memory.
                   When the amount of data in the cache
@@ -5646,12 +6118,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   memory is not supported values represented as %
                   fall back to unlimited.
                   Note that the detection of physical memory is done only
-                  once at startup, so named will not
+                  once at startup, so named will not
                   adjust the cache size if the amount of physical memory
                   is changed during runtime.
-                

-
tcp-listen-queue

-

+                

+              

+
tcp-listen-queue

+

+                

                   The listen queue depth.  The default and minimum is 10.
                   If the kernel supports the accept filter "dataready" this
                   also controls how
@@ -5661,38 +6135,48 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   less than 10 will be silently raised. A value of 0 may also
                   be used; on most platforms this sets the listen queue
                   length to a system-defined default value.
-                

+                

+              
 

-

-

+
+        

+
+        

 

-Periodic Task Intervals

-

-
cleaning-interval

-

+Periodic Task Intervals

+          
+
+          

+
cleaning-interval

+

+                

                   This interval is effectively obsolete.  Previously,
                   the server would remove expired resource records
-                  from the cache every cleaning-interval minutes.
+                  from the cache every cleaning-interval minutes.
                   BIND 9 now manages cache
                   memory in a more sophisticated manner and does not
                   rely on the periodic cleaning any more.
                   Specifying this option therefore has no effect on
                   the server's behavior.
-                

-
heartbeat-interval

-

+                

+              

+
heartbeat-interval

+

+                

                   The server will perform zone maintenance tasks
-                  for all zones marked as dialup whenever this
+                  for all zones marked as dialup whenever this
                   interval expires. The default is 60 minutes. Reasonable
                   values are up
                   to 1 day (1440 minutes).  The maximum value is 28 days
                   (40320 minutes).
                   If set to 0, no zone maintenance for these zones will occur.
-                

-
interface-interval

-

+                

+              

+
interface-interval

+

+                

                   The server will scan the network interface list
-                  every interface-interval
+                  every interface-interval
                   minutes. The default
                   is 60 minutes. The maximum value is 28 days (40320 minutes).
                   If set to 0, interface scanning will only occur when
@@ -5700,38 +6184,43 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   server will
                   begin listening for queries on any newly discovered
                   interfaces (provided they are allowed by the
-                  listen-on configuration), and
+                  listen-on configuration), and
                   will
                   stop listening on interfaces that have gone away.
-                

-
statistics-interval

+                

+              
+
statistics-interval

 

-

+                

                   Name server statistics will be logged
-                  every statistics-interval
+                  every statistics-interval
                   minutes. The default is
                   60. The maximum value is 28 days (40320 minutes).
                   If set to 0, no statistics will be logged.
                   

 

 
Note

-

+                  

                     Not yet implemented in
                     BIND 9.
                   

-

-

+                

+              
 
-
-

+
+        

+
+        

 

 Topology

-

+          
+
+          

             All other things being equal, when the server chooses a name
             server
             to query from a list of name servers, it prefers the one that is
-            topologically closest to itself. The topology statement
-            takes an address_match_list and
+            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.
@@ -5743,40 +6232,48 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             any non-negated list element, and closer than any negated element.
             For example,
           

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

-

+
+          

 
Note

-

-              The topology option
+            

+              The topology option
               is not implemented in BIND 9.
             

-

-

-

+          

+        

+
+        

 

-The sortlist Statement

-

+The sortlist Statement

+
+          
+
+          

             The response to a DNS query may consist of multiple resource
             records (RRs) forming a resource records set (RRset).
             The name server will normally return the
             RRs within the RRset in an indeterminate order
-            (but see the rrset-order
-            statement in the section called “RRset Ordering”).
+            (but see the rrset-order
+            statement in the section called “RRset Ordering”).
             The client resolver code should rearrange the RRs as appropriate,
             that is, using any addresses on the local net in preference to
             other addresses.
@@ -5786,23 +6283,24 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             in the server, based on the client's address. This only requires
             configuring the name servers, not all the clients.
           

-

-            The sortlist statement (see below)
+
+          

+            The sortlist statement (see below)
             takes
-            an address_match_list and
+            an address_match_list and
             interprets it even
-            more specifically than the topology
+            more specifically than the topology
             statement
-            does (the section called “Topology”).
-            Each top level statement in the sortlist must
-            itself be an explicit address_match_list with
+            does (the section called “Topology”).
+            Each top level statement in the sortlist must
+            itself be an explicit address_match_list with
             one or two elements. The first element (which may be an IP
             address,
-            an IP prefix, an ACL name or a nested address_match_list)
+            an IP prefix, an ACL name or a nested 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
@@ -5810,14 +6308,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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 the same as the address_match_list in
-            a topology statement. Each top
+            treated the same as the address_match_list in
+            a 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
@@ -5835,6 +6333,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             or the 192.168.5/24 network will only prefer other addresses on
             their directly connected networks.
           

+
 
sortlist {
     // IF the local host
     // THEN first fit on the following nets
@@ -5858,7 +6357,8 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
     { { 192.168.4/24; 192.168.5/24; };
     };
 };

-

+
+          

             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 4.9.x. Responses sent
@@ -5870,52 +6370,57 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             Responses
             to other queries will not be sorted.
           

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

-
-

+
+        

+        

 

 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.
-            The rrset-order statement permits
+            The rrset-order statement permits
             configuration
             of the ordering of the records in a multiple record response.
-            See also the sortlist statement,
-            the section called “The sortlist Statement”.
+            See also the sortlist statement,
+            the section called “The sortlist Statement”.
           

-

-            An order_spec is defined as
+
+          

+            An order_spec is defined as
             follows:
           

-

+          

             [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 "*" (asterisk).
+          

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

-

-            The legal values for ordering are:
+          

+            The legal values for ordering are:
           

-

+          

+            
--++
-

 




 
 
 

 
-                    
fixed

+                    
fixed

                   		
 
                     

@@ -5926,7 +6431,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 

 

 
-                    
random

+                    
random

                   		
 
                     

@@ -5936,7 +6441,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 

 

 
-                    
cyclic

+                    
cyclic

                   		
 
                     

@@ -5951,55 +6456,65 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   

 

 

-

+
+          

+          

             For example:
           

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

-

+
+          

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

-

-            If multiple rrset-order statements
+          

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

-

+          

             By default, all records are returned in random order.
           

-

+
+          

 
Note

-

+            

               In this release of BIND 9, the
-              rrset-order statement does not support
+              rrset-order statement does not support
               "fixed" ordering by default.  Fixed ordering can be enabled
               at compile time by specifying "--enable-fixed-rrset" on
               the "configure" command line.
             

-

-

-

+          

+        
+
+        

 

 Tuning

-

-
lame-ttl

-

+          
+
+          

+
lame-ttl

+

+                

                   Sets the number of seconds to cache a
                   lame server indication. 0 disables caching. (This is
                   NOT recommended.)
                   The default is 600 (10 minutes) and the
                   maximum value is
                   1800 (30 minutes).
-                

-
servfail-ttl

+                

+
+              

+
servfail-ttl

 

-

+                

                   Sets the number of seconds to cache a
                   SERVFAIL response due to DNSSEC validation failure or
                   other general server failure.  If set to
@@ -6009,27 +6524,30 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   query that failed due to DNSSEC validation to be retried
                   without waiting for the SERVFAIL TTL to expire.
                 

-

+                

                   The maximum value is 300
                   (5 minutes); any higher value will be silently
                   reduced.  The default is 10
                   seconds.
                 

-

-
max-ncache-ttl

-

+              

+
max-ncache-ttl

+

+                

                   To reduce network traffic and increase performance,
-                  the server stores negative answers. max-ncache-ttl is
+                  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
-                  max-ncache-ttl is 10800 seconds (3 hours).
-                  max-ncache-ttl cannot exceed
+                  max-ncache-ttl is 10800 seconds (3 hours).
+                  max-ncache-ttl cannot exceed
                   7 days and will
                   be silently truncated to 7 days if set to a greater value.
-                

-
max-cache-ttl

-

+                

+              

+
max-cache-ttl

+

+                

                   Sets the maximum time for which the server will
                   cache ordinary (positive) answers in seconds.
                   The default is 604800 (one week).
@@ -6037,28 +6555,29 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   SERVFAIL, because of lost caches of intermediate
                   RRsets (such as NS and glue AAAA/A records) in the
                   resolution process.
-                

-
min-roots

+                

+              
+
min-roots

 

-

+                

                   The minimum number of root servers that
                   is required for a request for the root servers to be
                   accepted. The default
                   is 2.
                 

-

+                

 
Note

-

+                  

                     Not implemented in BIND 9.
                   

-

-

-
sig-validity-interval

+                

+              
+
sig-validity-interval

 

-

+                

                   Specifies the number of days into the future when
                   DNSSEC signatures automatically generated as a
-                  result of dynamic updates (the section called “Dynamic Update”) will expire.  There
+                  result of dynamic updates (the section called “Dynamic Update”) will expire.  There
                   is an optional second field which specifies how
                   long before expiry that the signatures will be
                   regenerated.  If not specified, the signatures will
@@ -6069,65 +6588,69 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   giving a re-signing interval of 7 1/2 days.  The maximum
                   values are 10 years (3660 days).
                 

-

+                

                   The signature inception time is unconditionally
                   set to one hour before the current time to allow
                   for a limited amount of clock skew.
                 

-

-                  The sig-validity-interval
+                

+                  The sig-validity-interval
                   should be, at least, several multiples of the SOA
                   expire interval to allow for reasonable interaction
                   between the various timer and expiry dates.
                 

-

-
sig-signing-nodes

-

+              

+
sig-signing-nodes

+

+                

                   Specify the maximum number of nodes to be
                   examined in each quantum when signing a zone with
                   a new DNSKEY. The default is
                   100.
-                

-
sig-signing-signatures

-

+                

+              

+
sig-signing-signatures

+

+                

                   Specify a threshold number of signatures that
                   will terminate processing a quantum when signing
                   a zone with a new DNSKEY.  The default is
                   10.
-                

-
sig-signing-type

+                

+              
+
sig-signing-type

 

-

+                

                   Specify a private RDATA type to be used when generating
                   signing state records.  The default is
                   65534.
                 

-

+                

                   It is expected that this parameter may be removed
                   in a future version once there is a standard type.
                 

-

+                

                   Signing state records are used to internally by
-                  named to track the current state of
+                  named to track the current state of
                   a zone-signing process, i.e., whether it is still active
                   or has been completed.  The records can be inspected
                   using the command
-                  rndc signing -list zone.
-                  Once named has finished signing
+                  rndc signing -list zone.
+                  Once named has finished signing
                   a zone with a particular key, the signing state
                   record associated with that key can be removed from
                   the zone by running
-                  rndc signing -clear keyid/algorithm zone.
+                  rndc signing -clear keyid/algorithm zone.
                   To clear all of the completed signing state
                   records for a zone, use
-                  rndc signing -clear all zone.
+                  rndc signing -clear all zone.
                 

-

+              
 

-min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
+min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
 

 

-

+                

                   These options control the server's behavior on refreshing a
                   zone
                   (querying for SOA changes) or retrying failed transfers.
@@ -6137,7 +6660,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   little
                   control over their contents.
                 

-

+                

                   These options allow the administrator to set a minimum and
                   maximum refresh and retry time in seconds per-zone,
                   per-view, or globally.
@@ -6145,18 +6668,18 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   and clamp the SOA refresh and retry times to the specified
                   values.
                 

-

+                

                   The following defaults apply.
-                  min-refresh-time 300 seconds,
-                  max-refresh-time 2419200 seconds
-                  (4 weeks), min-retry-time 500 seconds,
-                  and max-retry-time 1209600 seconds
+                  min-refresh-time 300 seconds,
+                  max-refresh-time 2419200 seconds
+                  (4 weeks), min-retry-time 500 seconds,
+                  and max-retry-time 1209600 seconds
                   (2 weeks).
                 

-

-
edns-udp-size

+              
+
edns-udp-size

 

-

+                

                   Sets the maximum advertised EDNS UDP buffer size in
                   bytes, to control the size of packets received from
                   authoritative servers in response to recursive queries.
@@ -6164,120 +6687,120 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   will be silently adjusted to the nearest value within
                   it).  The default value is 4096.
                 

-

+                

                   The usual reason for setting
-                  edns-udp-size to a non-default value
+                  edns-udp-size to a non-default value
                   is to get UDP answers to pass through broken firewalls
                   that block fragmented packets and/or block UDP DNS
                   packets that are greater than 512 bytes.
                 

-

-                  When named first queries a remote
+                

+                  When named first queries a remote
                   server, it will advertise a UDP buffer size of 512, as
                   this has the greatest chance of success on the first try.
                 

-

-                  If the initial response times out, named
+                

+                  If the initial response times out, named
                   will try again with plain DNS, and if that is successful,
                   it will be taken as evidence that the server does not
                   support EDNS. After enough failures using EDNS and
-                  successes using plain DNS, named
+                  successes using plain DNS, named
                   will default to plain DNS for future communications
-                  with that server.  (Periodically, named
+                  with that server.  (Periodically, named
                   will send an EDNS query to see if the situation has
                   improved.)
                 

-

+                

                   However, if the initial query is successful with
                   EDNS advertising a buffer size of 512, then
-                  named will advertise progressively
+                  named will advertise progressively
                   larger buffer sizes on successive queries, until
                   responses begin timing out or
-                  edns-udp-size is reached.
+                  edns-udp-size is reached.
                 

-

-                  The default buffer sizes used by named
+                

+                  The default buffer sizes used by named
                   are 512, 1232, 1432, and 4096, but never exceeding
-                  edns-udp-size.  (The values 1232 and
+                  edns-udp-size.  (The values 1232 and
                   1432 are chosen to allow for an IPv4/IPv6 encapsulated
                   UDP message to be sent without fragmentation at the
                   minimum MTU sizes for Ethernet and IPv6 networks.)
                 

-

-
max-udp-size

+              
+
max-udp-size

 

-

+                

                   Sets the maximum EDNS UDP message size
-                  named will send in bytes.
+                  named will send in bytes.
                   Valid values are 512 to 4096 (values outside this
                   range will be silently adjusted to the nearest
                   value within it).  The default value is 4096.
                 

-

+                

                   This value applies to responses sent by a server; to
                   set the advertised buffer size in queries, see
-                  edns-udp-size.
+                  edns-udp-size.
                 

-

+                

                   The usual reason for setting
-                  max-udp-size to a non-default
+                  max-udp-size to a non-default
                   value is to get UDP answers to pass through broken
                   firewalls that block fragmented packets and/or
                   block UDP packets that are greater than 512 bytes.
                   This is independent of the advertised receive
-                  buffer (edns-udp-size).
+                  buffer (edns-udp-size).
                 

-

+                

                   Setting this to a low value will encourage additional
                   TCP traffic to the nameserver.
                 

-

-
masterfile-format

+              
+
masterfile-format

 

-
Specifies
+                
Specifies
                   the file format of zone files (see
-                  the section called “Additional File Formats”).
+                  the section called “Additional File Formats”).
                   The default value is text, which is the
                   standard textual representation, except for slave zones,
                   in which the default value is raw.
                   Files in other formats than text are
                   typically expected to be generated by the
-                  named-compilezone tool, or dumped by
-                  named.
+                  named-compilezone tool, or dumped by
+                  named.
                 

-

+                

                   Note that when a zone file in a different format than
-                  text is loaded, named
+                  text is loaded, named
                   may omit some of the checks which would be performed for a
                   file in the text format.  In particular,
-                  check-names checks do not apply
+                  check-names checks do not apply
                   for the raw format.  This means
                   a zone file in the raw format
                   must be generated with the same check level as that
-                  specified in the named configuration
+                  specified in the named configuration
                   file.  Also, map format files are
                   loaded directly into memory via memory mapping, with only
                   minimal checking.
                 

-

+                

                   This statement sets the
-                  masterfile-format for all zones,
+                  masterfile-format for all zones,
                   but can be overridden on a per-zone or per-view basis
-                  by including a masterfile-format
-                  statement within the zone or
-                  view block in the configuration
+                  by including a masterfile-format
+                  statement within the zone or
+                  view block in the configuration
                   file.
                 

-

-
masterfile-style

+              
+
masterfile-style

 

-

+                

                   Specifies the formatting of zone files during dump
                   when the masterfile-format is
                   text. (This option is ignored
                   with any other masterfile-format.)
                 

-

+                

                   When set to relative,
                   records are printed in a multi-line format with owner
                   names expressed relative to a shared origin.  When set
@@ -6290,11 +6813,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   zone is to be edited by hand.  The default is
                   relative.
                 

-

+              
 

-max-recursion-depth
+max-recursion-depth
 

-

+

+                

                   Sets the maximum number of levels of recursion
                   that are permitted at any one time while servicing
                   a recursive query. Resolving a name may require
@@ -6303,11 +6827,13 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   of indirections exceeds this value, the recursive
                   query is terminated and returns SERVFAIL.  The
                   default is 7.
-                

+                

+              
 

-max-recursion-queries
+max-recursion-queries
 

-

+

+                

                   Sets the maximum number of iterative queries that
                   may be sent while servicing a recursive query.
                   If more queries are sent, the recursive query
@@ -6315,35 +6841,38 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   look up top level comains such as "com" and "net"
                   and the DNS root zone are exempt from this limitation.
                   The default is 75.
-                

-
notify-delay

+                

+              
+
notify-delay

 

-

+                

                   The delay, in seconds, between sending sets of notify
                   messages for a zone.  The default is five (5) seconds.
                 

-

+                

                   The overall rate that NOTIFY messages are sent for all
-                  zones is controlled by serial-query-rate.
+                  zones is controlled by serial-query-rate.
                 

-

-
max-rsa-exponent-size

-

+              

+
max-rsa-exponent-size

+

+                

                   The maximum RSA exponent size, in bits, that will
                   be accepted when validating.  Valid values are 35
                   to 4096 bits.  The default zero (0) is also accepted
                   and is equivalent to 4096.
-                

-
prefetch

+                

+              
+
prefetch

 

-

+                

                   When a query is received for cached data which
-                  is to expire shortly, named can
+                  is to expire shortly, named can
                   refresh the data from the authoritative server
                   immediately, ensuring that the cache always has an
                   answer available.
                 

-

+                

                   The prefetch specifies the
                   "trigger" TTL value at which prefetch of the current
                   query will take place: when a cache record with a
@@ -6355,98 +6884,114 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   prefetch to be disabled.
                   The default trigger TTL is 2.
                 

-

+                

                   An optional second argument specifies the "eligibility"
                   TTL: the smallest original
                   TTL value that will be accepted for a record to be
                   eligible for prefetching.  The eligibility TTL must
                   be at least six seconds longer than the trigger TTL;
-                  if it isn't, named will silently
+                  if it isn't, named will silently
                   adjust it upward.
                   The default eligibility TTL is 9.
                 

-

-
v6-bias

-

+              

+
v6-bias

+

+                

                   When determining the next nameserver to try
                   preference IPv6 nameservers by this many milliseconds.
                   The default is 50 milliseconds.
-                

+                

+              
 

-
-

+
+        

+
+        

 

 Built-in server information zones

-

+          
+
+          

             The server provides some helpful diagnostic information
             through a number of built-in zones under the
             pseudo-top-level-domain bind in the
-            CHAOS class.  These zones are part
+            CHAOS class.  These zones are part
             of a
-            built-in view (see the section called “view Statement Grammar”) of
+            built-in view (see the section called “view Statement Grammar”) of
             class
-            CHAOS which is separate from the
-            default view of class IN. Most global
-            configuration options (allow-query,
+            CHAOS which is separate from the
+            default view of class IN. Most global
+            configuration options (allow-query,
             etc) will apply to this view, but some are locally
-            overridden: notify,
-            recursion and
-            allow-new-zones are
+            overridden: notify,
+            recursion and
+            allow-new-zones are
             always set to no, and
-            rate-limit is set to allow
+            rate-limit is set to allow
             three responses per second.
           

-

+          

             If you need to disable these zones, use the options
-            below, or hide the built-in CHAOS
+            below, or hide the built-in CHAOS
             view by
-            defining an explicit view of class CHAOS
+            defining an explicit view of class CHAOS
             that matches all clients.
           

-

-
version

-

+
+          

+
version

+

+                

                   The version the server should report
                   via a query of the name version.bind
-                  with type TXT, class CHAOS.
+                  with type TXT, class CHAOS.
                   The default is the real version number of this server.
-                  Specifying version none
+                  Specifying version none
                   disables processing of the queries.
-                

-
hostname

-

+                

+              

+
hostname

+

+                

                   The hostname the server should report via a query of
                   the name hostname.bind
-                  with type TXT, class CHAOS.
+                  with type TXT, class CHAOS.
                   This defaults to the hostname of the machine hosting the
                   name server as
                   found by the gethostname() function.  The primary purpose of such queries
                   is to
                   identify which of a group of anycast servers is actually
-                  answering your queries.  Specifying hostname none;
+                  answering your queries.  Specifying hostname none;
                   disables processing of the queries.
-                

-
server-id

-

+                

+              

+
server-id

+

+                

                   The ID the server should report when receiving a Name
                   Server Identifier (NSID) query, or a query of the name
                   ID.SERVER with type
-                  TXT, class CHAOS.
+                  TXT, class CHAOS.
                   The primary purpose of such queries is to
                   identify which of a group of anycast servers is actually
-                  answering your queries.  Specifying server-id none;
+                  answering your queries.  Specifying server-id none;
                   disables processing of the queries.
-                  Specifying server-id hostname; will cause named to
+                  Specifying server-id hostname; will cause named to
                   use the hostname as found by the gethostname() function.
-                  The default server-id is none.
-                

+                  The default server-id is none.
+                

+              

 

-

-

+
+        

+
+        

 

 Built-in Empty Zones

-

-            The named server has some built-in
+          
+          

+            The named server has some built-in
             empty zones (SOA and NS records only).
             These are for zones that should normally be answered locally
             and which queries should not be sent to the Internet's root
@@ -6458,117 +7003,117 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             IPv6 link local addresses, the IPv6 loopback address and the
             IPv6 unknown address.
           

-

+          

             The server will attempt to determine if a built-in zone
             already exists or is active (covered by a forward-only
             forwarding declaration) and will not create an empty
             zone in that case.
           

-

+          

             The current list of empty zones is:
             

-
    
-
  • 10.IN-ADDR.ARPA
    • 
-
  • 16.172.IN-ADDR.ARPA
    • 
-
  • 17.172.IN-ADDR.ARPA
    • 
-
  • 18.172.IN-ADDR.ARPA
    • 
-
  • 19.172.IN-ADDR.ARPA
    • 
-
  • 20.172.IN-ADDR.ARPA
    • 
-
  • 21.172.IN-ADDR.ARPA
    • 
-
  • 22.172.IN-ADDR.ARPA
    • 
-
  • 23.172.IN-ADDR.ARPA
    • 
-
  • 24.172.IN-ADDR.ARPA
    • 
-
  • 25.172.IN-ADDR.ARPA
    • 
-
  • 26.172.IN-ADDR.ARPA
    • 
-
  • 27.172.IN-ADDR.ARPA
    • 
-
  • 28.172.IN-ADDR.ARPA
    • 
-
  • 29.172.IN-ADDR.ARPA
    • 
-
  • 30.172.IN-ADDR.ARPA
    • 
-
  • 31.172.IN-ADDR.ARPA
    • 
-
  • 168.192.IN-ADDR.ARPA
    • 
-
  • 64.100.IN-ADDR.ARPA
    • 
-
  • 65.100.IN-ADDR.ARPA
    • 
-
  • 66.100.IN-ADDR.ARPA
    • 
-
  • 67.100.IN-ADDR.ARPA
    • 
-
  • 68.100.IN-ADDR.ARPA
    • 
-
  • 69.100.IN-ADDR.ARPA
    • 
-
  • 70.100.IN-ADDR.ARPA
    • 
-
  • 71.100.IN-ADDR.ARPA
    • 
-
  • 72.100.IN-ADDR.ARPA
    • 
-
  • 73.100.IN-ADDR.ARPA
    • 
-
  • 74.100.IN-ADDR.ARPA
    • 
-
  • 75.100.IN-ADDR.ARPA
    • 
-
  • 76.100.IN-ADDR.ARPA
    • 
-
  • 77.100.IN-ADDR.ARPA
    • 
-
  • 78.100.IN-ADDR.ARPA
    • 
-
  • 79.100.IN-ADDR.ARPA
    • 
-
  • 80.100.IN-ADDR.ARPA
    • 
-
  • 81.100.IN-ADDR.ARPA
    • 
-
  • 82.100.IN-ADDR.ARPA
    • 
-
  • 83.100.IN-ADDR.ARPA
    • 
-
  • 84.100.IN-ADDR.ARPA
    • 
-
  • 85.100.IN-ADDR.ARPA
    • 
-
  • 86.100.IN-ADDR.ARPA
    • 
-
  • 87.100.IN-ADDR.ARPA
    • 
-
  • 88.100.IN-ADDR.ARPA
    • 
-
  • 89.100.IN-ADDR.ARPA
    • 
-
  • 90.100.IN-ADDR.ARPA
    • 
-
  • 91.100.IN-ADDR.ARPA
    • 
-
  • 92.100.IN-ADDR.ARPA
    • 
-
  • 93.100.IN-ADDR.ARPA
    • 
-
  • 94.100.IN-ADDR.ARPA
    • 
-
  • 95.100.IN-ADDR.ARPA
    • 
-
  • 96.100.IN-ADDR.ARPA
    • 
-
  • 97.100.IN-ADDR.ARPA
    • 
-
  • 98.100.IN-ADDR.ARPA
    • 
-
  • 99.100.IN-ADDR.ARPA
    • 
-
  • 100.100.IN-ADDR.ARPA
    • 
-
  • 101.100.IN-ADDR.ARPA
    • 
-
  • 102.100.IN-ADDR.ARPA
    • 
-
  • 103.100.IN-ADDR.ARPA
    • 
-
  • 104.100.IN-ADDR.ARPA
    • 
-
  • 105.100.IN-ADDR.ARPA
    • 
-
  • 106.100.IN-ADDR.ARPA
    • 
-
  • 107.100.IN-ADDR.ARPA
    • 
-
  • 108.100.IN-ADDR.ARPA
    • 
-
  • 109.100.IN-ADDR.ARPA
    • 
-
  • 110.100.IN-ADDR.ARPA
    • 
-
  • 111.100.IN-ADDR.ARPA
    • 
-
  • 112.100.IN-ADDR.ARPA
    • 
-
  • 113.100.IN-ADDR.ARPA
    • 
-
  • 114.100.IN-ADDR.ARPA
    • 
-
  • 115.100.IN-ADDR.ARPA
    • 
-
  • 116.100.IN-ADDR.ARPA
    • 
-
  • 117.100.IN-ADDR.ARPA
    • 
-
  • 118.100.IN-ADDR.ARPA
    • 
-
  • 119.100.IN-ADDR.ARPA
    • 
-
  • 120.100.IN-ADDR.ARPA
    • 
-
  • 121.100.IN-ADDR.ARPA
    • 
-
  • 122.100.IN-ADDR.ARPA
    • 
-
  • 123.100.IN-ADDR.ARPA
    • 
-
  • 124.100.IN-ADDR.ARPA
    • 
-
  • 125.100.IN-ADDR.ARPA
    • 
-
  • 126.100.IN-ADDR.ARPA
    • 
-
  • 127.100.IN-ADDR.ARPA
    • 
-
  • 0.IN-ADDR.ARPA
    • 
-
  • 127.IN-ADDR.ARPA
    • 
-
  • 254.169.IN-ADDR.ARPA
    • 
-
  • 2.0.192.IN-ADDR.ARPA
    • 
-
  • 100.51.198.IN-ADDR.ARPA
    • 
-
  • 113.0.203.IN-ADDR.ARPA
    • 
-
  • 255.255.255.255.IN-ADDR.ARPA
    • 
-
  • 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
    • 
-
  • 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
    • 
-
  • 8.B.D.0.1.0.0.2.IP6.ARPA
    • 
-
  • D.F.IP6.ARPA
    • 
-
  • 8.E.F.IP6.ARPA
    • 
-
  • 9.E.F.IP6.ARPA
    • 
-
  • A.E.F.IP6.ARPA
    • 
-
  • B.E.F.IP6.ARPA
    • 
+
      
+
    • 10.IN-ADDR.ARPA
      • 
+
    • 16.172.IN-ADDR.ARPA
      • 
+
    • 17.172.IN-ADDR.ARPA
      • 
+
    • 18.172.IN-ADDR.ARPA
      • 
+
    • 19.172.IN-ADDR.ARPA
      • 
+
    • 20.172.IN-ADDR.ARPA
      • 
+
    • 21.172.IN-ADDR.ARPA
      • 
+
    • 22.172.IN-ADDR.ARPA
      • 
+
    • 23.172.IN-ADDR.ARPA
      • 
+
    • 24.172.IN-ADDR.ARPA
      • 
+
    • 25.172.IN-ADDR.ARPA
      • 
+
    • 26.172.IN-ADDR.ARPA
      • 
+
    • 27.172.IN-ADDR.ARPA
      • 
+
    • 28.172.IN-ADDR.ARPA
      • 
+
    • 29.172.IN-ADDR.ARPA
      • 
+
    • 30.172.IN-ADDR.ARPA
      • 
+
    • 31.172.IN-ADDR.ARPA
      • 
+
    • 168.192.IN-ADDR.ARPA
      • 
+
    • 64.100.IN-ADDR.ARPA
      • 
+
    • 65.100.IN-ADDR.ARPA
      • 
+
    • 66.100.IN-ADDR.ARPA
      • 
+
    • 67.100.IN-ADDR.ARPA
      • 
+
    • 68.100.IN-ADDR.ARPA
      • 
+
    • 69.100.IN-ADDR.ARPA
      • 
+
    • 70.100.IN-ADDR.ARPA
      • 
+
    • 71.100.IN-ADDR.ARPA
      • 
+
    • 72.100.IN-ADDR.ARPA
      • 
+
    • 73.100.IN-ADDR.ARPA
      • 
+
    • 74.100.IN-ADDR.ARPA
      • 
+
    • 75.100.IN-ADDR.ARPA
      • 
+
    • 76.100.IN-ADDR.ARPA
      • 
+
    • 77.100.IN-ADDR.ARPA
      • 
+
    • 78.100.IN-ADDR.ARPA
      • 
+
    • 79.100.IN-ADDR.ARPA
      • 
+
    • 80.100.IN-ADDR.ARPA
      • 
+
    • 81.100.IN-ADDR.ARPA
      • 
+
    • 82.100.IN-ADDR.ARPA
      • 
+
    • 83.100.IN-ADDR.ARPA
      • 
+
    • 84.100.IN-ADDR.ARPA
      • 
+
    • 85.100.IN-ADDR.ARPA
      • 
+
    • 86.100.IN-ADDR.ARPA
      • 
+
    • 87.100.IN-ADDR.ARPA
      • 
+
    • 88.100.IN-ADDR.ARPA
      • 
+
    • 89.100.IN-ADDR.ARPA
      • 
+
    • 90.100.IN-ADDR.ARPA
      • 
+
    • 91.100.IN-ADDR.ARPA
      • 
+
    • 92.100.IN-ADDR.ARPA
      • 
+
    • 93.100.IN-ADDR.ARPA
      • 
+
    • 94.100.IN-ADDR.ARPA
      • 
+
    • 95.100.IN-ADDR.ARPA
      • 
+
    • 96.100.IN-ADDR.ARPA
      • 
+
    • 97.100.IN-ADDR.ARPA
      • 
+
    • 98.100.IN-ADDR.ARPA
      • 
+
    • 99.100.IN-ADDR.ARPA
      • 
+
    • 100.100.IN-ADDR.ARPA
      • 
+
    • 101.100.IN-ADDR.ARPA
      • 
+
    • 102.100.IN-ADDR.ARPA
      • 
+
    • 103.100.IN-ADDR.ARPA
      • 
+
    • 104.100.IN-ADDR.ARPA
      • 
+
    • 105.100.IN-ADDR.ARPA
      • 
+
    • 106.100.IN-ADDR.ARPA
      • 
+
    • 107.100.IN-ADDR.ARPA
      • 
+
    • 108.100.IN-ADDR.ARPA
      • 
+
    • 109.100.IN-ADDR.ARPA
      • 
+
    • 110.100.IN-ADDR.ARPA
      • 
+
    • 111.100.IN-ADDR.ARPA
      • 
+
    • 112.100.IN-ADDR.ARPA
      • 
+
    • 113.100.IN-ADDR.ARPA
      • 
+
    • 114.100.IN-ADDR.ARPA
      • 
+
    • 115.100.IN-ADDR.ARPA
      • 
+
    • 116.100.IN-ADDR.ARPA
      • 
+
    • 117.100.IN-ADDR.ARPA
      • 
+
    • 118.100.IN-ADDR.ARPA
      • 
+
    • 119.100.IN-ADDR.ARPA
      • 
+
    • 120.100.IN-ADDR.ARPA
      • 
+
    • 121.100.IN-ADDR.ARPA
      • 
+
    • 122.100.IN-ADDR.ARPA
      • 
+
    • 123.100.IN-ADDR.ARPA
      • 
+
    • 124.100.IN-ADDR.ARPA
      • 
+
    • 125.100.IN-ADDR.ARPA
      • 
+
    • 126.100.IN-ADDR.ARPA
      • 
+
    • 127.100.IN-ADDR.ARPA
      • 
+
    • 0.IN-ADDR.ARPA
      • 
+
    • 127.IN-ADDR.ARPA
      • 
+
    • 254.169.IN-ADDR.ARPA
      • 
+
    • 2.0.192.IN-ADDR.ARPA
      • 
+
    • 100.51.198.IN-ADDR.ARPA
      • 
+
    • 113.0.203.IN-ADDR.ARPA
      • 
+
    • 255.255.255.255.IN-ADDR.ARPA
      • 
+
    • 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
      • 
+
    • 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
      • 
+
    • 8.B.D.0.1.0.0.2.IP6.ARPA
      • 
+
    • D.F.IP6.ARPA
      • 
+
    • 8.E.F.IP6.ARPA
      • 
+
    • 9.E.F.IP6.ARPA
      • 
+
    • A.E.F.IP6.ARPA
      • 
+
    • B.E.F.IP6.ARPA
      • 
 
    
 
    
           
    
-
    
+          
    
             Empty zones are settable at the view level and only apply to
             views of class IN.  Disabled empty zones are only inherited
             from options if there are no disabled empty zones specified
@@ -6580,7 +7125,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 

 

           

-

+          

             If you are using the address ranges covered here, you should
             already have reverse zones covering the addresses you use.
             In practice this appears to not be the case with many queries
@@ -6589,52 +7134,64 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             to be deployed to channel the query load away from the
             infrastructure servers.
           

-

+          

 
Note

             The real parent servers for these zones should disable all
             empty zone under the parent zone they serve.  For the real
             root servers, this is all built-in empty zones.  This will
             enable them to return referrals to deeper in the tree.
           

-

-
empty-server

-

+          

+
empty-server

+

+                

                   Specify what server name will appear in the returned
                   SOA record for empty zones.  If none is specified, then
                   the zone's name will be used.
-                

-
empty-contact

-

+                

+               

+
empty-contact

+

+                

                   Specify what contact name will appear in the returned
                   SOA record for empty zones.  If none is specified, then
                   "." will be used.
-                

-
empty-zones-enable

-

+                

+              

+
empty-zones-enable

+

+                

                   Enable or disable all empty zones.  By default, they
                   are enabled.
-                

-
disable-empty-zone

-

+                

+              

+
disable-empty-zone

+

+                

                   Disable individual empty zones.  By default, none are
                   disabled.  This option can be specified multiple times.
-                

+                

+              

 

-

-

+        

+
+        

 

 Additional Section Caching

-

-            The additional section cache, also called acache,
+          
+
+          

+            The additional section cache, also called acache,
             is an internal cache to improve the response performance of BIND 9.
             When additional section caching is enabled, BIND 9 will
             cache an internal short-cut to the additional section content for
             each answer RR.
-            Note that acache is an internal caching
+            Note that acache is an internal caching
             mechanism of BIND 9, and is not related to the DNS caching
             server function.
           

-

+
+          

             Additional section caching does not change the
             response content (except the RRsets ordering of the additional
             section, see below), but can improve the response performance
@@ -6642,64 +7199,74 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             It is particularly effective when BIND 9 acts as an authoritative
             server for a zone that has many delegations with many glue RRs.
           

-

+
+          

             In order to obtain the maximum performance improvement
             from additional section caching, setting
-            additional-from-cache
-            to no is recommended, since the current
-            implementation of acache
+            additional-from-cache
+            to no is recommended, since the current
+            implementation of acache
             does not short-cut of additional section information from the
             DNS cache data.
           

-

-            One obvious disadvantage of acache is
+
+          

+            One obvious disadvantage of acache is
             that it requires much more
             memory for the internal cached data.
             Thus, if the response performance does not matter and memory
             consumption is much more critical, the
-            acache mechanism can be
-            disabled by setting acache-enable to
-            no.
+            acache mechanism can be
+            disabled by setting acache-enable to
+            no.
             It is also possible to specify the upper limit of memory
             consumption
-            for acache by using max-acache-size.
+            for acache by using max-acache-size.
           

-

+
+          

             Additional section caching also has a minor effect on the
             RRset ordering in the additional section.
-            Without acache,
-            cyclic order is effective for the additional
+            Without acache,
+            cyclic order is effective for the additional
             section as well as the answer and authority sections.
             However, additional section caching fixes the ordering when it
             first caches an RRset for the additional section, and the same
             ordering will be kept in succeeding responses, regardless of the
-            setting of rrset-order.
+            setting of rrset-order.
             The effect of this should be minor, however, since an
             RRset in the additional section
             typically only contains a small number of RRs (and in many cases
             it only contains a single RR), in which case the
             ordering does not matter much.
           

-

+
+          

             The following is a summary of options related to
-            acache.
+            acache.
           

-

-
acache-enable

-

-                  If yes, additional section caching is
-                  enabled.  The default value is no.
-                

-
acache-cleaning-interval

-

+
+          

+
acache-enable

+

+                

+                  If yes, additional section caching is
+                  enabled.  The default value is no.
+                

+              

+
acache-cleaning-interval

+

+                

                   The server will remove stale cache entries, based on an LRU
                   based
-                  algorithm, every acache-cleaning-interval minutes.
+                  algorithm, every acache-cleaning-interval minutes.
                   The default is 60 minutes.
                   If set to 0, no periodic cleaning will occur.
-                

-
max-acache-size

-

+                

+              

+
max-acache-size

+

+                

                   The maximum amount of memory in bytes to use for the server's acache.
                   When the amount of data in the acache reaches this limit,
                   the server
@@ -6709,55 +7276,63 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   separately to the
                   acache of each view.
                   The default is 16M.
-                

+                

+              

 

-

-

+
+        

+
+        

 

-Content Filtering

-

+Content Filtering

+          
+          

             BIND 9 provides the ability to filter
             out DNS responses from external DNS servers containing
             certain types of data in the answer section.
             Specifically, it can reject address (A or AAAA) records if
             the corresponding IPv4 or IPv6 addresses match the given
             address_match_list of the
-            deny-answer-addresses option.
+            deny-answer-addresses option.
             It can also reject CNAME or DNAME records if the "alias"
             name (i.e., the CNAME alias or the substituted query name
             due to DNAME) matches the
             given namelist of the
-            deny-answer-aliases option, where
+            deny-answer-aliases option, where
             "match" means the alias name is a subdomain of one of
             the name_list elements.
             If the optional namelist is specified
-            with except-from, records whose query name
+            with except-from, records whose query name
             matches the list will be accepted regardless of the filter
             setting.
             Likewise, if the alias name is a subdomain of the
-            corresponding zone, the deny-answer-aliases
+            corresponding zone, the deny-answer-aliases
             filter will not apply;
             for example, even if "example.com" is specified for
-            deny-answer-aliases,
+            deny-answer-aliases,
           

 
www.example.com. CNAME xxx.example.com.

-

+
+          

             returned by an "example.com" server will be accepted.
           

-

+
+          

             In the address_match_list of the
-            deny-answer-addresses option, only
+            deny-answer-addresses option, only
             ip_addr
             and ip_prefix
             are meaningful;
             any key_id will be silently ignored.
           

-

+
+          

             If a response message is rejected due to the filtering,
             the entire message is discarded without being cached, and
             a SERVFAIL error will be returned to the client.
           

-

+
+          

             This filtering is intended to prevent "DNS rebinding attacks," in
             which an attacker, in response to a query for a domain name the
             attacker controls, returns an IP address within your own network or
@@ -6767,44 +7342,53 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             to get access to an internal node of your local network
             that couldn't be externally accessed otherwise.
             See the paper available at
-            
+            
             http://portal.acm.org/citation.cfm?id=1315245.1315298
             
             for more details about the attacks.
           

-

+
+          

             For example, if you own a domain named "example.net" and
             your internal network uses an IPv4 prefix 192.0.2.0/24,
             you might specify the following rules:
           

+
 
deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
 deny-answer-aliases { "example.net"; };
 

-

+
+          

             If an external attacker lets a web browser in your local
             network look up an IPv4 address of "attacker.example.com",
             the attacker's DNS server would return a response like this:
           

+
 
attacker.example.com. A 192.0.2.1

-

+
+          

             in the answer section.
             Since the rdata of this record (the IPv4 address) matches
             the specified prefix 192.0.2.0/24, this response will be
             ignored.
           

-

+
+          

             On the other hand, if the browser looks up a legitimate
             internal web server "www.example.net" and the
             following response is returned to
             the BIND 9 server
           

+
 
www.example.net. A 192.0.2.2

-

+
+          

             it will be accepted since the owner name "www.example.net"
-            matches the except-from element,
+            matches the except-from element,
             "example.net".
           

-

+
+          

             Note that this is not really an attack on the DNS per se.
             In fact, there is nothing wrong for an "external" name to
             be mapped to your "internal" IP address or domain name
@@ -6825,7 +7409,8 @@ deny-answer-aliases { "example.net"; };
             very sure you have no other choice and the attack is a
             real threat for your applications.
           

-

+
+          

             Care should be particularly taken if you want to use this
             option for addresses within 127.0.0.0/8.
             These addresses are obviously "internal", but many
@@ -6834,11 +7419,13 @@ deny-answer-aliases { "example.net"; };
             Filtering out DNS records containing this address
             spuriously can break such applications.
           

-
-

+        

+
+        

 

-Response Policy Zone (RPZ) Rewriting

-

+Response Policy Zone (RPZ) Rewriting

+          
+          

             BIND 9 includes a limited
             mechanism to modify DNS responses for requests
             analogous to email anti-spam DNS blacklists.
@@ -6846,36 +7433,39 @@ deny-answer-aliases { "example.net"; };
             deny the existence of IP addresses for domains (NODATA),
             or contain other IP addresses or data.
           

-

+
+          

             Response policy zones are named in the
-            response-policy option for the view or among the
+            response-policy option for the view or among the
             global options if there is no response-policy option for the view.
             Response policy zones are ordinary DNS zones containing RRsets
             that can be queried normally if allowed.
             It is usually best to restrict those queries with something like
-            allow-query { localhost; };.
+            allow-query { localhost; };.
           

-

-            A response-policy option can support
+
+          

+            A response-policy option can support
             multiple policy zones.  To maximize performance, a radix
             tree is used to quickly identify response policy zones
             containing triggers that match the current query.  This
             imposes an upper limit of 32 on the number of policy zones
-            in a single response-policy option; more
+            in a single response-policy option; more
             than that is a configuration error.
           

-

+
+          

             Five policy triggers can be encoded in RPZ records.
             

-

-
RPZ-CLIENT-IP

+

+
RPZ-CLIENT-IP

 

-

+                  

                     IP records are triggered by the IP address of the
                     DNS client.
                     Client IP address triggers are encoded in records that have
                     owner names that are subdomains of
-                    rpz-client-ip relativized to the
+                    rpz-client-ip relativized to the
                     policy zone origin name
                     and encode an address or address block.
                     IPv4 addresses are represented as
@@ -6885,7 +7475,8 @@ deny-answer-aliases { "example.net"; };
                     B4 is the decimal value of the least significant byte of the
                     IPv4 address as in IN-ADDR.ARPA.
                   

-

+
+                  

                     IPv6 addresses are encoded in a format similar
                     to the standard IPv6 text representation,
                     prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-client-ip.
@@ -6901,136 +7492,158 @@ deny-answer-aliases { "example.net"; };
                     encodings.
                     The IPv6 prefix length must be between 1 and 128.
                   

-

-
QNAME

-

+                

+
QNAME

+

+                  

                     QNAME policy records are triggered by query names of
                     requests and targets of CNAME records resolved to generate
                     the response.
                     The owner name of a QNAME policy record is
                     the query name relativized to the policy zone.
-                  

-
RPZ-IP

-

+                  

+                

+
RPZ-IP

+

+                  

                     IP triggers are IP addresses in an
                     A or AAAA record in the ANSWER section of a response.
                     They are encoded like client-IP triggers except as
-                    subdomains of rpz-ip.
-                  

-
RPZ-NSDNAME

-

+                    subdomains of rpz-ip.
+                  

+                

+
RPZ-NSDNAME

+

+                  

                     NSDNAME triggers match names of authoritative servers
                     for the query name, a parent of the query name, a CNAME for
                     query name, or a parent of a CNAME.
                     They are encoded as subdomains of
-                    rpz-nsdname relativized
+                    rpz-nsdname relativized
                     to the RPZ origin name.
                     NSIP triggers match IP addresses in A and
                     AAAA RRsets for domains that can be checked against NSDNAME
                     policy records.
-                  

-
RPZ-NSIP

-

+                  

+                

+
RPZ-NSIP

+

+                  

                     NSIP triggers are encoded like IP triggers except as
-                    subdomains of rpz-nsip.
+                    subdomains of rpz-nsip.
                     NSDNAME and NSIP triggers are checked only for names with at
-                    least min-ns-dots dots.
-                    The default value of min-ns-dots is 1 to
+                    least min-ns-dots dots.
+                    The default value of min-ns-dots is 1 to
                     exclude top level domains.
-                  

+                  

+                
 

 

           

-

+
+          

             The query response is checked against all response policy zones,
             so two or more policy records can be triggered by a response.
             Because DNS responses are rewritten according to at most one
             policy record, a single record encoding an action (other than
-            DISABLED actions) must be chosen.
+            DISABLED actions) must be chosen.
             Triggers or the records that encode them are chosen for the
             rewriting in the following order:
             

-
    
-
  1. Choose the triggered record in the zone that appears
-                first in the response-policy option.
+
      
+
    1. Choose the triggered record in the zone that appears
+                first in the response-policy option.
               
      2. 
-
    2. Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
+
    3. Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
                 triggers in a single zone.
               
      4. 
-
    4. Among NSDNAME triggers, prefer the
+
    5. Among NSDNAME triggers, prefer the
                 trigger that matches the smallest name under the DNSSEC ordering.
               
      6. 
-
    6. Among IP or NSIP triggers, prefer the trigger
+
    7. Among IP or NSIP triggers, prefer the trigger
                 with the longest prefix.
               
      8. 
-
    8. Among triggers with the same prefix length,
+
    9. Among triggers with the same prefix length,
                 prefer the IP or NSIP trigger that matches
                 the smallest IP address.
               
      10. 
 
    
 
    
           
    
-
    
+
+          
    
             When the processing of a response is restarted to resolve
             DNAME or CNAME records and a policy record set has
             not been triggered,
             all response policy zones are again consulted for the
             DNAME or CNAME names and addresses.
           
    
-
    
+
+          
    
             RPZ record sets are any types of DNS record except
             DNAME or DNSSEC that encode actions or responses to
             individual queries.
             Any of the policies can be used with any of the triggers.
-            For example, while the TCP-only policy is
-            commonly used with client-IP triggers,
+            For example, while the TCP-only policy is
+            commonly used with client-IP triggers,
             it can be used with any type of trigger to force the use of
             TCP for responses with owner names in a zone.
             
    
-
    
-
    PASSTHRU
    
-
    
+
    
+
    PASSTHRU
    
+
    
+                  
    
                     The whitelist policy is specified
-                    by a CNAME whose target is rpz-passthru.
+                    by a CNAME whose target is rpz-passthru.
                     It causes the response to not be rewritten
                     and is most often used to "poke holes" in policies for
                     CIDR blocks.
-                  
    
-
    DROP
    
-
    
+                  
    
+                
    
+
    DROP
    
+
    
+                  
    
                     The blacklist policy is specified
-                    by a CNAME whose target is rpz-drop.
+                    by a CNAME whose target is rpz-drop.
                     It causes the response to be discarded.
                     Nothing is sent to the DNS client.
-                  
    
-
    TCP-Only
    
-
    
+                  
    
+                
    
+
    TCP-Only
    
+
    
+                  
    
                     The "slip" policy is specified
-                    by a CNAME whose target is rpz-tcp-only.
+                    by a CNAME whose target is rpz-tcp-only.
                     It changes UDP responses to short, truncated DNS responses
                     that require the DNS client to try again with TCP.
                     It is used to mitigate distributed DNS reflection attacks.
-                  
    
-
    NXDOMAIN
    
-
    
+                  
    
+                
    
+
    NXDOMAIN
    
+
    
+                  
    
                     The domain undefined response is encoded
                     by a CNAME whose target is the root domain (.)
-                  
    
-
    NODATA
    
-
    
+                  
    
+                
    
+
    NODATA
    
+
    
+                  
    
                     The empty set of resource records is specified by
                     CNAME whose target is the wildcard top-level
                     domain (*.).
                     It rewrites the response to NODATA or ANCOUNT=1.
-                  
    
-
    Local Data
    
+                  
    
+                
    
+
    Local Data
    
 
    
-
    
+                  
    
                     A set of ordinary DNS records can be used to answer queries.
                     Queries for record types not the set are answered with
                     NODATA.
                   
    
-
    
+
+                  
    
                     A special form of local data is a CNAME whose target is a
                     wildcard such as *.example.com.
                     It is used as if were an ordinary CNAME after the astrisk (*)
@@ -7038,26 +7651,30 @@ deny-answer-aliases { "example.net"; };
                     The purpose for this special form is query logging in the
                     walled garden's authority DNS server.
                   
    
-
    
+                
 
    
 
    
           
    
-
    
+
+          
    
             All of the actions specified in all of the individual records
             in a policy zone
-            can be overridden with a policy clause in the
-            response-policy option.
+            can be overridden with a policy clause in the
+            response-policy option.
             An organization using a policy zone provided by another
             organization might use this mechanism to redirect domains
             to its own walled garden.
             
    
-
    
-
    GIVEN
    
-
    The placeholder policy says "do not override but
+
    
+
    GIVEN
    
+
    
+                  
    The placeholder policy says "do not override but
                     perform the action specified in the zone."
-                  
    
-
    DISABLED
    
-
    
+                  
    
+                
    
+
    DISABLED
    
+
    
+                  
    
                     The testing override policy causes policy zone records to do
                     nothing but log what they would have done if the
                     policy zone were not disabled.
@@ -7067,44 +7684,52 @@ deny-answer-aliases { "example.net"; };
                     Disabled policy zones should appear first,
                     because they will often not be logged
                     if a higher precedence trigger is found first.
-                  
    
+                  
    
+                
    
 
    
-PASSTHRU, DROP, TCP-Only, NXDOMAIN, NODATA
+PASSTHRU, DROP, TCP-Only, NXDOMAIN, NODATA
 
    
-
    
+
    
+                  
    
                     override with the corresponding per-record policy.
-                  
    
-
    CNAME domain
    
-
    
+                  
    
+                
    
+
    CNAME domain
    
+
    
+                    
    
                       causes all RPZ policy records to act as if they were
                       "cname domain" records.
-                    
    
+                    
    
+                  
 
    
 
    
           
    
-
    
+
+          
    
             By default, the actions encoded in a response policy zone
             are applied only to queries that ask for recursion (RD=1).
             That default can be changed for a single policy zone or
             all response policy zones in a view
-            with a recursive-only no clause.
+            with a recursive-only no clause.
             This feature is useful for serving the same zone files
             both inside and outside an RFC 1918 cloud and using RPZ to
             delete answers that would otherwise contain RFC 1918 values
             on the externally visible name server or view.
           
    
-
    
+
+          
    
             Also by default, RPZ actions are applied only to DNS requests
             that either do not request DNSSEC metadata (DO=0) or when no
             DNSSEC records are available for request name in the original
             zone (not the response policy zone).  This default can be
             changed for all response policy zones in a view with a
-            break-dnssec yes clause.  In that case, RPZ
+            break-dnssec yes clause.  In that case, RPZ
             actions are applied regardless of DNSSEC.  The name of the
             clause option reflects the fact that results rewritten by RPZ
             actions cannot verify.
           
    
-
    
+
+          
    
             No DNS records are needed for a QNAME or Client-IP trigger.
             The name or IP address itself is sufficient,
             so in principle the query name need not be recursively resolved.
@@ -7116,7 +7741,7 @@ deny-answer-aliases { "example.net"; };
             policy triggers are considered.  Because listed domains often
             have slow authoritative servers, this default behavior can cost
             significant time.
-            The qname-wait-recurse no option
+            The qname-wait-recurse no option
             overrides that default behavior when recursion cannot
             change a non-error response.
             The option does not affect QNAME or client-IP triggers
@@ -7124,29 +7749,31 @@ deny-answer-aliases { "example.net"; };
             after other zones containing IP, NSIP and NSDNAME triggers, because
             those may depend on the A, AAAA, and NS records that would be
             found during recursive resolution.  It also does not affect
-            DNSSEC requests (DO=1) unless break-dnssec yes
+            DNSSEC requests (DO=1) unless break-dnssec yes
             is in use, because the response would depend on whether or not
             RRSIG records were found during resolution.
             Using this option can cause error responses such as SERVFAIL to
             appear to be rewritten, since no recursion is being done to
             discover problems at the authoritative server.
           
    
-
    
+
+          
    
             The TTL of a record modified by RPZ policies is set from the
             TTL of the relevant record in policy zone.  It is then limited
             to a maximum value.
-            The max-policy-ttl clause changes the
+            The max-policy-ttl clause changes the
             maximum seconds from its default of 5.
           
    
-
    
+
+          
    
             For example, you might use this option statement
           
    
 
        response-policy { zone "badlist"; };
    
-
    
+          
    
             and this zone statement
           
    
 
        zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };
    
-
    
+          
    
             with this zone file
           
    
 
    $TTL 1H
@@ -7188,7 +7815,7 @@ example.com                 CNAME   rpz-tcp-only.
 *.example.com               CNAME   rpz-tcp-only.
 
 
    
-
    
+          
    
             RPZ can affect server performance.
             Each configured response policy zone requires the server to
             perform one to four additional database lookups before a
@@ -7203,24 +7830,28 @@ example.com                 CNAME   rpz-tcp-only.
             A server with four response policy zones with QNAME and IP
             triggers might have a maximum QPS rate about 50% lower.
           
    
-
    
+
+          
    
             Responses rewritten by RPZ are counted in the
-            RPZRewrites statistics.
+            RPZRewrites statistics.
           
    
-
    
-            The log clause can be used to optionally
+
+          
    
+            The log clause can be used to optionally
             turn off rewrite logging for a particular response policy
             zone. By default, all rewrites are logged.
           
    
-

-

+        

+
+        

 

-Response Rate Limiting

-

+Response Rate Limiting

+          
+          

             Excessive almost identical UDP responses
             can be controlled by configuring a
-            rate-limit clause in an
-            options or view statement.
+            rate-limit clause in an
+            options or view statement.
             This mechanism keeps authoritative BIND 9 from being used
             in amplifying reflection denial of service (DoS) attacks.
             Short truncated (TC=1) responses can be sent to provide
@@ -7229,7 +7860,8 @@ example.com                 CNAME   rpz-tcp-only.
             Legitimate clients react to dropped or truncated response
             by retrying with UDP or with TCP respectively.
           

-

+
+          

             This mechanism is intended for authoritative DNS servers.
             It can be used on recursive servers but can slow
             applications such as SMTP servers (mail receivers) and
@@ -7237,7 +7869,8 @@ example.com                 CNAME   rpz-tcp-only.
             same domains.
             When possible, closing "open" recursive servers is better.
           

-

+
+          

             Response rate limiting uses a "credit" or "token bucket" scheme.
             Each combination of identical response and client
             has a conceptual account that earns a specified number
@@ -7247,65 +7880,70 @@ example.com                 CNAME   rpz-tcp-only.
             while the account is negative.
             Responses are tracked within a rolling window of time
             which defaults to 15 seconds, but can be configured with
-            the window option to any value from
+            the window option to any value from
             1 to 3600 seconds (1 hour).
             The account cannot become more positive than
             the per-second limit
-            or more negative than window
+            or more negative than window
             times the per-second limit.
             When the specified number of credits for a class of
             responses is set to 0, those responses are not rate limited.
           

-

+
+          

             The notions of "identical response" and "DNS client"
             for rate limiting are not simplistic.
             All responses to an address block are counted as if to a
             single client.
             The prefix lengths of addresses blocks are
-            specified with ipv4-prefix-length (default 24)
-            and ipv6-prefix-length (default 56).
+            specified with ipv4-prefix-length (default 24)
+            and ipv6-prefix-length (default 56).
           

-

+
+          

             All non-empty responses for a valid domain name (qname)
             and record type (qtype) are identical and have a limit specified
-            with responses-per-second
+            with responses-per-second
             (default 0 or no limit).
             All empty (NODATA) responses for a valid domain,
             regardless of query type, are identical.
             Responses in the NODATA class are limited by
-            nodata-per-second
-            (default responses-per-second).
+            nodata-per-second
+            (default responses-per-second).
             Requests for any and all undefined subdomains of a given
             valid domain result in NXDOMAIN errors, and are identical
             regardless of query type.
-            They are limited by nxdomains-per-second
-            (default responses-per-second).
+            They are limited by nxdomains-per-second
+            (default responses-per-second).
             This controls some attacks using random names, but
             can be relaxed or turned off (set to 0)
             on servers that expect many legitimate
             NXDOMAIN responses, such as from anti-spam blacklists.
             Referrals or delegations to the server of a given
             domain are identical and are limited by
-            referrals-per-second
-            (default responses-per-second).
+            referrals-per-second
+            (default responses-per-second).
           

-

+
+          

             Responses generated from local wildcards are counted and limited
             as if they were for the parent domain name.
             This controls flooding using random.wild.example.com.
           

-

+
+          

             All requests that result in DNS errors other
             than NXDOMAIN, such as SERVFAIL and FORMERR, are identical
             regardless of requested name (qname) or record type (qtype).
             This controls attacks using invalid requests or distant,
             broken authoritative servers.
             By default the limit on errors is the same as the
-            responses-per-second value,
+            responses-per-second value,
             but it can be set separately with
-            errors-per-second.
+            errors-per-second.
           

-

+
+          

             Many attacks using DNS involve UDP requests with forged source
             addresses.
             Rate limiting prevents the use of BIND 9 to flood a network
@@ -7313,13 +7951,13 @@ example.com                 CNAME   rpz-tcp-only.
             but could let a third party block responses to legitimate requests.
             There is a mechanism that can answer some legitimate
             requests from a client whose address is being forged in a flood.
-            Setting slip to 2 (its default) causes every
+            Setting slip to 2 (its default) causes every
             other UDP request to be answered with a small truncated (TC=1)
             response.
             The small size and reduced frequency, and so lack of
             amplification, of "slipped" responses make them unattractive
             for reflection DoS attacks.
-            slip must be between 0 and 10.
+            slip must be between 0 and 10.
             A value of 0 does not "slip":
             no truncated responses are sent due to rate limiting,
             all responses are dropped.
@@ -7327,9 +7965,10 @@ example.com                 CNAME   rpz-tcp-only.
             values between 2 and 10 cause every n'th response to slip.
             Some error responses including REFUSED and SERVFAIL
             cannot be replaced with truncated responses and are instead
-            leaked at the slip rate.
+            leaked at the slip rate.
           

-

+
+          

             (NOTE: Dropped responses from an authoritative server may
             reduce the difficulty of a third party successfully forging
             a response to a recursive resolver. The best security
@@ -7338,21 +7977,22 @@ example.com                 CNAME   rpz-tcp-only.
             to validate the responses. When this is not an option,
             operators who are more concerned with response integrity
             than with flood mitigation may consider setting
-            slip to 1, causing all rate-limited
+            slip to 1, causing all rate-limited
             responses to be truncated rather than dropped.  This reduces
             the effectiveness of rate-limiting against reflection attacks.)
           

-

+
+          

             When the approximate query per second rate exceeds
-            the qps-scale value,
-            then the responses-per-second,
-            errors-per-second,
-            nxdomains-per-second and
-            all-per-second values are reduced by the
-            ratio of the current rate to the qps-scale value.
+            the qps-scale value,
+            then the responses-per-second,
+            errors-per-second,
+            nxdomains-per-second and
+            all-per-second values are reduced by the
+            ratio of the current rate to the qps-scale value.
             This feature can tighten defenses during attacks.
             For example, with
-            qps-scale 250; responses-per-second 20; and
+            qps-scale 250; responses-per-second 20; and
             a total query rate of 1000 queries/second for all queries from
             all DNS clients including via TCP,
             then the effective responses/second limit changes to
@@ -7360,56 +8000,61 @@ example.com                 CNAME   rpz-tcp-only.
             Responses sent via TCP are not limited
             but are counted to compute the query per second rate.
           

-

-            The optional domain clause specifies
+
+          

+            The optional domain clause specifies
             the namespace to which rate limits will apply.  It
             is possible to use different rate limits for different names
-            by specifying multiple rate-limit blocks
-            with different domain clauses.
-            The rate-limit statement's
-            domain most closely matches the query
+            by specifying multiple rate-limit blocks
+            with different domain clauses.
+            The rate-limit statement's
+            domain most closely matches the query
             name will be the one applied to a given query.
           

-

+
+          

             Rate limiters for different name spaces maintain
             separate counters: If, for example, there is a
-            rate-limit statement for "com" and
+            rate-limit statement for "com" and
             another for "example.com", queries matching "example.com"
             will not be debited against the rate limiter for "com".
           

-

-            If a rate-limit statement does not specify a
-            domain, then it applies to the root domain
+
+          

+            If a rate-limit statement does not specify a
+            domain, then it applies to the root domain
             (".") and thus affects the entire DNS namespace, except those
-            portions covered by other rate-limit
+            portions covered by other rate-limit
             statements.
           

-

+
+          

             Communities of DNS clients can be given their own parameters or no
             rate limiting by putting
-            rate-limit statements in view
-            statements instead of the global option
+            rate-limit statements in view
+            statements instead of the global option
             statement.
-            A rate-limit statement in a view replaces,
-            rather than supplementing, a rate-limit
+            A rate-limit statement in a view replaces,
+            rather than supplementing, a rate-limit
             statement among the main options.
             DNS clients within a view can be exempted from rate limits
-            with the exempt-clients clause.
+            with the exempt-clients clause.
           

-

+
+          

             UDP responses of all kinds can be limited with the
-            all-per-second phrase.  This rate
+            all-per-second phrase.  This rate
             limiting is unlike the rate limiting provided by
-            responses-per-second,
-            errors-per-second, and
-            nxdomains-per-second on a DNS server
+            responses-per-second,
+            errors-per-second, and
+            nxdomains-per-second on a DNS server
             which are often invisible to the victim of a DNS
             reflection attack.  Unless the forged requests of the
             attack are the same as the legitimate requests of the
             victim, the victim's requests are not affected.  Responses
-            affected by an all-per-second limit
-            are always dropped; the slip value
-            has no effect.  An all-per-second
+            affected by an all-per-second limit
+            are always dropped; the slip value
+            has no effect.  An all-per-second
             limit should be at least 4 times as large as the other
             limits, because single DNS clients often send bursts
             of legitimate requests.  For example, the receipt of a
@@ -7417,10 +8062,10 @@ example.com                 CNAME   rpz-tcp-only.
             server for NS, PTR, A, and AAAA records as the incoming
             SMTP/TCP/IP connection is considered.  The SMTP server
             can need additional NS, A, AAAA, MX, TXT, and SPF records
-            as it considers the STMP Mail From
+            as it considers the STMP Mail From
             command.  Web browsers often repeatedly resolve the
             same names that are repeated in HTML <IMG> tags
-            in a page.  all-per-second is similar
+            in a page.  all-per-second is similar
             to the rate limiting offered by firewalls but often
             inferior.  Attacks that justify ignoring the contents
             of DNS responses are likely to be attacks on the DNS
@@ -7429,60 +8074,63 @@ example.com                 CNAME   rpz-tcp-only.
             or parsing DNS requests, but that rate limiting must
             be done before the DNS server sees the requests.
           

-

+
+          

             The maximum size of the table used to track requests and
-            rate limit responses is set with max-table-size.
+            rate limit responses is set with max-table-size.
             Each entry in the table is between 40 and 80 bytes.
             The table needs approximately as many entries as the number
             of requests received per second.
             The default is 20,000.
             To reduce the cold start of growing the table,
-            min-table-size (default 500)
+            min-table-size (default 500)
             can set the minimum table size.
-            Enable rate-limit category logging to monitor
+            Enable rate-limit category logging to monitor
             expansions of the table and inform
             choices for the initial and maximum table size.
           

-

-            Use log-only yes to test rate limiting parameters
+
+          

+            Use log-only yes to test rate limiting parameters
             without actually dropping any requests.
           

-

+
+          

             Responses dropped by rate limits are included in the
-            RateDropped and QryDropped
+            RateDropped and QryDropped
             statistics.
             Responses that truncated by rate limits are included in
-            RateSlipped and RespTruncated.
+            RateSlipped and RespTruncated.
           

-
-

+        

+
+        

 

-

+          

             Named supports NXDOMAIN redirection via two methods:
             

-
    
-
  • Redirect zone the section called “zone
+
    
 
    
           
    
-
    
+          
    
             With both methods when named gets a NXDOMAIN response
             it examines a seperate namespace to see if the NXDOMAIN
             response should be replaced with a alternative response.
           
    
-
    
-            With a redirect zone (zone "." { type redirect; };), the
+          
    
+            With a redirect zone (zone "." { type redirect; };), the
             data used to replace the NXDOMAIN is held in a single
             zone which is not part of the normal namespace.  All the
             redirect information is contained in the zone; there are
             no delegations.
           
    
-
    
-            With a redirect namespace (option { nxdomain-redirect
+          
    
+            With a redirect namespace (option { nxdomain-redirect
             <suffix> };) the data used to replace the
             NXDOMAIN is part of the normal namespace and is looked up by
             appending the specified suffix to the original query name.
@@ -7491,16 +8139,19 @@ example.com                 CNAME   rpz-tcp-only.
             the replacement data or a NXDOMAIN indicating that there
             is no replacement.
           
    
-
    
+          
    
             If both a redirect zone and a redirect namespace are configured,
             the redirect zone is tried first.
           
    
-

-

-

+        

+      
+
+      

 

-server Statement Grammar

-
server ip_addr[/prefixlen] {
+server Statement Grammar

+        
+
+
server ip_addr[/prefixlen] {
     [ bogus yes_or_no ; ]
     [ provide-ixfr yes_or_no ; ]
     [ request-ixfr yes_or_no ; ]
@@ -7528,13 +8179,17 @@ example.com                 CNAME   rpz-tcp-only.
     [ queryport-pool-updateinterval number; ]
 };
 

-
-

+
+        

+
+        

 

-server Statement Definition and
+server Statement Definition and
             Usage

-

-            The server statement defines
+          
+
+          

+            The server statement defines
             characteristics
             to be associated with a remote name server.  If a prefix length is
             specified, then a range of servers is covered.  Only the most
@@ -7542,69 +8197,74 @@ example.com                 CNAME   rpz-tcp-only.
             server clause applies regardless of the order in
             named.conf.
           

-

-            The server statement can occur at
+
+          

+            The server statement can occur at
             the top level of the
-            configuration file or inside a view
+            configuration file or inside a view
             statement.
-            If a view statement contains
-            one or more server statements, only
+            If a view statement contains
+            one or more server statements, only
             those
             apply to the view and any top-level ones are ignored.
-            If a view contains no server
+            If a view contains no server
             statements,
-            any top-level server statements are
+            any top-level server statements are
             used as
             defaults.
           

-

+
+          

             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 no.
+            value of bogus is no.
           

-

-            The provide-ixfr clause determines
+          

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

-

-            The request-ixfr clause determines
+
+          

+            The request-ixfr clause determines
             whether
             the local server, acting as a slave, will request incremental zone
             transfers from the given remote server, a master. If not set, the
-            value of the request-ixfr option in
+            value of the request-ixfr option in
             the view or global options block is used as a default. It may
             also be set in the zone block and, if set there, it will
             override the global or view setting for that zone.
           

-

+
+          

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

-

-            The request-expire clause determines
+
+          

+            The request-expire clause determines
             whether the local server, when acting as a slave, will
             request the EDNS EXPIRE value.  The EDNS EXPIRE value
             indicates the remaining time before the zone data will
@@ -7613,16 +8273,18 @@ example.com                 CNAME   rpz-tcp-only.
             secondary server; when transferring from the primary, the
             expiration timer is set from the EXPIRE field of the SOA
             record instead.
-            The default is yes.
+            The default is yes.
           

-

-            The edns clause determines whether
+
+          

+            The edns clause determines whether
             the local server will attempt to use EDNS when communicating
-            with the remote server.  The default is yes.
+            with the remote server.  The default is yes.
           

-

-            The edns-udp-size option sets the
-            EDNS UDP size that is advertised by named
+
+          

+            The edns-udp-size option sets the
+            EDNS UDP size that is advertised by named
             when querying the remote server.  Valid values are 512
             to 4096 bytes (values outside this range will be silently
             adjusted to the nearest value within it).  This option
@@ -7631,16 +8293,17 @@ example.com                 CNAME   rpz-tcp-only.
             for example, when there is a firewall at the remote
             site that is blocking large replies. (Note: Currently,
             this sets a single UDP size for all packets sent to the
-            server; named will not deviate from
+            server; named will not deviate from
             this value.  This differs from the behavior of
-            edns-udp-size in options
-            or view statements, where it specifies
-            a maximum value. The server statement
+            edns-udp-size in options
+            or view statements, where it specifies
+            a maximum value. The server statement
             behavior may be brought into conformance with the
-            options/view behavior in future releases.)
+            options/view behavior in future releases.)
           

-

-            The edns-version option sets the
+
+          

+            The edns-version option sets the
             maximum EDNS VERSION that will be sent to the server(s)
             by the resolver.  The actual EDNS version sent is still
             subject to normal EDNS version negotiation rules (see
@@ -7654,45 +8317,50 @@ example.com                 CNAME   rpz-tcp-only.
             adjusted.  This option will not be needed until higher
             EDNS versions than 0 are in use.
           

-

-            The max-udp-size option sets the
-            maximum EDNS UDP message size named
+
+          

+            The max-udp-size option sets the
+            maximum EDNS UDP message size named
             will send.  Valid values are 512 to 4096 bytes (values
             outside this range will be silently adjusted).  This
             option is useful when you know that there is a firewall
-            that is blocking large replies from named.
+            that is blocking large replies from named.
           

-

-            The tcp-only option sets the transport
+
+          

+            The tcp-only option sets the transport
             protocol to TCP. The default is to use the UDP transport
             and to fallback on TCP only when a truncated response
             is received.
           

-

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

+            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 transfer-format option.
-            If transfer-format is not
-            specified, the transfer-format
+            to use for a server with the transfer-format option.
+            If transfer-format is not
+            specified, the transfer-format
             specified
-            by the options statement will be
+            by the options statement will be
             used.
           

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

-

-            The keys clause identifies a
-            key_id defined by the key statement,
-            to be used for transaction security (TSIG, the section called “TSIG”)
+
+          

+            The keys clause identifies a
+            key_id defined by the key statement,
+            to be used for transaction security (TSIG, the section called “TSIG”)
             when talking to the remote server.
             When a request is sent to the remote server, a request signature
             will be generated using the key specified here and appended to the
@@ -7700,197 +8368,223 @@ example.com                 CNAME   rpz-tcp-only.
             required
             to be signed by this key.
           

-

+
+          

             Only a single key per server is currently supported.
           

-

-            The transfer-source and
-            transfer-source-v6 clauses specify
+
+          

+            The transfer-source and
+            transfer-source-v6 clauses specify
             the IPv4 and IPv6 source
             address to be used for zone transfer with the remote server,
             respectively.
-            For an IPv4 remote server, only transfer-source can
+            For an IPv4 remote server, only transfer-source can
             be specified.
             Similarly, for an IPv6 remote server, only
-            transfer-source-v6 can be
+            transfer-source-v6 can be
             specified.
             For more details, see the description of
-            transfer-source and
-            transfer-source-v6 in
-            the section called “Zone Transfers”.
+            transfer-source and
+            transfer-source-v6 in
+            the section called “Zone Transfers”.
           

-

-            The notify-source and
-            notify-source-v6 clauses specify the
+
+          

+            The notify-source and
+            notify-source-v6 clauses specify the
             IPv4 and IPv6 source address to be used for notify
             messages sent to remote servers, respectively.  For an
-            IPv4 remote server, only notify-source
+            IPv4 remote server, only notify-source
             can be specified.  Similarly, for an IPv6 remote server,
-            only notify-source-v6 can be specified.
+            only notify-source-v6 can be specified.
           

-

-            The query-source and
-            query-source-v6 clauses specify the
+
+          

+            The query-source and
+            query-source-v6 clauses specify the
             IPv4 and IPv6 source address to be used for queries
             sent to remote servers, respectively.  For an IPv4
-            remote server, only query-source can
+            remote server, only query-source can
             be specified.  Similarly, for an IPv6 remote server,
-            only query-source-v6 can be specified.
+            only query-source-v6 can be specified.
           

-

-            The request-nsid clause determines
+
+          

+            The request-nsid clause determines
             whether the local server will add a NSID EDNS option
             to requests sent to the server.  This overrides
-            request-nsid set at the view or
+            request-nsid set at the view or
             option level.
           

-

-            The send-cookie clause determines
+
+          

+            The send-cookie clause determines
             whether the local server will add a COOKIE EDNS option
             to requests sent to the server.  This overrides
-            send-cookie set at the view or
-            option level.  The named server may
+            send-cookie set at the view or
+            option level.  The named server may
             determine that COOKIE is not supported by the remote server
             and not add a COOKIE EDNS option to requests.
           

-

-

+        

+
+      

 

-statistics-channels Statement Grammar

-
statistics-channels {
+statistics-channels Statement Grammar

+        
+
+
statistics-channels {
    [ inet ( ip_addr | * ) [ port ip_port ]
    [ allow {  address_match_list  } ]; ]
    [ inet ...; ]
 };
 

-
-

+      

+
+      

 

-statistics-channels Statement Definition and
+statistics-channels Statement Definition and
             Usage

-

-          The statistics-channels statement
+          
+
+        

+          The statistics-channels statement
           declares communication channels to be used by system
           administrators to get access to statistics information of
           the name server.
         

-

+
+        

           This statement intends to be flexible to support multiple
           communication protocols in the future, but currently only
           HTTP access is supported.
           It requires that BIND 9 be compiled with libxml2 and/or
           json-c (also known as libjson0); the
-          statistics-channels statement is
+          statistics-channels statement is
           still accepted even if it is built without the library,
           but any HTTP access will fail with an error.
         

-

-          An inet control channel is a TCP socket
-          listening at the specified ip_port on the
-          specified ip_addr, which can be an IPv4 or IPv6
-          address.  An ip_addr of *
+
+        

+          An inet control channel is a TCP socket
+          listening at the specified ip_port on the
+          specified ip_addr, which can be an IPv4 or IPv6
+          address.  An ip_addr of *
           (asterisk) is
           interpreted as the IPv4 wildcard address; connections will be
           accepted on any of the system's IPv4 addresses.
           To listen on the IPv6 wildcard address,
-          use an ip_addr of ::.
+          use an ip_addr of ::.
         

-

+
+        

           If no port is specified, port 80 is used for HTTP channels.
           The asterisk "*" cannot be used for
-          ip_port.
+          ip_port.
         

-

+
+        

           The attempt of opening a statistics channel is
-          restricted by the optional allow clause.
+          restricted by the optional allow clause.
           Connections to the statistics channel are permitted based on the
-          address_match_list.
-          If no allow clause is present,
-          named accepts connection
+          address_match_list.
+          If no allow clause is present,
+          named accepts connection
           attempts from any address; since the statistics may
           contain sensitive internal information, it is highly
           recommended to restrict the source of connection requests
           appropriately.
         

-

-          If no statistics-channels statement is present,
-          named will not open any communication channels.
+
+        

+          If no statistics-channels statement is present,
+          named will not open any communication channels.
         

-

+
+        

           The statistics are available in various formats and views
           depending on the URI used to access them.  For example, if
           the statistics channel is configured to listen on 127.0.0.1
           port 8888, then the statistics are accessible in XML format at
-          http://127.0.0.1:8888/ or
-          http://127.0.0.1:8888/xml. A CSS file is
+          http://127.0.0.1:8888/ or
+          http://127.0.0.1:8888/xml. A CSS file is
           included which can format the XML statistics into tables
           when viewed with a stylesheet-capable browser, and into
           charts and graphs using the Google Charts API when using a
           javascript-capable browser.
         

-

+
+        

           Applications that depend on a particular XML schema
           can request
-          http://127.0.0.1:8888/xml/v2 for version 2
+          http://127.0.0.1:8888/xml/v2 for version 2
           of the statistics XML schema or
-          http://127.0.0.1:8888/xml/v3 for version 3.
+          http://127.0.0.1:8888/xml/v3 for version 3.
           If the requested schema is supported by the server, then
           it will respond; if not, it will return a "page not found"
           error.
         

-

+
+        

           Broken-out subsets of the statistics can be viewed at
-          http://127.0.0.1:8888/xml/v3/status
+          http://127.0.0.1:8888/xml/v3/status
           (server uptime and last reconfiguration time),
-          http://127.0.0.1:8888/xml/v3/server
+          http://127.0.0.1:8888/xml/v3/server
           (server and resolver statistics),
-          http://127.0.0.1:8888/xml/v3/zones
+          http://127.0.0.1:8888/xml/v3/zones
           (zone statistics),
-          http://127.0.0.1:8888/xml/v3/net
+          http://127.0.0.1:8888/xml/v3/net
           (network status and socket statistics),
-          http://127.0.0.1:8888/xml/v3/mem
+          http://127.0.0.1:8888/xml/v3/mem
           (memory manager statistics),
-          http://127.0.0.1:8888/xml/v3/tasks
+          http://127.0.0.1:8888/xml/v3/tasks
           (task manager statistics), and
-          http://127.0.0.1:8888/xml/v3/traffic
+          http://127.0.0.1:8888/xml/v3/traffic
           (traffic sizes).
         

-

+
+        

           The full set of statistics can also be read in JSON format at
-          http://127.0.0.1:8888/json,
+          http://127.0.0.1:8888/json,
           with the broken-out subsets at
-          http://127.0.0.1:8888/json/v1/status
+          http://127.0.0.1:8888/json/v1/status
           (server uptime and last reconfiguration time),
-          http://127.0.0.1:8888/json/v1/server
+          http://127.0.0.1:8888/json/v1/server
           (server and resolver statistics),
-          http://127.0.0.1:8888/json/v1/zones
+          http://127.0.0.1:8888/json/v1/zones
           (zone statistics),
-          http://127.0.0.1:8888/json/v1/net
+          http://127.0.0.1:8888/json/v1/net
           (network status and socket statistics),
-          http://127.0.0.1:8888/json/v1/mem
+          http://127.0.0.1:8888/json/v1/mem
           (memory manager statistics),
-          http://127.0.0.1:8888/json/v1/tasks
+          http://127.0.0.1:8888/json/v1/tasks
           (task manager statistics), and
-          http://127.0.0.1:8888/json/v1/traffic
+          http://127.0.0.1:8888/json/v1/traffic
           (traffic sizes).
         

-

-

+      

+
+        

 

-trusted-keys Statement Grammar

-
trusted-keys {
+trusted-keys Statement Grammar

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

-
-

+
+        

+        

 

-trusted-keys Statement Definition
+trusted-keys Statement Definition
             and Usage

-

-            The trusted-keys statement defines
-            DNSSEC security roots. DNSSEC is described in the section called “DNSSEC”. A security root is defined when the
+          
+          

+            The trusted-keys statement defines
+            DNSSEC security roots. DNSSEC is described in the section called “DNSSEC”. A security root is defined when the
             public key for a non-authoritative zone is known, but
             cannot be securely obtained through DNS, either because
             it is the DNS root zone or because its parent zone is
@@ -7899,16 +8593,16 @@ example.com                 CNAME   rpz-tcp-only.
             proven secure. The resolver attempts DNSSEC validation
             on all DNS data in subdomains of a security root.
           

-

+          

             All keys (and corresponding zones) listed in
-            trusted-keys are deemed to exist regardless
+            trusted-keys are deemed to exist regardless
             of what parent zones say.  Similarly for all keys listed in
-            trusted-keys only those keys are
+            trusted-keys only those keys are
             used to validate the DNSKEY RRset.  The parent's DS RRset
             will not be used.
           

-

-            The trusted-keys statement can contain
+          

+            The trusted-keys statement can contain
             multiple key entries, each consisting of the key's
             domain name, flags, protocol, algorithm, and the Base-64
             representation of the key data.
@@ -7916,116 +8610,121 @@ example.com                 CNAME   rpz-tcp-only.
             in the key data, so the configuration may be split up into
             multiple lines.
           

-

-            trusted-keys may be set at the top level
+          

+            trusted-keys may be set at the top level
             of named.conf or within a view.  If it is
             set in both places, they are additive: keys defined at the top
             level are inherited by all views, but keys defined in a view
             are only used within that view.
           

-

+          

             Validation below specified names can be temporarily disabled
-            by using rndc nta.
+            by using rndc nta.
           

-

-

+        

+
+        

 

-managed-keys Statement Grammar

-
managed-keys {
+managed-keys Statement Grammar

+          
+
+
managed-keys {
     name initial-key flags protocol algorithm key-data ;
     [ name initial-key flags protocol algorithm key-data ; [...]]
 };
 

-
-

+
+        

+        

 

-managed-keys Statement Definition
+managed-keys Statement Definition
             and Usage

-

-            The managed-keys statement, like
-            trusted-keys, defines DNSSEC
+          
+          

+            The managed-keys statement, like
+            trusted-keys, defines DNSSEC
             security roots.  The difference is that
-            managed-keys can be kept up to date
+            managed-keys can be kept up to date
             automatically, without intervention from the resolver
             operator.
           

-

+          

             Suppose, for example, that a zone's key-signing
             key was compromised, and the zone owner had to revoke and
             replace the key.  A resolver which had the old key in a
-            trusted-keys statement would be
+            trusted-keys statement would be
             unable to validate this zone any longer; it would
             reply with a SERVFAIL response code.  This would
             continue until the resolver operator had updated the
-            trusted-keys statement with the new key.
+            trusted-keys statement with the new key.
           

-

+          

             If, however, the zone were listed in a
-            managed-keys statement instead, then the
+            managed-keys statement instead, then the
             zone owner could add a "stand-by" key to the zone in advance.
-            named would store the stand-by key, and
-            when the original key was revoked, named
+            named would store the stand-by key, and
+            when the original key was revoked, named
             would be able to transition smoothly to the new key.  It would
             also recognize that the old key had been revoked, and cease
             using that key to validate answers, minimizing the damage that
             the compromised key could do.
           

-

-            A managed-keys statement contains a list of
+          

+            A managed-keys statement contains a list of
             the keys to be managed, along with information about how the
             keys are to be initialized for the first time.  The only
             initialization method currently supported (as of
             BIND 9.7.0) is initial-key.
-            This means the managed-keys statement must
+            This means the managed-keys statement must
             contain a copy of the initializing key.  (Future releases may
             allow keys to be initialized by other methods, eliminating this
             requirement.)
           

-

-            Consequently, a managed-keys statement
-            appears similar to a trusted-keys, differing
+          

+            Consequently, a managed-keys statement
+            appears similar to a trusted-keys, differing
             in the presence of the second field, containing the keyword
             initial-key.  The difference is, whereas the
-            keys listed in a trusted-keys continue to be
+            keys listed in a trusted-keys continue to be
             trusted until they are removed from
             named.conf, an initializing key listed
-            in a managed-keys statement is only trusted
+            in a managed-keys statement is only trusted
             once: for as long as it takes to load the
             managed key database and start the RFC 5011 key maintenance
             process.
           

-

-            The first time named runs with a managed key
+          

+            The first time named runs with a managed key
             configured in named.conf, it fetches the
             DNSKEY RRset directly from the zone apex, and validates it
-            using the key specified in the managed-keys
+            using the key specified in the managed-keys
             statement.  If the DNSKEY RRset is validly signed, then it is
             used as the basis for a new managed keys database.
           

-

-            From that point on, whenever named runs, it
-            sees the managed-keys statement, checks to
+          

+            From that point on, whenever named runs, it
+            sees the managed-keys statement, checks to
             make sure RFC 5011 key maintenance has already been initialized
             for the specified domain, and if so, it simply moves on.  The
-            key specified in the managed-keys is not
+            key specified in the managed-keys is not
             used to validate answers; it has been superseded by the key or
             keys stored in the managed keys database.
           

-

-            The next time named runs after a name
+          

+            The next time named runs after a name
             has been removed from the
-            managed-keys statement, the corresponding
+            managed-keys statement, the corresponding
             zone will be removed from the managed keys database,
             and RFC 5011 key maintenance will no longer be used for that
             domain.
           

-

-            named only maintains a single managed keys
-            database; consequently, unlike trusted-keys,
-            managed-keys may only be set at the top
+          

+            named only maintains a single managed keys
+            database; consequently, unlike trusted-keys,
+            managed-keys may only be set at the top
             level of named.conf, not within a view.
           

-

+          

             In the current implementation, the managed keys database is
             stored as a master-format zone file called
             managed-keys.bind.  When the key database
@@ -8034,29 +8733,32 @@ example.com                 CNAME   rpz-tcp-only.
             managed-keys.bind.jnl.  They are committed
             to the master file as soon as possible afterward; in the case
             of the managed key database, this will usually occur within 30
-            seconds.  So, whenever named is using
+            seconds.  So, whenever named is using
             automatic key maintenance, those two files can be expected to
             exist in the working directory.  (For this reason among others,
             the working directory should be always be writable by
-            named.)
+            named.)
           

-

-            If the dnssec-validation option is
-            set to auto, named
+          

+            If the dnssec-validation option is
+            set to auto, named
             will automatically initialize a managed key for the
-            root zone.  Similarly, if the dnssec-lookaside
+            root zone.  Similarly, if the dnssec-lookaside
             option is set to auto,
-            named will automatically initialize
+            named will automatically initialize
             a managed key for the zone dlv.isc.org.
             In both cases, the key that is used to initialize the key
-            maintenance process is built into named,
-            and can be overridden from bindkeys-file.
+            maintenance process is built into named,
+            and can be overridden from bindkeys-file.
           

-

-

+        

+
+        

 

-view Statement Grammar

-
view view_name
+view Statement Grammar

+          
+
+
view view_name
       [class] {
       match-clients { address_match_list };
       match-destinations { address_match_list };
@@ -8065,12 +8767,15 @@ example.com                 CNAME   rpz-tcp-only.
       [ zone_statement; ...]
 };
 

-
-

+
+        

+        

 

-view Statement Definition and Usage

-

-            The view statement is a powerful
+view Statement Definition and Usage

+          
+
+          

+            The view statement is a powerful
             feature
             of BIND 9 that lets a name server
             answer a DNS query differently
@@ -8078,81 +8783,88 @@ example.com                 CNAME   rpz-tcp-only.
             implementing
             split DNS setups without having to run multiple servers.
           

-

-            Each view statement defines a view
+
+          

+            Each view statement defines a view
             of the
             DNS namespace that will be seen by a subset of clients.  A client
             matches
             a view if its source IP address matches the
             address_match_list of the view's
-            match-clients clause and its
+            match-clients clause and its
             destination IP address matches
             the address_match_list of the
             view's
-            match-destinations clause.  If not
+            match-destinations clause.  If not
             specified, both
-            match-clients and match-destinations
+            match-clients and match-destinations
             default to matching all addresses.  In addition to checking IP
             addresses
-            match-clients and match-destinations
-            can also take keys which provide an
+            match-clients and match-destinations
+            can also take keys which provide an
             mechanism for the
             client to select the view.  A view can also be specified
-            as match-recursive-only, which
+            as match-recursive-only, which
             means that only recursive
             requests from matching clients will match that view.
-            The order of the view statements is
+            The order of the view statements is
             significant —
             a client request will be resolved in the context of the first
-            view that it matches.
+            view that it matches.
           

-

-            Zones defined within a view
+
+          

+            Zones defined within a view
             statement will
-            only be accessible to clients that match the view.
+            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, for example,
             "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
+
+          

+            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
             view-specific
-            value is given, the value in the options statement
+            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
+            in the view statement; these
             view-specific defaults
-            take precedence over those in the options statement.
+            take precedence over those in the options statement.
           

-

+
+          

             Views are class specific.  If no class is given, class IN
             is assumed.  Note that all non-IN views must contain a hint zone,
             since only the IN class has compiled-in default hints.
           

-

-            If there are no view statements in
+
+          

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

-

+
+          

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

+
 
view "internal" {
       // This should match our internal networks.
       match-clients { 10.0.0.0/8; };
@@ -8185,12 +8897,15 @@ view "external" {
       };
 };
 

-
-

+
+        

+        

 

-zone
+zone
             Statement Grammar

-
zone zone_name [class] {
+          
+
+
zone zone_name [class] {
     type master;
     [ allow-query { address_match_list }; ]
     [ allow-query-on { address_match_list }; ]
@@ -8387,27 +9102,31 @@ zone zone_name [
-

-

+
+        

+        

 

-zone Statement Definition and Usage

-

+zone Statement Definition and Usage

+          
+          

 

-Zone Types

-

-              The type keyword is required
-              for the zone configuration unless
-              it is an in-view configuration. Its
+Zone Types

+            

+              The type keyword is required
+              for the zone configuration unless
+              it is an in-view configuration. Its
               acceptable values include: delegation-only,
               forward, hint,
               master, redirect,
               slave, static-stub,
               and stub.
             

-

+            
+            

+              
--++
@@ -8434,7 +9153,7 @@ zone zone_name [
                       

                         A slave zone is a replica of a master
-                        zone. The masters list
+                        zone. The masters list
                         specifies one or more IP addresses
                         of master servers that the slave contacts to update
                         its copy of the zone.
@@ -8549,14 +9268,14 @@ zone zone_name [
                       

                         Zone data is configured via the
-                        server-addresses and
-                        server-names zone options.
+                        server-addresses and
+                        server-names zone options.
                       

                       

                         The zone data is maintained in the form of NS
                         and (if necessary) glue A or AAAA RRs
                         internally, which can be seen by dumping zone
-                        databases by rndc dumpdb -all.
+                        databases by rndc dumpdb -all.
                         The configured RRs are considered local configuration
                         parameters rather than public data.
                         Non recursive queries (i.e., those with the RD
@@ -8587,22 +9306,22 @@ zone zone_name [
                       

                         A "forward zone" is a way to configure
-                        forwarding on a per-domain basis.  A zone statement
-                        of type forward can
-                        contain a forward
-                        and/or forwarders
+                        forwarding on a per-domain basis.  A zone statement
+                        of type forward can
+                        contain a forward
+                        and/or forwarders
                         statement,
                         which will apply to queries within the domain given by
                         the zone
-                        name. If no forwarders
+                        name. If no forwarders
                         statement is present or
-                        an empty list for forwarders is given, then no
+                        an empty list for forwarders is given, then no
                         forwarding will be done for the domain, canceling the
                         effects of
-                        any forwarders in the options statement. Thus
+                        any forwarders in the options statement. Thus
                         if you want to use this type of zone to change the
                         behavior of the
-                        global forward option
+                        global forward option
                         (that is, "forward first"
                         to, then "forward only", or vice versa, but want to
                         use the same
@@ -8644,7 +9363,7 @@ zone zone_name [allow-query can be
+                        per view.  allow-query can be
                         used to restrict which clients see these answers.
                       

                       

@@ -8681,10 +9400,10 @@ zone zone_name [rndc reload
+                        rndc reload
                                 zonename
                         to reload a redirect zone.  However, when using
-                        rndc reload without specifying
+                        rndc reload without specifying
                         a zone name, redirect zones will be reloaded along
                         with other zones.
                       

@@ -8712,22 +9431,25 @@ zone zone_name [
                       

-                        See caveats in root-delegation-only.
+                        See caveats in root-delegation-only.
                       

                     
 
-

 




 
 
 

 

-
-

+
+            

+          
+
+          

 

-Class

-

+Class

+            
+            

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

-

+            

               The hesiod class is
               named for an information service from MIT's Project Athena. It
               is
@@ -8736,53 +9458,71 @@ zone zone_name [HS is
               a synonym for hesiod.
             

-

+            

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

-
-

+          

+
+          

 

-Zone Options

-

-
allow-notify

-

+Zone Options

+            
+
+            

+
allow-notify

+

+                  

                     See the description of
-                    allow-notify in the section called “Access Control”.
-                  

-
allow-query

-

+                    allow-notify in the section called “Access Control”.
+                  

+                

+
allow-query

+

+                  

                     See the description of
-                    allow-query in the section called “Access Control”.
-                  

-
allow-query-on

-

+                    allow-query in the section called “Access Control”.
+                  

+                

+
allow-query-on

+

+                  

                     See the description of
-                    allow-query-on in the section called “Access Control”.
-                  

-
allow-transfer

-

-                    See the description of allow-transfer
-                    in the section called “Access Control”.
-                  

-
allow-update

-

-                    See the description of allow-update
-                    in the section called “Access Control”.
-                  

-
update-policy

-

+                    allow-query-on in the section called “Access Control”.
+                  

+                

+
allow-transfer

+

+                  

+                    See the description of allow-transfer
+                    in the section called “Access Control”.
+                  

+                

+
allow-update

+

+                  

+                    See the description of allow-update
+                    in the section called “Access Control”.
+                  

+                

+
update-policy

+

+                  

                     Specifies a "Simple Secure Update" policy. See
-                    the section called “Dynamic Update Policies”.
-                  

-
allow-update-forwarding

-

-                    See the description of allow-update-forwarding
-                    in the section called “Access Control”.
-                  

-
also-notify

-

-                    Only meaningful if notify
+                    the section called “Dynamic Update Policies”.
+                  

+                

+
allow-update-forwarding

+

+                  

+                    See the description of allow-update-forwarding
+                    in the section called “Access Control”.
+                  

+                

+
also-notify

+

+                  

+                    Only meaningful if notify
                     is
                     active for this zone. The set of machines that will
                     receive a
@@ -8791,92 +9531,115 @@ zone zone_name [also-notify. A port
+                    with also-notify. A port
                     may be specified
-                    with each also-notify
+                    with each also-notify
                     address to send the notify
                     messages to a port other than the default of 53.
                     A TSIG key may also be specified to cause the
                     NOTIFY to be signed by the
                     given key.
-                    also-notify is not
+                    also-notify is not
                     meaningful for stub zones.
                     The default is the empty list.
-                  

-
check-names

-

+                  

+                

+
check-names

+

+                  

                     This option is used to restrict the character set and
                     syntax of
                     certain domain names in master files and/or DNS responses
                     received from the
-                    network.  The default varies according to zone type.  For master zones the default is fail.  For slave
-                    zones the default is warn.
-                    It is not implemented for hint zones.
-                  

-
check-mx

-

-                    See the description of
-                    check-mx in the section called “Boolean Options”.
-                  

-
check-spf

-

-                    See the description of
-                    check-spf in the section called “Boolean Options”.
-                  

-
check-wildcard

-

-                    See the description of
-                    check-wildcard in the section called “Boolean Options”.
-                  

-
check-integrity

-

-                    See the description of
-                    check-integrity in the section called “Boolean Options”.
-                  

-
check-sibling

-

-                    See the description of
-                    check-sibling in the section called “Boolean Options”.
-                  

-
zero-no-soa-ttl

-

-                    See the description of
-                    zero-no-soa-ttl in the section called “Boolean Options”.
-                  

-
update-check-ksk

-

-                    See the description of
-                    update-check-ksk in the section called “Boolean Options”.
-                  

-
dnssec-loadkeys-interval

-

-                    See the description of
-                    dnssec-loadkeys-interval in the section called “options Statement Definition and
-          Usage”.
-                  

-
dnssec-update-mode

-

-                    See the description of
-                    dnssec-update-mode in the section called “options Statement Definition and
-          Usage”.
-                  

-
dnssec-dnskey-kskonly

-

-                    See the description of
-                    dnssec-dnskey-kskonly in the section called “Boolean Options”.
-                  

-
try-tcp-refresh

-

-                    See the description of
-                    try-tcp-refresh in the section called “Boolean Options”.
-                  

-
database

+                    network.  The default varies according to zone type.  For master zones the default is fail.  For slave
+                    zones the default is warn.
+                    It is not implemented for hint zones.
+                  

+                
+
check-mx

 

-

+                  

+                    See the description of
+                    check-mx in the section called “Boolean Options”.
+                  

+                

+
check-spf

+

+                  

+                    See the description of
+                    check-spf in the section called “Boolean Options”.
+                  

+                

+
check-wildcard

+

+                  

+                    See the description of
+                    check-wildcard in the section called “Boolean Options”.
+                  

+                

+
check-integrity

+

+                  

+                    See the description of
+                    check-integrity in the section called “Boolean Options”.
+                  

+                

+
check-sibling

+

+                  

+                    See the description of
+                    check-sibling in the section called “Boolean Options”.
+                  

+                

+
zero-no-soa-ttl

+

+                  

+                    See the description of
+                    zero-no-soa-ttl in the section called “Boolean Options”.
+                  

+                

+
update-check-ksk

+

+                  

+                    See the description of
+                    update-check-ksk in the section called “Boolean Options”.
+                  

+                

+
dnssec-loadkeys-interval

+

+                  

+                    See the description of
+                    dnssec-loadkeys-interval in the section called “options Statement Definition and
+          Usage”.
+                  

+                

+
dnssec-update-mode

+

+                  

+                    See the description of
+                    dnssec-update-mode in the section called “options Statement Definition and
+          Usage”.
+                  

+                

+
dnssec-dnskey-kskonly

+

+                  

+                    See the description of
+                    dnssec-dnskey-kskonly in the section called “Boolean Options”.
+                  

+                

+
try-tcp-refresh

+

+                  

+                    See the description of
+                    try-tcp-refresh in the section called “Boolean Options”.
+                  

+                

+
database

+

+                  

                     Specify the type of database to be used for storing the
-                    zone data.  The string following the database keyword
+                    zone data.  The string following the database keyword
                     is interpreted as a list of whitespace-delimited words.
                     The first word
                     identifies the database type, and any subsequent words are
@@ -8885,53 +9648,60 @@ zone zone_name [
-

+                  

                     The default is "rbt", BIND 9's
                     native in-memory
                     red-black-tree database.  This database does not take
                     arguments.
                   

-

+                  

                     Other values are possible if additional database drivers
                     have been linked into the server.  Some sample drivers are
                     included
                     with the distribution but none are linked in by default.
                   

-

-
dialup

-

-                    See the description of
-                    dialup in the section called “Boolean Options”.
-                  

-
delegation-only

+                
+
dialup

 

-

+                  

+                    See the description of
+                    dialup in the section called “Boolean Options”.
+                  

+                

+
delegation-only

+

+                  

                     The flag only applies to forward, hint and stub
                     zones.  If set to yes,
                     then the zone will also be treated as if it is
                     also a delegation-only type zone.
                   

-

-                    See caveats in root-delegation-only.
+                  

+                    See caveats in root-delegation-only.
                   

-

-
forward

-

+                

+
forward

+

+                  

                     Only meaningful if the zone has a forwarders
-                    list. The only value causes
+                    list. The only value causes
                     the lookup to fail
-                    after trying the forwarders and getting no answer, while first would
+                    after trying the forwarders and getting no answer, while first would
                     allow a normal lookup to be tried.
-                  

-
forwarders

-

+                  

+                

+
forwarders

+

+                  

                     Used to override the list of global forwarders.
-                    If it is not specified in a zone of type forward,
+                    If it is not specified in a zone of type forward,
                     no forwarding is done for the zone and the global options are
                     not used.
-                  

-
ixfr-base

-

+                  

+                

+
ixfr-base

+

+                  

                     Was used in BIND 8 to
                     specify the name
                     of the transaction log (journal) file for dynamic update
@@ -8941,79 +9711,103 @@ zone zone_name [.jnl"
                     to the name of the
                     zone file.
-                  

-
ixfr-tmp-file

-

+                  

+                

+
ixfr-tmp-file

+

+                  

                     Was an undocumented option in BIND 8.
                     Ignored in BIND 9.
-                  

-
journal

-

+                  

+                

+
journal

+

+                  

                     Allow the default journal's filename to be overridden.
                     The default is the zone's filename with ".jnl" appended.
-                    This is applicable to master and slave zones.
-                  

-
max-journal-size

-

+                    This is applicable to master and slave zones.
+                  

+                

+
max-journal-size

+

+                  

                     See the description of
-                    max-journal-size in the section called “Server  Resource Limits”.
-                  

-
max-transfer-time-in

-

+                    max-journal-size in the section called “Server  Resource Limits”.
+                  

+                

+
max-transfer-time-in

+

+                  

                     See the description of
-                    max-transfer-time-in in the section called “Zone Transfers”.
-                  

-
max-transfer-idle-in

-

+                    max-transfer-time-in in the section called “Zone Transfers”.
+                  

+                

+
max-transfer-idle-in

+

+                  

                     See the description of
-                    max-transfer-idle-in in the section called “Zone Transfers”.
-                  

-
max-transfer-time-out

-

+                    max-transfer-idle-in in the section called “Zone Transfers”.
+                  

+                

+
max-transfer-time-out

+

+                  

                     See the description of
-                    max-transfer-time-out in the section called “Zone Transfers”.
-                  

-
max-transfer-idle-out

-

+                    max-transfer-time-out in the section called “Zone Transfers”.
+                  

+                

+
max-transfer-idle-out

+

+                  

                     See the description of
-                    max-transfer-idle-out in the section called “Zone Transfers”.
-                  

-
notify

-

+                    max-transfer-idle-out in the section called “Zone Transfers”.
+                  

+                

+
notify

+

+                  

                     See the description of
-                    notify in the section called “Boolean Options”.
-                  

-
notify-delay

-

+                    notify in the section called “Boolean Options”.
+                  

+                

+
notify-delay

+

+                  

                     See the description of
-                    notify-delay in the section called “Tuning”.
-                  

-
notify-to-soa

-

+                    notify-delay in the section called “Tuning”.
+                  

+                

+
notify-to-soa

+

+                  

                     See the description of
-                    notify-to-soa in
-                    the section called “Boolean Options”.
-                  

-
pubkey

-

+                    notify-to-soa in
+                    the section called “Boolean Options”.
+                  

+                

+
pubkey

+

+                  

                     In BIND 8, this option was
                     intended for specifying
                     a public zone key for verification of signatures in DNSSEC
                     signed
                     zones when they are loaded from disk. BIND 9 does not verify signatures
                     on load and ignores the option.
-                  

-
zone-statistics

-

-                    See the description of
-                    zone-statistics in
-                    the section called “options Statement Definition and
-          Usage”.
-                  

-
server-addresses

+                  

+                
+
zone-statistics

 

-

+                  

+                    See the description of
+                    zone-statistics in
+                    the section called “options Statement Definition and
+          Usage”.
+                  

+                

+
server-addresses

+

+                  

                     Only meaningful for static-stub zones.
                     This is a list of IP addresses to which queries
                     should be sent in recursive resolution for the
@@ -9022,16 +9816,16 @@ zone zone_name [
-

+                  

                     For example, if "example.com" is configured as a
                     static-stub zone with 192.0.2.1 and 2001:db8::1234
-                    in a server-addresses option,
+                    in a server-addresses option,
                     the following RRs will be internally configured.
                   

 
example.com. NS example.com.
 example.com. A 192.0.2.1
 example.com. AAAA 2001:db8::1234

-

+                  

                     These records are internally used to resolve
                     names under the static-stub zone.
                     For instance, if the server receives a query for
@@ -9039,16 +9833,16 @@ example.com. AAAA 2001:db8::1234

                     will initiate recursive resolution and send
                     queries to 192.0.2.1 and/or 2001:db8::1234.
                   

-
-
server-names

+                
+
server-names

 

-

+                  

                     Only meaningful for static-stub zones.
                     This is a list of domain names of nameservers that
                     act as authoritative servers of the static-stub
                     zone.
                     These names will be resolved to IP addresses when
-                    named needs to send queries to
+                    named needs to send queries to
                     these servers.
                     To make this supplemental resolution successful,
                     these names must not be a subdomain of the origin
@@ -9056,23 +9850,23 @@ example.com. AAAA 2001:db8::1234

                     That is, when "example.net" is the origin of a
                     static-stub zone, "ns.example" and
                     "master.example.com" can be specified in the
-                    server-names option, but
+                    server-names option, but
                     "ns.example.net" cannot, and will be rejected by
                     the configuration parser.
                   

-

+                  

                     A non empty list for this option will internally
                     configure the apex NS RR with the specified names.
                     For example, if "example.com" is configured as a
                     static-stub zone with "ns1.example.net" and
                     "ns2.example.net"
-                    in a server-names option,
+                    in a server-names option,
                     the following RRs will be internally configured.
                   

 
example.com. NS ns1.example.net.
 example.com. NS ns2.example.net.
 

-

+                  

                     These records are internally used to resolve
                     names under the static-stub zone.
                     For instance, if the server receives a query for
@@ -9082,150 +9876,190 @@ example.com. NS ns2.example.net.
                     "ns2.example.net" to IP addresses, and then send
                     queries to (one or more of) these addresses.
                   

-
-
sig-validity-interval

-

+                

+
sig-validity-interval

+

+                  

                     See the description of
-                    sig-validity-interval in the section called “Tuning”.
-                  

-
sig-signing-nodes

-

+                    sig-validity-interval in the section called “Tuning”.
+                  

+                

+
sig-signing-nodes

+

+                  

                     See the description of
-                    sig-signing-nodes in the section called “Tuning”.
-                  

-
sig-signing-signatures

-

+                    sig-signing-nodes in the section called “Tuning”.
+                  

+                

+
sig-signing-signatures

+

+                  

                     See the description of
-                    sig-signing-signatures in the section called “Tuning”.
-                  

-
sig-signing-type

-

+                    sig-signing-signatures in the section called “Tuning”.
+                  

+                

+
sig-signing-type

+

+                  

                     See the description of
-                    sig-signing-type in the section called “Tuning”.
-                  

-
transfer-source

-

+                    sig-signing-type in the section called “Tuning”.
+                  

+                

+
transfer-source

+

+                  

                     See the description of
-                    transfer-source in the section called “Zone Transfers”.
-                  

-
transfer-source-v6

-

+                    transfer-source in the section called “Zone Transfers”.
+                  

+                

+
transfer-source-v6

+

+                  

                     See the description of
-                    transfer-source-v6 in the section called “Zone Transfers”.
-                  

-
alt-transfer-source

-

+                    transfer-source-v6 in the section called “Zone Transfers”.
+                  

+                

+
alt-transfer-source

+

+                  

                     See the description of
-                    alt-transfer-source in the section called “Zone Transfers”.
-                  

-
alt-transfer-source-v6

-

+                    alt-transfer-source in the section called “Zone Transfers”.
+                  

+                

+
alt-transfer-source-v6

+

+                  

                     See the description of
-                    alt-transfer-source-v6 in the section called “Zone Transfers”.
-                  

-
use-alt-transfer-source

-

+                    alt-transfer-source-v6 in the section called “Zone Transfers”.
+                  

+                

+
use-alt-transfer-source

+

+                  

                     See the description of
-                    use-alt-transfer-source in the section called “Zone Transfers”.
-                  

-
notify-source

-

+                    use-alt-transfer-source in the section called “Zone Transfers”.
+                  

+                

+
notify-source

+

+                  

                     See the description of
-                    notify-source in the section called “Zone Transfers”.
-                  

-
notify-source-v6

-

+                    notify-source in the section called “Zone Transfers”.
+                  

+                

+
notify-source-v6

+

+                  

                     See the description of
-                    notify-source-v6 in the section called “Zone Transfers”.
-                  

+                    notify-source-v6 in the section called “Zone Transfers”.
+                  

+                
 

-min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
+min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
 

-

-                    See the description in the section called “Tuning”.
-                  

-
ixfr-from-differences

-

+

+                  

+                    See the description in the section called “Tuning”.
+                  

+                

+
ixfr-from-differences

+

+                  

                     See the description of
-                    ixfr-from-differences in the section called “Boolean Options”.
-                    (Note that the ixfr-from-differences
+                    ixfr-from-differences in the section called “Boolean Options”.
+                    (Note that the ixfr-from-differences
                     master and
                     slave choices are not
                     available at the zone level.)
-                  

-
key-directory

-

+                  

+                

+
key-directory

+

+                  

                     See the description of
-                    key-directory in the section called “options Statement Definition and
+                    key-directory in the section called “options Statement Definition and
           Usage”.
-                  

-
auto-dnssec

-

+                  

+                

+
auto-dnssec

+

+                  

                     See the description of
-                    auto-dnssec in
-                    the section called “options Statement Definition and
+                    auto-dnssec in
+                    the section called “options Statement Definition and
           Usage”.
-                  

-
serial-update-method

-

+                  

+                

+
serial-update-method

+

+                  

                     See the description of
-                    serial-update-method in
-                    the section called “options Statement Definition and
+                    serial-update-method in
+                    the section called “options Statement Definition and
           Usage”.
-                  

-
inline-signing

-

+                  

+                

+
inline-signing

+

+                  

                     If yes, this enables
                     "bump in the wire" signing of a zone, where a
                     unsigned zone is transferred in or loaded from
                     disk and a signed version of the zone is served,
                     with possibly, a different serial number.  This
                     behaviour is disabled by default.
-                  

-
multi-master

-

-                    See the description of multi-master in
-                    the section called “Boolean Options”.
-                  

-
masterfile-format

-

-                    See the description of masterfile-format
-                    in the section called “Tuning”.
-                  

-
max-zone-ttl

-

-                    See the description of max-zone-ttl
-                    in the section called “options Statement Definition and
+                  

+                

+
multi-master

+

+                  

+                    See the description of multi-master in
+                    the section called “Boolean Options”.
+                  

+                

+
masterfile-format

+

+                  

+                    See the description of masterfile-format
+                    in the section called “Tuning”.
+                  

+                

+
max-zone-ttl

+

+                  

+                    See the description of max-zone-ttl
+                    in the section called “options Statement Definition and
           Usage”.
-                  

-
dnssec-secure-to-insecure

-

+                  

+                

+
dnssec-secure-to-insecure

+

+                  

                     See the description of
-                    dnssec-secure-to-insecure in the section called “Boolean Options”.
-                  

+                    dnssec-secure-to-insecure in the section called “Boolean Options”.
+                  

+                
 
-
-

+
+          

+          

 

 Dynamic Update Policies

-
BIND 9 supports two alternative
+            
+            
BIND 9 supports two alternative
               methods of granting clients the right to perform
               dynamic updates to a zone, configured by the
-              allow-update and
-              update-policy option, respectively.
+              allow-update and
+              update-policy option, respectively.
             

-

-              The allow-update clause works the
+            

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

+              The update-policy clause
               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
@@ -9234,51 +10068,56 @@ example.com. NS ns2.example.net.
               it includes either a TSIG or SIG(0) record), the
               identity of the signer can be determined.
             

-

-              Rules are specified in the update-policy
+            

+              Rules are specified in the update-policy
               zone option, and are only meaningful for master zones.
-              When the update-policy statement
+              When the update-policy statement
               is present, it is a configuration error for the
-              allow-update statement to be
-              present.  The update-policy statement
+              allow-update statement to be
+              present.  The update-policy statement
               only examines the signer of a message; the source
               address is not relevant.
             

-

-              There is a pre-defined update-policy
+            

+              There is a pre-defined update-policy
               rule which can be switched on with the command
-              update-policy local;.
+              update-policy local;.
               Switching on this rule in a zone causes
-              named to generate a TSIG session
+              named to generate a TSIG session
               key and place it in a file, and to allow that key
               to update the zone.  (By default, the file is
               /var/run/named/session.key, the key
               name is "local-ddns" and the key algorithm is HMAC-SHA256,
               but these values are configurable with the
-              session-keyfile,
-              session-keyname and
-              session-keyalg options, respectively).
+              session-keyfile,
+              session-keyname and
+              session-keyalg options, respectively).
             

-

+            

               A client running on the local system, and with appropriate
               permissions, may read that file and use the key to sign update
               requests.  The zone's update policy will be set to allow that
               key to change any record within the zone.  Assuming the
               key name is "local-ddns", this policy is equivalent to:
             

-
update-policy { grant local-ddns zonesub any; };
+
+            
update-policy { grant local-ddns zonesub any; };
             

-

-              The command nsupdate -l sends update
+
+            

+              The command nsupdate -l sends update
               requests to localhost, and signs them using the session key.
             

-

+
+            

               Other rule definitions look like this:
             

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

-

+
+            

               Each rule grants or denies privileges.  Once a message has
               successfully matched a rule, the operation is immediately
               granted or denied and no further rules are examined.  A rule
@@ -9287,13 +10126,13 @@ example.com. NS ns2.example.net.
               field, and the type matches the types specified in the type
               field.
             

-

+            

               No signer is required for tcp-self
               or 6to4-self however the standard
               reverse mapping / prefix conversion must match the identity
               field.
             

-

+            

               The identity field specifies a name or a wildcard
               name.  Normally, this is the name of the TSIG or
               SIG(0) key used to sign the update request.  When a
@@ -9310,14 +10149,14 @@ example.com. NS ns2.example.net.
               The identity field must
               contain a fully-qualified domain name.
             

-

+            

               For nametypes krb5-self,
               ms-self, krb5-subdomain,
               and ms-subdomain the
               identity field specifies
               the Windows or Kerberos realm of the machine belongs to.
             

-

+            

               The nametype field has 13
               values:
               name, subdomain,
@@ -9329,10 +10168,11 @@ example.com. NS ns2.example.net.
               tcp-self, 6to4-self,
               zonesub, and external.
             

-

+            

+              
--++
@@ -9376,10 +10216,10 @@ example.com. NS ns2.example.net.
                         This rule is similar to subdomain, except that
                         it matches when the name being updated is a
                         subdomain of the zone in which the
-                        update-policy statement
+                        update-policy statement
                         appears.  This obviates the need to type the zone
                         name twice, and enables the use of a standard
-                        update-policy statement in
+                        update-policy statement in
                         multiple zones without modification.
                       

@@ -9572,7 +10412,7 @@ example.com. NS ns2.example.net.
                     
 

-

 




 
 
 

                       
                       

-                        This rule allows named
+                        This rule allows named
                         to defer the decision of whether to allow a
                         given update to an external daemon.
                       

@@ -9609,12 +10449,15 @@ example.com. NS ns2.example.net.
                     		
 

 

-

+
+            

+
+            

               In all cases, the name
               field must specify a fully-qualified domain name.
             

-

+
+            

               If no types are explicitly specified, this rule matches
               all types except RRSIG, NS, SOA, NSEC and NSEC3. Types
               may be specified by name, including "ANY" (ANY matches
@@ -9623,22 +10466,24 @@ example.com. NS ns2.example.net.
               all records associated with a name, the rules are
               checked for each existing record type.
             

-
-

+          

+
+          

 

-Multiple views

-

+Multiple views

+            
+            

               When multiple views are in use, a zone may be
               referenced by more than one of them. Often, the views
               will contain different zones with the same name, allowing
               different clients to receive different answers for the same
               queries. At times, however, it is desirable for multiple
               views to contain identical zones.  The
-              in-view zone option provides an efficient
+              in-view zone option provides an efficient
               way to do this: it allows a view to reference a zone that
               was defined in a previously configured view. Example:
             

-
+            
 view internal {
     match-clients { 10/8; };
 
@@ -9656,53 +10501,58 @@ view external {
     };
 };
             

-

-              An in-view option cannot refer to a view
+            

+              An in-view option cannot refer to a view
               that is configured later in the configuration file.
             

-

-              A zone statement which uses the
-              in-view option may not use any other
-              options with the exception of forward
-              and forwarders. (These options control
+            

+              A zone statement which uses the
+              in-view option may not use any other
+              options with the exception of forward
+              and forwarders. (These options control
               the behavior of the containing view, rather than changing
               the zone object itself.)
             

-

+            

               Zone level acls (e.g. allow-query, allow-transfer) and
               other configuration details of the zone are all set
               in the view the referenced zone is defined in.  Care
               need to be taken to ensure that acls are wide enough
               for all views referencing the zone.
             

-

-              An in-view zone cannot be used as a
+            

+              An in-view zone cannot be used as a
               response policy zone.
             

-

-              An in-view zone is not intended to reference
-              a forward zone.
+            

+              An in-view zone is not intended to reference
+              a forward zone.
             

-
-
-
-

+          

+
+        
+      
+      

 

-Zone File

-

+Zone File

+        
+        

 

 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.
           

-

+          

 

-Resource Records

-

+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
@@ -9710,15 +10560,17 @@ view external {
               need not be preserved by name servers, 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 section called “The sortlist Statement” and the section called “RRset Ordering”.
+              that a particular nearby server be tried first. See the section called “The sortlist Statement” and the section called “RRset Ordering”.
             

-

+
+            

               The components of a Resource Record are:
             

-

+            

+              
--++
@@ -9790,14 +10642,16 @@ view external {
                     
-

 




 
 
 

 

 

-

+
+            
+            

               The following are types of valid RRs:
             

-

+            

+              
--++
@@ -10775,15 +11629,17 @@ view external {
                     
-

 




 
 
 

 

 

-

+
+            
+            

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

-

+            

+
--++
@@ -10833,8 +11689,10 @@ view external {
                     
-

 




 
 
 

 

 

-

+
+            
+
+            

               The owner name is often implicit, rather than forming an
               integral
               part of the RR.  For example, many name servers internally form
@@ -10845,7 +11703,7 @@ view external {
               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
@@ -10865,17 +11723,18 @@ view external {
               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.
             

-
-

+          

+          

 

-Textual expression of RRs

-

+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
@@ -10888,13 +11747,13 @@ view external {
               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
@@ -10905,18 +11764,19 @@ view external {
               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:
             

-

+            

+
---+++
@@ -11016,25 +11876,27 @@ view external {
                     
-

 






 
 
 

 

 

-

+
+            
+            

               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.
             

-

+            

               The above example shows six RRs, with two RRs at each of three
               domain names.
             

-

+            

               Similarly we might see:
             

-

+            

+
---+++
@@ -11068,17 +11930,21 @@ view external {
                     
-

 






 
 
 

 

 

-

+
+            
+            

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

-
-
-

+          

+        
+
+        

 

-Discussion of MX Records

-

+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,
@@ -11087,7 +11953,8 @@ view external {
             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
@@ -11104,7 +11971,7 @@ view external {
             It must have an associated address record
             (A or AAAA) — 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,
@@ -11113,13 +11980,14 @@ view external {
             pointed to by the CNAME.
             For example:
           

-

+          

+            
-----+++++
@@ -11250,18 +12118,20 @@ view external {
                   
-

 










 
 
 

 

 

+
+            
 

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

-
-

+        

+        

 

 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
@@ -11269,10 +12139,11 @@ view external {
             currently
             used in a zone file.
           

-

+          

+            
--++
@@ -11324,16 +12195,18 @@ view external {
                   
-

 




 
 
 

 

 

-

+
+          

+          

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

-
-

+        

+        

 

-Inverse Mapping in IPv4

-

+Inverse Mapping in IPv4

+          
+          

             Reverse name resolution (that is, translation from IP address
             to name) is achieved by means of the in-addr.arpa domain
             and PTR records. Entries in the in-addr.arpa domain are made in
@@ -11348,10 +12221,11 @@ view external {
             PTR records if the machine has more than one name. For example,
             in the [example.com] domain:
           

-

+          

+            
--++
@@ -11379,22 +12253,24 @@ view external {
                   
-

 




 
 
 

 

 

-

+
+          

+          

 
Note

-

-              The $ORIGIN lines in the examples
+            

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

-

-
-

+          

+        
+        

 

-Other Zone File Directives

-

+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
@@ -11402,110 +12278,119 @@ view external {
             same
             class.
           

-

-            Master File Directives include $ORIGIN, $INCLUDE,
-            and $TTL.
+          

+            Master File Directives include $ORIGIN, $INCLUDE,
+            and $TTL.
           

-

+          

 

-The @ (at-sign)

-

+The @ (at-sign)

+            
+            

               When used in the label (or name) field, the asperand or
               at-sign (@) symbol represents the current origin.
               At the start of the zone file, it is the
               <zone_name> (followed by
               trailing dot).
             

-
-

+          

+          

 

-The $ORIGIN Directive

-

-              Syntax: $ORIGIN
+The $ORIGIN Directive

+            
+            

+              Syntax: $ORIGIN
               domain-name
               [comment]
             

-
$ORIGIN
+            
$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>.
+              is an implicit $ORIGIN
+              <zone_name>.
               (followed by trailing dot).
-              The current $ORIGIN is appended to
-              the domain specified in the $ORIGIN
+              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
 

-

+
+            

               is equivalent to
             

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

-
-

+
+          

+          

 

-The $INCLUDE Directive

-

-              Syntax: $INCLUDE
+The $INCLUDE Directive

+            
+            

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

-

+            

               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 $ORIGIN set
-              to that value, otherwise the current $ORIGIN is
+              if it were included into the file at this point.  If origin is
+              specified the file is processed with $ORIGIN set
+              to that value, otherwise the current $ORIGIN is
               used.
             

-

+            

               The origin and the current domain name
-              revert to the values they had prior to the $INCLUDE once
+              revert to the values they had prior to the $INCLUDE once
               the file has been read.
             

-

+            

 
Note

-

+              

                 RFC 1035 specifies that the current origin should be restored
                 after
-                an $INCLUDE, but it is silent
+                an $INCLUDE, but it is silent
                 on whether the current
                 domain name should also be restored.  BIND 9 restores both of
                 them.
                 This could be construed as a deviation from RFC 1035, a
                 feature, or both.
               

-

-

-

+            

+          
+          

 

-The $TTL Directive

-

-              Syntax: $TTL
+The $TTL Directive

+            
+            

+              Syntax: $TTL
               default-ttl
               [
 comment ]
             

-

+            

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

-
$TTL
+            
$TTL
                is defined in RFC 2308.
             

-
-
-

+          

+        
+        

 

-BIND Master File Extension: the  $GENERATE Directive

-

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

+          
+          

+            Syntax: $GENERATE
             range
             lhs
             [ttl]
@@ -11514,20 +12399,23 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
             rhs
             [comment]
           

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

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

-

+
+          

             is equivalent to
           

+
 
0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
 0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
 1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
@@ -11535,18 +12423,22 @@ $GENERATE 1-127 $ CNAME $.0

 ...
 127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA.
 

-

+
+           

             Generate a set of A and MX records.  Note the MX's right hand
             side is a quoted string.  The quotes will be stripped when the
             right hand side is processed.
            

+
 
 $ORIGIN EXAMPLE.
 $GENERATE 1-127 HOST-$ A 1.2.3.$
 $GENERATE 1-127 HOST-$ MX "0 ."

-

+
+          

             is equivalent to
           

+
 
HOST-1.EXAMPLE.   A  1.2.3.1
 HOST-1.EXAMPLE.   MX 0 .
 HOST-2.EXAMPLE.   A  1.2.3.2
@@ -11557,15 +12449,17 @@ HOST-3.EXAMPLE.   MX 0 .
 HOST-127.EXAMPLE. A  1.2.3.127
 HOST-127.EXAMPLE. MX 0 .
 

-

+
+          

+            
--++
-

 




 
 
 

 
-                    
range

+                    
range

                   		
 
                     

@@ -11579,43 +12473,43 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                    
lhs

+                    
lhs

                   		
 
                     
This
                       describes the owner name of the resource records
-                      to be created.  Any single $
+                      to be created.  Any single $
                       (dollar sign)
-                      symbols within the lhs string
+                      symbols within the lhs string
                       are replaced by the iterator value.
 
                       To get a $ in the output, you need to escape the
-                      $ using a backslash
-                      \,
-                      e.g. \$. The
-                      $ may optionally be followed
+                      $ using a backslash
+                      \,
+                      e.g. \$. The
+                      $ may optionally be followed
                       by modifiers which change the offset from the
                       iterator, field width and base.
 
                       Modifiers are introduced by a
-                      { (left brace) immediately following the
-                      $ as
-                      ${offset[,width[,base]]}.
-                      For example, ${-20,3,d}
+                      { (left brace) immediately following the
+                      $ as
+                      ${offset[,width[,base]]}.
+                      For example, ${-20,3,d}
                       subtracts 20 from the current value, prints the
                       result as a decimal in a zero-padded field of
                       width 3.
 
                       Available output forms are decimal
-                      (d), octal
-                      (o), hexadecimal
-                      (x or X
+                      (d), octal
+                      (o), hexadecimal
+                      (x or X
                       for uppercase) and nibble
-                      (n or N\
+                      (n or N\
                       for uppercase).  The default modifier is
-                      ${0,0,d}.  If the
-                      lhs is not absolute, the
-                      current $ORIGIN is appended
+                      ${0,0,d}.  If the
+                      lhs is not absolute, the
+                      current $ORIGIN is appended
                       to the name.
                     

                     

@@ -11627,14 +12521,14 @@ HOST-127.EXAMPLE. MX 0 .
                     

                     

                       For compatibility with earlier versions,
-                      $$ is still recognized as
+                      $$ is still recognized as
                       indicating a literal $ in the output.
                     

                   		
 

 

 
-                    
ttl

+                    
ttl

                   		
 
                     

@@ -11642,15 +12536,15 @@ HOST-127.EXAMPLE. MX 0 .
                       not specified this will be inherited using the
                       normal TTL inheritance rules.
                     

-                    
class
-                      and ttl can be
+                    
class
+                      and ttl can be
                       entered in either order.
                     

                   		
 

 

 
-                    
class

+                    
class

                   		
 
                     

@@ -11658,15 +12552,15 @@ HOST-127.EXAMPLE. MX 0 .
                       This must match the zone class if it is
                       specified.
                     

-                    
class
-                      and ttl can be
+                    
class
+                      and ttl can be
                       entered in either order.
                     

                   		
 

 

 
-                    
type

+                    
type

                   		
 
                     

@@ -11676,67 +12570,70 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                    
rhs

+                    
rhs

                   		
 
                     

-                      rhs, optionally, quoted string.
+                      rhs, optionally, quoted string.
                     

                   		
 

 

-

-            The $GENERATE directive is a BIND extension
+
+          
+          

+            The $GENERATE directive is a BIND extension
             and not part of the standard zone file format.
           

-

+          

             BIND 8 does not support the optional TTL and CLASS fields.
           

-
-

+        

+
+        

 

 Additional File Formats

-

+          
+          

             In addition to the standard textual format, BIND 9
             supports the ability to read or dump to zone files in
             other formats.
           

-

+          

             The raw format is
             a binary representation of zone data in a manner similar
             to that used in zone transfers.  Since it does not require
             parsing text, load time is significantly reduced.
           

-

+          

             An even faster alternative is the map
             format, which is an image of a BIND 9
             in-memory zone database; it is capable of being loaded
-            directly into memory via the mmap()
+            directly into memory via the mmap()
             function; the zone can begin serving queries almost
             immediately.
           

-

+          

             For a primary server, a zone file in
             raw or map
             format is expected to be generated from a textual zone
-            file by the named-compilezone command.
+            file by the named-compilezone command.
             For a secondary server or for a dynamic zone, it is automatically
             generated (if this format is specified by the
-            masterfile-format option) when
-            named dumps the zone contents after
+            masterfile-format option) when
+            named dumps the zone contents after
             zone transfer or when applying prior updates.
           

-

+          

             If a zone file in a binary format needs manual modification,
             it first must be converted to a textual form by the
-            named-compilezone command.  All
+            named-compilezone command.  All
             necessary modification should go to the text file, which
             should then be converted to the binary form by the
-            named-compilezone command again.
+            named-compilezone command again.
           

-

-            Note that map format is extremely
+          

+            Note that map format is extremely
             architecture-specific.  A map
             file cannot be used on a system
             with different pointer size, endianness or data alignment
@@ -11752,12 +12649,14 @@ HOST-127.EXAMPLE. MX 0 .
             portable backup of such a file, conversion to
             text format is recommended.
           

-

-
-

+        

+      
+
+      

 

 BIND9 Statistics

-

+        
+        

           BIND 9 maintains lots of statistics
           information and provides several interfaces for users to
           get access to the statistics.
@@ -11766,14 +12665,17 @@ HOST-127.EXAMPLE. MX 0 .
           are meaningful in BIND 9,
           and other information that is considered useful.
         

-

+
+        

           The statistics information is categorized into the following
           sections.
         

-

+
+        

+          
--++
@@ -11869,42 +12771,47 @@ HOST-127.EXAMPLE. MX 0 .
                 
-

 




 
 
 

 

 

-

+
+        

+
+        

           A subset of Name Server Statistics is collected and shown
           per zone for which the server has the authority when
-          zone-statistics is set to
+          zone-statistics is set to
           full (or yes
           for backward compatibility. See the description of
-          zone-statistics in the section called “options Statement Definition and
+          zone-statistics in the section called “options Statement Definition and
           Usage”
           for further details.
         

-

+
+        

           These statistics counters are shown with their zone and
           view names. The view name is omitted when the server is
           not configured with explicit views.

-

+
+        

           There are currently two user interfaces to get access to the
           statistics.
           One is in the plain text format dumped to the file specified
-          by the statistics-file configuration option.
+          by the statistics-file configuration option.
           The other is remotely accessible via a statistics channel
-          when the statistics-channels statement
+          when the statistics-channels statement
           is specified in the configuration file
-          (see the section called “statistics-channels Statement Grammar”.)
+          (see the section called “statistics-channels Statement Grammar”.)
         

-

-

-The Statistics File

-

+
+        

+

+The Statistics File

+          
+          

             The text format statistics dump begins with a line, like:
           

-

-            +++ Statistics Dump +++ (973798949)
+          

+            +++ Statistics Dump +++ (973798949)
           

-

+          

             The number in parentheses is a standard
             Unix-style timestamp, measured as seconds since January 1, 1970.
 
@@ -11913,28 +12820,33 @@ HOST-127.EXAMPLE. MX 0 .
             as described above.
             Each section begins with a line, like:
           

-

-            ++ Name Server Statistics ++
+
+          

+            ++ Name Server Statistics ++
           

-

+
+          

             Each section consists of lines, each containing the statistics
             counter value followed by its textual description.
             See below for available counters.
             For brevity, counters that have a value of 0 are not shown
             in the statistics file.
           

-

+
+          

             The statistics dump ends with the line where the
             number is identical to the number in the beginning line; for example:
           

-

-            --- Statistics Dump --- (973798949)
+          

+            --- Statistics Dump --- (973798949)
           

-

-

+        

+
+        

 

 Statistics Counters

-

+          
+          

             The following tables summarize statistics counters that
             BIND 9 provides.
             For each row of the tables, the leftmost column is the
@@ -11950,14 +12862,18 @@ HOST-127.EXAMPLE. MX 0 .
             it gives the corresponding counter name of the
             BIND 8 statistics, if applicable.
           

-

+
+          

 

-Name Server Statistics Counters

-

+Name Server Statistics Counters
+            
+
+            

+              
---+++
@@ -11979,10 +12895,10 @@ HOST-127.EXAMPLE. MX 0 .
 
-

 






 
 
 

 

 
-                      
Requestv4

+                      
Requestv4

                     		
 
-                      
RQ

+                      
RQ

                     		
 
                       

@@ -11993,10 +12909,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Requestv6

+                      
Requestv6

                     		
 
-                      
RQ

+                      
RQ

                     		
 
                       

@@ -12007,10 +12923,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqEdns0

+                      
ReqEdns0

                     		
 
-                      

+                      

                     		
 
                       

@@ -12020,10 +12936,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqBadEDNSVer

+                      
ReqBadEDNSVer

                     		
 
-                      

+                      

                     		
 
                       

@@ -12033,10 +12949,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqTSIG

+                      
ReqTSIG

                     		
 
-                      

+                      

                     		
 
                       

@@ -12046,10 +12962,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqSIG0

+                      
ReqSIG0

                     		
 
-                      

+                      

                     		
 
                       

@@ -12059,10 +12975,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqBadSIG

+                      
ReqBadSIG

                     		
 
-                      

+                      

                     		
 
                       

@@ -12072,10 +12988,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ReqTCP

+                      
ReqTCP

                     		
 
-                      
RTCP

+                      
RTCP

                     		
 
                       

@@ -12085,10 +13001,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
AuthQryRej

+                      
AuthQryRej

                     		
 
-                      
RUQ

+                      
RUQ

                     		
 
                       

@@ -12098,10 +13014,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RecQryRej

+                      
RecQryRej

                     		
 
-                      
RURQ

+                      
RURQ

                     		
 
                       

@@ -12111,10 +13027,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
XfrRej

+                      
XfrRej

                     		
 
-                      
RUXFR

+                      
RUXFR

                     		
 
                       

@@ -12124,10 +13040,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateRej

+                      
UpdateRej

                     		
 
-                      
RUUpd

+                      
RUUpd

                     		
 
                       

@@ -12137,10 +13053,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Response

+                      
Response

                     		
 
-                      
SAns

+                      
SAns

                     		
 
                       

@@ -12150,10 +13066,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RespTruncated

+                      
RespTruncated

                     		
 
-                      

+                      

                     		
 
                       

@@ -12163,10 +13079,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RespEDNS0

+                      
RespEDNS0

                     		
 
-                      

+                      

                     		
 
                       

@@ -12176,10 +13092,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RespTSIG

+                      
RespTSIG

                     		
 
-                      

+                      

                     		
 
                       

@@ -12189,10 +13105,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RespSIG0

+                      
RespSIG0

                     		
 
-                      

+                      

                     		
 
                       

@@ -12202,10 +13118,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QrySuccess

+                      
QrySuccess

                     		
 
-                      

+                      

                     		
 
                       

@@ -12213,7 +13129,7 @@ HOST-127.EXAMPLE. MX 0 .
                         This means the query which returns a NOERROR response
                         with at least one answer RR.
                         This corresponds to the
-                        success counter
+                        success counter
                         of previous versions of
                         BIND 9.
                       

@@ -12221,10 +13137,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryAuthAns

+                      
QryAuthAns

                     		
 
-                      

+                      

                     		
 
                       

@@ -12234,10 +13150,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryNoauthAns

+                      
QryNoauthAns

                     		
 
-                      
SNaAns

+                      
SNaAns

                     		
 
                       

@@ -12247,16 +13163,16 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryReferral

+                      
QryReferral

                     		
 
-                      

+                      

                     		
 
                       

                         Queries resulted in referral answer.
                         This corresponds to the
-                        referral counter
+                        referral counter
                         of previous versions of
                         BIND 9.
                       

@@ -12264,16 +13180,16 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryNxrrset

+                      
QryNxrrset

                     		
 
-                      

+                      

                     		
 
                       

                         Queries resulted in NOERROR responses with no data.
                         This corresponds to the
-                        nxrrset counter
+                        nxrrset counter
                         of previous versions of
                         BIND 9.
                       

@@ -12281,10 +13197,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QrySERVFAIL

+                      
QrySERVFAIL

                     		
 
-                      
SFail

+                      
SFail

                     		
 
                       

@@ -12294,10 +13210,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryFORMERR

+                      
QryFORMERR

                     		
 
-                      
SFErr

+                      
SFErr

                     		
 
                       

@@ -12307,16 +13223,16 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryNXDOMAIN

+                      
QryNXDOMAIN

                     		
 
-                      
SNXD

+                      
SNXD

                     		
 
                       

                         Queries resulted in NXDOMAIN.
                         This corresponds to the
-                        nxdomain counter
+                        nxdomain counter
                         of previous versions of
                         BIND 9.
                       

@@ -12324,17 +13240,17 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryRecursion

+                      
QryRecursion

                     		
 
-                      
RFwdQ

+                      
RFwdQ

                     		
 
                       

                         Queries which caused the server
                         to perform recursion in order to find the final answer.
                         This corresponds to the
-                        recursion counter
+                        recursion counter
                         of previous versions of
                         BIND 9.
                       

@@ -12342,10 +13258,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryDuplicate

+                      
QryDuplicate

                     		
 
-                      
RDupQ

+                      
RDupQ

                     		
 
                       

@@ -12354,7 +13270,7 @@ HOST-127.EXAMPLE. MX 0 .
                         IP address, port, query ID, name, type and class
                         already being processed.
                         This corresponds to the
-                        duplicate counter
+                        duplicate counter
                         of previous versions of
                         BIND 9.
                       

@@ -12362,10 +13278,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryDropped

+                      
QryDropped

                     		
 
-                      

+                      

                     		
 
                       

@@ -12375,14 +13291,14 @@ HOST-127.EXAMPLE. MX 0 .
                         class and were subsequently dropped.
                         This is the number of dropped queries due to
                         the reason explained with the
-                        clients-per-query
+                        clients-per-query
                         and
-                        max-clients-per-query
+                        max-clients-per-query
                         options
                         (see the description about
-                        clients-per-query.)
+                        clients-per-query.)
                         This corresponds to the
-                        dropped counter
+                        dropped counter
                         of previous versions of
                         BIND 9.
                       

@@ -12390,23 +13306,23 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryFailure

+                      
QryFailure

                     		
 
-                      

+                      

                     		
 
                       

                         Other query failures.
                         This corresponds to the
-                        failure counter
+                        failure counter
                         of previous versions of
                         BIND 9.
                         Note: this counter is provided mainly for
                         backward compatibility with the previous versions.
                         Normally a more fine-grained counters such as
-                        AuthQryRej and
-                        RecQryRej
+                        AuthQryRej and
+                        RecQryRej
                         that would also fall into this counter are provided,
                         and so this counter would not be of much
                         interest in practice.
@@ -12415,10 +13331,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryNXRedir

+                      
QryNXRedir

                     		
 
-                      

+                      

                     		
 
                       

@@ -12428,10 +13344,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryNXRedirRLookup

+                      
QryNXRedirRLookup

                     		
 
-                      

+                      

                     		
 
                       

@@ -12442,10 +13358,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
XfrReqDone

+                      
XfrReqDone

                     		
 
-                      

+                      

                     		
 
                       

@@ -12455,10 +13371,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateReqFwd

+                      
UpdateReqFwd

                     		
 
-                      

+                      

                     		
 
                       

@@ -12468,10 +13384,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateRespFwd

+                      
UpdateRespFwd

                     		
 
-                      

+                      

                     		
 
                       

@@ -12481,10 +13397,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateFwdFail

+                      
UpdateFwdFail

                     		
 
-                      

+                      

                     		
 
                       

@@ -12494,10 +13410,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateDone

+                      
UpdateDone

                     		
 
-                      

+                      

                     		
 
                       

@@ -12507,10 +13423,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateFail

+                      
UpdateFail

                     		
 
-                      

+                      

                     		
 
                       

@@ -12520,10 +13436,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
UpdateBadPrereq

+                      
UpdateBadPrereq

                     		
 
-                      

+                      

                     		
 
                       

@@ -12533,10 +13449,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RateDropped

+                      
RateDropped

                     		
 
-                      

+                      

                     		
 
                       

@@ -12546,10 +13462,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RateSlipped

+                      
RateSlipped

                     		
 
-                      

+                      

                     		
 
                       

@@ -12559,10 +13475,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
RPZRewrites

+                      
RPZRewrites

                     		
 
-                      

+                      

                     		
 
                       

@@ -12571,15 +13487,20 @@ HOST-127.EXAMPLE. MX 0 .
                     

 

 

-

-

+
+            

+          

+
+          

 

-Zone Maintenance Statistics Counters

-

+Zone Maintenance Statistics Counters
+            
+
+            

+              
--++
@@ -12596,7 +13517,7 @@ HOST-127.EXAMPLE. MX 0 .
 
-

 




 
 
 

 

 
-                      
NotifyOutv4

+                      
NotifyOutv4

                     		
 
                       

@@ -12606,7 +13527,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
NotifyOutv6

+                      
NotifyOutv6

                     		
 
                       

@@ -12616,7 +13537,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
NotifyInv4

+                      
NotifyInv4

                     		
 
                       

@@ -12626,7 +13547,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
NotifyInv6

+                      
NotifyInv6

                     		
 
                       

@@ -12636,7 +13557,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
NotifyRej

+                      
NotifyRej

                     		
 
                       

@@ -12646,7 +13567,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
SOAOutv4

+                      
SOAOutv4

                     		
 
                       

@@ -12656,7 +13577,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
SOAOutv6

+                      
SOAOutv6

                     		
 
                       

@@ -12666,7 +13587,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
AXFRReqv4

+                      
AXFRReqv4

                     		
 
                       

@@ -12676,7 +13597,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
AXFRReqv6

+                      
AXFRReqv6

                     		
 
                       

@@ -12686,7 +13607,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
IXFRReqv4

+                      
IXFRReqv4

                     		
 
                       

@@ -12696,7 +13617,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
IXFRReqv6

+                      
IXFRReqv6

                     		
 
                       

@@ -12706,7 +13627,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
XfrSuccess

+                      
XfrSuccess

                     		
 
                       

@@ -12716,7 +13637,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
XfrFail

+                      
XfrFail

                     		
 
                       

@@ -12725,16 +13646,21 @@ HOST-127.EXAMPLE. MX 0 .
                     

 

 

-

-

+
+            

+          

+
+          

 

-Resolver Statistics Counters

-

+Resolver Statistics Counters
+            
+
+            

+              
---+++
@@ -12756,10 +13682,10 @@ HOST-127.EXAMPLE. MX 0 .
 
-

 






 
 
 

 

 
-                      
Queryv4

+                      
Queryv4

                     		
 
-                      
SFwdQ

+                      
SFwdQ

                     		
 
                       

@@ -12769,10 +13695,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Queryv6

+                      
Queryv6

                     		
 
-                      
SFwdQ

+                      
SFwdQ

                     		
 
                       

@@ -12782,10 +13708,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Responsev4

+                      
Responsev4

                     		
 
-                      
RR

+                      
RR

                     		
 
                       

@@ -12795,10 +13721,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Responsev6

+                      
Responsev6

                     		
 
-                      
RR

+                      
RR

                     		
 
                       

@@ -12808,10 +13734,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
NXDOMAIN

+                      
NXDOMAIN

                     		
 
-                      
RNXD

+                      
RNXD

                     		
 
                       

@@ -12821,10 +13747,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
SERVFAIL

+                      
SERVFAIL

                     		
 
-                      
RFail

+                      
RFail

                     		
 
                       

@@ -12834,10 +13760,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
FORMERR

+                      
FORMERR

                     		
 
-                      
RFErr

+                      
RFErr

                     		
 
                       

@@ -12847,10 +13773,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
OtherError

+                      
OtherError

                     		
 
-                      
RErr

+                      
RErr

                     		
 
                       

@@ -12860,10 +13786,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
EDNS0Fail

+                      
EDNS0Fail

                                                  		
 
-                      

+                      

                     		
 
                       

@@ -12873,10 +13799,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Mismatch

+                      
Mismatch

                     		
 
-                      
RDupR

+                      
RDupR

                     		
 
                       

@@ -12885,7 +13811,7 @@ HOST-127.EXAMPLE. MX 0 .
                         and/or the response's source port does not
                         match what was expected.
                         (The port must be 53 or as defined by
-                        the port option.)
+                        the port option.)
                         This may be an indication of a cache
                         poisoning attempt.
                       

@@ -12893,10 +13819,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Truncated

+                      
Truncated

                     		
 
-                      

+                      

                     		
 
                       

@@ -12906,10 +13832,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Lame

+                      
Lame

                     		
 
-                      
RLame

+                      
RLame

                     		
 
                       

@@ -12919,10 +13845,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
Retry

+                      
Retry

                     		
 
-                      
SDupQ

+                      
SDupQ

                     		
 
                       

@@ -12932,10 +13858,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QueryAbort

+                      
QueryAbort

                     		
 
-                      

+                      

                     		
 
                       

@@ -12945,10 +13871,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QuerySockFail

+                      
QuerySockFail

                     		
 
-                      

+                      

                     		
 
                       

@@ -12961,10 +13887,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QueryTimeout

+                      
QueryTimeout

                     		
 
-                      

+                      

                     		
 
                       

@@ -12974,10 +13900,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
GlueFetchv4

+                      
GlueFetchv4

                     		
 
-                      
SSysQ

+                      
SSysQ

                     		
 
                       

@@ -12987,10 +13913,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
GlueFetchv6

+                      
GlueFetchv6

                     		
 
-                      
SSysQ

+                      
SSysQ

                     		
 
                       

@@ -13000,10 +13926,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
GlueFetchv4Fail

+                      
GlueFetchv4Fail

                     		
 
-                      

+                      

                     		
 
                       

@@ -13013,10 +13939,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
GlueFetchv6Fail

+                      
GlueFetchv6Fail

                     		
 
-                      

+                      

                     		
 
                       

@@ -13026,10 +13952,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ValAttempt

+                      
ValAttempt

                     		
 
-                      

+                      

                     		
 
                       

@@ -13039,10 +13965,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ValOk

+                      
ValOk

                     		
 
-                      

+                      

                     		
 
                       

@@ -13052,10 +13978,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ValNegOk

+                      
ValNegOk

                     		
 
-                      

+                      

                     		
 
                       

@@ -13065,10 +13991,10 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
ValFail

+                      
ValFail

                     		
 
-                      

+                      

                     		
 
                       

@@ -13078,60 +14004,67 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
QryRTTnn

+                      
QryRTTnn

                     		
 
-                      

+                      

                     		
 
                       

                         Frequency table on round trip times (RTTs) of
                         queries.
-                        Each nn specifies the corresponding
+                        Each nn specifies the corresponding
                         frequency.
                         In the sequence of
-                        nn_1,
-                        nn_2,
+                        nn_1,
+                        nn_2,
                         ...,
-                        nn_m,
-                        the value of nn_i is the
+                        nn_m,
+                        the value of nn_i is the
                         number of queries whose RTTs are between
-                        nn_(i-1) (inclusive) and
-                        nn_i (exclusive) milliseconds.
+                        nn_(i-1) (inclusive) and
+                        nn_i (exclusive) milliseconds.
                         For the sake of convenience we define
-                        nn_0 to be 0.
+                        nn_0 to be 0.
                         The last entry should be represented as
-                        nn_m+, which means the
+                        nn_m+, which means the
                         number of queries whose RTTs are equal to or over
-                        nn_m milliseconds.
+                        nn_m milliseconds.
                       

                     		
 

 

-

-

+
+            

+
+          

+
+          

 

-Socket I/O Statistics Counters

-

+Socket I/O Statistics Counters

+            
+
+            

               Socket I/O statistics counters are defined per socket
               types, which are
-              UDP4 (UDP/IPv4),
-              UDP6 (UDP/IPv6),
-              TCP4 (TCP/IPv4),
-              TCP6 (TCP/IPv6),
-              Unix (Unix Domain), and
-              FDwatch (sockets opened outside the
+              UDP4 (UDP/IPv4),
+              UDP6 (UDP/IPv6),
+              TCP4 (TCP/IPv4),
+              TCP6 (TCP/IPv6),
+              Unix (Unix Domain), and
+              FDwatch (sockets opened outside the
               socket module).
-              In the following table <TYPE>
+              In the following table <TYPE>
               represents a socket type.
               Not all counters are available for all socket types;
               exceptions are noted in the description field.
             

-

+
+            

+              
--++
@@ -13148,31 +14081,31 @@ HOST-127.EXAMPLE. MX 0 .
 
-

 




 
 
 

 

 
-                      
<TYPE>Open

+                      
<TYPE>Open

                     		
 
                       

                         Sockets opened successfully.
                         This counter is not applicable to the
-                        FDwatch type.
+                        FDwatch type.
                       

                     		
 

 

 
-                      
<TYPE>OpenFail

+                      
<TYPE>OpenFail

                     		
 
                       

                         Failures of opening sockets.
                         This counter is not applicable to the
-                        FDwatch type.
+                        FDwatch type.
                       

                     		
 

 

 
-                      
<TYPE>Close

+                      
<TYPE>Close

                     		
 
                       

@@ -13182,7 +14115,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
<TYPE>BindFail

+                      
<TYPE>BindFail

                     		
 
                       

@@ -13192,7 +14125,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
<TYPE>ConnFail

+                      
<TYPE>ConnFail

                     		
 
                       

@@ -13202,7 +14135,7 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
<TYPE>Conn

+                      
<TYPE>Conn

                     		
 
                       

@@ -13212,46 +14145,46 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 
-                      
<TYPE>AcceptFail

+                      
<TYPE>AcceptFail

                     		
 
                       

                         Failures of accepting incoming connection requests.
                         This counter is not applicable to the
-                        UDP and
-                        FDwatch types.
+                        UDP and
+                        FDwatch types.
                       

                     		
 

 

 
-                      
<TYPE>Accept

+                      
<TYPE>Accept

                     		
 
                       

                         Incoming connections successfully accepted.
                         This counter is not applicable to the
-                        UDP and
-                        FDwatch types.
+                        UDP and
+                        FDwatch types.
                       

                     		
 

 

 
-                      
<TYPE>SendErr

+                      
<TYPE>SendErr

                     		
 
                       

                         Errors in socket send operations.
                         This counter corresponds
-                        to SErr counter of
-                        BIND 8.
+                        to SErr counter of
+                        BIND 8.
                       

                     		
 

 

 
-                      
<TYPE>RecvErr

+                      
<TYPE>RecvErr

                     		
 
                       

@@ -13263,45 +14196,57 @@ HOST-127.EXAMPLE. MX 0 .
                     

 

 

-
-

+
+            

+          
+          

 

-Compatibility with BIND 8 Counters

-

+Compatibility with BIND 8 Counters

+            
+            

               Most statistics counters that were available
-              in BIND 8 are also supported in
-              BIND 9 as shown in the above tables.
+              in BIND 8 are also supported in
+              BIND 9 as shown in the above tables.
               Here are notes about other counters that do not appear
               in these tables.
             

-

-
RFwdR,SFwdR

-

+
+            

+
RFwdR,SFwdR

+

+                  

                     These counters are not supported
-                    because BIND 9 does not adopt
+                    because BIND 9 does not adopt
                     the notion of forwarding
-                    as BIND 8 did.
-                  

-
RAXFR

-

+                    as BIND 8 did.
+                  

+                

+
RAXFR

+

+                  

                     This counter is accessible in the Incoming Queries section.
-                  

-
RIQ

-

+                  

+                

+
RIQ

+

+                  

                     This counter is accessible in the Incoming Requests section.
-                  

-
ROpts

-

+                  

+                

+
ROpts

+

+                  

                     This counter is not supported
-                    because BIND 9 does not care
+                    because BIND 9 does not care
                     about IP options in the first place.
-                  

+                  

+                

 

-
-
-
-
+          
+        
+      
+
+    
 

 

 
@@ -13319,6 +14264,6 @@ HOST-127.EXAMPLE. MX 0 .
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html
index 2651fc48db..ec016207fd 100644
--- a/doc/arm/Bv9ARM.ch07.html
+++ b/doc/arm/Bv9ARM.ch07.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Chapter 7. BIND 9 Security Considerations
-
-
+
+
 
 
 
@@ -39,52 +38,55 @@
 
 

 
-

-

-Chapter 7. BIND 9 Security Considerations

+

+

+Chapter 7. BIND 9 Security Considerations

 

 
Table of Contents

-

-
Access Control Lists

-
Chroot and Setuid

+

+
Access Control Lists

+
Chroot and Setuid

 

-
The chroot Environment

-
Using the setuid Function

+
The chroot Environment

+
Using the setuid Function

 

-
Dynamic Update Security

+
Dynamic Update Security

 

 

-

+      
+      

 

 Access Control Lists

-

+        
+        

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

-

+        

           Using ACLs allows you to have finer control over who can access
           your name server, 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 denial of service
           (DoS) attacks against your server.
         

-

+        

           ACLs match clients on the basis of up to three characteristics:
           1) The client's IP address; 2) the TSIG or SIG(0) key that was
           used to sign the request, if any; and 3) an address prefix
           encoded in an EDNS Client Subnet option, if any.
         

-

+        

           Here is an example of ACLs based on client addresses:
         

+
 
 // Set up an ACL named "bogusnets" that will block
 // RFC1918 space and some reserved space, which is
@@ -113,13 +115,14 @@ zone "example.com" {
   allow-query { any; };
 };
 

-

+
+        

           This allows authoritative queries for "example.com" from any
           address, but recursive queries only from the networks specified
           in "our-nets", and no queries at all from the networks
           specified in "bogusnets".
         

-

+        

           In addition to network addresses and prefixes, which are
           matched against the source address of the DNS request, ACLs
           may include key elements, which specify the
@@ -128,34 +131,34 @@ zone "example.com" {
           if that prefix matches an EDNS client subnet option included
           in the request.
         

-

+        

           The EDNS Client Subnet (ECS) option is used by a recursive
           resolver to inform an authoritative name server of the network
           address block from which the original query was received, enabling
           authoritative servers to give different answers to the same
           resolver for different resolver clients.  An ACL containing
           an element of the form
-          ecs prefix
+          ecs prefix
           will match if a request arrives in containing an ECS option
           encoding an address within that prefix.  If the request has no
           ECS option, then "ecs" elements are simply ignored.  Addresses
           in ACLs that are not prefixed with "ecs" are matched only
           against the source address.
         

-

+        

           When BIND 9 is built with GeoIP support,
           ACLs can also be used for geographic access restrictions.
           This is done by specifying an ACL element of the form:
-          geoip [db database] field value
+          geoip [db database] field value
         

-

+        

           The field indicates which field
           to search for a match.  Available fields are "country",
           "region", "city", "continent", "postal" (postal code),
           "metro" (metro code), "area" (area code), "tz" (timezone),
           "isp", "org", "asnum", "domain" and "netspeed".
         

-

+        

           value is the value to search
           for within the database.  A string may be quoted if it
           contains spaces or other special characters.  If this is
@@ -171,7 +174,7 @@ zone "example.com" {
           standard two-letter state or province abbreviation;
           otherwise it is the full name of the state or province.
         

-

+        

           The database field indicates which
           GeoIP database to search for a match.  In most cases this is
           unnecessary, because most search fields can only be found in
@@ -186,18 +189,18 @@ zone "example.com" {
           database if it is installed, or the "region" database if it is
           installed, or the "country" database, in that order.
         

-

+        

           By default, if a DNS query includes an EDNS Client Subnet (ECS)
           option which encodes a non-zero address prefix, then GeoIP ACLs
           will be matched against that address prefix.  Otherwise, they
           are matched against the source address of the query.  To
           prevent GeoIP ACLs from matching against ECS options, set
-          the geoip-use-ecs to no.
+          the geoip-use-ecs to no.
         

-

+        

           Some example GeoIP ACLs:
         

-
geoip country US;
+        
geoip country US;
 geoip country JAP;
 geoip db country country Canada;
 geoip db region region WA;
@@ -207,17 +210,18 @@ geoip postal 95062;
 geoip tz "America/Los_Angeles";
 geoip org "Internet Systems Consortium";
 

-

+
+        

           ACLs use a "first-match" logic rather than "best-match":
           if an address prefix matches an ACL element, then that ACL
           is considered to have matched even if a later element would
           have matched more specifically.  For example, the ACL
-           { 10/8; !10.0.0.1; } would actually
+           { 10/8; !10.0.0.1; } would actually
           match a query from 10.0.0.1, because the first element
           indicated that the query should be accepted, and the second
           element is ignored.
         

-

+        

           When using "nested" ACLs (that is, ACLs included or referenced
           within other ACLs), a negative match of a nested ACL will
           the containing ACL to continue looking for matches.  This
@@ -227,10 +231,10 @@ geoip org "Internet Systems Consortium";
           it originates from a particular network and
           only when it is signed with a particular key, use:
         

-
+        
 allow-query { !{ !10/8; any; }; key example; };
 

-

+        

           Within the nested ACL, any address that is
           not in the 10/8 network prefix will
           be rejected, and this will terminate processing of the
@@ -242,38 +246,43 @@ allow-query { !{ !10/8; any; }; key example; };
           will only matches when both conditions
           are true.
         

-

-

+      

+
+      

 

-Chroot and Setuid
+Chroot and Setuid
 

-

+        
+        

           On UNIX servers, it is possible to run BIND
           in a chrooted environment (using
-          the chroot() function) by specifying
-          the -t option for named.
+          the chroot() function) by specifying
+          the -t option for named.
           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 an unprivileged user ( -u user ).
-          We suggest running as an unprivileged user when using the chroot feature.
+          We suggest running as an unprivileged user when using the chroot feature.
         

-

-          Here is an example command line to load BIND in a chroot sandbox,
-          /var/named, and to run named setuid to
+        

+          Here is an example command line to load BIND in a chroot sandbox,
+          /var/named, and to run named setuid to
           user 202:
         

-

+        

           /usr/local/sbin/named -u 202 -t /var/named
         

-

+
+        

 

-The chroot Environment

-

-            In order for a chroot environment
+The chroot Environment

+          
+
+          

+            In order for a chroot environment
             to
             work properly in a particular directory
             (for example, /var/named),
@@ -282,12 +291,12 @@ allow-query { !{ !10/8; any; }; key example; };
             From BIND's point of view, /var/named is
             the root of the filesystem.  You will need to adjust the values of
             options like
-            like directory and pid-file to account
+            like directory and pid-file to account
             for this.
           

-

+          

             Unlike with earlier versions of BIND, you typically will
-            not need to compile named
+            not need to compile named
             statically nor install shared libraries under the new root.
             However, depending on your operating system, you may need
             to set up things like
@@ -296,45 +305,51 @@ allow-query { !{ !10/8; any; }; key example; };
             /dev/log, and
             /etc/localtime.
           

-

-

+        

+
+        

 

-Using the setuid Function

-

-            Prior to running the named daemon,
+Using the setuid Function

+          
+
+          

+            Prior to running the named daemon,
             use
-            the touch utility (to change file
+            the touch utility (to change file
             access and
-            modification times) or the chown
+            modification times) or the chown
             utility (to
             set the user id and/or group id) on files
             to which you want BIND
             to write.
           

-

+          

 
Note

-            Note that if the named daemon is running as an
+            Note that if the named daemon is running as an
             unprivileged user, it will not be able to bind to new restricted
             ports if the server is reloaded.
           

-

-
-

+        

+      
+
+      

 

 Dynamic Update Security

-

+        
+
+        

           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, by listing an IP address
           or
-          network prefix in the allow-update
+          network prefix in the allow-update
           zone option.
           This method is insecure since the source address of the update UDP
           packet
           is easily forged.  Also note that if the IP addresses allowed by the
-          allow-update option include the
+          allow-update option include the
           address of a slave
           server which performs forwarding of dynamic updates, the master can
           be
@@ -342,16 +357,18 @@ allow-query { !{ !10/8; any; }; key example; };
           forward it to the master with its own source IP address causing the
           master to approve it without question.
         

-

+
+        

           For these reasons, we strongly recommend that updates be
           cryptographically authenticated by means of transaction signatures
-          (TSIG).  That is, the allow-update
+          (TSIG).  That is, the allow-update
           option should
           list only TSIG key names, not IP addresses or network
-          prefixes. Alternatively, the new update-policy
+          prefixes. Alternatively, the new update-policy
           option can be used.
         

-

+
+        

           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
@@ -359,8 +376,9 @@ allow-query { !{ !10/8; any; }; key example; };
           of public web and mail servers need not allow dynamic update at
           all.
         

-

-
+
+      
+    
 

 

 
@@ -378,6 +396,6 @@ allow-query { !{ !10/8; any; }; key example; };
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html
index 0d5067c0f5..dd5587624a 100644
--- a/doc/arm/Bv9ARM.ch08.html
+++ b/doc/arm/Bv9ARM.ch08.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Chapter 8. Troubleshooting
-
-
+
+
 
 
 
@@ -39,37 +38,44 @@
 
 

 
-

-

-Chapter 8. Troubleshooting

+

+

+Chapter 8. Troubleshooting

 

 
Table of Contents

-

-
Common Problems

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

-
Incrementing and Changing the Serial Number

-
Where Can I Get Help?

+

+
Common Problems

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

+
Incrementing and Changing the Serial Number

+
Where Can I Get Help?

 

 

-

+      
+      

 

-Common Problems

-

+Common Problems

+        
+        

 

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

-

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

-
-
-

+
+        

+      
+      

 

-Incrementing and Changing the Serial Number

-

+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.
@@ -81,22 +87,27 @@
           lower than the serial number on the master, the slave
           server will attempt to update its copy of the zone.
         

-

+
+        

           Setting the serial number to a lower number on the master
           server than the slave server means that the slave 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 slaves have updated to
           the new zone serial number, then reset the number to what you want
           it to be, and reload the zone again.
         

-
-

+
+      

+      

 

-Where Can I Get Help?

-

+Where Can I Get Help?

+        
+
+        

           The Internet Systems Consortium
           (ISC) offers a wide range
           of support and service agreements for BIND and DHCP servers. Four
@@ -109,15 +120,16 @@
           fix announcements to remote support. It also includes training in
           BIND and DHCP.
         

-

+
+        

           To discuss arrangements for support, contact
-          info@isc.org or visit the
+          info@isc.org or visit the
           ISC web page at
-          http://www.isc.org/services/support/
+          http://www.isc.org/services/support/
           to read more.
         

-
-
+      
+    
 

 

 
@@ -135,6 +147,6 @@
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index 9c05c40c90..624679ddb7 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Appendix A. Release Notes
-
-
+
+
 
 
 
@@ -39,11 +38,912 @@
 
 

 
-

-

-Appendix A. Release Notes

-<xi:include></xi:include>
+

+

+Appendix A. Release Notes

+

+
Table of Contents

+

+
Release Notes for BIND Version 9.11.0pre-alpha

+

+
Introduction

+
Download

+
Security Fixes

+
New Features

+
Feature Changes

+
Porting Changes

+
Bug Fixes

+
End of Life

+
Thank You

+

+

 

+      
+      

+

+Release Notes for BIND Version 9.11.0pre-alpha

+  
+  

+

+Introduction

+    
+    

+      This document summarizes changes since the last production release
+      of BIND on the corresponding major release branch.
+    

+  

+  

+

+Download

+    
+    

+      The latest versions of BIND 9 software can always be found at
+      http://www.isc.org/downloads/.
+      There you will find additional information about each release,
+      source code, and pre-compiled versions for Microsoft Windows
+      operating systems.
+    

+  

+  

+

+Security Fixes

+    
+    
    
+
  • 
+	
    
+	  An incorrect boundary check in the OPENPGPKEY rdatatype
+	  could trigger an assertion failure. This flaw is disclosed
+	  in CVE-2015-5986. [RT #40286]
+	
    
+      
    • 
+
  • 
+	
    
+	  A buffer accounting error could trigger an assertion failure
+	  when parsing certain malformed DNSSEC keys.
+	
    
+	
    
+	  This flaw was discovered by Hanno Böck of the Fuzzing
+	  Project, and is disclosed in CVE-2015-5722. [RT #40212]
+	
    
+      
    • 
+
  • 
+	
    
+	  A specially crafted query could trigger an assertion failure
+	  in message.c.
+	
    
+	
    
+	  This flaw was discovered by Jonathan Foote, and is disclosed
+	  in CVE-2015-5477. [RT #40046]
+	
    
+      
    • 
+
  • 
+	
    
+	  On servers configured to perform DNSSEC validation, an
+	  assertion failure could be triggered on answers from
+	  a specially configured server.
+	
    
+	
    
+	  This flaw was discovered by Breno Silveira Soares, and is
+	  disclosed in CVE-2015-4620. [RT #39795]
+	
    
+      
    • 
+
  • 
+	
    
+	  On servers configured to perform DNSSEC validation using
+	  managed trust anchors (i.e., keys configured explicitly
+	  via managed-keys, or implicitly
+	  via dnssec-validation auto; or
+	  dnssec-lookaside auto;), revoking
+	  a trust anchor and sending a new untrusted replacement
+	  could cause named to crash with an
+	  assertion failure. This could occur in the event of a
+	  botched key rollover, or potentially as a result of a
+	  deliberate attack if the attacker was in position to
+	  monitor the victim's DNS traffic.
+	
    
+	
    
+	  This flaw was discovered by Jan-Piet Mens, and is
+	  disclosed in CVE-2015-1349. [RT #38344]
+	
    
+      
    • 
+
  • 
+	
    
+	  A flaw in delegation handling could be exploited to put
+	  named into an infinite loop, in which
+	  each lookup of a name server triggered additional lookups
+	  of more name servers.  This has been addressed by placing
+	  limits on the number of levels of recursion
+	  named will allow (default 7), and
+	  on the number of queries that it will send before
+	  terminating a recursive query (default 50).
+	
    
+	
    
+	  The recursion depth limit is configured via the
+	  max-recursion-depth option, and the query limit
+	  via the max-recursion-queries option.
+	
    
+	
    
+	  The flaw was discovered by Florian Maury of ANSSI, and is
+	  disclosed in CVE-2014-8500. [RT #37580]
+	
    
+      
    • 
+
  • 
+	
    
+	  Two separate problems were identified in BIND's GeoIP code that
+	  could lead to an assertion failure. One was triggered by use of
+	  both IPv4 and IPv6 address families, the other by referencing
+	  a GeoIP database in named.conf which was
+	  not installed. Both are covered by CVE-2014-8680. [RT #37672]
+	  [RT #37679]
+	
    
+	
    
+	  A less serious security flaw was also found in GeoIP: changes
+	  to the geoip-directory option in
+	  named.conf were ignored when running
+	  rndc reconfig. In theory, this could allow
+	  named to allow access to unintended clients.
+	
    
+      
    • 
+

+  

+  

+

+New Features

+    
+    
    
+
  • 
+	
    
+	  Added support for DynDB, a new interface for loading zone data
+	  from an external database, developed by Red Hat for the FreeIPA
+	  project.  (Thanks in particular to Adam Tkac and Petr
+	  Spacek of Red Hat for the contribution.)
+	
    
+	
    
+	  Unlike the existing DLZ and SDB interfaces, which provide a
+	  limited subset of database functionality within BIND —
+	  translating DNS queries into real-time database lookups with
+	  relatively poor performance and with no ability to handle
+	  DNSSEC-signed data — DynDB is able to fully implement
+	  and extend the database API used natively by BIND.
+	
    
+	
    
+	  A DynDB module could pre-load data from an external data
+	  source, then serve it with the same performance and
+	  functionality as conventional BIND zones, and with the
+	  ability to take advantage of database features not
+	  available in BIND, such as multi-master replication.
+	
    
+      
    • 
+
  • 
+	
    
+	  New quotas have been added to limit the queries that are
+	  sent by recursive resolvers to authoritative servers
+	  experiencing denial-of-service attacks. When configured,
+	  these options can both reduce the harm done to authoritative
+	  servers and also avoid the resource exhaustion that can be
+	  experienced by recursives when they are being used as a
+	  vehicle for such an attack.
+	
    
+	
      
+
    • 
+	    
      
+	      fetches-per-server limits the number of
+	      simultaneous queries that can be sent to any single
+	      authoritative server.  The configured value is a starting
+	      point; it is automatically adjusted downward if the server is
+	      partially or completely non-responsive. The algorithm used to
+	      adjust the quota can be configured via the
+	      fetch-quota-params option.
+	    
      
+	  
      • 
+
    • 
+	    
      
+	      fetches-per-zone limits the number of
+	      simultaneous queries that can be sent for names within a
+	      single domain.  (Note: Unlike "fetches-per-server", this
+	      value is not self-tuning.)
+	    
      
+	  
      • 
+
    
+	
    
+	  Statistics counters have also been added to track the number
+	  of queries affected by these quotas.
+	
    
+      
    • 
+
  • 
+	
    
+	  Added support for dnstap, a fast,
+	  flexible method for capturing and logging DNS traffic,
+	  developed by Robert Edmonds at Farsight Security, Inc.,
+	  whose assistance is gratefully acknowledged.
+	
    
+	
    
+	  To enable dnstap at compile time, 
+	  the fstrm and protobuf-c
+	  libraries must be available, and BIND must be configured with
+	  --enable-dnstap.
+	
    
+	
    
+	  A new utility dnstap-read has been added
+	  to allow dnstap data to be presented in
+	  a human-readable format.
+	
    
+	
    
+	  For more information on dnstap, see
+	  http://dnstap.info.
+	
    
+      
    • 
+
  • 
+	
    
+	  New statistics counters have been added to track traffic
+	  sizes, as specified in RSSAC002.  Query and response
+	  message sizes are broken up into ranges of histogram buckets:
+	  TCP and UDP queries of size 0-15, 16-31, ..., 272-288, and 288+,
+	  and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
+	  and 4096+.  These values can be accessed via the XML and JSON
+	  statistics channels at, for example,
+	  http://localhost:8888/xml/v3/traffic
+	  or
+	  http://localhost:8888/json/v1/traffic.
+	
    
+      
    • 
+
  • 
+	
    
+	  The serial number of a dynamically updatable zone can
+	  now be set using
+	  rndc signing -serial number zonename.
+	  This is particularly useful with inline-signing
+	  zones that have been reset.  Setting the serial number to a value
+	  larger than that on the slaves will trigger an AXFR-style
+	  transfer.
+	
    
+      
    • 
+
  • 
+	
    
+	  When answering recursive queries, SERVFAIL responses can now be
+	  cached by the server for a limited time; subsequent queries for
+	  the same query name and type will return another SERVFAIL until
+	  the cache times out.  This reduces the frequency of retries
+	  when a query is persistently failing, which can be a burden
+	  on recursive serviers.  The SERVFAIL cache timeout is controlled
+	  by servfail-ttl, which defaults to 10 seconds
+	  and has an upper limit of 30.
+	
    
+      
    • 
+
  • 
+	
    
+	  The new rndc nta command can now be used to
+	  set a "negative trust anchor" (NTA), disabling DNSSEC validation for
+	  a specific domain; this can be used when responses from a domain
+	  are known to be failing validation due to administrative error
+	  rather than because of a spoofing attack. NTAs are strictly
+	  temporary; by default they expire after one hour, but can be
+	  configured to last up to one week.  The default NTA lifetime
+	  can be changed by setting the nta-lifetime in
+	  named.conf. When added, NTAs are stored in a
+	  file (viewname.nta)
+	  in order to persist across restarts of the named server.
+	
    
+      
    • 
+
  • 
+	
    
+	  The EDNS Client Subnet (ECS) option is now supported for
+	  authoritative servers; if a query contains an ECS option then
+	  ACLs containing geoip or ecs
+	  elements can match against the the address encoded in the option.
+	  This can be used to select a view for a query, so that different
+	  answers can be provided depending on the client network.
+	
    
+      
    • 
+
  • 
+	
    
+	  The EDNS EXPIRE option has been implemented on the client
+	  side, allowing a slave server to set the expiration timer
+	  correctly when transferring zone data from another slave
+	  server.
+	
    
+      
    • 
+
  • 
+	
    
+	  A new masterfile-style zone option controls
+	  the formatting of text zone files:  When set to
+	  full, the zone file will dumped in
+	  single-line-per-record format.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +ednsopt can now be used to set
+	  arbitrary EDNS options in DNS requests.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +ednsflags can now be used to set
+	  yet-to-be-defined EDNS flags in DNS requests.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +[no]ednsnegotiation can now be used enable /
+	  disable EDNS version negotiation.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +header-only can now be used to send
+	  queries without a question section.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +ttlunits causes dig
+	  to print TTL values with time-unit suffixes: w, d, h, m, s for
+	  weeks, days, hours, minutes, and seconds.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +zflag can be used to set the last
+	  unassigned DNS header flag bit.  This bit in normally zero.
+	
    
+      
    • 
+
  • 
+	
    
+	  dig +dscp=value
+	  can now be used to set the DSCP code point in outgoing query
+	  packets.
+	
    
+      
    • 
+
  • 
+	
    
+	  serial-update-method can now be set to
+	  date. On update, the serial number will
+	  be set to the current date in YYYYMMDDNN format.
+	
    
+      
    • 
+
  • 
+	
    
+	  dnssec-signzone -N date also sets the serial
+	  number to YYYYMMDDNN.
+	
    
+      
    • 
+
  • 
+	
    
+	  named -L filename
+	  causes named to send log messages to the specified file by
+	  default instead of to the system log.
+	
    
+      
    • 
+
  • 
+	
    
+	  The rate limiter configured by the
+	  serial-query-rate option no longer covers
+	  NOTIFY messages; those are now separately controlled by
+	  notify-rate and
+	  startup-notify-rate (the latter of which
+	  controls the rate of NOTIFY messages sent when the server
+	  is first started up or reconfigured).
+	
    
+      
    • 
+
  • 
+	
    
+	  The default number of tasks and client objects available
+	  for serving lightweight resolver queries have been increased,
+	  and are now configurable via the new lwres-tasks
+	  and lwres-clients options in
+	  named.conf. [RT #35857]
+	
    
+      
    • 
+
  • 
+	
    
+	  Log output to files can now be buffered by specifying
+	  buffered yes; when creating a channel.
+	
    
+      
    • 
+
  • 
+	
    
+	  delv +tcp will exclusively use TCP when
+	  sending queries.
+	
    
+      
    • 
+
  • 
+	
    
+	  named will now check to see whether
+	  other name server processes are running before starting up.
+	  This is implemented in two ways: 1) by refusing to start
+	  if the configured network interfaces all return "address
+	  in use", and 2) by attempting to acquire a lock on a file
+	  specified by the lock-file option or
+	  the -X command line option.  The
+	  default lock file is
+	  /var/run/named/named.lock.
+	  Specifying none will disable the lock
+	  file check.
+	
    
+      
    • 
+
  • 
+	
    
+	  rndc delzone can now be applied to zones
+	  which were configured in named.conf;
+	  it is no longer restricted to zones which were added by
+	  rndc addzone.  (Note, however, that
+	  this does not edit named.conf; the zone
+	  must be removed from the configuration or it will return
+	  when named is restarted or reloaded.)
+	
    
+      
    • 
+
  • 
+	
    
+	  rndc modzone can be used to reconfigure
+	  a zone, using similar syntax to rndc addzone.
+	
    
+      
    • 
+
  • 
+	
    
+	  rndc showzone displays the current
+	  configuration for a specified zone.
+	
    
+      
    • 
+
  • 
+	
    
+	  Added server-side support for pipelined TCP queries.  Clients
+	  may continue sending queries via TCP while previous queries are
+	  processed in parallel.  Responses are sent when they are
+	  ready, not necessarily in the order in which the queries were
+	  received.
+	
    
+	
    
+	  To revert to the former behavior for a particular
+	  client address or range of addresses, specify the address prefix
+	  in the "keep-response-order" option.  To revert to the former
+	  behavior for all clients, use "keep-response-order { any; };".
+	
    
+      
    • 
+
  • 
+	
    
+	  The new mdig command is a version of
+	  dig that sends multiple pipelined
+	  queries and then waits for responses, instead of sending one
+	  query and waiting the response before sending the next. [RT #38261]
+	
    
+      
    • 
+
  • 
+	
    
+	  To enable better monitoring and troubleshooting of RFC 5011
+	  trust anchor management, the new rndc managed-keys
+	  can be used to check status of trust anchors or to force keys
+	  to be refreshed.  Also, the managed-keys data file now has
+	  easier-to-read comments. [RT #38458]
+	
    
+      
    • 
+
  • 
+	
    
+	  An --enable-querytrace configure switch is
+	  now available to enable very verbose query tracelogging. This
+	  option can only be set at compile time. This option has a
+	  negative performance impact and should be used only for
+	  debugging. [RT #37520]
+	
    
+      
    • 
+
  • 
+	
    
+	  A new tcp-only option can be specified
+	  in server statements to force
+	  named to connect to the specified
+	  server via TCP. [RT #37800]
+	
    
+      
    • 
+
  • 
+	
    
+	  The nxdomain-redirect option specifies
+	  a DNS namespace to use for NXDOMAIN redirection. When a
+	  recursive lookup returns NXDOMAIN, a second lookup is
+	  initiated with the specified name appended to the query
+	  name. This allows NXDOMAIN redirection data to be supplied
+	  by multiple zones configured on the server or by recursive
+	  queries to other servers. (The older method, using
+	  a single type redirect zone, has
+	  better average performance but is less flexible.) [RT #37989]
+	
    
+      
    • 
+
  • 
+	
    
+	  The following types have been implemented: CSYNC, NINFO, RKEY,
+	  SINK, TA, TALINK.
+	
    
+      
    • 
+

+  

+  

+

+Feature Changes

+    
+    
    
+
  • 
+	
    
+	  ACLs containing geoip asnum elements were
+	  not correctly matched unless the full organization name was
+	  specified in the ACL (as in
+	  geoip asnum "AS1234 Example, Inc.";).
+	  They can now match against the AS number alone (as in
+	  geoip asnum "AS1234";).
+	
    
+      
    • 
+
  • 
+	
    
+	  When using native PKCS#11 cryptography (i.e.,
+	  configure --enable-native-pkcs11) HSM PINs
+	  of up to 256 characters can now be used.
+	
    
+      
    • 
+
  • 
+	
    
+	  NXDOMAIN responses to queries of type DS are now cached separately
+	  from those for other types. This helps when using "grafted" zones
+	  of type forward, for which the parent zone does not contain a
+	  delegation, such as local top-level domains.  Previously a query
+	  of type DS for such a zone could cause the zone apex to be cached
+	  as NXDOMAIN, blocking all subsequent queries.  (Note: This
+	  change is only helpful when DNSSEC validation is not enabled.
+	  "Grafted" zones without a delegation in the parent are not a
+	  recommended configuration.)
+	
    
+      
    • 
+
  • 
+	
    
+	  Update forwarding performance has been improved by allowing
+	  a single TCP connection to be shared between multiple updates.
+	
    
+      
    • 
+
  • 
+	
    
+	  By default, nsupdate will now check
+	  the correctness of hostnames when adding records of type
+	  A, AAAA, MX, SOA, NS, SRV or PTR.  This behavior can be
+	  disabled with check-names no.
+	
    
+      
    • 
+
  • 
+	
    
+	  Added support for OPENPGPKEY type.
+	
    
+      
    • 
+
  • 
+	
    
+	  The names of the files used to store managed keys and added
+	  zones for each view are no longer based on the SHA256 hash
+	  of the view name, except when this is necessary because the
+	  view name contains characters that would be incompatible with use
+	  as a file name.  For views whose names do not contain forward
+	  slashes ('/'), backslashes ('\'), or capital letters - which
+	  could potentially cause namespace collision problems on
+	  case-insensitive filesystems - files will now be named
+	  after the view (for example, internal.mkeys
+	  or external.nzf).  However, to ensure
+	  consistent behavior when upgrading, if a file using the old
+	  name format is found to exist, it will continue to be used.
+	
    
+      
    • 
+
  • 
+	
    
+	  "rndc" can now return text output of arbitrary size to
+	  the caller. (Prior to this, certain commands such as
+	  "rndc tsig-list" and "rndc zonestatus" could return
+	  truncated output.)
+	
    
+      
    • 
+
  • 
+	
    
+	  Errors reported when running rndc addzone
+	  (e.g., when a zone file cannot be loaded) have been clarified
+	  to make it easier to diagnose problems.
+	
    
+      
    • 
+
  • 
+	
    
+	  When encountering an authoritative name server whose name is
+	  an alias pointing to another name, the resolver treats
+	  this as an error and skips to the next server. Previously
+	  this happened silently; now the error will be logged to
+	  the newly-created "cname" log category.
+	
    
+      
    • 
+
  • 
+	
    
+	  If named is not configured to validate the answer then
+	  allow fallback to plain DNS on timeout even when we know
+	  the server supports EDNS.  This will allow the server to
+	  potentially resolve signed queries when TCP is being
+	  blocked.
+	
    
+      
    • 
+
  • 
+	
    
+	  Large inline-signing changes should be less disruptive.
+	  Signature generation is now done incrementally; the number
+	  of signatures to be generated in each quantum is controlled
+	  by "sig-signing-signatures number;".
+	  [RT #37927]
+	
    
+      
    • 
+
  • 
+	
    
+	  The experimental SIT option (code point 65001) of BIND
+	  9.10.0 through BIND 9.10.2 has been replaced with the COOKIE
+	  option (code point 10). It is no longer experimental, and
+	  is sent by default, by both named and
+	  dig.
+	
    
+	
    
+	  The SIT-related named.conf options have been marked as
+	  obsolete, and are otherwise ignored.
+	
    
+      
    • 
+
  • 
+	
    
+	  When dig receives a truncated (TC=1)
+	  response or a BADCOOKIE response code from a server, it
+	  will automatically retry the query using the server COOKIE
+	  that was returned by the server in its initial response.
+	  [RT #39047]
+	
    
+      
    • 
+
  • 
+	
    
+	  A alternative NXDOMAIN redirect method (nxdomain-redirect)
+	  which allows the redirect information to be looked up from
+	  a namespace on the Internet rather than requiring a zone
+	  to be configured on the server is now available.
+	
    
+      
    • 
+
  • 
+	
    
+	  Retrieving the local port range from net.ipv4.ip_local_port_range
+	  on Linux is now supported.
+	
    
+      
    • 
+
  • 
+	
    
+	  Within the response-policy option, it is now
+	  possible to configure RPZ rewrite logging on a per-zone basis
+	  using the log clause.
+	
    
+      
    • 
+
  • 
+	
    
+	  The default preferred glue is now the address type of the
+	   transport the query was received over.
+	
    
+      
    • 
+
  • 
+	
    
+	  On machines with 2 or more processors (CPU), the default value
+	  for the number of UDP listeners has been changed to the number
+	  of detected processors minus one.
+	
    
+      
    • 
+

+  

+  

+

+Porting Changes

+    
+    
  • 
+	
    
+	  The Microsoft Windows install tool
+	  BINDInstall.exe which requires a
+	  non-free version of Visual Studio to be built, now uses two
+	  files (lists of flags and files) created by the Configure
+	  perl script with all the needed information which were
+	  previously compiled in the binary. Read
+	  win32utils/build.txt for more details.
+	  [RT #38915]
+	
    
+      

+  

+  

+

+Bug Fixes

+    
+    
    
+
  • 
+	
    
+	  dig, host and
+	  nslookup aborted when encountering
+	  a name which, after appending search list elements,
+	  exceeded 255 bytes. Such names are now skipped, but
+	  processing of other names will continue. [RT #36892]
+	
    
+      
    • 
+
  • 
+	
    
+	  The error message generated when
+	  named-checkzone or
+	  named-checkconf -z encounters a
+	  $TTL directive without a value has
+	  been clarified. [RT #37138]
+	
    
+      
    • 
+
  • 
+	
    
+	  Semicolon characters (;) included in TXT records were
+	  incorrectly escaped with a backslash when the record was
+	  displayed as text. This is actually only necessary when there
+	  are no quotation marks. [RT #37159]
+	
    
+      
    • 
+
  • 
+	
    
+	  When files opened for writing by named,
+	  such as zone journal files, were referenced more than once
+	  in named.conf, it could lead to file
+	  corruption as multiple threads wrote to the same file. This
+	  is now detected when loading named.conf
+	  and reported as an error. [RT #37172]
+	
    
+      
    • 
+
  • 
+	
    
+	  When checking for updates to trust anchors listed in
+	  managed-keys, named
+	  now revalidates keys based on the current set of
+	  active trust anchors, without relying on any cached
+	  record of previous validation. [RT #37506]
+	
    
+      
    • 
+
  • 
+	
    
+	  Large-system tuning
+	  (configure --with-tuning=large) caused
+	  problems on some platforms by setting a socket receive
+	  buffer size that was too large.  This is now detected and
+	  corrected at run time. [RT #37187]
+	
    
+      
    • 
+
  • 
+	
    
+	  When NXDOMAIN redirection is in use, queries for a name
+	  that is present in the redirection zone but a type that
+	  is not present will now return NOERROR instead of NXDOMAIN.
+	
    
+      
    • 
+
  • 
+	
    
+	  Due to an inadvertent removal of code in the previous
+	  release, when named encountered an
+	  authoritative name server which dropped all EDNS queries,
+	  it did not always try plain DNS. This has been corrected.
+	  [RT #37965]
+	
    
+      
    • 
+
  • 
+	
    
+	  A regression caused nsupdate to use the default recursive servers
+	  rather than the SOA MNAME server when sending the UPDATE.
+	
    
+      
    • 
+
  • 
+	
    
+	  Adjusted max-recursion-queries to accommodate the smaller
+	  initial packet sizes used in BIND 9.10 and higher when
+	  contacting authoritative servers for the first time.
+	
    
+      
    • 
+
  • 
+	
    
+	  Built-in "empty" zones did not correctly inherit the
+	  "allow-transfer" ACL from the options or view. [RT #38310]
+	
    
+      
    • 
+
  • 
+	
    
+	  Two leaks were fixed that could cause named
+	  processes to grow to very large sizes. [RT #38454]
+	
    
+      
    • 
+
  • 
+	
    
+	  Fixed some bugs in RFC 5011 trust anchor management,
+	  including a memory leak and a possible loss of state
+	  information. [RT #38458]
+	
    
+      
    • 
+
  • 
+	
    
+	  Asynchronous zone loads were not handled correctly when the
+	  zone load was already in progress; this could trigger a crash
+	  in zt.c. [RT #37573]
+	
    
+      
    • 
+
  • 
+	
    
+	  A race during shutdown or reconfiguration could
+	  cause an assertion failure in mem.c. [RT #38979]
+	
    
+      
    • 
+
  • 
+	
    
+	  Some answer formatting options didn't work correctly with
+	  dig +short. [RT #39291]
+	
    
+      
    • 
+
  • 
+	
    
+	  Several bugs have been fixed in the RPZ implementation:
+	
    
+	
      
+
    • 
+	    
      
+	      Policy zones that did not specifically require recursion
+	      could be treated as if they did; consequently, setting
+	      qname-wait-recurse no; was
+	      sometimes ineffective.  This has been corrected.
+	      In most configurations, behavioral changes due to this
+	      fix will not be noticeable. [RT #39229]
+	    
      
+	  
      • 
+
    • 
+	    
      
+	      The server could crash if policy zones were updated (e.g.
+	      via rndc reload or an incoming zone
+	      transfer) while RPZ processing was still ongoing for an
+	      active query. [RT #39415]
+	    
      
+	  
      • 
+
    • 
+	    
      
+	      On servers with one or more policy zones configured as
+	      slaves, if a policy zone updated during regular operation
+	      (rather than at startup) using a full zone reload, such as
+	      via AXFR, a bug could allow the RPZ summary data to fall out
+	      of sync, potentially leading to an assertion failure in
+	      rpz.c when further incremental updates were made to the
+	      zone, such as via IXFR. [RT #39567]
+	    
      
+	  
      • 
+
    • 
+	    
      
+	      The server could match a shorter prefix than what was
+	      available in CLIENT-IP policy triggers, and so, an
+	      unexpected action could be taken. This has been
+	      corrected. [RT #39481]
+	    
      
+	  
      • 
+
    • 
+	    
      
+	      The server could crash if a reload of an RPZ zone was
+	      initiated while another reload of the same zone was
+	      already in progress. [RT #39649]
+	    
      
+	  
      • 
+
    
+      
    • 
+

+  

+  

+

+End of Life

+    
+    

+      The end of life for BIND 9.11 is yet to be determined but
+      will not be before BIND 9.13.0 has been released for 6 months.
+      https://www.isc.org/downloads/software-support-policy/
+    

+  

+  

+

+Thank You

+    
+    

+      Thank you to everyone who assisted us in making this release possible.
+      If you would like to contribute to ISC to assist us in continuing to
+      make quality open source software, please visit our donations page at
+      http://www.isc.org/donate/.
+    

+  

+

+    

 

 

 
@@ -62,6 +962,6 @@
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch10.html b/doc/arm/Bv9ARM.ch10.html
index 749e2c3d49..bdf4b4d77b 100644
--- a/doc/arm/Bv9ARM.ch10.html
+++ b/doc/arm/Bv9ARM.ch10.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Appendix B. A Brief History of the DNS and BIND
-
-
+
+
 
 
 
@@ -40,11 +39,22 @@
 
 

 

-

-

+

+

 Appendix B. A Brief History of the DNS and BIND
-

-

+

+

+
Table of Contents

+

+
DNS

+
BIND

+

+

+      
+      

+

+DNS

+          

             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
@@ -59,7 +69,8 @@
             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
@@ -77,7 +88,12 @@
             Administration
             (DARPA).
           

-

+      

+
+      

+

+BIND

+          

             Versions of BIND through
             4.8.3 were maintained by the Computer
             Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
@@ -92,7 +108,7 @@
             Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently
             handled by Mike Karels and Øivind Kure.
           

-

+          

             BIND versions 4.9 and 4.9.1 were
             released by Digital Equipment
             Corporation (now Compaq Computer Corporation). Paul Vixie, then
@@ -104,41 +120,42 @@
             Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
             Wolfhugel, and others.
           

-

+          

             In 1994, 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 Systems Consortium and its predecessor,
             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 version 9 was released in September 2000 and is a
             major rewrite of nearly all aspects of the underlying
             BIND architecture.
           

-

+          

             BIND versions 4 and 8 are officially deprecated.
             No additional development is done
             on BIND version 4 or BIND version 8.
           

-

+          

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

-

+      

+    
 

 

 
@@ -156,6 +173,6 @@
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch11.html b/doc/arm/Bv9ARM.ch11.html
index 183a24f84e..035906aa1c 100644
--- a/doc/arm/Bv9ARM.ch11.html
+++ b/doc/arm/Bv9ARM.ch11.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Appendix C. General DNS Reference Information
-
-
+
+
 
 
 
@@ -39,25 +38,27 @@
 
 

 
-

-

-Appendix C. General DNS Reference Information

+

+

+Appendix C. General DNS Reference Information

 

 
Table of Contents

-

-
IPv6 addresses (AAAA)

-
Bibliography (and Suggested Reading)

+

+
IPv6 addresses (AAAA)

+
Bibliography (and Suggested Reading)

 

-
Request for Comments (RFCs)

-
Internet Drafts

-
Other Documents About BIND

+
Request for Comments (RFCs)

+
Internet Drafts

+
Other Documents About BIND

 

 

 

-

+      
+      

 

 IPv6 addresses (AAAA)

-

+          
+          

             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,
@@ -68,13 +69,13 @@
             Unicast address scheme. For more information, see RFC 3587,
             "Global Unicast Address Format."
           

-

+          

             IPv6 unicast addresses consist of a
             global routing prefix, a
             subnet identifier, and an
             interface identifier.
           

-

+          

             The global routing prefix is provided by the
             upstream provider or ISP, and (roughly) corresponds to the
             IPv4 network section
@@ -88,22 +89,22 @@
             interface on a given network; in IPv6, addresses belong to
             interfaces rather than to machines.
           

-

+          

             The subnetting capability of IPv6 is much more flexible than
             that of IPv4: subnetting can be carried out on bit boundaries,
             in much the same way as Classless InterDomain Routing
             (CIDR), and the DNS PTR representation ("nibble" format)
             makes setting up reverse zones easier.
           

-

+          

             The Interface Identifier must be unique on the local link,
             and is usually generated automatically by the IPv6
             implementation, although it is usually possible to
             override the default setting if necessary.  A typical IPv6
             address might look like:
-            2001:db8:201:9:a00:20ff:fe81:2b32
+            2001:db8:201:9:a00:20ff:fe81:2b32
           

-

+          

             IPv6 address specifications often contain long strings
             of zeros, so the architects have included a shorthand for
             specifying
@@ -111,14 +112,16 @@
             string
             of zeros that can fit, and can be used only once in an address.
           

-

-

+      

+      

 

 Bibliography (and Suggested Reading)

-

+        
+        

 

 Request for Comments (RFCs)

-

+          
+          

             Specification documents for the Internet protocol suite, including
             the DNS, are published as part of
             the Request for Comments (RFCs)
@@ -126,352 +129,776 @@
             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/RFCxxxx.txt
             
           

-

+          

             (where xxxx is
             the number of the RFC). RFCs are also available via the Web at:
           

-

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

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

-

+          

 

-Bibliography

-

-
Standards

-

-
[RFC974] C. Partridge. Mail Routing and the Domain System. January 1986. 

+Bibliography

+            

+

+Standards

+              
+              
+              

+
[RFC974] 
+                
+                C. Partridge. 
+                Mail Routing and the Domain System. 
+                January 1986. 
+              

 

-

-
[RFC1034] P.V. Mockapetris. Domain Names — Concepts and Facilities. November 1987. 

+              

+
[RFC1034] 
+                
+                P.V. Mockapetris. 
+                Domain Names — Concepts and Facilities. 
+                November 1987. 
+              

 

-

-
[RFC1035] P. V. Mockapetris. Domain Names — Implementation and
-                  Specification. November 1987. 

+              

+
[RFC1035] 
+                
+                P. V. Mockapetris.  Domain Names — Implementation and
+                  Specification. 
+                November 1987. 
+              

 

-

-

+            

+            

 

 Proposed Standards

-

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

+
+              
+              
+              

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

 

-

-
[RFC2308] M. Andrews. Negative Caching of DNS
-                  Queries. March 1998. 

+              

+
[RFC2308] 
+                
+                M. Andrews. 
+                Negative Caching of DNS
+                  Queries. 
+                March 1998. 
+              

 

-

-
[RFC1995] M. Ohta. Incremental Zone Transfer in DNS. August 1996. 

+              

+
[RFC1995] 
+                
+                M. Ohta. 
+                Incremental Zone Transfer in DNS. 
+                August 1996. 
+              

 

-

-
[RFC1996] P. Vixie. A Mechanism for Prompt Notification of Zone Changes. August 1996. 

+              

+
[RFC1996] 
+                
+                P. Vixie. 
+                A Mechanism for Prompt Notification of Zone Changes. 
+                August 1996. 
+              

 

-

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

+              

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

 

-

-
[RFC2671] P. Vixie. Extension Mechanisms for DNS (EDNS0). August 1997. 

+              

+
[RFC2671] 
+                
+                P. Vixie. 
+                Extension Mechanisms for DNS (EDNS0). 
+                August 1997. 
+              

 

-

-
[RFC2672] M. Crawford. Non-Terminal DNS Name Redirection. August 1999. 

+              

+
[RFC2672] 
+                
+                M. Crawford. 
+                Non-Terminal DNS Name Redirection. 
+                August 1999. 
+              

 

-

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

+              

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

 

-

-
[RFC2930] D. Eastlake, 3rd. Secret Key Establishment for DNS (TKEY RR). September 2000. 

+              

+
[RFC2930] 
+                
+                D. Eastlake, 3rd. 
+                Secret Key Establishment for DNS (TKEY RR). 
+                September 2000. 
+              

 

-

-
[RFC2931] D. Eastlake, 3rd. DNS Request and Transaction Signatures (SIG(0)s). September 2000. 

+              

+
[RFC2931] 
+                
+                D. Eastlake, 3rd. 
+                DNS Request and Transaction Signatures (SIG(0)s). 
+                September 2000. 
+              

 

-

-
[RFC3007] B. Wellington. Secure Domain Name System (DNS) Dynamic Update. November 2000. 

+              

+
[RFC3007] 
+                
+                B. Wellington. 
+                Secure Domain Name System (DNS) Dynamic Update. 
+                November 2000. 
+              

 

-

-
[RFC3645] S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. Generic Security Service Algorithm for Secret
+              

+
[RFC3645] 
+                
+                S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. 
+                Generic Security Service Algorithm for Secret
                        Key Transaction Authentication for DNS
-                       (GSS-TSIG). October 2003. 

+                       (GSS-TSIG). 
+                October 2003. 
+              

 

-

-

+            

+            

 

-DNS Security Proposed Standards

-

-
[RFC3225] D. Conrad. Indicating Resolver Support of DNSSEC. December 2001. 

+DNS Security Proposed Standards
+              
+              

+
[RFC3225] 
+                
+                D. Conrad. 
+                Indicating Resolver Support of DNSSEC. 
+                December 2001. 
+              

 

-

-
[RFC3833] D. Atkins and R. Austein. Threat Analysis of the Domain Name System (DNS). August 2004. 

+              

+
[RFC3833] 
+                
+                D. Atkins and R. Austein. 
+                Threat Analysis of the Domain Name System (DNS). 
+                August 2004. 
+              

 

-

-
[RFC4033] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. March 2005. 

+              

+
[RFC4033] 
+                
+                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
+                DNS Security Introduction and Requirements. 
+                March 2005. 
+              

 

-

-
[RFC4034] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Resource Records for the DNS Security Extensions. March 2005. 

+              

+
[RFC4034] 
+                
+                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
+                Resource Records for the DNS Security Extensions. 
+                March 2005. 
+              

 

-

-
[RFC4035] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Protocol Modifications for the DNS
-                       Security Extensions. March 2005. 

+              

+
[RFC4035] 
+                
+                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
+                Protocol Modifications for the DNS
+                       Security Extensions. 
+                March 2005. 
+              

 

-

-

-
Other Important RFCs About DNS
+            

+            

+

+Other Important RFCs About DNS
                 Implementation

-

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

+              
+              

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

 

-

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

+              

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

 

-

-
[RFC1982] R. Elz and R. Bush. Serial Number Arithmetic. August 1996. 

+              

+
[RFC1982] 
+                
+                R. Elz and R. Bush. 
+                Serial Number Arithmetic. 
+                August 1996. 
+              

 

-

-
[RFC4074] Y. Morishita and T. Jinmei. Common Misbehaviour Against DNS
-                Queries for IPv6 Addresses. May 2005. 

+              

+
[RFC4074] 
+                
+                Y. Morishita and T. Jinmei. 
+                Common Misbehaviour Against DNS
+                Queries for IPv6 Addresses. 
+                May 2005. 
+              

 

+            

+            

+

+Resource Record Types

+              
+              

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

 

-

-
Resource Record Types

-

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

+              

+
[RFC1706] 
+                
+                B. Manning and R. Colella. 
+                DNS NSAP Resource Records. 
+                October 1994. 
+              

 

-

-
[RFC1706] B. Manning and R. Colella. DNS NSAP Resource Records. October 1994. 

+              

+
[RFC2168] 
+                
+                R. Daniel and M. Mealling. 
+                Resolution of Uniform Resource Identifiers using
+                  the Domain Name System. 
+                June 1997. 
+              

 

-

-
[RFC2168] R. Daniel and M. Mealling. Resolution of Uniform Resource Identifiers using
-                  the Domain Name System. June 1997. 

-

-

-
[RFC1876] C. Davis, P. Vixie, T., and I. Dickinson. A Means for Expressing Location Information in the
+              

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

+                  Name System. 
+                January 1996. 
+              

 

-

-
[RFC2052] A. Gulbrandsen and P. Vixie. A DNS RR for Specifying the
+              

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

+                  Services. 
+                October 1996. 
+              

 

-

-
[RFC2163] A. Allocchio. Using the Internet DNS to
+              

+
[RFC2163] 
+                
+                A. Allocchio. 
+                Using the Internet DNS to
                   Distribute MIXER
-                  Conformant Global Address Mapping. January 1998. 

+                  Conformant Global Address Mapping. 
+                January 1998. 
+              

 

-

-
[RFC2230] R. Atkinson. Key Exchange Delegation Record for the DNS. October 1997. 

+              

+
[RFC2230] 
+                
+                R. Atkinson. 
+                Key Exchange Delegation Record for the DNS. 
+                October 1997. 
+              

 

-

-
[RFC2536] D. Eastlake, 3rd. DSA KEYs and SIGs in the Domain Name System (DNS). March 1999. 

+              

+
[RFC2536] 
+                
+                D. Eastlake, 3rd. 
+                DSA KEYs and SIGs in the Domain Name System (DNS). 
+                March 1999. 
+              

 

-

-
[RFC2537] D. Eastlake, 3rd. RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999. 

+              

+
[RFC2537] 
+                
+                D. Eastlake, 3rd. 
+                RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). 
+                March 1999. 
+              

 

-

-
[RFC2538] D. Eastlake, 3rd and O. Gudmundsson. Storing Certificates in the Domain Name System (DNS). March 1999. 

+              

+
[RFC2538] 
+                
+                D. Eastlake, 3rd and O. Gudmundsson. 
+                Storing Certificates in the Domain Name System (DNS). 
+                March 1999. 
+              

 

-

-
[RFC2539] D. Eastlake, 3rd. Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999. 

+              

+
[RFC2539] 
+                
+                D. Eastlake, 3rd. 
+                Storage of Diffie-Hellman Keys in the Domain Name System (DNS). 
+                March 1999. 
+              

 

-

-
[RFC2540] D. Eastlake, 3rd. Detached Domain Name System (DNS) Information. March 1999. 

+              

+
[RFC2540] 
+                
+                D. Eastlake, 3rd. 
+                Detached Domain Name System (DNS) Information. 
+                March 1999. 
+              

 

-

-
[RFC2782] A. Gulbrandsen. P. Vixie. L. Esibov. A DNS RR for specifying the location of services (DNS SRV). February 2000. 

+              

+
[RFC2782] 
+                
+                A. Gulbrandsen. 
+                P. Vixie. 
+                L. Esibov. 
+                A DNS RR for specifying the location of services (DNS SRV). 
+                February 2000. 
+              

 

-

-
[RFC2915] M. Mealling. R. Daniel. The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000. 

+              

+
[RFC2915] 
+                
+                M. Mealling. 
+                R. Daniel. 
+                The Naming Authority Pointer (NAPTR) DNS Resource Record. 
+                September 2000. 
+              

 

-

-
[RFC3110] D. Eastlake, 3rd. RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001. 

+              

+
[RFC3110] 
+                
+                D. Eastlake, 3rd. 
+                RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). 
+                May 2001. 
+              

 

-

-
[RFC3123] P. Koch. A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001. 

+              

+
[RFC3123] 
+                
+                P. Koch. 
+                A DNS RR Type for Lists of Address Prefixes (APL RR). 
+                June 2001. 
+              

 

-

-
[RFC3596] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. DNS Extensions to support IP
-                  version 6. October 2003. 

+              

+
[RFC3596] 
+                
+                S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. 
+                DNS Extensions to support IP
+                  version 6. 
+                October 2003. 
+              

 

-

-
[RFC3597] A. Gustafsson. Handling of Unknown DNS Resource Record (RR) Types. September 2003. 

+              

+
[RFC3597] 
+                
+                A. Gustafsson. 
+                Handling of Unknown DNS Resource Record (RR) Types. 
+                September 2003. 
+              

 

-

-

+            

+            

 

-DNS and the Internet

-

-
[RFC1101] P. V. Mockapetris. DNS Encoding of Network Names
-                  and Other Types. April 1989. 

+DNS and the Internet
+              
+              

+
[RFC1101] 
+                
+                P. V. Mockapetris. 
+                DNS Encoding of Network Names
+                  and Other Types. 
+                April 1989. 
+              

 

-

-
[RFC1123] Braden. Requirements for Internet Hosts - Application and
-                  Support. October 1989. 

+              

+
[RFC1123] 
+                
+                Braden. 
+                Requirements for Internet Hosts - Application and
+                  Support. 
+                October 1989. 
+              

 

-

-
[RFC1591] J. Postel. Domain Name System Structure and Delegation. March 1994. 

+              

+
[RFC1591] 
+                
+                J. Postel. 
+                Domain Name System Structure and Delegation. 
+                March 1994. 
+              

 

-

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

+              

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

 

-

-
[RFC2826] Internet Architecture Board. IAB Technical Comment on the Unique DNS Root. May 2000. 

+              

+
[RFC2826] 
+                
+                Internet Architecture Board. 
+                IAB Technical Comment on the Unique DNS Root. 
+                May 2000. 
+              

 

-

-
[RFC2929] D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. September 2000. 

+              

+
[RFC2929] 
+                
+                D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. 
+                Domain Name System (DNS) IANA Considerations. 
+                September 2000. 
+              

 

-

-

+            

+            

 

-DNS Operations

-

-
[RFC1033] M. Lottor. Domain administrators operations guide. November 1987. 

+DNS Operations
+              
+              

+
[RFC1033] 
+                
+                M. Lottor. 
+                Domain administrators operations guide. 
+                November 1987. 
+              

 

-

-
[RFC1537] P. Beertema. Common DNS Data File
-                  Configuration Errors. October 1993. 

+              

+
[RFC1537] 
+                
+                P. Beertema. 
+                Common DNS Data File
+                  Configuration Errors. 
+                October 1993. 
+              

 

-

-
[RFC1912] D. Barr. Common DNS Operational and
-                  Configuration Errors. February 1996. 

+              

+
[RFC1912] 
+                
+                D. Barr. 
+                Common DNS Operational and
+                  Configuration Errors. 
+                February 1996. 
+              

 

-

-
[RFC2010] B. Manning and P. Vixie. Operational Criteria for Root Name Servers. October 1996. 

+              

+
[RFC2010] 
+                
+                B. Manning and P. Vixie. 
+                Operational Criteria for Root Name Servers. 
+                October 1996. 
+              

 

-

-
[RFC2219] M. Hamilton and R. Wright. Use of DNS Aliases for
-                  Network Services. October 1997. 

+              

+
[RFC2219] 
+                
+                M. Hamilton and R. Wright. 
+                Use of DNS Aliases for
+                  Network Services. 
+                October 1997. 
+              

 

+            

+            

+

+Internationalized Domain Names

+              
+              

+
[RFC2825] 
+                
+                IAB and R. Daigle. 
+                A Tangled Web: Issues of I18N, Domain Names,
+                       and the Other Internet protocols. 
+                May 2000. 
+              

 

-

-
Internationalized Domain Names

-

-
[RFC2825] IAB and R. Daigle. A Tangled Web: Issues of I18N, Domain Names,
-                       and the Other Internet protocols. May 2000. 

+              

+
[RFC3490] 
+                
+                P. Faltstrom, P. Hoffman, and A. Costello. 
+                Internationalizing Domain Names in Applications (IDNA). 
+                March 2003. 
+              

 

-

-
[RFC3490] P. Faltstrom, P. Hoffman, and A. Costello. Internationalizing Domain Names in Applications (IDNA). March 2003. 

+              

+
[RFC3491] 
+                
+                P. Hoffman and M. Blanchet. 
+                Nameprep: A Stringprep Profile for Internationalized Domain Names. 
+                March 2003. 
+              

 

-

-
[RFC3491] P. Hoffman and M. Blanchet. Nameprep: A Stringprep Profile for Internationalized Domain Names. March 2003. 

-

-

-
[RFC3492] A. Costello. Punycode: A Bootstring encoding of Unicode
+              

+
[RFC3492] 
+                
+                A. Costello. 
+                Punycode: A Bootstring encoding of Unicode
                        for Internationalized Domain Names in
-                       Applications (IDNA). March 2003. 

+                       Applications (IDNA). 
+                March 2003. 
+              

 

-

-

-
Other DNS-related RFCs

-

+            

+            

+

+Other DNS-related RFCs

+              
+              

 
Note

-

+                

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

+              

+              

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

 

-

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

+              

+
[RFC1713] 
+                
+                A. Romao. 
+                Tools for DNS Debugging. 
+                November 1994. 
+              

 

-

-
[RFC1713] A. Romao. Tools for DNS Debugging. November 1994. 

+              

+
[RFC1794] 
+                
+                T. Brisco. 
+                DNS Support for Load
+                  Balancing. 
+                April 1995. 
+              

 

-

-
[RFC1794] T. Brisco. DNS Support for Load
-                  Balancing. April 1995. 

+              

+
[RFC2240] 
+                
+                O. Vaughan. 
+                A Legal Basis for Domain Name Allocation. 
+                November 1997. 
+              

 

-

-
[RFC2240] O. Vaughan. A Legal Basis for Domain Name Allocation. November 1997. 

+              

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

 

-

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

+              

+
[RFC2352] 
+                
+                O. Vaughan. 
+                A Convention For Using Legal Names as Domain Names. 
+                May 1998. 
+              

 

-

-
[RFC2352] O. Vaughan. A Convention For Using Legal Names as Domain Names. May 1998. 

+              

+
[RFC3071] 
+                
+                J. Klensin. 
+                Reflections on the DNS, RFC 1591, and Categories of Domains. 
+                February 2001. 
+              

 

-

-
[RFC3071] J. Klensin. Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001. 

+              

+
[RFC3258] 
+                
+                T. Hardie. 
+                Distributing Authoritative Name Servers via
+                       Shared Unicast Addresses. 
+                April 2002. 
+              

 

-

-
[RFC3258] T. Hardie. Distributing Authoritative Name Servers via
-                       Shared Unicast Addresses. April 2002. 

+              

+
[RFC3901] 
+                
+                A. Durand and J. Ihren. 
+                DNS IPv6 Transport Operational Guidelines. 
+                September 2004. 
+              

 

-

-
[RFC3901] A. Durand and J. Ihren. DNS IPv6 Transport Operational Guidelines. September 2004. 

+            

+            

+

+Obsolete and Unimplemented Experimental RFC

+              
+              

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

 

+              

+
[RFC2673] 
+                
+                M. Crawford. 
+                Binary Labels in the Domain Name System. 
+                August 1999. 
+              

 

-

-
Obsolete and Unimplemented Experimental RFC

-

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

+              

+
[RFC2874] 
+                
+                M. Crawford and C. Huitema. 
+                DNS Extensions to Support IPv6 Address Aggregation
+                       and Renumbering. 
+                July 2000. 
+              

 

-

-
[RFC2673] M. Crawford. Binary Labels in the Domain Name System. August 1999. 

-

-

-
[RFC2874] M. Crawford and C. Huitema. DNS Extensions to Support IPv6 Address Aggregation
-                       and Renumbering. July 2000. 

-

-

-

-
Obsoleted DNS Security RFCs

-

+            

+            

+

+Obsoleted DNS Security RFCs

+              
+              

 
Note

-

+                

                   Most of these have been consolidated into RFC4033,
                   RFC4034 and RFC4035 which collectively describe DNSSECbis.
                 

+              

+              

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

 

-

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

+              

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

 

-

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

+              

+
[RFC2535] 
+                
+                D. Eastlake, 3rd. 
+                Domain Name System Security Extensions. 
+                March 1999. 
+              

 

-

-
[RFC2535] D. Eastlake, 3rd. Domain Name System Security Extensions. March 1999. 

+              

+
[RFC3008] 
+                
+                B. Wellington. 
+                Domain Name System Security (DNSSEC)
+                       Signing Authority. 
+                November 2000. 
+              

 

-

-
[RFC3008] B. Wellington. Domain Name System Security (DNSSEC)
-                       Signing Authority. November 2000. 

+              

+
[RFC3090] 
+                
+                E. Lewis. 
+                DNS Security Extension Clarification on Zone Status. 
+                March 2001. 
+              

 

-

-
[RFC3090] E. Lewis. DNS Security Extension Clarification on Zone Status. March 2001. 

+              

+
[RFC3445] 
+                
+                D. Massey and S. Rose. 
+                Limiting the Scope of the KEY Resource Record (RR). 
+                December 2002. 
+              

 

-

-
[RFC3445] D. Massey and S. Rose. Limiting the Scope of the KEY Resource Record (RR). December 2002. 

+              

+
[RFC3655] 
+                
+                B. Wellington and O. Gudmundsson. 
+                Redefinition of DNS Authenticated Data (AD) bit. 
+                November 2003. 
+              

 

-

-
[RFC3655] B. Wellington and O. Gudmundsson. Redefinition of DNS Authenticated Data (AD) bit. November 2003. 

+              

+
[RFC3658] 
+                
+                O. Gudmundsson. 
+                Delegation Signer (DS) Resource Record (RR). 
+                December 2003. 
+              

 

-

-
[RFC3658] O. Gudmundsson. Delegation Signer (DS) Resource Record (RR). December 2003. 

+              

+
[RFC3755] 
+                
+                S. Weiler. 
+                Legacy Resolver Compatibility for Delegation Signer (DS). 
+                May 2004. 
+              

 

-

-
[RFC3755] S. Weiler. Legacy Resolver Compatibility for Delegation Signer (DS). May 2004. 

+              

+
[RFC3757] 
+                
+                O. Kolkman, J. Schlyter, and E. Lewis. 
+                Domain Name System KEY (DNSKEY) Resource Record
+                      (RR) Secure Entry Point (SEP) Flag. 
+                April 2004. 
+              

 

-

-
[RFC3757] O. Kolkman, J. Schlyter, and E. Lewis. Domain Name System KEY (DNSKEY) Resource Record
-                      (RR) Secure Entry Point (SEP) Flag. April 2004. 

+              

+
[RFC3845] 
+                
+                J. Schlyter. 
+                DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. 
+                August 2004. 
+              

 

-

-
[RFC3845] J. Schlyter. DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004. 

-

-

-

-

-

+            

+          

+        

+        

 

 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
@@ -481,22 +908,27 @@
             they are "works in progress." IDs have a lifespan of six months
             after which they are deleted unless updated by their authors.
           

-

-

+        

+        

 

-Other Documents About BIND
+Other Documents About BIND
 

-

-

+          
+          

+          

 

-Bibliography

-

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

-

-

-

-

+Bibliography

+            

+

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

 

+          

+        

+      

+    

 

 

 
@@ -514,6 +946,6 @@
 

 

 

-
BIND 9.11.0pre-alpha

+
BIND 9.11.0pre-alpha

 
 
diff --git a/doc/arm/Bv9ARM.ch12.html b/doc/arm/Bv9ARM.ch12.html
index 2ff2434666..7c33aeed6d 100644
--- a/doc/arm/Bv9ARM.ch12.html
+++ b/doc/arm/Bv9ARM.ch12.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Appendix D. BIND 9 DNS Library Support
-
-
+
+
 
 
 
@@ -39,111 +38,128 @@
 
 

 

-

-

-Appendix D. BIND 9 DNS Library Support

+

+

+Appendix D. BIND 9 DNS Library Support

 

 
Table of Contents

-

-
BIND 9 DNS Library Support

+

+
BIND 9 DNS Library Support

 

-
Prerequisite

-
Compilation

-
Installation

-
Known Defects/Restrictions

-
The dns.conf File

-
Sample Applications

-
Library References

+
Prerequisite

+
Compilation

+
Installation

+
Known Defects/Restrictions

+
The dns.conf File

+
Sample Applications

+
Library References

 

 

 

-

+      
+      

 

 BIND 9 DNS Library Support

-
This version of BIND 9 "exports" its internal libraries so
+  
+  
This version of BIND 9 "exports" its internal libraries so
   that they can be used by third-party applications more easily (we
   call them "export" libraries in this document). In addition to
   all major DNS-related APIs BIND 9 is currently using, the export
   libraries provide the following features:

-
    
-
  • The newly created "DNS client" module. This is a higher
+  
      
+
    • 
+      
      The newly created "DNS client" module. This is a higher
       level API that provides an interface to name resolution,
       single DNS transaction with a particular server, and dynamic
       update. Regarding name resolution, it supports advanced
       features such as DNSSEC validation and caching. This module
-      supports both synchronous and asynchronous mode.
      • 
-
    • The new "IRS" (Information Retrieval System) library.
+      supports both synchronous and asynchronous mode.
      
+    
      • 
+
    • 
+      
      The new "IRS" (Information Retrieval System) library.
       It provides an interface to parse the traditional resolv.conf
       file and more advanced, DNS-specific configuration file for
       the rest of this package (see the description for the
-      dns.conf file below).
      • 
-
    • As part of the IRS library, newly implemented standard
+      dns.conf file below).
      
+    
      • 
+
    • 
+      
      As part of the IRS library, newly implemented standard
       address-name mapping functions, getaddrinfo() and
       getnameinfo(), are provided. They use the DNSSEC-aware
       validating resolver backend, and could use other advanced
       features of the BIND 9 libraries such as caching. The
       getaddrinfo() function resolves both A and AAAA RRs
-      concurrently (when the address family is unspecified).
      • 
-
    • An experimental framework to support other event
-      libraries than BIND 9's internal event task system.
      • 
+      concurrently (when the address family is unspecified).
      
+    
+
    • 
+      
      An experimental framework to support other event
+      libraries than BIND 9's internal event task system.
      
+    
      • 
 
    
-
    
+  
    
 
    
-Prerequisite
    
-
    GNU make is required to build the export libraries (other
+Prerequisite

+    
+  
GNU make is required to build the export libraries (other
   part of BIND 9 can still be built with other types of make). In
   the reminder of this document, "make" means GNU make. Note that
   in some platforms you may need to invoke a different command name
   than "make" (e.g. "gmake") to indicate it's GNU make.

-

-

+  

+  

 

-Compilation

-
+Compilation

+    
+  
 $ ./configure --enable-exportlib [other flags]
 $ make
 

-

+  

   This will create (in addition to usual BIND 9 programs) and a
   separate set of libraries under the lib/export directory. For
   example, lib/export/dns/libdns.a is the archive file of the
   export version of the BIND 9 DNS library. Sample application
   programs using the libraries will also be built under the
   lib/export/samples directory (see below).

-

-

+  

+  

 

-Installation

-
+Installation

+    
+  
 $ cd lib/export
 $ make install
 

-

+  

   This will install library object files under the directory
   specified by the --with-export-libdir configure option (default:
   EPREFIX/lib/bind9), and header files under the directory
   specified by the --with-export-includedir configure option
   (default: PREFIX/include/bind9).
   Root privilege is normally required.
-  "make install" at the top directory will do the
+  "make install" at the top directory will do the
   same.
   

-

+  

   To see how to build your own
   application after the installation, see
   lib/export/samples/Makefile-postinstall.in.

-

-

+  

+  

 

-Known Defects/Restrictions

-
    
-
  • Currently, win32 is not supported for the export
+Known Defects/Restrictions

+    
+  
    
+
  • 
+
+      
    Currently, win32 is not supported for the export
       library. (Normal BIND 9 application can be built as
-      before).
    • 
-
  • 
-
    The "fixed" RRset order is not (currently) supported in
+      before).
    
+    
    • 
+
  • 
+      
    The "fixed" RRset order is not (currently) supported in
       the export library. If you want to use "fixed" RRset order
-      for, e.g. named while still building the
+      for, e.g. named while still building the
       export library even without the fixed order support, build
       them separately:
       
    
@@ -156,27 +172,34 @@ $ make
 

 

     

-
-
  • The client module and the IRS library currently do not
+    
    • 
+
  • 
+      
    The client module and the IRS library currently do not
       support DNSSEC validation using DLV (the underlying modules
       can handle it, but there is no tunable interface to enable
-      the feature).
    • 
-
  • RFC 5011 is not supported in the validating stub
+      the feature).
    
+    
    • 
+
  • 
+      
    RFC 5011 is not supported in the validating stub
       resolver of the export library. In fact, it is not clear
       whether it should: trust anchors would be a system-wide
       configuration which would be managed by an administrator,
       while the stub resolver will be used by ordinary applications
-      run by a normal user.
    • 
-
  • Not all common /etc/resolv.conf
+      run by a normal user.
    
+    
    • 
+
  • 
+      
    Not all common /etc/resolv.conf
       options are supported
       in the IRS library. The only available options in this
-      version are "debug" and "ndots".
    • 
+      version are "debug" and "ndots".
    
+    
 
-
-
    
+  
    
+  
    
 
    
-The dns.conf File
    
-
    The IRS library supports an "advanced" configuration file
+The dns.conf File
    
+    
+  
    The IRS library supports an "advanced" configuration file
   related to the DNS library for configuration parameters that
   would be beyond the capability of the
   resolv.conf file.
@@ -186,95 +209,98 @@ $ make
   This module is very
   experimental and the configuration syntax or library interfaces
   may change in future versions. Currently, only the
-  trusted-keys
+  trusted-keys
   statement is supported, whose syntax is the same as the same name
   of statement for named.conf. (See
-  the section called “trusted-keys Statement Grammar” for details.)
    
-
-
    
+  the section called “trusted-keys Statement Grammar” for details.)
    
+  
    
+  
    
 
    
-Sample Applications
    
-
    Some sample application programs using this API are
+Sample Applications
    
+    
+  
    Some sample application programs using this API are
   provided for reference. The following is a brief description of
   these applications.
   
    
-
    
+  
    
 
    
-sample: a simple stub resolver utility
    
-
    
+sample: a simple stub resolver utility
    
+    
+  
    
   It sends a query of a given name (of a given optional RR type) to a
   specified recursive server, and prints the result as a list of
   RRs. It can also act as a validating stub resolver if a trust
   anchor is given via a set of command line options.
    
-
    
+  
    
   Usage: sample [options] server_address hostname
   
    
-
    
+  
    
   Options and Arguments:
   
    
-
    
+  
    
 
    
   -t RRtype
   
    
 
    
-        specify the RR type of the query.  The default is the A RR.
+	specify the RR type of the query.  The default is the A RR.
   
    
 
    
   [-a algorithm] [-e] -k keyname -K keystring
   
    
 
    
 
    
-        specify a command-line DNS key to validate the answer.  For
-        example, to specify the following DNSKEY of example.com:
+	specify a command-line DNS key to validate the answer.  For
+	example, to specify the following DNSKEY of example.com:
 
    
 

    
-                example.com. 3600 IN DNSKEY 257 3 5 xxx
    
+		example.com. 3600 IN DNSKEY 257 3 5 xxx
    
 
    
 
    
-        specify the options as follows:
+	specify the options as follows:
 
    
 
     
-          -e -k example.com -K "xxx"
+	  -e -k example.com -K "xxx"
 
 
    
 
    
-        -e means that this key is a zone's "key signing key" (as known
-        as "secure Entry point").
-        When -a is omitted rsasha1 will be used by default.
+	-e means that this key is a zone's "key signing key" (as known
+	as "secure Entry point").
+	When -a is omitted rsasha1 will be used by default.
   
    
 
    
 
    
   -s domain:alt_server_address
   
    
 
    
-         specify a separate recursive server address for the specific
-        "domain".  Example: -s example.com:2001:db8::1234
+	 specify a separate recursive server address for the specific
+	"domain".  Example: -s example.com:2001:db8::1234
   
    
 
    server_address
    
 
    
-        an IP(v4/v6) address of the recursive server to which queries
-        are sent.
+	an IP(v4/v6) address of the recursive server to which queries
+	are sent.
   
    
 
    hostname
    
 
    
-        the domain name for the query
+	the domain name for the query
   
    
 
    
-
    
-
    
+  
    
+  
    
 
    
-sample-async: a simple stub resolver, working asynchronously
    
-
    
+sample-async: a simple stub resolver, working asynchronously
    
+    
+  
    
   Similar to "sample", but accepts a list
   of (query) domain names as a separate file and resolves the names
   asynchronously.
    
-
    
+  
    
     Usage: sample-async [-s server_address] [-t RR_type] input_file
    
-
    
+  
    
  Options and Arguments:
   
    
-
    
+  
    
 
    
    -s server_address
    
    
@@ -300,54 +326,62 @@ $ make
   mx.example.net
    
   ns.xxx.example
    
 
    
-
+  
 
    
-
-
    
+  
    
+  
    
 
    
-sample-request: a simple DNS transaction client
    
-
    
+sample-request: a simple DNS transaction client
    
+    
+  
    
   It sends a query to a specified server, and
   prints the response with minimal processing. It doesn't act as a
   "stub resolver": it stops the processing once it gets any
   response from the server, whether it's a referral or an alias
   (CNAME or DNAME) that would require further queries to get the
   ultimate answer. In other words, this utility acts as a very
-  simplified dig.
+  simplified dig.
   
    
-
    
+  
    
   Usage: sample-request [-t RRtype] server_address hostname
   
    
-
    
+  
    
     Options and Arguments:
   
    
-
    
+  
    
 
    
    -t RRtype
   
    
-
    
+
    
+  
    
   specify the RR type of
   the queries. The default is the A RR.
-  
    
+  
    
+  
 
    
   server_address
   
    
-
    
+
    
+  
    
    an IP(v4/v6)
   address of the recursive server to which the query is sent.
-  
    
+  
    
+  
 
    
   hostname
   
    
-
    
+
    
+  
    
   the domain name for the query
-  
    
+  
    
+  
 
    
-
    
-
    
+  
    
+  
    
 
    
-sample-gai: getaddrinfo() and getnameinfo() test code
    
-
    
+sample-gai: getaddrinfo() and getnameinfo() test code
    
+    
+  
    
   This is a test program
   to check getaddrinfo() and getnameinfo() behavior. It takes a
   host name as an argument, calls getaddrinfo() with the given host
@@ -357,172 +391,178 @@ $ make
   validating resolver, and getaddrinfo()/getnameinfo() will fail
   with an EAI_INSECUREDATA error when DNSSEC validation fails.
   
    
-
    
+  
    
   Usage: sample-gai hostname
   
    
-
-
    
+  
    
+  
    
 
    
-sample-update: a simple dynamic update client program
    
-
    
+sample-update: a simple dynamic update client program
    
+    
+  
    
   It accepts a single update command as a
   command-line argument, sends an update request message to the
   authoritative server, and shows the response from the server. In
-  other words, this is a simplified nsupdate.
+  other words, this is a simplified nsupdate.
   
    
-
    
+  
    
    Usage: sample-update [options] (add|delete) "update data"
   
    
-
    
+  
    
   Options and Arguments:
   
    
-
    
+  
    
 
    
   -a auth_server
    
    
 
    
-        An IP address of the authoritative server that has authority
-        for the zone containing the update name.  This should normally
-        be the primary authoritative server that accepts dynamic
-        updates.  It can also be a secondary server that is configured
-        to forward update requests to the primary server.
+	An IP address of the authoritative server that has authority
+	for the zone containing the update name.  This should normally
+	be the primary authoritative server that accepts dynamic
+	updates.  It can also be a secondary server that is configured
+	to forward update requests to the primary server.
    
    
 
    
   -k keyfile
    
    
 
    
-        A TSIG key file to secure the update transaction.  The keyfile
-        format is the same as that for the nsupdate utility.
+	A TSIG key file to secure the update transaction.  The keyfile
+	format is the same as that for the nsupdate utility.
    
    
 
    
   -p prerequisite
    
    
 
    
-        A prerequisite for the update (only one prerequisite can be
-        specified).  The prerequisite format is the same as that is
-        accepted by the nsupdate utility.
+	A prerequisite for the update (only one prerequisite can be
+	specified).  The prerequisite format is the same as that is
+	accepted by the nsupdate utility.
    
    
 
    
   -r recursive_server
    
    
 
    
-        An IP address of a recursive server that this utility will
-        use.  A recursive server may be necessary to identify the
-        authoritative server address to which the update request is
-        sent.
+	An IP address of a recursive server that this utility will
+	use.  A recursive server may be necessary to identify the
+	authoritative server address to which the update request is
+	sent.
    
    
 
    
   -z zonename
    
    
 
    
-        The domain name of the zone that contains
+	The domain name of the zone that contains
    
    
 
    
   (add|delete)
    
    
 
    
-        Specify the type of update operation.  Either "add" or "delete"
-        must be specified.
+	Specify the type of update operation.  Either "add" or "delete"
+	must be specified.
    
    
 
    
   "update data"
    
    
 
    
-        Specify the data to be updated.  A typical example of the data
-        would look like "name TTL RRtype RDATA".
+	Specify the data to be updated.  A typical example of the data
+	would look like "name TTL RRtype RDATA".
   
    
 
    
-
    
+
+   
    
 
    Note
    In practice, either -a or -r must be specified.  Others can
    be optional; the underlying library routine tries to identify the
    appropriate server and the zone name for the update.
    
-
    
+
+   
    
    Examples: assuming the primary authoritative server of the
    dynamic.example.com zone has an IPv6 address 2001:db8::1234,
    
    
-
    +   
     $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key add "foo.dynamic.example.com 30 IN A 192.168.2.1"
    
-
    
+   
    
      adds an A RR for foo.dynamic.example.com using the given key.
    
    
-
    +   
     $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com 30 IN A"
    
-
    
+   
    
      removes all A RRs for foo.dynamic.example.com using the given key.
    
    
-
       
+   
       
 $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com"
    
-
    
+   
    
      removes all RRs for foo.dynamic.example.com using the given key.
    
    
-
    
-
    
+  
    
+  
    
 
    
-nsprobe: domain/name server checker in terms of RFC 4074
    
-
    
+nsprobe: domain/name server checker in terms of RFC 4074
    
+    
+  
    
   It checks a set
   of domains to see the name servers of the domains behave
   correctly in terms of RFC 4074. This is included in the set of
   sample programs to show how the export library can be used in a
   DNS-related application.
   
    
-
    
+  
    
  Usage: nsprobe [-d] [-v [-v...]] [-c cache_address] [input_file]
   
    
-
    
+  
    
    Options
   
    
-
    
+
+  
    
 
    
   -d
   
    
 
    
-        run in the "debug" mode.  with this option nsprobe will dump
-        every RRs it receives.
+	run in the "debug" mode.  with this option nsprobe will dump
+	every RRs it receives.
   
    
 
    
   -v
   
    
 
    
-        increase verbosity of other normal log messages.  This can be
-        specified multiple times
+	increase verbosity of other normal log messages.  This can be
+	specified multiple times
   
    
 
    
   -c cache_address
   
    
 
    
-        specify an IP address of a recursive (caching) name server.
-        nsprobe uses this server to get the NS RRset of each domain and
-        the A and/or AAAA RRsets for the name servers.  The default
-        value is 127.0.0.1.
+	specify an IP address of a recursive (caching) name server.
+	nsprobe uses this server to get the NS RRset of each domain and
+	the A and/or AAAA RRsets for the name servers.  The default
+	value is 127.0.0.1.
   
    
 
    
   input_file
   
    
 
    
-        a file name containing a list of domain (zone) names to be
-        probed.  when omitted the standard input will be used.  Each
-        line of the input file specifies a single domain name such as
-        "example.com".  In general this domain name must be the apex
-        name of some DNS zone (unlike normal "host names" such as
-        "www.example.com").  nsprobe first identifies the NS RRsets for
-        the given domain name, and sends A and AAAA queries to these
-        servers for some "widely used" names under the zone;
-        specifically, adding "www" and "ftp" to the zone name.
+	a file name containing a list of domain (zone) names to be
+	probed.  when omitted the standard input will be used.  Each
+	line of the input file specifies a single domain name such as
+	"example.com".  In general this domain name must be the apex
+	name of some DNS zone (unlike normal "host names" such as
+	"www.example.com").  nsprobe first identifies the NS RRsets for
+	the given domain name, and sends A and AAAA queries to these
+	servers for some "widely used" names under the zone;
+	specifically, adding "www" and "ftp" to the zone name.
   
    
 
    
-
    
-
-
    
+  
    
+  
+  
    
 
    
-Library References
    
-
    As of this writing, there is no formal "manual" of the
+Library References
    
+    
+  
    As of this writing, there is no formal "manual" of the
   libraries, except this document, header files (some of them
   provide pretty detailed explanations), and sample application
   programs.
    
+  
 
-
-
+    
 
    
 
    
 
@@ -540,6 +580,6 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mm
 
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/Bv9ARM.ch13.html b/doc/arm/Bv9ARM.ch13.html
index bba891993f..5704eb90ac 100644
--- a/doc/arm/Bv9ARM.ch13.html
+++ b/doc/arm/Bv9ARM.ch13.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 Manual pages
-
-
+
+
 
 
 
@@ -39,7 +38,7 @@
 
 
    
 
-
    
+
    
 
    
 
    
 Manual pages
    
@@ -47,7 +46,7 @@
 
    
 
    
 
    Table of Contents
    
-
    
+
    
 
    
 dig — DNS lookup utility
 
    
@@ -88,19 +87,19 @@
 dnssec-verify — DNSSEC zone verification tool
 
 
    
-named-checkconf — named configuration file syntax checking tool
-
    
-
    
-named-checkzone — zone file validity checking or converting tool
+lwresd — lightweight resolver daemon
 
    
 
    
 named — Internet domain name server
 
    
 
    
-named.conf — configuration file for named
+named.conf — configuration file for named
 
    
 
    
-lwresd — lightweight resolver daemon
+named-checkconf — named configuration file syntax checking tool
+
    
+
    
+named-checkzone — zone file validity checking or converting tool
 
    
 
    
 named-journalprint — print zone journal in human-readable form
@@ -136,17 +135,42 @@
 isc-hmac-fixup — fixes HMAC keys generated by older versions of BIND
 
    
 
    
-named-journalprint — print zone journal in human-readable form
-
    
-
    
-named-rrchecker — A syntax checker for individual DNS resource records
-
    
-
    
 nsec3hash — generate NSEC3 hash
 
    
 
    
 
    
-
    
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+      
+    
    
 
    
 
    
 
@@ -164,6 +188,6 @@
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/Bv9ARM.conf b/doc/arm/Bv9ARM.conf
new file mode 100644
index 0000000000..cf095caa92
--- /dev/null
+++ b/doc/arm/Bv9ARM.conf
@@ -0,0 +1,3 @@
+TexInputs: ../tex//
+TexStyle:  armstyle
+XslParam:  ../xsl/arm-param.xsl
diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html
index 7b425cc0f0..ef4d150c9c 100644
--- a/doc/arm/Bv9ARM.html
+++ b/doc/arm/Bv9ARM.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 BIND 9 Administrator Reference Manual
-
-
+
+
 
 
 
@@ -36,11 +35,11 @@
 
 
    
 
-
    
+
    
 
    
 
    
 
    
-BIND 9 Administrator Reference Manual
    
+BIND 9 Administrator Reference Manual
    
 
    BIND Version 9.11.0pre-alpha
    
 
    Copyright © 2004-2015 Internet Systems Consortium, Inc. ("ISC")
    
 
    Copyright © 2000-2003 Internet Software Consortium.
    
@@ -49,223 +48,244 @@
 
    
 
    
 
    Table of Contents
    
-
    
+
    
 
    1. Introduction
    
 
    
-
    Scope of Document
    
-
    Organization of This Document
    
-
    Conventions Used in This Document
    
-
    The Domain Name System (DNS)
    
+
    Scope of Document
    
+
    Organization of This Document
    
+
    Conventions Used in This Document
    
+
    The Domain Name System (DNS)
    
 
    
-
    DNS Fundamentals
    
-
    Domains and Domain Names
    
-
    Zones
    
-
    Authoritative Name Servers
    
-
    Caching Name Servers
    
-
    Name Servers in Multiple Roles
    
+
    DNS Fundamentals
    
+
    Domains and Domain Names
    
+
    Zones
    
+
    Authoritative Name Servers
    
+
    Caching Name Servers
    
+
    Name Servers in Multiple Roles
    
 
    
 
    
 
    2. BIND Resource Requirements
    
 
    
-
    Hardware requirements
    
-
    CPU Requirements
    
-
    Memory Requirements
    
-
    Name Server Intensive Environment Issues
    
-
    Supported Operating Systems
    
+
    Hardware requirements
    
+
    CPU Requirements
    
+
    Memory Requirements
    
+
    Name Server Intensive Environment Issues
    
+
    Supported Operating Systems
    
 
    
 
    3. Name Server Configuration
    
 
    
-
    Sample Configurations
    
+
    Sample Configurations
    
 
    
-
    A Caching-only Name Server
    
-
    An Authoritative-only Name Server
    
+
    A Caching-only Name Server
    
+
    An Authoritative-only Name Server
    
 
    
-
    Load Balancing
    
-
    Name Server Operations
    
+
    Load Balancing
    
+
    Name Server Operations
    
 
    
-
    Tools for Use With the Name Server Daemon
    
-
    Signals
    
+
    Tools for Use With the Name Server Daemon
    
+
    Signals
    
 
    
 
    
 
    4. Advanced DNS Features
    
 
    
-
    Notify
    
-
    Dynamic Update
    
-
    The journal file
    
-
    Incremental Zone Transfers (IXFR)
    
-
    Split DNS
    
-
    Example split DNS setup
    
-
    TSIG
    
+
    Notify
    
+
    Dynamic Update
    
+
    The journal file
    
+
    Incremental Zone Transfers (IXFR)
    
+
    Split DNS
    
+
    Example split DNS setup
    
+
    TSIG
    
 
    
-
    Generate Shared Keys for Each Pair of Hosts
    
-
    Copying the Shared Secret to Both Machines
    
-
    Informing the Servers of the Key's Existence
    
-
    Instructing the Server to Use the Key
    
-
    TSIG Key Based Access Control
    
-
    Errors
    
+
    Generate Shared Keys for Each Pair of Hosts
    
+
    Copying the Shared Secret to Both Machines
    
+
    Informing the Servers of the Key's Existence
    
+
    Instructing the Server to Use the Key
    
+
    TSIG Key Based Access Control
    
+
    Errors
    
 
    
-
    TKEY
    
-
    SIG(0)
    
-
    DNSSEC
    
+
    TKEY
    
+
    SIG(0)
    
+
    DNSSEC
    
 
    
-
    Generating Keys
    
-
    Signing the Zone
    
-
    Configuring Servers
    
+
    Generating Keys
    
+
    Signing the Zone
    
+
    Configuring Servers
    
 
    
-
    DNSSEC, Dynamic Zones, and Automatic Signing
    
+
    DNSSEC, Dynamic Zones, and Automatic Signing
    
 
    
-
    Converting from insecure to secure
    
-
    Dynamic DNS update method
    
-
    Fully automatic zone signing
    
-
    Private-type records
    
-
    DNSKEY rollovers
    
-
    Dynamic DNS update method
    
-
    Automatic key rollovers
    
-
    NSEC3PARAM rollovers via UPDATE
    
-
    Converting from NSEC to NSEC3
    
-
    Converting from NSEC3 to NSEC
    
-
    Converting from secure to insecure
    
-
    Periodic re-signing
    
-
    NSEC3 and OPTOUT
    
+
    Converting from insecure to secure
    
+
    Dynamic DNS update method
    
+
    Fully automatic zone signing
    
+
    Private-type records
    
+
    DNSKEY rollovers
    
+
    Dynamic DNS update method
    
+
    Automatic key rollovers
    
+
    NSEC3PARAM rollovers via UPDATE
    
+
    Converting from NSEC to NSEC3
    
+
    Converting from NSEC3 to NSEC
    
+
    Converting from secure to insecure
    
+
    Periodic re-signing
    
+
    NSEC3 and OPTOUT
    
 
    
-
    Dynamic Trust Anchor Management
    
+
    Dynamic Trust Anchor Management
    
 
    
-
    Validating Resolver
    
-
    Authoritative Server
    
+
    Validating Resolver
    
+
    Authoritative Server
    
 
    
-
    PKCS#11 (Cryptoki) support
    
+
    PKCS#11 (Cryptoki) support
    
 
    
-
    Prerequisites
    
-
    Native PKCS#11
    
-
    OpenSSL-based PKCS#11
    
-
    PKCS#11 Tools
    
-
    Using the HSM
    
-
    Specifying the engine on the command line
    
-
    Running named with automatic zone re-signing
    
+
    Prerequisites
    
+
    Native PKCS#11
    
+
    OpenSSL-based PKCS#11
    
+
    PKCS#11 Tools
    
+
    Using the HSM
    
+
    Specifying the engine on the command line
    
+
    Running named with automatic zone re-signing
    
 
    
-
    DLZ (Dynamically Loadable Zones)
    
+
    DLZ (Dynamically Loadable Zones)
    
 
    
-
    Configuring DLZ
    
-
    Sample DLZ Driver
    
+
    Configuring DLZ
    
+
    Sample DLZ Driver
    
 
    
-
    DynDB (Dynamic Database)
    
+
    DynDB (Dynamic Database)
    
 
    
-
    Configuring DynDB
    
-
    Sample DynDB Module
    
+
    Configuring DynDB
    
+
    Sample DynDB Module
    
 
    
-
    IPv6 Support in BIND 9
    
+
    IPv6 Support in BIND 9
    
 
    
-
    Address Lookups Using AAAA Records
    
-
    Address to Name Lookups Using Nibble Format
    
+
    Address Lookups Using AAAA Records
    
+
    Address to Name Lookups Using Nibble Format
    
 
    
 
    
 
    5. The BIND 9 Lightweight Resolver
    
 
    
-
    The Lightweight Resolver Library
    
-
    Running a Resolver Daemon
    
+
    The Lightweight Resolver Library
    
+
    Running a Resolver Daemon
    
 
    
 
    6. BIND 9 Configuration Reference
    
 
    
-
    Configuration File Elements
    
+
    Configuration File Elements
    
 
    
-
    Address Match Lists
    
-
    Comment Syntax
    
+
    Address Match Lists
    
+
    Comment Syntax
    
 
    
-
    Configuration File Grammar
    
+
    Configuration File Grammar
    
 
    
-
    acl Statement Grammar
    
-
    acl Statement Definition and
+
    acl Statement Grammar
    
+
    acl Statement Definition and
           Usage
    
-
    controls Statement Grammar
    
-
    controls Statement Definition and
+
    controls Statement Grammar
    
+
    controls Statement Definition and
           Usage
    
-
    include Statement Grammar
    
-
    include Statement Definition and
+
    include Statement Grammar
    
+
    include Statement Definition and
           Usage
    
-
    key Statement Grammar
    
-
    key Statement Definition and Usage
    
-
    logging Statement Grammar
    
-
    logging Statement Definition and
+
    key Statement Grammar
    
+
    key Statement Definition and Usage
    
+
    logging Statement Grammar
    
+
    logging Statement Definition and
           Usage
    
-
    lwres Statement Grammar
    
-
    lwres Statement Definition and Usage
    
-
    masters Statement Grammar
    
-
    masters Statement Definition and
+
    lwres Statement Grammar
    
+
    lwres Statement Definition and Usage
    
+
    masters Statement Grammar
    
+
    masters Statement Definition and
           Usage
    
-
    options Statement Grammar
    
-
    options Statement Definition and
+
    options Statement Grammar
    
+
    options Statement Definition and
           Usage
    
-
    server Statement Grammar
    
-
    server Statement Definition and
+
    server Statement Grammar
    
+
    server Statement Definition and
             Usage
    
-
    statistics-channels Statement Grammar
    
-
    statistics-channels Statement Definition and
+
    statistics-channels Statement Grammar
    
+
    statistics-channels Statement Definition and
             Usage
    
-
    trusted-keys Statement Grammar
    
-
    trusted-keys Statement Definition
+
    trusted-keys Statement Grammar
    
+
    trusted-keys Statement Definition
             and Usage
    
-
    managed-keys Statement Grammar
    
-
    managed-keys Statement Definition
+
    managed-keys Statement Grammar
    
+
    managed-keys Statement Definition
             and Usage
    
-
    view Statement Grammar
    
-
    view Statement Definition and Usage
    
-
    zone
+
    view Statement Grammar
    
+
    view Statement Definition and Usage
    
+
    zone
             Statement Grammar
    
-
    zone Statement Definition and Usage
    
+
    zone Statement Definition and Usage
    
 
    
-
    Zone File
    
+
    Zone File
    
 
    
-
    Types of Resource Records and When to Use Them
    
-
    Discussion of MX Records
    
-
    Setting TTLs
    
-
    Inverse Mapping in IPv4
    
-
    Other Zone File Directives
    
-
    BIND Master File Extension: the  $GENERATE Directive
    
-
    Additional File Formats
    
+
    Types of Resource Records and When to Use Them
    
+
    Discussion of MX Records
    
+
    Setting TTLs
    
+
    Inverse Mapping in IPv4
    
+
    Other Zone File Directives
    
+
    BIND Master File Extension: the  $GENERATE Directive
    
+
    Additional File Formats
    
+
    
+
    BIND9 Statistics
    
+
    
+
    The Statistics File
    
+
    Statistics Counters
    
 
    
-
    BIND9 Statistics
    
-
    Statistics Counters
    
 
    
 
    7. BIND 9 Security Considerations
    
 
    
-
    Access Control Lists
    
-
    Chroot and Setuid
    
+
    Access Control Lists
    
+
    Chroot and Setuid
    
 
    
-
    The chroot Environment
    
-
    Using the setuid Function
    
+
    The chroot Environment
    
+
    Using the setuid Function
    
 
    
-
    Dynamic Update Security
    
+
    Dynamic Update Security
    
 
    
 
    8. Troubleshooting
    
 
    
-
    Common Problems
    
-
    It's not working; how can I figure out what's wrong?
    
-
    Incrementing and Changing the Serial Number
    
-
    Where Can I Get Help?
    
+
    Common Problems
    
+
    It's not working; how can I figure out what's wrong?
    
+
    Incrementing and Changing the Serial Number
    
+
    Where Can I Get Help?
    
 
    
 
    A. Release Notes
    
+
    
+
    Release Notes for BIND Version 9.11.0pre-alpha
    
+
    
+
    Introduction
    
+
    Download
    
+
    Security Fixes
    
+
    New Features
    
+
    Feature Changes
    
+
    Porting Changes
    
+
    Bug Fixes
    
+
    End of Life
    
+
    Thank You
    
+
    
+
    
 
    B. A Brief History of the DNS and BIND
    
+
    
+
    DNS
    
+
    BIND
    
+
    
 
    C. General DNS Reference Information
    
 
    
-
    IPv6 addresses (AAAA)
    
-
    Bibliography (and Suggested Reading)
    
+
    IPv6 addresses (AAAA)
    
+
    Bibliography (and Suggested Reading)
    
 
    
-
    Request for Comments (RFCs)
    
-
    Internet Drafts
    
-
    Other Documents About BIND
    
+
    Request for Comments (RFCs)
    
+
    Internet Drafts
    
+
    Other Documents About BIND
    
 
    
 
    
 
    D. BIND 9 DNS Library Support
    
 
    
-
    BIND 9 DNS Library Support
    
+
    BIND 9 DNS Library Support
    
 
    
-
    Prerequisite
    
-
    Compilation
    
-
    Installation
    
-
    Known Defects/Restrictions
    
-
    The dns.conf File
    
-
    Sample Applications
    
-
    Library References
    
+
    Prerequisite
    
+
    Compilation
    
+
    Installation
    
+
    Known Defects/Restrictions
    
+
    The dns.conf File
    
+
    Sample Applications
    
+
    Library References
    
 
    
 
    
 
    I. Manual pages
    
@@ -310,19 +330,19 @@
 dnssec-verify — DNSSEC zone verification tool
 
 
    
-named-checkconf — named configuration file syntax checking tool
-
    
-
    
-named-checkzone — zone file validity checking or converting tool
+lwresd — lightweight resolver daemon
 
    
 
    
 named — Internet domain name server
 
    
 
    
-named.conf — configuration file for named
+named.conf — configuration file for named
 
    
 
    
-lwresd — lightweight resolver daemon
+named-checkconf — named configuration file syntax checking tool
+
    
+
    
+named-checkzone — zone file validity checking or converting tool
 
    
 
    
 named-journalprint — print zone journal in human-readable form
@@ -358,18 +378,39 @@
 isc-hmac-fixup — fixes HMAC keys generated by older versions of BIND
 
    
 
    
-named-journalprint — print zone journal in human-readable form
-
    
-
    
-named-rrchecker — A syntax checker for individual DNS resource records
-
    
-
    
 nsec3hash — generate NSEC3 hash
 
    
 
    
 
    
 
    
-
    
+  
+
+  
+
+  
+
+  
+
+  
+
+  
+
+  
+    
+
+    
+
+    
+
+    
+
+    
+
+    
+
+    
+
+  
    
 
    
 
    
 
@@ -386,6 +427,6 @@
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/Bv9ARM.pdf b/doc/arm/Bv9ARM.pdf
index 0f3c654a5b..df8973da4d 100644
Binary files a/doc/arm/Bv9ARM.pdf and b/doc/arm/Bv9ARM.pdf differ
diff --git a/doc/arm/Makefile.in b/doc/arm/Makefile.in
index 501133e0db..4b2aa72822 100644
--- a/doc/arm/Makefile.in
+++ b/doc/arm/Makefile.in
@@ -13,8 +13,6 @@
 # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 # PERFORMANCE OF THIS SOFTWARE.
 
-# $Id: Makefile.in,v 1.22 2009/02/12 23:47:56 tbox Exp $
-
 srcdir =	@srcdir@
 VPATH =		@srcdir@
 top_srcdir =	@top_srcdir@
@@ -33,9 +31,9 @@ doc man:: ${MANOBJS} ${PDFOBJS}
 
 clean::
 	rm -f Bv9ARM.aux Bv9ARM.brf Bv9ARM.glo Bv9ARM.idx Bv9ARM.toc
-	rm -f Bv9ARM.log Bv9ARM.out Bv9ARM.tex Bv9ARM.tex.tmp
+	rm -f Bv9ARM.log Bv9ARM.out
 	rm -f notes.aux notes.brf notes.glo notes.idx notes.toc
-	rm -f notes.log notes.out notes.tex notes.tex.tmp
+	rm -f notes.log notes.out
 
 docclean manclean maintainer-clean:: clean
 	rm -f *.html ${PDFOBJS}
@@ -47,19 +45,11 @@ docclean manclean maintainer-clean distclean::
 
 notes.html: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
 	expand notes-wrapper.xml | \
-	${XSLTPROC} --stringparam generate.toc "" ../xsl/isc-notes-html.xsl - |\
-	@PERL@ html-fixup.pl > notes.html
+	${XSLTPROC} --stringparam generate.toc "" ../xsl/isc-notes-html.xsl - > notes.html
 
-notes.tex: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
-	expand notes-wrapper.xml | \
-	${XSLTPROC} --stringparam generate.toc "book toc" ${top_srcdir}/doc/xsl/pre-latex.xsl - | \
-	${XSLTPROC} ${top_srcdir}/doc/xsl/isc-notes-latex.xsl - | \
-	@PERL@ latex-fixup.pl >$@.tmp 
-	if test -s $@.tmp; then mv $@.tmp $@; else rm -f $@.tmp; exit 1; fi
-
-notes.pdf: notes.tex releaseinfo.xml pkgversion.xml noteversion.xml
-	rm -f notes-wrapper.aux notes.pdf notes.log
-	${PDFLATEX} '\batchmode\input notes.tex' || (rm -f $@ ; exit 1)
+notes.pdf: notes-wrapper.xml notes.xml releaseinfo.xml pkgversion.xml noteversion.xml
+	${XSLTPROC} ${top_srcdir}/doc/xsl/pre-latex.xsl notes-wrapper.xml | \
+	${DBLATEX} -c notes.conf -Pdoc.layout="mainmatter" -o notes.pdf -
 
 Bv9ARM.html: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
 	expand Bv9ARM-book.xml | \
@@ -70,24 +60,10 @@ Bv9ARM-all.html: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
 	expand Bv9ARM-book.xml | \
 	${XSLTPROC} -o Bv9ARM-all.html ../xsl/isc-docbook-html.xsl -
 
-Bv9ARM.tex: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
+Bv9ARM.pdf: Bv9ARM-book.xml releaseinfo.xml pkgversion.xml noteversion.xml
 	expand Bv9ARM-book.xml | \
 	${XSLTPROC} ${top_srcdir}/doc/xsl/pre-latex.xsl - | \
-	${XSLTPROC} ${top_srcdir}/doc/xsl/isc-docbook-latex.xsl - | \
-	@PERL@ latex-fixup.pl >$@.tmp 
-	if test -s $@.tmp; then mv $@.tmp $@; else rm -f $@.tmp; exit 1; fi
-
-Bv9ARM.dvi: Bv9ARM.tex releaseinfo.xml pkgversion.xml noteversion.xml
-	rm -f Bv9ARM-book.aux Bv9ARM-book.dvi Bv9ARM-book.log
-	${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-	${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-	${LATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-
-Bv9ARM.pdf: Bv9ARM.tex releaseinfo.xml pkgversion.xml noteversion.xml
-	rm -f Bv9ARM-book.aux Bv9ARM-book.pdf Bv9ARM-book.log
-	${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-	${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
-	${PDFLATEX} '\batchmode\input Bv9ARM.tex' || (rm -f $@ ; exit 1)
+	${DBLATEX} -c Bv9ARM.conf -o Bv9ARM.pdf -
 
 FORCE:
 
diff --git a/doc/arm/dlz.xml b/doc/arm/dlz.xml
index 8022513eb4..0583778ba2 100644
--- a/doc/arm/dlz.xml
+++ b/doc/arm/dlz.xml
@@ -1,4 +1,3 @@
-
 
-
-
-
-
-  DLZ (Dynamically Loadable Zones)
+
+
    DLZ (Dynamically Loadable Zones)
+  
   
     DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows
     zone data to be retrieved directly from an external database.  There is
@@ -56,16 +53,16 @@
     zones in the database.)
   
 
-  
-    Configuring DLZ
+  
    Configuring DLZ
+    
     
       A DLZ database is configured with a dlz
       statement in named.conf:
     
     
     dlz example {
-        database "dlopen driver.so ";
-        search yes;
+	database "dlopen driver.so ";
+	search yes;
     };
     
     
@@ -94,18 +91,18 @@
     
     
     dlz other {
-        database "dlopen driver.so ";
-        search no;
+	database "dlopen driver.so ";
+	search no;
     };
 
     zone "." {
-        type redirect;
-        dlz other;
+	type redirect;
+	dlz other;
     };
     
-  
-  
-    Sample DLZ Driver
+  
    
+  
    Sample DLZ Driver
+    
     
       For guidance in implementation of DLZ modules, the directory
       contrib/dlz/example contains a basic
@@ -117,7 +114,7 @@
     
     
     dlz other {
-        database "dlopen driver.so example.nil";
+	database "dlopen driver.so example.nil";
     };
     
     
@@ -128,8 +125,8 @@
     
     
  example.nil.  3600    IN      SOA     example.nil. hostmaster.example.nil. (
-                                               123 900 600 86400 3600
-                                       )
+					       123 900 600 86400 3600
+				       )
  example.nil.  3600    IN      NS      example.nil.
  example.nil.  1800    IN      A       10.53.0.1
     
@@ -137,7 +134,7 @@
       The sample driver is capable of retrieving information about the
       querying client, and altering its response on the basis of this
       information.  To demonstrate this feature, the example driver
-      responds to queries for "source-addr.>/TXT"
+      responds to queries for "source-addr.>/TXT"
       with the source address of the query.  Note, however, that this
       record will *not* be included in AXFR or ANY responses.  Normally,
       this feature would be used to alter responses in some other fashion,
@@ -151,5 +148,5 @@
       defines the API and should be included by any dynamically-linkable
       DLZ module.
     
-  
-
+  
    
+
    
diff --git a/doc/arm/dnssec.xml b/doc/arm/dnssec.xml
index c2efb2a5b6..7a56a60e1c 100644
--- a/doc/arm/dnssec.xml
+++ b/doc/arm/dnssec.xml
@@ -1,4 +1,3 @@
-
 
-
-
-  DNSSEC, Dynamic Zones, and Automatic Signing
+
+
    DNSSEC, Dynamic Zones, and Automatic Signing
+  
   As of BIND 9.7.0 it is possible to change a dynamic zone
   from insecure to signed and back again. A secure zone can use
   either NSEC or NSEC3 chains.
-  
-    Converting from insecure to secure
-  
+  
    Converting from insecure to secure
+    
+  
    
   Changing a zone from insecure to secure can be done in two
   ways: using a dynamic DNS update, or the 
   auto-dnssec zone option.
@@ -35,28 +34,28 @@
   in the key-directory, as specified in 
   named.conf:
   
-        zone example.net {
-                type master;
-                update-policy local;
-                file "dynamic/example.net/example.net";
-                key-directory "dynamic/example.net";
-        };
+	zone example.net {
+		type master;
+		update-policy local;
+		file "dynamic/example.net/example.net";
+		key-directory "dynamic/example.net";
+	};
 
   If one KSK and one ZSK DNSKEY key have been generated, this
   configuration will cause all records in the zone to be signed
   with the ZSK, and the DNSKEY RRset to be signed with the KSK as
   well. An NSEC chain will be generated as part of the initial
   signing process.
-  
-    Dynamic DNS update method
-  
+  
    Dynamic DNS update method
+    
+  
    
   To insert the keys via dynamic update:
   
-        % nsupdate
-        > ttl 3600
-        > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
-        > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
-        > send
+	% nsupdate
+	> ttl 3600
+	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+	> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+	> send
 
   While the update request will complete almost immediately,
   the zone will not be completely signed until 
@@ -69,12 +68,12 @@
   wish the NSEC3 chain to have the OPTOUT bit set, set it in the
   flags field of the NSEC3PARAM record.
   
-        % nsupdate
-        > ttl 3600
-        > update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
-        > update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
-        > update add example.net NSEC3PARAM 1 1 100 1234567890
-        > send
+	% nsupdate
+	> ttl 3600
+	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
+	> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
+	> update add example.net NSEC3PARAM 1 1 100 1234567890
+	> send
 
   Again, this update request will complete almost
   immediately; however, the record won't show up until 
@@ -84,9 +83,9 @@
   be removed once the operation completes.
   While the initial signing and NSEC/NSEC3 chain generation
   is happening, other updates are possible as well.
-  
-    Fully automatic zone signing
-  
+  
    Fully automatic zone signing
+    
+  
    
   To enable automatic signing, add the 
   auto-dnssec option to the zone statement in 
   named.conf. 
@@ -148,9 +147,9 @@
   update-policy statement to the zone
   configuration. If this has not been done, the configuration will
   fail.
-  
-    Private-type records
-  
+  
    Private-type records
+    
+  
    
   The state of the signing process is signaled by
   private-type records (with a default type value of 65534). When
   signing is complete, these records will have a nonzero value for
@@ -186,15 +185,15 @@
   0x20 NONSEC
 
   
-  
-    DNSKEY rollovers
-  
+  
    DNSKEY rollovers
+    
+  
    
   As with insecure-to-secure conversions, rolling DNSSEC
   keys can be done in two ways: using a dynamic DNS update, or the 
   auto-dnssec zone option.
-  
-    Dynamic DNS update method
-  
+  
    Dynamic DNS update method
+    
+  
    
    To perform key rollovers via dynamic update, you need to add
   the K* files for the new keys so that 
   named can find them. You can then add the new
@@ -215,9 +214,9 @@
   specify the correct key. 
   named will clean out any signatures generated
   by the old key after the update completes.
-  
-    Automatic key rollovers
-  
+  
    Automatic key rollovers
+    
+  
    
   When a new key reaches its activation date (as set by
   dnssec-keygen or dnssec-settime),
   if the auto-dnssec zone option is set to 
@@ -231,32 +230,32 @@
   signature validity periods expire.  By default, this rollover
   completes in 30 days, after which it will be safe to remove the
   old key from the DNSKEY RRset.
-  
-    NSEC3PARAM rollovers via UPDATE
-  
+  
    NSEC3PARAM rollovers via UPDATE
+    
+  
    
   Add the new NSEC3PARAM record via dynamic update. When the
   new NSEC3 chain has been generated, the NSEC3PARAM flag field
   will be zero. At this point you can remove the old NSEC3PARAM
   record. The old chain will be removed after the update request
   completes.
-  
-    Converting from NSEC to NSEC3
-  
+  
    Converting from NSEC to NSEC3
+    
+  
    
   To do this, you just need to add an NSEC3PARAM record. When
   the conversion is complete, the NSEC chain will have been removed
   and the NSEC3PARAM record will have a zero flag field. The NSEC3
   chain will be generated before the NSEC chain is
   destroyed.
-  
-    Converting from NSEC3 to NSEC
-  
+  
    Converting from NSEC3 to NSEC
+    
+  
    
   To do this, use nsupdate to
   remove all NSEC3PARAM records with a zero flag
   field. The NSEC chain will be generated before the NSEC3 chain is
   removed.
-  
-    Converting from secure to insecure
-  
+  
    Converting from secure to insecure
+    
+  
    
   To convert a signed zone to unsigned using dynamic DNS,
   delete all the DNSKEY records from the zone apex using
   nsupdate. All signatures, NSEC or NSEC3 chains,
@@ -270,17 +269,17 @@
   zone statement is used, it should be removed or changed to
   allow instead (or it will re-sign).
   
-  
-    Periodic re-signing
-  
+  
    Periodic re-signing
+    
+  
    
   In any secure zone which supports dynamic updates, named
   will periodically re-sign RRsets which have not been re-signed as
   a result of some update action. The signature lifetimes will be
   adjusted so as to spread the re-sign load over time rather than
   all at once.
-  
-    NSEC3 and OPTOUT
-  
+  
    NSEC3 and OPTOUT
+    
+  
    
   
   named only supports creating new NSEC3 chains
   where all the NSEC3 records in the zone have the same OPTOUT
@@ -291,4 +290,4 @@
   state of an individual NSEC3 record, the entire chain needs to be
   changed if the OPTOUT state of an individual NSEC3 needs to be
   changed.
-
+
    
diff --git a/doc/arm/dyndb.xml b/doc/arm/dyndb.xml
index 4d92b22e7b..61888a7ffa 100644
--- a/doc/arm/dyndb.xml
+++ b/doc/arm/dyndb.xml
@@ -1,4 +1,3 @@
-
 
-
-
-  DynDB (Dynamic Database)
+
+
    DynDB (Dynamic Database)
+  
   
     DynDB is an extension to BIND 9 which, like DLZ
     (see ), allows zone data to be
@@ -32,8 +31,7 @@
   
     A DynDB module supporting LDAP has been created by Red Hat
     and is available from
-    https://fedorahosted.org/bind-dyndb-ldap/.
+    https://fedorahosted.org/bind-dyndb-ldap/.
   
   
     A sample DynDB module for testing and developer guidance
@@ -41,8 +39,8 @@
     bin/tests/system/dyndb/driver.
   
 
-  
-    Configuring DynDB
+  
    Configuring DynDB
+    
     
       A DynDB database is configured with a dyndb
       statement in named.conf:
@@ -67,9 +65,9 @@
       string to the DynDB module's initialization routine. Configuration
       syntax will differ depending on the driver.
     
-  
-  
-    Sample DynDB Module
+  
    
+  
    Sample DynDB Module
+    
     
       For guidance in implementation of DynDB modules, the directory
       bin/tests/system/dyndb/driver.
@@ -101,5 +99,5 @@
       reverse zone.  (Updates are not stored permanently; all updates are
       lost when the server is restarted.)
     
-  
-
+  
    
+
    
diff --git a/doc/arm/latex-fixup.pl b/doc/arm/latex-fixup.pl
deleted file mode 100644
index bad6e9f99b..0000000000
--- a/doc/arm/latex-fixup.pl
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/usr/bin/perl -w
-#
-# Copyright (C) 2005, 2007, 2012, 2015  Internet Systems Consortium, Inc. ("ISC")
-#
-# Permission to use, copy, modify, and/or distribute this software for any
-# purpose with or without fee is hereby granted, provided that the above
-# copyright notice and this permission notice appear in all copies.
-#
-# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
-# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
-# AND FITNESS.  IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
-# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
-# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
-# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
-# PERFORMANCE OF THIS SOFTWARE.
-
-# $Id: latex-fixup.pl,v 1.5 2007/06/19 23:47:13 tbox Exp $
-
-# Sadly, the final stages of generating a presentable PDF file always
-# seem to require some manual tweaking.  Doesn't seem to matter what
-# typesetting tool one uses, sane forms of automation only go so far,
-# at least with present technology.
-#
-# This script is intended to be a collection of tweaks.  The theory is
-# that, while we can't avoid the need for tweaking, we can at least
-# write the silly things down in a form that a program might be able
-# to execute.  Undoubtedly everythig in here will break, eventually,
-# at which point it will need to be updated, but since the alternative
-# is to do the final editing by hand every time, this approach seems
-# the lesser of two evils.
-
-while (<>) {
-
-    # Fix a db2latex oops.  LaTeX2e does not like having tables with
-    # duplicate names.  Perhaps the dblatex project will fix this
-    # someday, but we can get by with just deleting the offending
-    # LaTeX commands for now.
-
-    s/\\addtocounter\{table\}\{-1\}//g;
-
-    # Line break in the middle of quoting one period looks weird.
-
-    s/{\\texttt{{\.\\dbz{}}}}/\\mbox{{\\texttt{{\.\\dbz{}}}}}/;
-
-    # Add any further tweaking here.
-    # https://en.wikibooks.org/wiki/LaTeX/Special_Characters
-    s/쎶/{\\"o}/;  # umlaut o 쎶 or 쎶
-
-    # Write out whatever we have now.
-    print;
-}
diff --git a/doc/arm/libdns.xml b/doc/arm/libdns.xml
index 6b5e81739d..cda668a575 100644
--- a/doc/arm/libdns.xml
+++ b/doc/arm/libdns.xml
@@ -1,4 +1,3 @@
-
 
-
-
-  BIND 9 DNS Library Support
+
+
    BIND 9 DNS Library Support
+  
   This version of BIND 9 "exports" its internal libraries so
   that they can be used by third-party applications more easily (we
   call them "export" libraries in this document). In addition to
@@ -52,16 +51,16 @@
       libraries than BIND 9's internal event task system.
     
   
-  
-    Prerequisite
+  
    Prerequisite
+    
   GNU make is required to build the export libraries (other
   part of BIND 9 can still be built with other types of make). In
   the reminder of this document, "make" means GNU make. Note that
   in some platforms you may need to invoke a different command name
   than "make" (e.g. "gmake") to indicate it's GNU make.
-  
-  
-    Compilation
+  
    
+  
    Compilation
+    
   
 $ ./configure --enable-exportlib [other flags]
 $ make
@@ -73,9 +72,9 @@ $ make
   export version of the BIND 9 DNS library. Sample application
   programs using the libraries will also be built under the
   lib/export/samples directory (see below).
-  
-  
-    Installation
+  
    
+  
    Installation
+    
   
 $ cd lib/export
 $ make install
@@ -94,9 +93,9 @@ $ make install
   To see how to build your own
   application after the installation, see
   lib/export/samples/Makefile-postinstall.in.
-  
-  
-    Known Defects/Restrictions
+  
    
+  
    Known Defects/Restrictions
+    
   
     
 
@@ -140,9 +139,9 @@ $ make
       version are "debug" and "ndots".
     
   
-  
-  
-    The dns.conf File
+  
    
+  
    The dns.conf File
+    
   The IRS library supports an "advanced" configuration file
   related to the DNS library for configuration parameters that
   would be beyond the capability of the
@@ -156,16 +155,16 @@ $ make
   trusted-keys
   statement is supported, whose syntax is the same as the same name
   of statement for named.conf. (See
-   for details.)
-  
-  
-    Sample Applications
+   for details.)
+  
    
+  
    Sample Applications
+    
   Some sample application programs using this API are
   provided for reference. The following is a brief description of
   these applications.
   
-  
-    sample: a simple stub resolver utility
+  
    sample: a simple stub resolver utility
+    
   
   It sends a query of a given name (of a given optional RR type) to a
   specified recursive server, and prints the result as a list of
@@ -183,7 +182,7 @@ $ make
   -t RRtype
   
   
-        specify the RR type of the query.  The default is the A RR.
+	specify the RR type of the query.  The default is the A RR.
   
   
   
@@ -191,20 +190,20 @@ $ make
   [-a algorithm] [-e] -k keyname -K keystring
   
   
-        specify a command-line DNS key to validate the answer.  For
-        example, to specify the following DNSKEY of example.com:
+	specify a command-line DNS key to validate the answer.  For
+	example, to specify the following DNSKEY of example.com:
 
-                example.com. 3600 IN DNSKEY 257 3 5 xxx
+		example.com. 3600 IN DNSKEY 257 3 5 xxx
 
-        specify the options as follows:
+	specify the options as follows:
 
 
-          -e -k example.com -K "xxx"
+	  -e -k example.com -K "xxx"
 
 
-        -e means that this key is a zone's "key signing key" (as known
-        as "secure Entry point").
-        When -a is omitted rsasha1 will be used by default.
+	-e means that this key is a zone's "key signing key" (as known
+	as "secure Entry point").
+	When -a is omitted rsasha1 will be used by default.
   
   
   
@@ -212,27 +211,27 @@ $ make
   -s domain:alt_server_address
   
   
-         specify a separate recursive server address for the specific
-        "domain".  Example: -s example.com:2001:db8::1234
+	 specify a separate recursive server address for the specific
+	"domain".  Example: -s example.com:2001:db8::1234
   
   
   
   server_address
   
-        an IP(v4/v6) address of the recursive server to which queries
-        are sent.
+	an IP(v4/v6) address of the recursive server to which queries
+	are sent.
   
   
   
   hostname
   
-        the domain name for the query
+	the domain name for the query
   
   
   
-  
-  
-    sample-async: a simple stub resolver, working asynchronously
+  
    
+  
    sample-async: a simple stub resolver, working asynchronously
+    
   
   Similar to "sample", but accepts a list
   of (query) domain names as a separate file and resolves the names
@@ -276,9 +275,9 @@ $ make
   
     
     
-  
-  
-    sample-request: a simple DNS transaction client
+  
    
+  
    sample-request: a simple DNS transaction client
+    
   
   It sends a query to a specified server, and
   prints the response with minimal processing. It doesn't act as a
@@ -328,9 +327,9 @@ $ make
   
   
   
-  
-  
-    sample-gai: getaddrinfo() and getnameinfo() test code
+  
    
+  
    sample-gai: getaddrinfo() and getnameinfo() test code
+    
   
   This is a test program
   to check getaddrinfo() and getnameinfo() behavior. It takes a
@@ -344,9 +343,9 @@ $ make
   
   Usage: sample-gai hostname
   
-  
-  
-    sample-update: a simple dynamic update client program
+  
    
+  
    sample-update: a simple dynamic update client program
+    
   
   It accepts a single update command as a
   command-line argument, sends an update request message to the
@@ -365,11 +364,11 @@ $ make
   -a auth_server
    
    
-        An IP address of the authoritative server that has authority
-        for the zone containing the update name.  This should normally
-        be the primary authoritative server that accepts dynamic
-        updates.  It can also be a secondary server that is configured
-        to forward update requests to the primary server.
+	An IP address of the authoritative server that has authority
+	for the zone containing the update name.  This should normally
+	be the primary authoritative server that accepts dynamic
+	updates.  It can also be a secondary server that is configured
+	to forward update requests to the primary server.
    
    
    
@@ -377,8 +376,8 @@ $ make
   -k keyfile
    
    
-        A TSIG key file to secure the update transaction.  The keyfile
-        format is the same as that for the nsupdate utility.
+	A TSIG key file to secure the update transaction.  The keyfile
+	format is the same as that for the nsupdate utility.
    
    
    
@@ -386,9 +385,9 @@ $ make
   -p prerequisite
    
    
-        A prerequisite for the update (only one prerequisite can be
-        specified).  The prerequisite format is the same as that is
-        accepted by the nsupdate utility.
+	A prerequisite for the update (only one prerequisite can be
+	specified).  The prerequisite format is the same as that is
+	accepted by the nsupdate utility.
    
    
    
@@ -396,10 +395,10 @@ $ make
   -r recursive_server
    
    
-        An IP address of a recursive server that this utility will
-        use.  A recursive server may be necessary to identify the
-        authoritative server address to which the update request is
-        sent.
+	An IP address of a recursive server that this utility will
+	use.  A recursive server may be necessary to identify the
+	authoritative server address to which the update request is
+	sent.
    
    
    
@@ -407,7 +406,7 @@ $ make
   -z zonename
    
    
-        The domain name of the zone that contains
+	The domain name of the zone that contains
    
    
    
@@ -415,8 +414,8 @@ $ make
   (add|delete)
    
    
-        Specify the type of update operation.  Either "add" or "delete"
-        must be specified.
+	Specify the type of update operation.  Either "add" or "delete"
+	must be specified.
    
    
    
@@ -424,8 +423,8 @@ $ make
   "update data"
    
    
-        Specify the data to be updated.  A typical example of the data
-        would look like "name TTL RRtype RDATA".
+	Specify the data to be updated.  A typical example of the data
+	would look like "name TTL RRtype RDATA".
   
   
   
@@ -453,9 +452,9 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dy
    
      removes all RRs for foo.dynamic.example.com using the given key.
    
-  
-  
-    nsprobe: domain/name server checker in terms of RFC 4074
+  
    
+  
    nsprobe: domain/name server checker in terms of RFC 4074
+    
   
   It checks a set
   of domains to see the name servers of the domains behave
@@ -476,8 +475,8 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dy
   -d
   
   
-        run in the "debug" mode.  with this option nsprobe will dump
-        every RRs it receives.
+	run in the "debug" mode.  with this option nsprobe will dump
+	every RRs it receives.
   
   
   
@@ -485,8 +484,8 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dy
   -v
   
   
-        increase verbosity of other normal log messages.  This can be
-        specified multiple times
+	increase verbosity of other normal log messages.  This can be
+	specified multiple times
   
   
   
@@ -494,10 +493,10 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dy
   -c cache_address
   
   
-        specify an IP address of a recursive (caching) name server.
-        nsprobe uses this server to get the NS RRset of each domain and
-        the A and/or AAAA RRsets for the name servers.  The default
-        value is 127.0.0.1.
+	specify an IP address of a recursive (caching) name server.
+	nsprobe uses this server to get the NS RRset of each domain and
+	the A and/or AAAA RRsets for the name servers.  The default
+	value is 127.0.0.1.
   
   
   
@@ -505,26 +504,25 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dy
   input_file
   
   
-        a file name containing a list of domain (zone) names to be
-        probed.  when omitted the standard input will be used.  Each
-        line of the input file specifies a single domain name such as
-        "example.com".  In general this domain name must be the apex
-        name of some DNS zone (unlike normal "host names" such as
-        "www.example.com").  nsprobe first identifies the NS RRsets for
-        the given domain name, and sends A and AAAA queries to these
-        servers for some "widely used" names under the zone;
-        specifically, adding "www" and "ftp" to the zone name.
+	a file name containing a list of domain (zone) names to be
+	probed.  when omitted the standard input will be used.  Each
+	line of the input file specifies a single domain name such as
+	"example.com".  In general this domain name must be the apex
+	name of some DNS zone (unlike normal "host names" such as
+	"www.example.com").  nsprobe first identifies the NS RRsets for
+	the given domain name, and sends A and AAAA queries to these
+	servers for some "widely used" names under the zone;
+	specifically, adding "www" and "ftp" to the zone name.
   
   
   
-  
-  
-  
-    Library References
+  
    
+  
    
+  
    Library References
+    
   As of this writing, there is no formal "manual" of the
   libraries, except this document, header files (some of them
   provide pretty detailed explanations), and sample application
   programs.
-  
-
-
+  
    
+
    
diff --git a/doc/arm/logging-categories.xml b/doc/arm/logging-categories.xml
index f5d8591e2f..64df919d63 100644
--- a/doc/arm/logging-categories.xml
+++ b/doc/arm/logging-categories.xml
@@ -13,8 +13,8 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
-
+
+
   
     
     
diff --git a/doc/arm/man.arpaname.html b/doc/arm/man.arpaname.html
index 73c28a3444..a3b0b14c5d 100644
--- a/doc/arm/man.arpaname.html
+++ b/doc/arm/man.arpaname.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 arpaname
-
-
+
+
 
 
 
@@ -39,34 +38,47 @@
 
 
    
 
-
    
+
    
 
    
-
    
+  
+  
+  
+
+  
    
 
    Name
    
-
    arpaname — translate IP addresses to the corresponding ARPA names
    
-
    
-
    
-
    Synopsis
    
-
    arpaname  {ipaddress ...}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      arpaname translates IP addresses (IPv4 and
+    arpaname
+     — translate IP addresses to the corresponding ARPA names
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      arpaname 
+       {ipaddress ...}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      arpaname translates IP addresses (IPv4 and
       IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -87,6 +99,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.ddns-confgen.html b/doc/arm/man.ddns-confgen.html
index fcef6b3e88..a398f174bc 100644
--- a/doc/arm/man.ddns-confgen.html
+++ b/doc/arm/man.ddns-confgen.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 ddns-confgen
-
-
+
+
 
 
 
@@ -39,70 +38,111 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    ddns-confgen — ddns key generation tool
    
-
    
-
    
-
    Synopsis
    
-
    tsig-keygen  [-a algorithm] [-h] [-r randomfile] [name]
    
-
    ddns-confgen  [-a algorithm] [-h] [-k keyname] [-q] [-r randomfile] [ -s name  |   -z zone ]
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      tsig-keygen and ddns-confgen
+    ddns-confgen
+     — ddns key generation tool
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      tsig-keygen 
+       [-a algorithm]
+       [-h]
+       [-r randomfile]
+       [name]
+    
    
+    
    
+      ddns-confgen 
+       [-a algorithm]
+       [-h]
+       [-k keyname]
+       [-q]
+       [-r randomfile]
+       [
+         -s name 
+         |   -z zone 
+      ]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      tsig-keygen and ddns-confgen
       are invocation methods for a utility that generates keys for use
       in TSIG signing.  The resulting keys can be used, for example,
       to secure dynamic DNS updates to a zone or for the
-      rndc command channel.
+      rndc command channel.
     
    
-
    
-      When run as tsig-keygen, a domain name
+
+    
    
+      When run as tsig-keygen, a domain name
       can be specified on the command line which will be used as
       the name of the generated key.  If no name is specified,
       the default is tsig-key.
     
    
-
    
-      When run as ddns-confgen, the generated
+
+    
    
+      When run as ddns-confgen, the generated
       key is accompanied by configuration text and instructions
-      that can be used with nsupdate and
-      named when setting up dynamic DNS,
-      including an example update-policy
+      that can be used with nsupdate and
+      named when setting up dynamic DNS,
+      including an example update-policy
       statement.  (This usage similar to the
-      rndc-confgen command for setting
+      rndc-confgen command for setting
       up command channel security.)
     
    
-
    
-      Note that named itself can configure a
-      local DDNS key for use with nsupdate -l:
+
+    
    
+      Note that named itself can configure a
+      local DDNS key for use with nsupdate -l:
       it does this when a zone is configured with
-      update-policy local;.
-      ddns-confgen is only needed when a 
+      update-policy local;.
+      ddns-confgen is only needed when a 
       more elaborate configuration is required: for instance,
-      if nsupdate is to be used from a remote
+      if nsupdate is to be used from a remote
       system.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -a algorithm
    
-
    
+
    
+	  
    
             Specifies the algorithm to use for the TSIG key.  Available
             choices are: hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256,
             hmac-sha384 and hmac-sha512.  The default is hmac-sha256.
             Options are case-insensitive, and the "hmac-" prefix
             may be omitted.
-	  
    
+	  
    
+	
 
    -h
    
-
    
+
    
+	  
    
 	    Prints a short summary of options and arguments.
-	  
    
+	  
    
+	
 
    -k keyname
    
-
    
+
    
+	  
    
 	    Specifies the key name of the DDNS authentication key.
 	    The default is ddns-key when neither
 	    the -s nor -z option is
@@ -112,15 +152,19 @@
 	    ddns-key.example.com.
 	    The key name must have the format of a valid domain name,
 	    consisting of letters, digits, hyphens and periods.
-	  
    
+	  
    
+	
 
    -q
    
-
    
-	    (ddns-confgen only.) Quiet mode:  Print
+
    
+	  
    
+	    (ddns-confgen only.) Quiet mode:  Print
             only the key, with no explanatory text or usage examples;
-            This is essentially identical to tsig-keygen.
-	  
    
+            This is essentially identical to tsig-keygen.
+	  
    
+	
 
    -r randomfile
    
-
    
+
    
+	  
    
             Specifies a source of random data for generating the
             authorization.  If the operating system does not provide a
             /dev/random or equivalent device, the
@@ -130,12 +174,14 @@
             instead of the default.  The special value
             keyboard indicates that keyboard input
             should be used.
-	  
    
+	  
    
+	
 
    -s name
    
-
    
-            (ddns-confgen only.)
+
    
+	  
    
+            (ddns-confgen only.)
 	    Generate configuration example to allow dynamic updates
-            of a single hostname.  The example named.conf
+            of a single hostname.  The example named.conf
             text shows how to set an update policy for the specified
             name
 	    using the "name" nametype.  The default key name is
@@ -143,34 +189,41 @@
 	    Note that the "self" nametype cannot be used, since
 	    the name to be updated may differ from the key name.
 	    This option cannot be used with the -z option.
-	  
    
+	  
    
+	
 
    -z zone
    
-
    
-            (ddns-confgen only.)
+
    
+	  
    
+            (ddns-confgen only.)
 	    Generate configuration example to allow dynamic updates
-            of a zone:  The example named.conf text
+            of a zone:  The example named.conf text
             shows how to set an update policy for the specified
 	    zone
 	    using the "zonesub" nametype, allowing updates to
             all subdomain names within that
             zone.
 	    This option cannot be used with the -s option.
-	  
    
+	  
    
+	
 
    
-
    
-
    
-
    SEE ALSO
    
-
    nsupdate(1),
-      named.conf(5),
-      named(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+	nsupdate(1)
+      ,
+      
+	named.conf(5)
+      ,
+      
+	named(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -191,6 +244,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.delv.html b/doc/arm/man.delv.html
index 816850ebf9..d67587d29f 100644
--- a/doc/arm/man.delv.html
+++ b/doc/arm/man.delv.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 delv
-
-
+
+
 
 
 
@@ -39,28 +38,73 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    delv — DNS lookup and validation utility
    
+
    
+    delv
+     — DNS lookup and validation utility
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    delv  [@server] [-4] [-6] [-a anchor-file] [-b address] [-c class] [-d level] [-i] [-m] [-p port#] [-q name] [-t type] [-x addr] [name] [type] [class] [queryopt...]
    
-
    delv  [-h]
    
-
    delv  [-v]
    
-
    delv  [queryopt...] [query...]
    
-
    
-
    
-
    DESCRIPTION
    
-
    delv
+    
    
+      delv 
+       [@server]
+       [-4]
+       [-6]
+       [-a anchor-file]
+       [-b address]
+       [-c class]
+       [-d level]
+       [-i]
+       [-m]
+       [-p port#]
+       [-q name]
+       [-t type]
+       [-x addr]
+       [name]
+       [type]
+       [class]
+       [queryopt...]
+    
    
+
+    
    
+      delv 
+       [-h]
+    
    
+
+    
    
+      delv 
+       [-v]
+    
    
+
+    
    
+      delv 
+       [queryopt...]
+       [query...]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    delv
       (Domain Entity Lookup & Validation) is a tool for sending
       DNS queries and validating the results, using the same internal
-      resolver and validator logic as named.
+      resolver and validator logic as named.
     
    
-
    
-      delv will send to a specified name server all
+    
    
+      delv will send to a specified name server all
       queries needed to fetch and validate the requested data; this
       includes the original requested query, subsequent queries to follow
       CNAME or DNAME chains, and queries for DNSKEY, DS and DLV records
@@ -69,182 +113,208 @@
       behavior of a name server configured for DNSSEC validating and
       forwarding.
     
    
-
    
+    
    
       By default, responses are validated using built-in DNSSEC trust
       anchors for the root zone (".") and for the ISC DNSSEC lookaside
       validation zone ("dlv.isc.org").  Records returned by
-      delv are either fully validated or
+      delv are either fully validated or
       were not signed.  If validation fails, an explanation of
       the failure is included in the output; the validation process
-      can be traced in detail.  Because delv does
+      can be traced in detail.  Because delv does
       not rely on an external server to carry out validation, it can
       be used to check the validity of DNS responses in environments
       where local name servers may not be trustworthy.
     
    
-
    
+    
    
       Unless it is told to query a specific name server,
-      delv will try each of the servers listed in
+      delv will try each of the servers listed in
       /etc/resolv.conf. If no usable server
-      addresses are found, delv will send
+      addresses are found, delv will send
       queries to the localhost addresses (127.0.0.1 for IPv4, ::1
       for IPv6).
     
    
-
    
+    
    
       When no command line arguments or options are given,
-      delv will perform an NS query for "."
+      delv will perform an NS query for "."
       (the root zone).
     
    
-
    
-
    
-
    SIMPLE USAGE
    
-
    
-      A typical invocation of delv looks like:
+  
    
+
+  
    
+
    SIMPLE USAGE
    
+    
+
+    
    
+      A typical invocation of delv looks like:
       
    
 
     delv @server name type 
    
 
    
       where:
 
       
    
-
    
+
    
 
    server
    
 
    
-
    
+	    
    
 	      is the name or IP address of the name server to query.  This
 	      can be an IPv4 address in dotted-decimal notation or an IPv6
 	      address in colon-delimited notation.  When the supplied
 	      server argument is a hostname,
-	      delv resolves that name before
+	      delv resolves that name before
 	      querying that name server (note, however, that this
 	      initial lookup is not validated
 	      by DNSSEC).
 	    
    
-
    
+	    
    
 	      If no server argument is
-	      provided, delv consults
+	      provided, delv consults
 	      /etc/resolv.conf; if an
 	      address is found there, it queries the name server at
 	      that address. If either of the -4 or
 	      -6 options are in use, then
 	      only addresses for the corresponding transport
 	      will be tried.  If no usable addresses are found,
-	      delv will send queries to
+	      delv will send queries to
 	      the localhost addresses (127.0.0.1 for IPv4,
 	      ::1 for IPv6).
 	    
    
-
    
+	  
 
    name
    
-
    
+
    
+	    
    
 	      is the domain name to be looked up.
-	    
    
+	    
    
+	  
 
    type
    
-
    
+
    
+	    
    
 	      indicates what type of query is required —
 	      ANY, A, MX, etc.
 	      type can be any valid query
 	      type.  If no
 	      type argument is supplied,
-	      delv will perform a lookup for an
+	      delv will perform a lookup for an
 	      A record.
-	    
    
+	    
    
+	  
 
    
 
    
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+
+  
    
+
+  
    
+
    OPTIONS
    
+    
+    
    
 
    -a anchor-file
    
 
    
-
    
+	  
    
 	    Specifies a file from which to read DNSSEC trust anchors.
 	    The default is /etc/bind.keys, which
 	    is included with BIND 9 and contains
 	    trust anchors for the root zone (".") and for the ISC
 	    DNSSEC lookaside validation zone ("dlv.isc.org").
 	  
    
-
    
+	  
    
 	    Keys that do not match the root or DLV trust-anchor
 	    names are ignored; these key names can be overridden
 	    using the +dlv=NAME or
 	    +root=NAME options.
 	  
    
-
    
+	  
    
 	    Note: When reading the trust anchor file,
-	    delv treats managed-keys
+	    delv treats managed-keys
 	    statements and trusted-keys statements
 	    identically.  That is, for a managed key, it is the
 	    initial key that is trusted; RFC 5011
-	    key management is not supported. delv
+	    key management is not supported. delv
 	    will not consult the managed-keys database maintained by
-	    named. This means that if either of the
+	    named. This means that if either of the
 	    keys in /etc/bind.keys is revoked
 	    and rolled over, it will be necessary to update
 	    /etc/bind.keys to use DNSSEC
-	    validation in delv.
+	    validation in delv.
 	  
    
-
    
+	
 
    -b  address
    
-
    
+
    
+	  
    
 	    Sets the source IP address of the query to
 	    address.  This must be a valid address
 	    on one of the host's network interfaces or "0.0.0.0" or "::".
 	    An optional source port may be specified by appending
 	    "#<port>"
-	  
    
+	  
    
+	
 
    -c class
    
-
    
+
    
+	  
    
 	    Sets the query class for the requested data. Currently,
-	    only class "IN" is supported in delv
+	    only class "IN" is supported in delv
 	    and any other value is ignored.
-	  
    
+	  
    
+	
 
    -d level
    
-
    
+
    
+	  
    
 	    Set the systemwide debug level to level.
 	    The allowed range is from 0 to 99.
 	    The default is 0 (no debugging).
-	    Debugging traces from delv become
+	    Debugging traces from delv become
 	    more verbose as the debug level increases.
 	    See the +mtrace, +rtrace,
 	    and +vtrace options below for additional
 	    debugging details.
-	  
    
+	  
    
+	
 
    -h
    
-
    
-	    Display the delv help usage output and exit.
-	  
    
+
    
+	  
    
+	    Display the delv help usage output and exit.
+	  
    
+	
    
 
    -i
    
-
    
+
    
+	  
    
 	    Insecure mode. This disables internal DNSSEC validation.
 	    (Note, however, this does not set the CD bit on upstream
 	    queries. If the server being queried is performing DNSSEC
 	    validation, then it will not return invalid data; this
-	    can cause delv to time out. When it
+	    can cause delv to time out. When it
 	    is necessary to examine invalid data to debug a DNSSEC
-	    problem, use dig +cd.)
-	  
    
+	    problem, use dig +cd.)
+	  
    
+	
 
    -m
    
-
    
+
    
+	  
    
 	    Enables memory usage debugging.
-	  
    
+	  
    
+	
 
    -p port#
    
-
    
+
    
+	  
    
 	    Specifies a destination port to use for queries instead of
 	    the standard DNS port number 53.  This option would be used
 	    with a name server that has been configured to listen
 	    for queries on a non-standard port number.
-	  
    
+	  
    
+	
 
    -q name
    
-
    
+
    
+	  
    
 	    Sets the query name to name.
 	    While the query name can be specified without using the
 	    -q, it is sometimes necessary to disambiguate
 	    names from types or classes (for example, when looking up the
 	    name "ns", which could be misinterpreted as the type NS,
 	    or "ch", which could be misinterpreted as class CH).
-	  
    
+	  
    
+	
 
    -t type
    
 
    
-
    
+	  
    
 	    Sets the query type to type, which
 	    can be any valid query type supported in BIND 9 except
 	    for zone transfer types AXFR and IXFR. As with
@@ -252,45 +322,57 @@
 	    query name type or class when they are ambiguous.
 	    it is sometimes necessary to disambiguate names from types.
 	  
    
-
    
+	  
    
 	    The default query type is "A", unless the -x
 	    option is supplied to indicate a reverse lookup, in which case
 	    it is "PTR".
 	  
    
-
    
+	
 
    -v
    
-
    
-	    Print the delv version and exit.
-	  
    
+
    
+	  
    
+	    Print the delv version and exit.
+	  
    
+	
    
 
    -x addr
    
-
    
+
    
+	  
    
 	    Performs a reverse lookup, mapping an addresses to
 	    a name.  addr is an IPv4 address in
 	    dotted-decimal notation, or a colon-delimited IPv6 address.
 	    When -x is used, there is no need to provide
 	    the name or type
-	    arguments.  delv automatically performs a
+	    arguments.  delv automatically performs a
 	    lookup for a name like 11.12.13.10.in-addr.arpa
 	    and sets the query type to PTR.  IPv6 addresses are looked up
 	    using nibble format under the IP6.ARPA domain.
-	  
    
+	  
    
+	
 
    -4
    
-
    
-	    Forces delv to only use IPv4.
-	  
    
+
    
+	  
    
+	    Forces delv to only use IPv4.
+	  
    
+	
    
 
    -6
    
-
    
-	    Forces delv to only use IPv6.
-	  
    
+
    
+	  
    
+	    Forces delv to only use IPv6.
+	  
    
+	
    
 
    
-
    
-
    
-
    QUERY OPTIONS
    
-
    delv
+  
    
+
+  
    
+
    QUERY OPTIONS
    
+    
+
+    
    delv
       provides a number of query options which affect the way results are
       displayed, and in some cases the way lookups are performed.
     
    
-
    
+
+    
    
       Each query option is identified by a keyword preceded by a plus sign
       (+).  Some keywords set or reset an
       option.  These may be preceded by the string
@@ -300,94 +382,107 @@
       The query options are:
 
       
    
-
    
+
    
 
    +[no]cdflag
    
-
    
+
    
+	    
    
 	      Controls whether to set the CD (checking disabled) bit in
-	      queries sent by delv. This may be useful
+	      queries sent by delv. This may be useful
 	      when troubleshooting DNSSEC problems from behind a validating
 	      resolver. A validating resolver will block invalid responses,
 	      making it difficult to retrieve them for analysis. Setting
 	      the CD flag on queries will cause the resolver to return
-	      invalid responses, which delv can then
+	      invalid responses, which delv can then
 	      validate internally and report the errors in detail.
-	    
    
+	    
    
+	  
 
    +[no]class
    
-
    
+
    
+	    
    
 	      Controls whether to display the CLASS when printing
 	      a record. The default is to display the CLASS.
-	    
    
+	    
    
+	  
 
    +[no]ttl
    
-
    
+
    
+	    
    
 	      Controls whether to display the TTL when printing
 	      a record. The default is to display the TTL.
-	    
    
+	    
    
+	  
 
    +[no]rtrace
    
 
    
-
    
+	    
    
 	      Toggle resolver fetch logging. This reports the
-	      name and type of each query sent by delv
+	      name and type of each query sent by delv
 	      in the process of carrying out the resolution and validation
 	      process: this includes including the original query and
 	      all subsequent queries to follow CNAMEs and to establish a
 	      chain of trust for DNSSEC validation.
 	    
    
-
    
+	    
    
 	      This is equivalent to setting the debug level to 1 in
 	      the "resolver" logging category. Setting the systemwide
 	      debug level to 1 using the -d option will
 	      product the same output (but will affect other logging
 	      categories as well).
 	    
    
-
    
+	  
 
    +[no]mtrace
    
 
    
-
    
+	    
    
 	      Toggle message logging. This produces a detailed dump of
-	      the responses received by delv in the
+	      the responses received by delv in the
 	      process of carrying out the resolution and validation process.
 	    
    
-
    
+	    
    
 	      This is equivalent to setting the debug level to 10
 	      for the "packets" module of the "resolver" logging
 	      category. Setting the systemwide debug level to 10 using
 	      the -d option will produce the same output
 	      (but will affect other logging categories as well).
 	    
    
-
    
+	  
 
    +[no]vtrace
    
 
    
-
    
+	    
    
 	      Toggle validation logging. This shows the internal
 	      process of the validator as it determines whether an
 	      answer is validly signed, unsigned, or invalid.
 	    
    
-
    
+	    
    
 	      This is equivalent to setting the debug level to 3
 	      for the "validator" module of the "dnssec" logging
 	      category. Setting the systemwide debug level to 3 using
 	      the -d option will produce the same output
 	      (but will affect other logging categories as well).
 	    
    
-
    
+	  
 
    +[no]short
    
-
    
+
    
+	    
    
 	      Provide a terse answer.  The default is to print the answer in a
 	      verbose form.
-	    
    
+	    
    
+	  
 
    +[no]comments
    
-
    
+
    
+	    
    
 	      Toggle the display of comment lines in the output.  The default
 	      is to print comments.
-	    
    
+	    
    
+	  
 
    +[no]rrcomments
    
-
    
+
    
+	    
    
 	      Toggle the display of per-record comments in the output (for
 	      example, human-readable key information about DNSKEY records).
 	      The default is to print per-record comments.
-	    
    
+	    
    
+	  
 
    +[no]crypto
    
-
    
+
    
+	    
    
 	      Toggle the display of cryptographic fields in DNSSEC records.
 	      The contents of these field are unnecessary to debug most DNSSEC
 	      validation failures and removing them makes it easier to see
@@ -395,14 +490,18 @@
 	      When omitted they are replaced by the string "[omitted]" or
 	      in the DNSKEY case the key id is displayed as the replacement,
 	      e.g. "[ key id = value ]".
-	    
    
+	    
    
+	  
 
    +[no]trust
    
-
    
+
    
+	    
    
 	      Controls whether to display the trust level when printing
 	      a record. The default is to display the trust level.
-	    
    
+	    
    
+	  
 
    +[no]split[=W]
    
-
    
+
    
+	    
    
 	      Split long hex- or base64-formatted fields in resource
 	      records into chunks of W characters
 	      (where W is rounded up to the nearest
@@ -411,36 +510,44 @@
 	      +split=0 causes fields not to be
 	      split at all.  The default is 56 characters, or 44 characters
 	      when multiline mode is active.
-	    
    
+	    
    
+	  
 
    +[no]all
    
-
    
+
    
+	    
    
 	      Set or clear the display options
 	      +[no]comments, 
 	      +[no]rrcomments, and
 	      +[no]trust as a group.
-	    
    
+	    
    
+	  
 
    +[no]multiline
    
-
    
+
    
+	    
    
 	      Print long records (such as RRSIG, DNSKEY, and SOA records)
 	      in a verbose multi-line format with human-readable comments.
 	      The default is to print each record on a single line, to
-	      facilitate machine parsing of the delv
+	      facilitate machine parsing of the delv
 	      output.
-	    
    
+	    
    
+	  
 
    +[no]dnssec
    
-
    
+
    
+	    
    
 	      Indicates whether to display RRSIG records in the
-	      delv output.  The default is to
-	      do so.  Note that (unlike in dig)
+	      delv output.  The default is to
+	      do so.  Note that (unlike in dig)
 	      this does not control whether to
 	      request DNSSEC records or whether to validate them.
 	      DNSSEC records are always requested, and validation
 	      will always occur unless suppressed by the use of
 	      -i or +noroot and
 	      +nodlv.
-	    
    
+	    
    
+	  
 
    +[no]root[=ROOT]
    
-
    
+
    
+	    
    
 	      Indicates whether to perform conventional (non-lookaside)
 	      DNSSEC validation, and if so, specifies the
 	      name of a trust anchor.  The default is to validate using
@@ -448,9 +555,11 @@
 	      a built-in key.  If specifying a different trust anchor,
 	      then -a must be used to specify a file
 	      containing the key.
-	    
    
+	    
    
+	  
 
    +[no]dlv[=DLV]
    
-
    
+
    
+	    
    
 	      Indicates whether to perform DNSSEC lookaside validation,
 	      and if so, specifies the name of the DLV trust anchor.
 	      The default is to perform lookaside validation using
@@ -458,34 +567,46 @@
 	      built-in key.  If specifying a different name, then
 	      -a must be used to specify a file
 	      containing the DLV key.
-	    
    
+	    
    
+	  
 
    +[no]tcp
    
-
    
+
    
+	    
    
 	      Controls whether to use TCP when sending queries.
 	      The default is to use UDP unless a truncated
 	      response has been received.
-	    
    
+	    
    
+	  
 
    
 
    
 
     
    
-
    
-
    
-
    FILES
    
-
    /etc/bind.keys
    
-
    /etc/resolv.conf
    
-
    
-
    
-
    SEE ALSO
    
-
    dig(1),
-      named(8),
+  
    
+
+  
    
+
    FILES
    
+    
+    
    /etc/bind.keys
    
+    
    /etc/resolv.conf
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+	dig(1)
+      ,
+      
+	named(8)
+      ,
       RFC4034,
       RFC4035,
       RFC4431,
       RFC5074,
       RFC5155.
     
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -505,6 +626,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html
index 4633a782fc..012a39bcaa 100644
--- a/doc/arm/man.dig.html
+++ b/doc/arm/man.dig.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dig
-
-
+
+
 
 
 
@@ -39,188 +38,270 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dig — DNS lookup utility
    
+
    
+    dig
+     — DNS lookup utility
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dig  [@server] [-b address] [-c class] [-f filename] [-k filename] [-m] [-p port#] [-q name] [-t type] [-v] [-x addr] [-y [hmac:]name:key] [-4] [-6] [name] [type] [class] [queryopt...]
    
-
    dig  [-h]
    
-
    dig  [global-queryopt...] [query...]
    
-
    
-
    
-
    DESCRIPTION
    
-
    dig
+    
    
+      dig 
+       [@server]
+       [-b address]
+       [-c class]
+       [-f filename]
+       [-k filename]
+       [-m]
+       [-p port#]
+       [-q name]
+       [-t type]
+       [-v]
+       [-x addr]
+       [-y [hmac:]name:key]
+       [-4]
+       [-6]
+       [name]
+       [type]
+       [class]
+       [queryopt...]
+    
    
+
+    
    
+      dig 
+       [-h]
+    
    
+
+    
    
+      dig 
+       [global-queryopt...]
+       [query...]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dig
       (domain information groper) is a flexible tool
       for interrogating DNS name servers.  It performs DNS lookups and
       displays the answers that are returned from the name server(s) that
-      were queried.  Most DNS administrators use dig to
+      were queried.  Most DNS administrators use dig to
       troubleshoot DNS problems because of its flexibility, ease of use and
       clarity of output.  Other lookup tools tend to have less functionality
-      than dig.
+      than dig.
     
    
-
    
-      Although dig is normally used with
+
+    
    
+      Although dig is normally used with
       command-line
       arguments, it also has a batch mode of operation for reading lookup
       requests from a file.  A brief summary of its command-line arguments
       and options is printed when the -h option is given.
       Unlike earlier versions, the BIND 9 implementation of
-      dig allows multiple lookups to be issued
+      dig allows multiple lookups to be issued
       from the
       command line.
     
    
-
    
+
+    
    
       Unless it is told to query a specific name server,
-      dig will try each of the servers listed in
+      dig will try each of the servers listed in
       /etc/resolv.conf. If no usable server addresses
-      are found, dig will send the query to the local
+      are found, dig will send the query to the local
       host.
     
    
-
    
+
+    
    
       When no command line arguments or options are given,
-      dig will perform an NS query for "." (the root).
+      dig will perform an NS query for "." (the root).
     
    
-
    
-      It is possible to set per-user defaults for dig via
+
+    
    
+      It is possible to set per-user defaults for dig via
       ${HOME}/.digrc.  This file is read and
       any options in it
       are applied before the command line arguments.
     
    
-
    
+
+    
    
       The IN and CH class names overlap with the IN and CH top level
       domain names.  Either use the -t and
       -c options to specify the type and class, 
       use the -q the specify the domain name, or
       use "IN." and "CH." when looking up these top level domains.
     
    
-
    
-
    
-
    SIMPLE USAGE
    
-
    
-      A typical invocation of dig looks like:
+
+  
    
+
+  
    
+
    SIMPLE USAGE
    
+    
+
+    
    
+      A typical invocation of dig looks like:
       
    
 
     dig @server name type 
    
 
    
       where:
 
       
    
-
    
+
    
 
    server
    
 
    
-
    
+	    
    
 	      is the name or IP address of the name server to query.  This
 	      can be an IPv4 address in dotted-decimal notation or an IPv6
 	      address in colon-delimited notation.  When the supplied
 	      server argument is a hostname,
-	      dig resolves that name before querying
+	      dig resolves that name before querying
 	      that name server.
 	    
    
-
    
+	    
    
 	      If no server argument is
-	      provided, dig consults
+	      provided, dig consults
 	      /etc/resolv.conf; if an
 	      address is found there, it queries the name server at
 	      that address. If either of the -4 or
 	      -6 options are in use, then
 	      only addresses for the corresponding transport
 	      will be tried.  If no usable addresses are found,
-	      dig will send the query to the
+	      dig will send the query to the
 	      local host.  The reply from the name server that
 	      responds is displayed.
 	    
    
-
    
+	  
 
    name
    
-
    
+
    
+	    
    
 	      is the name of the resource record that is to be looked up.
-	    
    
+	    
    
+	  
 
    type
    
-
    
+
    
+	    
    
 	      indicates what type of query is required —
 	      ANY, A, MX, SIG, etc.
 	      type can be any valid query
 	      type.  If no
 	      type argument is supplied,
-	      dig will perform a lookup for an
+	      dig will perform a lookup for an
 	      A record.
-	    
    
+	    
    
+	  
 
    
 
    
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -4
    
-
    
+
    
+	  
    
 	    Use IPv4 only.
-	  
    
+	  
    
+	
 
    -6
    
-
    
+
    
+	  
    
 	    Use IPv6 only.
-	  
    
+	  
    
+	
 
    -b address[#port]
    
-
    
+
    
+	  
    
 	    Set the source IP address of the query.
 	    The address must be a valid address on
 	    one of the host's network interfaces, or "0.0.0.0" or "::". An
 	    optional port may be specified by appending "#<port>"
-	  
    
+	  
    
+	
 
    -c class
    
-
    
+
    
+	  
    
 	    Set the query class. The
 	    default class is IN; other classes
 	    are HS for Hesiod records or CH for Chaosnet records.
-	  
    
+	  
    
+	
 
    -f file
    
-
    
-	    Batch mode: dig reads a list of lookup
+
    
+	  
    
+	    Batch mode: dig reads a list of lookup
 	    requests to process from the
 	    given file. Each line in the file
 	    should be organized in the same way they would be
 	    presented as queries to
-	    dig using the command-line interface.
-	  
    
+	    dig using the command-line interface.
+	  
    
+	
 
    -i
    
-
    
+
    
+	  
    
 	    Do reverse IPv6 lookups using the obsolete RFC1886 IP6.INT
 	    domain, which is no longer in use. Obsolete bit string
 	    label queries (RFC2874) are not attempted.
-	  
    
+	  
    
+	
 
    -k keyfile
    
-
    
+
    
+	  
    
 	    Sign queries using TSIG using a key read from the given file.
 	    Key files can be generated using
-	    tsig-keygen(8).
-	    When using TSIG authentication with dig,
+	    
+	      tsig-keygen(8)
+	    .
+	    When using TSIG authentication with dig,
 	    the name server that is queried needs to know the key and
 	    algorithm that is being used. In BIND, this is done by
-	    providing appropriate key
-	    and server statements in
+	    providing appropriate key
+	    and server statements in
 	    named.conf.
-	  
    
+	  
    
+	
 
    -m
    
-
    
+
    
+	  
    
 	    Enable memory usage debugging.
 	    
-	  
    
+	  
    
+	
 
    -p port
    
-
    
+
    
+	  
    
 	    Send the query to a non-standard port on the server,
 	    instead of the defaut port 53. This option would be used
 	    to test a name server that has been configured to listen
 	    for queries on a non-standard port number.
-	  
    
+	  
    
+	
 
    -q name
    
-
    
+
    
+	  
    
 	    The domain name to query. This is useful to distinguish
 	    the name from other arguments.
-	  
    
+	  
    
+	
 
    -t type
    
-
    
+
    
+	  
    
 	    The resource record type to query. It can be any valid query type
 	    which is
 	    supported in BIND 9.  The default query type is "A", unless the
@@ -232,13 +313,17 @@
 	    made to the zone since the serial number in the zone's SOA
 	    record was
 	    N.
-	  
    
+	  
    
+	
 
    -v
    
-
    
+
    
+	  
    
 	    Print the version number and exit.
-	  
    
+	  
    
+	
 
    -x addr
    
-
    
+
    
+	  
    
 	    Simplified reverse lookups, for mapping addresses to
 	    names. The addr is an IPv4 address
 	    in dotted-decimal notation, or a colon-delimited IPv6
@@ -246,17 +331,18 @@
 	    need to provide
 	    the name, class
 	    and type
-	    arguments. dig automatically performs a
+	    arguments. dig automatically performs a
 	    lookup for a name like
 	    94.2.0.192.in-addr.arpa and sets the
 	    query type and class to PTR and IN respectively. IPv6
 	    addresses are looked up using nibble format under the
 	    IP6.ARPA domain (but see also the -i
 	    option).
-	  
    
+	  
    
+	
 
    -y [hmac:]keyname:secret
    
 
    
-
    
+	  
    
 	    Sign queries using TSIG with the given authentication key.
 	    keyname is the name of the key, and
 	    secret is the base64 encoded shared secret.
@@ -267,28 +353,34 @@
 	    hmac-sha512.  If hmac
 	    is not specified, the default is hmac-md5.
 	  
    
-
    
+	  
    
 	    NOTE: You should use the -k option and
 	    avoid the -y option, because
 	    with -y the shared secret is supplied as
 	    a command line argument in clear text. This may be visible
 	    in the output from
-	    ps(1)
+	    
+	      ps(1)
+	    
 	    or in a history file maintained by the user's shell.
 	  
    
-
    
+	
 
    
-
    
-
    
-
    QUERY OPTIONS
    
-
    dig
+  
    
+
+  
    
+
    QUERY OPTIONS
    
+    
+
+    
    dig
       provides a number of query options which affect
       the way in which lookups are made and the results displayed.  Some of
       these set or reset flag bits in the query header, some determine which
       sections of the answer get printed, and others determine the timeout
       and retry strategies.
     
    
-
    
+
+    
    
       Each query option is identified by a keyword preceded by a plus sign
       (+).  Some keywords set or reset an
       option.  These may be preceded
@@ -302,22 +394,29 @@
       The query options are:
 
       
    
-
    
+
    
 
    +[no]aaflag
    
-
    
+
    
+	    
    
 	      A synonym for +[no]aaonly.
-	    
    
+	    
    
+	  
 
    +[no]aaonly
    
-
    
+
    
+	    
    
 	      Sets the "aa" flag in the query.
-	    
    
+	    
    
+	  
 
    +[no]additional
    
-
    
+
    
+	    
    
 	      Display [do not display] the additional section of a
 	      reply.  The default is to display it.
-	    
    
+	    
    
+	  
 
    +[no]adflag
    
-
    
+
    
+	    
    
 	      Set [do not set] the AD (authentic data) bit in the
 	      query.  This requests the server to return whether
 	      all of the answer and authority sections have all
@@ -327,80 +426,102 @@
 	      from a OPT-OUT range.  AD=0 indicate that some part
 	      of the answer was insecure or not validated.  This
 	      bit is set by default.
-	    
    
+	    
    
+	  
 
    +[no]all
    
-
    
+
    
+	    
    
 	      Set or clear all display flags.
-	    
    
+	    
    
+	  
 
    +[no]answer
    
-
    
+
    
+	    
    
 	      Display [do not display] the answer section of a
 	      reply.  The default is to display it.
-	    
    
+	    
    
+	  
 
    +[no]authority
    
-
    
+
    
+	    
    
 	      Display [do not display] the authority section of a
 	      reply.  The default is to display it.
-	    
    
+	    
    
+	  
 
    +[no]badcookie
    
-
    
+
    
+	    
    
 	      Retry lookup with the new server cookie if a
 	      BADCOOKIE response is received.
-	    
    
+	    
    
+	  
 
    +[no]besteffort
    
-
    
+
    
+	    
    
 	      Attempt to display the contents of messages which are
 	      malformed.  The default is to not display malformed
 	      answers.
-	    
    
+	    
    
+	  
 
    +bufsize=B
    
-
    
+
    
+	    
    
 	      Set the UDP message buffer size advertised using EDNS0
 	      to B bytes.  The maximum and
 	      minimum sizes of this buffer are 65535 and 0 respectively.
 	      Values outside this range are rounded up or down
 	      appropriately.  Values other than zero will cause a
 	      EDNS query to be sent.
-	    
    
+	    
    
+	  
 
    +[no]cdflag
    
-
    
+
    
+	    
    
 	      Set [do not set] the CD (checking disabled) bit in
 	      the query.  This requests the server to not perform
 	      DNSSEC validation of responses.
-	    
    
+	    
    
+	  
 
    +[no]class
    
-
    
+
    
+	    
    
 	      Display [do not display] the CLASS when printing the
 	      record.
-	    
    
+	    
    
+	  
 
    +[no]cmd
    
-
    
+
    
+	    
    
 	      Toggles the printing of the initial comment in the
-	      output identifying the version of dig
+	      output identifying the version of dig
 	      and the query options that have been applied.  This
 	      comment is printed by default.
-	    
    
+	    
    
+	  
 
    +[no]comments
    
-
    
+
    
+	    
    
 	      Toggle the display of comment lines in the output.
 	      The default is to print comments.
-	    
    
+	    
    
+	  
 
    +[no]cookie[=####]
    
 
    
-
    
+	    
    
 	      Send a COOKIE EDNS option, with optional
 	      value.  Replaying a COOKIE from a previous response will
 	      allow the server to identify a previous client.  The
 	      default is +cookie.
 	    
    
-
    
-	      +cookie is also set when +trace
+	    
    
+	      +cookie is also set when +trace
 	      is set to better emulate the default queries from a
 	      nameserver.
 	    
    
-
    
+	  
 
    +[no]crypto
    
-
    
+
    
+	    
    
 	      Toggle the display of cryptographic fields in DNSSEC
 	      records.  The contents of these field are unnecessary
 	      to debug most DNSSEC validation failures and removing
@@ -409,106 +530,138 @@
 	      are replaced by the string "[omitted]" or in the
 	      DNSKEY case the key id is displayed as the replacement,
 	      e.g. "[ key id = value ]".
-	    
    
+	    
    
+	  
 
    +[no]defname
    
-
    
+
    
+	    
    
 	      Deprecated, treated as a synonym for
 	      +[no]search
-	    
    
+	    
    
+	  
 
    +[no]dnssec
    
-
    
+
    
+	    
    
 	      Requests DNSSEC records be sent by setting the DNSSEC
 	      OK bit (DO) in the OPT record in the additional section
 	      of the query.
-	    
    
+	    
    
+	  
 
    +domain=somename
    
-
    
+
    
+	    
    
 	      Set the search list to contain the single domain
 	      somename, as if specified in
-	      a domain directive in
+	      a domain directive in
 	      /etc/resolv.conf, and enable
 	      search list processing as if the
 	      +search option were given.
-	    
    
+	    
    
+	  
 
    +dscp=value
    
-
    
+
    
+	    
    
 	      Set the DSCP code point to be used when sending the
 	      query.  Valid DSCP code points are in the range
 	      [0..63].  By default no code point is explicitly set.
-	    
    
+	    
    
+	  
 
    +[no]edns[=#]
    
-
    
+
    
+	    
    
 	       Specify the EDNS version to query with.  Valid values
 	       are 0 to 255.  Setting the EDNS version will cause
 	       a EDNS query to be sent.  +noedns
 	       clears the remembered EDNS version.  EDNS is set to
 	       0 by default.
-	    
    
+	    
    
+	  
 
    +[no]ednsflags[=#]
    
-
    
+
    
+	    
    
 	      Set the must-be-zero EDNS flags bits (Z bits) to the
 	      specified value. Decimal, hex and octal encodings are
 	      accepted. Setting a named flag (e.g. DO) will silently be
 	      ignored. By default, no Z bits are set.
-	    
    
+	    
    
+	  
 
    +[no]ednsnegotiation
    
-
    
+
    
+	    
    
 	      Enable / disable EDNS version negotiation. By default
 	      EDNS version negotiation is enabled.
-	    
    
+	    
    
+	  
 
    +[no]ednsopt[=code[:value]]
    
-
    
+
    
+	    
    
 	      Specify EDNS option with code point code
 	      and optionally payload of value as a
 	      hexadecimal string.  +noednsopt
 	      clears the EDNS options to be sent.
-	    
    
+	    
    
+	  
 
    +[no]expire
    
-
    
+
    
+	    
    
 	      Send an EDNS Expire option.
-	    
    
+	    
    
+	  
 
    +[no]fail
    
-
    
+
    
+	    
    
 	      Do not try the next server if you receive a SERVFAIL.
 	      The default is to not try the next server which is
 	      the reverse of normal stub resolver behavior.
-	    
    
+	    
    
+	  
 
    +[no]header-only
    
-
    
+
    
+	    
    
 	      Send a query with a DNS header without a question section.
 	      The default is to add a question section.  The query type
 	      and query name are ignored when this is set.
-	    
    
+	    
    
+	  
 
    +[no]identify
    
-
    
+
    
+	    
    
 	      Show [or do not show] the IP address and port number
 	      that supplied the answer when the
 	      +short option is enabled.  If
 	      short form answers are requested, the default is not
 	      to show the source address and port number of the
 	      server that provided the answer.
-	    
    
+	    
    
+	  
 
    +[no]ignore
    
-
    
+
    
+	    
    
 	      Ignore truncation in UDP responses instead of retrying
 	      with TCP.  By default, TCP retries are performed.
-	    
    
+	    
    
+	  
 
    +[no]keepopen
    
-
    
+
    
+	    
    
 	      Keep the TCP socket open between queries and reuse
 	      it rather than creating a new TCP socket for each
 	      lookup.  The default is +nokeepopen.
-	    
    
+	    
    
+	  
 
    +[no]multiline
    
-
    
+
    
+	    
    
 	      Print records like the SOA records in a verbose
 	      multi-line format with human-readable comments.  The
 	      default is to print each record on a single line, to
-	      facilitate machine parsing of the dig
+	      facilitate machine parsing of the dig
 	      output.
-	    
    
+	    
    
+	  
 
    +ndots=D
    
-
    
+
    
+	    
    
 	      Set the number of dots that have to appear in
 	      name to D
 	      for it to be considered absolute.  The default value
@@ -520,102 +673,130 @@
 	      or domain directive in
 	      /etc/resolv.conf if
 	      +search is set.
-	    
    
+	    
    
+	  
 
    +[no]nsid
    
-
    
+
    
+	    
    
 	      Include an EDNS name server ID request when sending
 	      a query.
-	    
    
+	    
    
+	  
 
    +[no]nssearch
    
-
    
-	      When this option is set, dig
+
    
+	    
    
+	      When this option is set, dig
 	      attempts to find the authoritative name servers for
 	      the zone containing the name being looked up and
 	      display the SOA record that each name server has for
 	      the zone.
-	    
    
+	    
    
+	  
 
    +[no]onesoa
    
-
    
+
    
+	    
    
 	      Print only one (starting) SOA record when performing
 	      an AXFR. The default is to print both the starting
 	      and ending SOA records.
-	    
    
+	    
    
+	  
 
    +[no]opcode=value
    
-
    
+
    
+	    
    
 	      Set [restore] the DNS message opcode to the specified
 	      value.  The default value is QUERY (0).
-	    
    
+	    
    
+	  
 
    +[no]qr
    
-
    
+
    
+	    
    
 	      Print [do not print] the query as it is sent.  By
 	      default, the query is not printed.
-	    
    
+	    
    
+	  
 
    +[no]question
    
-
    
+
    
+	    
    
 	      Print [do not print] the question section of a query
 	      when an answer is returned.  The default is to print
 	      the question section as a comment.
-	    
    
+	    
    
+	  
 
    +[no]rdflag
    
-
    
+
    
+	    
    
 	      A synonym for +[no]recurse.
-	    
    
+	    
    
+	  
 
    +[no]recurse
    
-
    
+
    
+	    
    
 	      Toggle the setting of the RD (recursion desired) bit
 	      in the query.  This bit is set by default, which means
-	      dig normally sends recursive
+	      dig normally sends recursive
 	      queries.  Recursion is automatically disabled when
 	      the +nssearch or
 	      +trace query options are used.
-	    
    
+	    
    
+	  
 
    +retry=T
    
-
    
+
    
+	    
    
 	      Sets the number of times to retry UDP queries to
 	      server to T instead of the
 	      default, 2.  Unlike +tries,
 	      this does not include the initial query.
-	    
    
+	    
    
+	  
 
    +[no]rrcomments
    
-
    
+
    
+	    
    
 	      Toggle the display of per-record comments in the
 	      output (for example, human-readable key information
 	      about DNSKEY records).  The default is not to print
 	      record comments unless multiline mode is active.
-	    
    
+	    
    
+	  
 
    +[no]search
    
 
    
-
    
+	    
    
 	      Use [do not use] the search list defined by the
 	      searchlist or domain directive in
 	      resolv.conf (if any).  The search
 	      list is not used by default.
 	    
    
-
    
+	    
    
 	      'ndots' from resolv.conf (default 1)
 	       which may be overridden by +ndots
 	      determines if the name will be treated as relative
 	      or not and hence whether a search is eventually
 	      performed or not.
 	    
    
-
    
+	  
 
    +[no]short
    
-
    
+
    
+	    
    
 	      Provide a terse answer.  The default is to print the
 	      answer in a verbose form.
-	    
    
+	    
    
+	  
 
    +[no]showsearch
    
-
    
+
    
+	    
    
 	      Perform [do not perform] a search showing intermediate
 	      results.
-	    
    
+	    
    
+	  
 
    +[no]sigchase
    
-
    
+
    
+	    
    
 	      Chase DNSSEC signature chains.  Requires dig be
 	      compiled with -DDIG_SIGCHASE.
-	    
    
+	    
    
+	  
 
    +split=W
    
-
    
+
    
+	    
    
 	      Split long hex- or base64-formatted fields in resource
 	      records into chunks of W
 	      characters (where W is rounded
@@ -624,29 +805,37 @@
 	      +split=0 causes fields not to
 	      be split at all.  The default is 56 characters, or
 	      44 characters when multiline mode is active.
-	    
    
+	    
    
+	  
 
    +[no]stats
    
-
    
+
    
+	    
    
 	      This query option toggles the printing of statistics:
 	      when the query was made, the size of the reply and
 	      so on.  The default behavior is to print the query
 	      statistics.
-	    
    
+	    
    
+	  
 
    +[no]subnet=addr/prefix
    
-
    
+
    
+	    
    
 	      Send an EDNS Client Subnet option with the specified
 	      IP address or network prefix.
-	    
    
+	    
    
+	  
 
    +[no]tcp
    
-
    
+
    
+	    
    
 	      Use [do not use] TCP when querying name servers. The
 	      default behavior is to use UDP unless an
 	      ixfr=N query is requested, in which
 	      case the default is TCP.  AXFR queries always use
 	      TCP.
-	    
    
+	    
    
+	  
 
    +timeout=T
    
-
    
+
    
+	    
    
 
 	      Sets the timeout for a query to
 	      T seconds.  The default
@@ -654,97 +843,110 @@
 	      An attempt to set T to less
 	      than 1 will result
 	      in a query timeout of 1 second being applied.
-	    
    
+	    
    
+	  
 
    +[no]topdown
    
-
    
+
    
+	    
    
 	      When chasing DNSSEC signature chains perform a top-down
 	      validation.  Requires dig be compiled with -DDIG_SIGCHASE.
-	    
    
+	    
    
+	  
 
    +[no]trace
    
 
    
-
    
+	    
    
 	      Toggle tracing of the delegation path from the root
 	      name servers for the name being looked up.  Tracing
 	      is disabled by default.  When tracing is enabled,
-	      dig makes iterative queries to
+	      dig makes iterative queries to
 	      resolve the name being looked up.  It will follow
 	      referrals from the root servers, showing the answer
 	      from each server that was used to resolve the lookup.
-	    
    
-
    
+	    
     
    
 	      If @server is also specified, it affects only the
 	      initial query for the root zone name servers.
-	    
    
-
    
-	      +dnssec is also set when +trace
+	    
     
    
+	      +dnssec is also set when +trace
 	      is set to better emulate the default queries from a
 	      nameserver.
 	    
    
-
    
+	  
 
    +tries=T
    
-
    
+
    
+	    
    
 	      Sets the number of times to try UDP queries to server
 	      to T instead of the default,
 	      3.  If T is less than or equal
 	      to zero, the number of tries is silently rounded up
 	      to 1.
-	    
    
+	    
    
+	  
 
    +trusted-key=####
    
 
    
-
    
+	    
    
 	      Specifies a file containing trusted keys to be used
 	      with +sigchase.  Each DNSKEY record
 	      must be on its own line.
-	    
    
-
    
-	      If not specified, dig will look
+	    
     
    
+	      If not specified, dig will look
 	      for /etc/trusted-key.key then
 	      trusted-key.key in the current
 	      directory.
-	    
    
-
    
+	    
     
    
 	      Requires dig be compiled with -DDIG_SIGCHASE.
 	    
    
-
    
+	  
 
    +[no]ttlid
    
-
    
+
    
+	    
    
 	      Display [do not display] the TTL when printing the
 	      record.
-	    
    
+	    
    
+	  
 
    +[no]ttlunits
    
-
    
+
    
+	    
    
 	      Display [do not display] the TTL in friendly human-readable
 	      time units of "s", "m", "h", "d", and "w", representing
 	      seconds, minutes, hours, days and weeks.  Implies +ttlid.
-	    
    
+	    
    
+	  
 
    +[no]vc
    
-
    
+
    
+	    
    
 	      Use [do not use] TCP when querying name servers.  This
 	      alternate syntax to +[no]tcp
 	      is provided for backwards compatibility.  The "vc"
 	      stands for "virtual circuit".
-	    
    
+	    
    
+	  
 
    +[no]zflag
    
-
    
+
    
+	    
    
 	      Set [do not set] the last unassigned DNS header flag in a
 	      DNS query.  This flag is off by default.
-	    
    
+	    
    
+	  
 
    
 
    
 
     
    
-
    
-
    
-
    MULTIPLE QUERIES
    
-
    
-      The BIND 9 implementation of dig 
+  
    
+
+  
    
+
    MULTIPLE QUERIES
    
+    
+
+    
    
+      The BIND 9 implementation of dig 
       supports
       specifying multiple queries on the command line (in addition to
       supporting the -f batch file option).  Each of those
       queries can be supplied with its own set of flags, options and query
       options.
     
    
-
    
+
+    
    
       In this case, each query argument
       represent an
       individual query in the command-line syntax described above.  Each
@@ -752,7 +954,8 @@
       looked up, an optional query type and class and any query options that
       should be applied to that query.
     
    
-
    
+
+    
    
       A global set of query options, which should be applied to all queries,
       can also be supplied.  These global query options must precede the
       first tuple of name, class, type, options, flags, and query options
@@ -764,7 +967,7 @@
 dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
 
    
 
    
-      shows how dig could be used from the
+      shows how dig could be used from the
       command line
       to make three lookups: an ANY query for www.isc.org, a
       reverse lookup of 127.0.0.1 and a query for the NS records of
@@ -772,49 +975,65 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
 
       A global query option of +qr is
       applied, so
-      that dig shows the initial query it made
+      that dig shows the initial query it made
       for each
       lookup.  The final query has a local query option of
-      +noqr which means that dig
+      +noqr which means that dig
       will not print the initial query when it looks up the NS records for
       isc.org.
     
    
-
-
    
-
    IDN SUPPORT
    
-
    
-      If dig has been built with IDN (internationalized
+
+  
    
+
+  
    
+
    IDN SUPPORT
    
+    
+    
    
+      If dig has been built with IDN (internationalized
       domain name) support, it can accept and display non-ASCII domain names.
-      dig appropriately converts character encoding of
+      dig appropriately converts character encoding of
       domain name before sending a request to DNS server or displaying a
       reply from the server.
       If you'd like to turn off the IDN support for some reason, defines
       the IDN_DISABLE environment variable.
       The IDN support is disabled if the variable is set when 
-      dig runs.
+      dig runs.
     
    
-
    
-
    
-
    FILES
    
-
    /etc/resolv.conf
+  
    
+
+  
    
+
    FILES
    
+    
+    
    /etc/resolv.conf
     
    
-
    ${HOME}/.digrc
+    
    ${HOME}/.digrc
     
    
-
    
-
    
-
    SEE ALSO
    
-
    host(1),
-      named(8),
-      dnssec-keygen(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+	host(1)
+      ,
+      
+	named(8)
+      ,
+      
+	dnssec-keygen(8)
+      ,
       RFC1035.
     
    
-
    
-
    
-
    BUGS
    
-
    
+  
    
+
+  
    
+
    BUGS
    
+    
+    
    
       There are probably too many query options.
     
    
-
    
+  
+
 
 
    
 
    
@@ -833,6 +1052,6 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-checkds.html b/doc/arm/man.dnssec-checkds.html
index e79e294eae..7610521e42 100644
--- a/doc/arm/man.dnssec-checkds.html
+++ b/doc/arm/man.dnssec-checkds.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-checkds
-
-
+
+
 
 
 
@@ -39,66 +38,108 @@
 
 
    
 
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-checkds — A DNSSEC delegation consistency checking tool.
    
+
    
+    dnssec-checkds
+     — A DNSSEC delegation consistency checking tool.
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-checkds  [-l domain] [-f file] [-d dig path] [-D dsfromkey path] {zone}
    
-
    dnssec-dsfromkey  [-l domain] [-f file] [-d dig path] [-D dsfromkey path] {zone}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-checkds
+    
    
+      dnssec-checkds 
+       [-l domain]
+       [-f file]
+       [-d dig path]
+       [-D dsfromkey path]
+       {zone}
+    
    
+    
    
+      dnssec-dsfromkey 
+       [-l domain]
+       [-f file]
+       [-d dig path]
+       [-D dsfromkey path]
+       {zone}
+   
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-checkds
       verifies the correctness of Delegation Signer (DS) or DNSSEC
       Lookaside Validation (DLV) resource records for keys in a specified
       zone.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -f file
    
-
    
+
    
+          
    
             If a file is specified, then the zone is
             read from that file to find the DNSKEY records.  If not,
             then the DNSKEY records for the zone are looked up in the DNS.
-          
    
+          
    
+        
 
    -l domain
    
-
    
+
    
+          
    
             Check for a DLV record in the specified lookaside domain, 
             instead of checking for a DS record in the zone's parent.
             For example, to check for DLV records for "example.com"
             in ISC's DLV zone, use:
-            dnssec-checkds -l dlv.isc.org example.com
-          
    
+            dnssec-checkds -l dlv.isc.org example.com
+          
    
+        
 
    -d dig path
    
-
    
-            Specifies a path to a dig binary.  Used
+
    
+          
    
+            Specifies a path to a dig binary.  Used
             for testing.
-          
    
+          
    
+        
 
    -D dsfromkey path
    
-
    
-            Specifies a path to a dnssec-dsfromkey binary.
+
    
+          
    
+            Specifies a path to a dnssec-dsfromkey binary.
             Used for testing.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-dsfromkey(8),
-      dnssec-keygen(8),
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-dsfromkey(8)
+      ,
+      
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      ,
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -118,6 +159,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-coverage.html b/doc/arm/man.dnssec-coverage.html
index e5450dfd50..7bfb590faf 100644
--- a/doc/arm/man.dnssec-coverage.html
+++ b/doc/arm/man.dnssec-coverage.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-coverage
-
-
+
+
 
 
 
@@ -39,24 +38,49 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-coverage — checks future DNSKEY coverage for a zone
    
+
    
+    dnssec-coverage
+     — checks future DNSKEY coverage for a zone
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-coverage  [-K directory] [-l length] [-f file] [-d DNSKEY TTL] [-m max TTL] [-r interval] [-c compilezone path] [-k] [-z] [zone]
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-coverage
+    
    
+      dnssec-coverage 
+       [-K directory]
+       [-l length]
+       [-f file]
+       [-d DNSKEY TTL]
+       [-m max TTL]
+       [-r interval]
+       [-c compilezone path]
+       [-k]
+       [-z]
+       [zone]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-coverage
       verifies that the DNSSEC keys for a given zone or a set of zones
       have timing metadata set properly to ensure no future lapses in DNSSEC
       coverage.
     
    
-
    
+    
    
       If zone is specified, then keys found in
       the key repository matching that zone are scanned, and an ordered
       list is generated of the events scheduled for that key (i.e.,
@@ -69,47 +93,54 @@
       key is rolled, and cached data signed by the prior key has not had
       time to expire from resolver caches.
     
    
-
    
+    
    
       If zone is not specified, then all keys in the
       key repository will be scanned, and all zones for which there are
       keys will be analyzed.  (Note: This method of reporting is only
       accurate if all the zones that have keys in a given repository
       share the same TTL parameters.)
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which keys can be found.  Defaults to the
             current working directory.
-          
    
+          
    
+        
 
    -f file
    
-
    
+
    
+          
    
             If a file is specified, then the zone is
             read from that file; the largest TTL and the DNSKEY TTL are
             determined directly from the zone data, and the
             -m and -d options do
             not need to be specified on the command line.
-          
    
+          
    
+        
 
    -l duration
    
 
    
-
    
+          
    
             The length of time to check for DNSSEC coverage.  Key events
             scheduled further into the future than duration
             will be ignored, and assumed to be correct.  
           
    
-
    
+          
    
             The value of duration can be set in seconds,
             or in larger units of time by adding a suffix: 'mi' for minutes,
             'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months,
             'y' for years.
           
    
-
    
+        
 
    -m maximum TTL
    
 
    
-
    
+          
    
             Sets the value to be used as the maximum TTL for the zone or
             zones being analyzed when determining whether there is a
             possibility of validation failure.  When a zone-signing key is
@@ -118,21 +149,21 @@
             before that key can be purged from the DNSKEY RRset.  If that
             condition does not apply, a warning will be generated.
           
    
-
    
+          
    
             The length of the TTL can be set in seconds, or in larger units
             of time by adding a suffix: 'mi' for minutes, 'h' for hours,
             'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
           
    
-
    
+          
    
             This option is mandatory unless the -f has
             been used to specify a zone file.  (If -f has
             been specified, this option may still be used; it will override
             the value found in the file.)
           
    
-
    
+        
 
    -d DNSKEY TTL
    
 
    
-
    
+          
    
             Sets the value to be used as the DNSKEY TTL for the zone or
             zones being analyzed when determining whether there is a
             possibility of validation failure.  When a key is rolled (that
@@ -142,69 +173,81 @@
             signatures.  If that condition does not apply, a warning
             will be generated.
           
    
-
    
+          
    
             The length of the TTL can be set in seconds, or in larger units
             of time by adding a suffix: 'mi' for minutes, 'h' for hours,
             'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
           
    
-
    
+          
    
             This option is mandatory unless the -f has
             been used to specify a zone file, or a default key TTL was
             set with the -L to
-            dnssec-keygen.  (If either of those is true,
+            dnssec-keygen.  (If either of those is true,
             this option may still be used; it will override the value found
             in the zone or key file.)
           
    
-
    
+        
 
    -r resign interval
    
 
    
-
    
+          
    
             Sets the value to be used as the resign interval for the zone
             or zones being analyzed when determining whether there is a
             possibility of validation failure.  This value defaults to
             22.5 days, which is also the default in
-            named.  However, if it has been changed
+            named.  However, if it has been changed
             by the sig-validity-interval option in
             named.conf, then it should also be
             changed here.
           
    
-
    
+          
    
             The length of the interval can be set in seconds, or in larger
             units of time by adding a suffix: 'mi' for minutes, 'h' for hours,
             'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.
           
    
-
    
+        
 
    -k
    
-
    
+
    
+          
    
 	    Only check KSK coverage; ignore ZSK events. Cannot be
             used with -z.
-          
    
+          
    
+        
 
    -z
    
-
    
+
    
+          
    
 	    Only check ZSK coverage; ignore KSK events. Cannot be
             used with -k.
-          
    
+          
    
+        
 
    -c compilezone path
    
-
    
-            Specifies a path to a named-compilezone binary.
+
    
+          
    
+            Specifies a path to a named-compilezone binary.
             Used for testing.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
-      dnssec-checkds(8),
-      dnssec-dsfromkey(8),
-      dnssec-keygen(8),
-      dnssec-signzone(8)
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+      
+        dnssec-checkds(8)
+      ,
+      
+        dnssec-dsfromkey(8)
+      ,
+      
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -225,6 +268,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-dsfromkey.html b/doc/arm/man.dnssec-dsfromkey.html
index b27c2925ec..21d6fb7eb6 100644
--- a/doc/arm/man.dnssec-dsfromkey.html
+++ b/doc/arm/man.dnssec-dsfromkey.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-dsfromkey
-
-
+
+
 
 
 
@@ -39,166 +38,245 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-dsfromkey — DNSSEC DS RR generation tool
    
+
    
+    dnssec-dsfromkey
+     — DNSSEC DS RR generation tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-dsfromkey  [-v level] [-1] [-2] [-a alg] [-C] [-l domain] [-T TTL] {keyfile}
    
-
    dnssec-dsfromkey  {-s} [-1] [-2] [-a alg] [-K directory] [-l domain] [-s] [-c class] [-T TTL] [-f file] [-A] [-v level] {dnsname}
    
-
    dnssec-dsfromkey  [-h] [-V]
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-dsfromkey
+    
    
+      dnssec-dsfromkey 
+       [-v level]
+       [-1]
+       [-2]
+       [-a alg]
+       [-C]
+       [-l domain]
+       [-T TTL]
+       {keyfile}
+    
    
+    
    
+      dnssec-dsfromkey 
+       {-s}
+       [-1]
+       [-2]
+       [-a alg]
+       [-K directory]
+       [-l domain]
+       [-s]
+       [-c class]
+       [-T TTL]
+       [-f file]
+       [-A]
+       [-v level]
+       {dnsname}
+   
    
+    
    
+      dnssec-dsfromkey 
+       [-h]
+       [-V]
+   
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-dsfromkey
       outputs the Delegation Signer (DS) resource record (RR), as defined in
       RFC 3658 and RFC 4509, for the given key(s).
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -1
    
-
    
+
    
+          
    
             Use SHA-1 as the digest algorithm (the default is to use
             both SHA-1 and SHA-256).
-          
    
+          
    
+        
 
    -2
    
-
    
+
    
+          
    
             Use SHA-256 as the digest algorithm.
-          
    
+          
    
+        
 
    -a algorithm
    
-
    
+
    
+          
    
             Select the digest algorithm. The value of
             algorithm must be one of SHA-1 (SHA1),
             SHA-256 (SHA256), GOST or SHA-384 (SHA384).
             These values are case insensitive.
-          
    
+          
    
+        
 
    -C
    
-
    
+
    
+          
    
             Generate CDS records rather than DS records.  This is mutually
 	    exclusive with generating lookaside records.
-          
    
+          
    
+        
 
    -T TTL
    
-
    
+
    
+          
    
             Specifies the TTL of the DS records.
-          
    
+          
    
+	  
 
    -K directory
    
-
    
+
    
+          
    
             Look for key files (or, in keyset mode,
             keyset- files) in
             directory.
-          
    
+          
    
+        
 
    -f file
    
 
    
-
    
+          
    
             Zone file mode: in place of the keyfile name, the argument is
             the DNS domain name of a zone master file, which can be read
             from file.  If the zone name is the same as
             file, then it may be omitted.
           
    
-
    
+          
    
             If file is set to "-", then
             the zone data is read from the standard input.  This makes it
-            possible to use the output of the dig
+            possible to use the output of the dig
             command as input, as in:
           
    
-
    
+          
    
             dig dnskey example.com | dnssec-dsfromkey -f - example.com
           
    
-
    
+        
 
    -A
    
-
    
+
    
+          
    
             Include ZSKs when generating DS records.  Without this option,
             only keys which have the KSK flag set will be converted to DS
             records and printed.  Useful only in zone file mode. 
-          
    
+          
    
+        
 
    -l domain
    
-
    
+
    
+          
    
             Generate a DLV set instead of a DS set.  The specified
             domain is appended to the name for each
             record in the set.
             The DNSSEC Lookaside Validation (DLV) RR is described
             in RFC 4431.  This is mutually exclusive with generating
 	    CDS records.
-          
    
+          
    
+        
 
    -s
    
-
    
+
    
+          
    
             Keyset mode: in place of the keyfile name, the argument is
             the DNS domain name of a keyset file.
-          
    
+          
    
+        
 
    -c class
    
-
    
+
    
+          
    
             Specifies the DNS class (default is IN).  Useful only
             in keyset or zone file mode.
-          
    
+          
    
+	  
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Prints usage information.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+          
    
             Prints version information.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    EXAMPLE
    
-
    
+  
    
+
+  
    
+
    EXAMPLE
    
+    
+    
    
       To build the SHA-256 DS RR from the
       Kexample.com.+003+26160
       keyfile name, the following command would be issued:
     
    
-
    dnssec-dsfromkey -2 Kexample.com.+003+26160
+    
    dnssec-dsfromkey -2 Kexample.com.+003+26160
     
    
-
    
+    
    
       The command would print something like:
     
    
-
    example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94
+    
    example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94
     
    
-
    
-
    
-
    FILES
    
-
    
+  
    
+
+  
    
+
    FILES
    
+    
+    
    
       The keyfile can be designed by the key identification
       Knnnn.+aaa+iiiii or the full file name
       Knnnn.+aaa+iiiii.key as generated by
       dnssec-keygen(8).
     
    
-
    
+    
    
       The keyset file name is built from the directory,
       the string keyset- and the
       dnsname.
     
    
-
    
-
    
-
    CAVEAT
    
-
    
+  
    
+
+  
    
+
    CAVEAT
    
+    
+    
    
       A keyfile error can give a "file not found" even if the file exists.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 3658,
       RFC 4431.
       RFC 4509.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -219,6 +297,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-importkey.html b/doc/arm/man.dnssec-importkey.html
index 8a784bd885..d34785a275 100644
--- a/doc/arm/man.dnssec-importkey.html
+++ b/doc/arm/man.dnssec-importkey.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-importkey
-
-
+
+
 
 
 
@@ -39,20 +38,54 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-importkey — Import DNSKEY records from external systems so they can be managed.
    
+
    
+    dnssec-importkey
+     — Import DNSKEY records from external systems so they can be managed.
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-importkey  [-K directory] [-L ttl] [-P date/offset] [-D date/offset] [-h] [-v level] [-V] {keyfile}
    
-
    dnssec-importkey  {-f filename} [-K directory] [-L ttl] [-P date/offset] [-D date/offset] [-h] [-v level] [-V] [dnsname]
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-importkey
+    
    
+      dnssec-importkey 
+       [-K directory]
+       [-L ttl]
+       [-P date/offset]
+       [-D date/offset]
+       [-h]
+       [-v level]
+       [-V]
+       {keyfile}
+    
    
+    
    
+      dnssec-importkey 
+       {-f filename}
+       [-K directory]
+       [-L ttl]
+       [-P date/offset]
+       [-D date/offset]
+       [-h]
+       [-v level]
+       [-V]
+       [dnsname]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-importkey
       reads a public DNSKEY record and generates a pair of
       .key/.private files.  The DNSKEY record may be read from an
       existing .key file, in which case a corresponding .private file
@@ -60,7 +93,7 @@
       from the standard input, in which case both .key and .private
       files will be generated.
     
    
-
    
+    
    
       The newly-created .private file does not
       contain private key data, and cannot be used for signing.
       However, having a .private file makes it possible to set
@@ -69,53 +102,68 @@
       public key can be added to and removed from the DNSKEY RRset
       on schedule even if the true private key is stored offline.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -f filename
    
 
    
-
    
+          
    
             Zone file mode: instead of a public keyfile name, the argument
 	    is the DNS domain name of a zone master file, which can be read
             from file.  If the domain name is the same as
             file, then it may be omitted.
           
    
-
    
+          
    
             If file is set to "-", then
             the zone data is read from the standard input.
           
    
-
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which the key files are to reside.
-          
    
+          
    
+        
 
    -L ttl
    
-
    
+
    
+          
    
             Sets the default TTL to use for this key when it is converted
             into a DNSKEY RR.  If the key is imported into a zone,
             this is the TTL that will be used for it, unless there was
             already a DNSKEY RRset in place, in which case the existing TTL
             would take precedence.  Setting the default TTL to
             0 or none removes it.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+	  
    
 	    Emit usage message and exit.
-	  
    
+	  
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    
-
    
-
    
-
    TIMING OPTIONS
    
-
    
+  
    
+
+  
    
+
    TIMING OPTIONS
    
+    
+    
    
       Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
       If the argument begins with a '+' or '-', it is interpreted as
       an offset from the present time.  For convenience, if such an offset
@@ -126,43 +174,52 @@
       is computed in seconds.  To explicitly prevent a date from being
       set, use 'none' or 'never'.
     
    
-
    
+
+    
    
 
    -P date/offset
    
-
    
+
    
+          
    
             Sets the date on which a key is to be published to the zone.
             After that date, the key will be included in the zone but will
             not be used to sign it.
-          
    
+          
    
+        
 
    -D date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be deleted.  After that
             date, the key will no longer be included in the zone.  (It
             may remain in the key repository, however.)
-          
    
+          
    
+        
 
    
-
    
-
    
-
    FILES
    
-
    
+  
    
+
+  
    
+
    FILES
    
+    
+    
    
       A keyfile can be designed by the key identification
       Knnnn.+aaa+iiiii or the full file name
       Knnnn.+aaa+iiiii.key as generated by
       dnssec-keygen(8).
     
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 5011.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -183,6 +240,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-keyfromlabel.html b/doc/arm/man.dnssec-keyfromlabel.html
index b5fed9511d..6a96e841e6 100644
--- a/doc/arm/man.dnssec-keyfromlabel.html
+++ b/doc/arm/man.dnssec-keyfromlabel.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-keyfromlabel
-
-
+
+
 
 
 
@@ -39,72 +38,116 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-keyfromlabel — DNSSEC key generation tool
    
+
    
+    dnssec-keyfromlabel
+     — DNSSEC key generation tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-keyfromlabel  {-l label} [-3] [-a algorithm] [-A date/offset] [-c class] [-D date/offset] [-E engine] [-f flag] [-G] [-I date/offset] [-i interval] [-k] [-K directory] [-L ttl] [-n nametype] [-P date/offset] [-p protocol] [-R date/offset] [-S key] [-t type] [-v level] [-V] [-y] {name}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-keyfromlabel
+    
    
+      dnssec-keyfromlabel 
+       {-l label}
+       [-3]
+       [-a algorithm]
+       [-A date/offset]
+       [-c class]
+       [-D date/offset]
+       [-E engine]
+       [-f flag]
+       [-G]
+       [-I date/offset]
+       [-i interval]
+       [-k]
+       [-K directory]
+       [-L ttl]
+       [-n nametype]
+       [-P date/offset]
+       [-p protocol]
+       [-R date/offset]
+       [-S key]
+       [-t type]
+       [-v level]
+       [-V]
+       [-y]
+       {name}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-keyfromlabel
       generates a key pair of files that referencing a key object stored
       in a cryptographic hardware service module (HSM).  The private key
       file can be used for DNSSEC signing of zone data as if it were a
-      conventional signing key created by dnssec-keygen,
+      conventional signing key created by dnssec-keygen,
       but the key material is stored within the HSM, and the actual signing
       takes place there.
     
    
-
    
+    
    
       The name of the key is specified on the command
       line.  This must match the name of the zone for which the key is
       being generated.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -a algorithm
    
 
    
-
    
+	  
    
 	    Selects the cryptographic algorithm.  The value of
             algorithm must be one of RSAMD5, RSASHA1,
 	    DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
 	    ECDSAP256SHA256 or ECDSAP384SHA384.
 	    These values are case insensitive.
 	  
    
-
    
+          
    
             If no algorithm is specified, then RSASHA1 will be used by
             default, unless the -3 option is specified,
             in which case NSEC3RSASHA1 will be used instead.  (If
             -3 is used and an algorithm is specified,
             that algorithm will be checked for compatibility with NSEC3.)
           
    
-
    
+          
    
             Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
             algorithm, and DSA is recommended.
           
    
-
    
+          
    
             Note 2: DH automatically sets the -k flag.
           
    
-
    
+        
 
    -3
    
-
    
+
    
+          
    
 	    Use an NSEC3-capable algorithm to generate a DNSSEC key.
             If this option is used and no algorithm is explicitly
             set on the command line, NSEC3RSASHA1 will be used by
             default.
-          
    
+          
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             Specifies the cryptographic hardware to use.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -112,20 +155,20 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -l label
    
 
    
-
    
+          
    
             Specifies the label for a key pair in the crypto hardware.
           
    
-
    
+          
    
             When BIND 9 is built with OpenSSL-based
             PKCS#11 support, the label is an arbitrary string that
             identifies a particular key.  It may be preceded by an
             optional OpenSSL engine name, followed by a colon, as in
             "pkcs11:keylabel".
           
    
-
    
+          
    
             When BIND 9 is built with native PKCS#11
             support, the label is a PKCS#11 URI string in the format
             "pkcs11:keyword=value[;keyword=value;...]"
@@ -134,7 +177,7 @@
             which the HSM's PIN code can be obtained.  The label will be
             stored in the on-disk "private" file.
           
    
-
    
+          
    
             If the label contains a
             pin-source field, tools using the generated
             key files will be able to use the HSM for signing and other
@@ -143,72 +186,93 @@
             may reduce the security advantage of using an HSM; be sure
             this is what you want to do before making use of this feature.
           
    
-
    
+        
 
    -n nametype
    
-
    
+
    
+          
    
             Specifies the owner type of the key.  The value of
             nametype must either be ZONE (for a DNSSEC
             zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
             a host (KEY)),
             USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
             These values are case insensitive.
-          
    
+          
    
+        
 
    -C
    
-
    
+
    
+          
    
 	    Compatibility mode:  generates an old-style key, without
-	    any metadata.  By default, dnssec-keyfromlabel
+	    any metadata.  By default, dnssec-keyfromlabel
 	    will include the key's creation date in the metadata stored
 	    with the private key, and other dates may be set there as well
 	    (publication date, activation date, etc).  Keys that include
 	    this data may be incompatible with older versions of BIND; the
 	    -C option suppresses them.
-          
    
+          
    
+        
 
    -c class
    
-
    
+
    
+          
    
             Indicates that the DNS record containing the key should have
             the specified class.  If not specified, class IN is used.
-          
    
+          
    
+        
 
    -f flag
    
-
    
+
    
+          
    
             Set the specified flag in the flag field of the KEY/DNSKEY record.
             The only recognized flags are KSK (Key Signing Key) and REVOKE.
-          
    
+          
    
+        
 
    -G
    
-
    
+
    
+          
    
             Generate a key, but do not publish it or sign with it.  This
             option is incompatible with -P and -A.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Prints a short summary of the options and arguments to
-            dnssec-keyfromlabel.
-          
    
+            dnssec-keyfromlabel.
+          
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which the key files are to be written.
-          
    
+          
    
+        
 
    -k
    
-
    
+
    
+          
    
             Generate KEY records rather than DNSKEY records.
-          
    
+          
    
+        
 
    -L ttl
    
-
    
+
    
+          
    
             Sets the default TTL to use for this key when it is converted
             into a DNSKEY RR.  If the key is imported into a zone,
             this is the TTL that will be used for it, unless there was
             already a DNSKEY RRset in place, in which case the existing TTL
             would take precedence.  Setting the default TTL to
             0 or none removes it.
-          
    
+          
    
+        
 
    -p protocol
    
-
    
+
    
+          
    
             Sets the protocol value for the key.  The protocol
             is a number between 0 and 255.  The default is 3 (DNSSEC).
             Other possible values for this argument are listed in
             RFC 2535 and its successors.
-          
    
+          
    
+        
 
    -S key
    
-
    
+
    
+          
    
             Generate a key as an explicit successor to an existing key.
 	    The name, algorithm, size, and type of the key will be set
 	    to match the predecessor. The activation date of the new
@@ -216,35 +280,47 @@
 	    one. The publication date will be set to the activation
 	    date minus the prepublication interval, which defaults to
 	    30 days.
-          
    
+          
    
+        
 
    -t type
    
-
    
+
    
+          
    
             Indicates the use of the key.  type must be
             one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF.  The default
             is AUTHCONF.  AUTH refers to the ability to authenticate
             data, and CONF the ability to encrypt data.
-          
    
+          
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    -y
    
-
    
+
    
+          
    
             Allows DNSSEC key files to be generated even if the key ID
 	    would collide with that of an existing key, in the event of
 	    either key being revoked.  (This is only safe to use if you
             are sure you won't be using RFC 5011 trust anchor maintenance
             with either of the keys involved.)
-          
    
+          
    
+        
 
    
-
    
-
    
-
    TIMING OPTIONS
    
-
    
+  
    
+
+  
    
+
    TIMING OPTIONS
    
+    
+
+    
    
       Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
       If the argument begins with a '+' or '-', it is interpreted as
       an offset from the present time.  For convenience, if such an offset
@@ -255,42 +331,53 @@
       is computed in seconds.  To explicitly prevent a date from being
       set, use 'none' or 'never'.
     
    
-
    
+
+    
    
 
    -P date/offset
    
-
    
+
    
+          
    
             Sets the date on which a key is to be published to the zone.
             After that date, the key will be included in the zone but will
             not be used to sign it.  If not set, and if the -G option has
             not been used, the default is "now".
-          
    
+          
    
+        
 
    -A date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be activated.  After that
             date, the key will be included in the zone and used to sign
             it.  If not set, and if the -G option has not been used, the
             default is "now".
-          
    
+          
    
+        
 
    -R date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be revoked.  After that
             date, the key will be flagged as revoked.  It will be included
             in the zone and will be used to sign it.
-          
    
+          
    
+        
 
    -I date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be retired.  After that
             date, the key will still be included in the zone, but it
             will not be used to sign it.
-          
    
+          
    
+        
 
    -D date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be deleted.  After that
             date, the key will no longer be included in the zone.  (It
             may remain in the key repository, however.)
-          
    
+          
    
+        
 
    -i interval
    
 
    
-
    
+          
    
             Sets the prepublication interval for a key.  If set, then
             the publication and activation dates must be separated by at least
             this much time.  If the activation date is specified but the
@@ -299,74 +386,84 @@
             the publication date is specified but activation date isn't,
             then activation will be set to this much time after publication.
           
    
-
    
+          
    
             If the key is being created as an explicit successor to another
             key, then the default prepublication interval is 30 days; 
             otherwise it is zero.
           
    
-
    
+          
    
             As with date offsets, if the argument is followed by one of
             the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
             interval is measured in years, months, weeks, days, hours,
             or minutes, respectively.  Without a suffix, the interval is
             measured in seconds.
           
    
-
    
+        
 
    
-
    
-
    
-
    GENERATED KEY FILES
    
-
    
-      When dnssec-keyfromlabel completes
+  
    
+
+  
    
+
    GENERATED KEY FILES
    
+    
+    
    
+      When dnssec-keyfromlabel completes
       successfully,
       it prints a string of the form Knnnn.+aaa+iiiii
       to the standard output.  This is an identification string for
       the key files it has generated.
     
    
-
      
-
    • nnnn is the key name.
-        
      • 
-
    • aaa is the numeric representation
+    
        
+
      • 
+        
        nnnn is the key name.
+        
        
+      
        • 
+
      • 
+        
        aaa is the numeric representation
           of the algorithm.
-        
        • 
-
      • iiiii is the key identifier (or
+        
        
+      
        • 
+
      • 
+        
        iiiii is the key identifier (or
           footprint).
-        
        • 
+        
        
+      
 
      
-
      dnssec-keyfromlabel 
+    
      dnssec-keyfromlabel 
       creates two files, with names based
       on the printed string.  Knnnn.+aaa+iiiii.key
       contains the public key, and
       Knnnn.+aaa+iiiii.private contains the
       private key.
     
      
-
      
+    
      
       The .key file contains a DNS KEY record
       that
       can be inserted into a zone file (directly or with a $INCLUDE
       statement).
     
      
-
      
+    
      
       The .private file contains
       algorithm-specific
       fields.  For obvious security reasons, this file does not have
       general read permission.
     
      
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 4034,
       The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13).
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -387,6 +484,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-keygen.html b/doc/arm/man.dnssec-keygen.html
index 9a63f9ce5a..217046141f 100644
--- a/doc/arm/man.dnssec-keygen.html
+++ b/doc/arm/man.dnssec-keygen.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-keygen
-
-
+
+
 
 
 
@@ -39,36 +38,84 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-keygen — DNSSEC key generation tool
    
+
    
+    dnssec-keygen
+     — DNSSEC key generation tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-keygen  [-a algorithm] [-b keysize] [-n nametype] [-3] [-A date/offset] [-C] [-c class] [-D date/offset] [-E engine] [-f flag] [-G] [-g generator] [-h] [-I date/offset] [-i interval] [-K directory] [-L ttl] [-k] [-P date/offset] [-p protocol] [-q] [-R date/offset] [-r randomdev] [-S key] [-s strength] [-t type] [-v level] [-V] [-z] {name}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-keygen
+    
    
+      dnssec-keygen 
+       [-a algorithm]
+       [-b keysize]
+       [-n nametype]
+       [-3]
+       [-A date/offset]
+       [-C]
+       [-c class]
+       [-D date/offset]
+       [-E engine]
+       [-f flag]
+       [-G]
+       [-g generator]
+       [-h]
+       [-I date/offset]
+       [-i interval]
+       [-K directory]
+       [-L ttl]
+       [-k]
+       [-P date/offset]
+       [-p protocol]
+       [-q]
+       [-R date/offset]
+       [-r randomdev]
+       [-S key]
+       [-s strength]
+       [-t type]
+       [-v level]
+       [-V]
+       [-z]
+       {name}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-keygen
       generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
       and RFC 4034.  It can also generate keys for use with
       TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY
       (Transaction Key) as defined in RFC 2930.
     
    
-
    
+    
    
       The name of the key is specified on the command
       line.  For DNSSEC keys, this must match the name of the zone for
       which the key is being generated.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -a algorithm
    
 
    
-
    
+          
    
             Selects the cryptographic algorithm.  For DNSSEC keys, the value
             of algorithm must be one of RSAMD5, RSASHA1,
 	    DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECCGOST,
@@ -78,26 +125,26 @@
             HMAC-SHA256, HMAC-SHA384, or HMAC-SHA512.  These values are
             case insensitive.
           
    
-
    
+          
    
             If no algorithm is specified, then RSASHA1 will be used by
             default, unless the -3 option is specified,
             in which case NSEC3RSASHA1 will be used instead.  (If
             -3 is used and an algorithm is specified,
             that algorithm will be checked for compatibility with NSEC3.)
           
    
-
    
+          
    
             Note 1: that for DNSSEC, RSASHA1 is a mandatory to implement
             algorithm, and DSA is recommended.  For TSIG, HMAC-MD5 is
 	    mandatory.
           
    
-
    
+          
    
             Note 2: DH, HMAC-MD5, and HMAC-SHA1 through HMAC-SHA512
             automatically set the -T KEY option.
           
    
-
    
+        
 
    -b keysize
    
 
    
-
    
+          
    
             Specifies the number of bits in the key.  The choice of key
             size depends on the algorithm used.  RSA keys must be
             between 512 and 2048 bits.  Diffie Hellman keys must be between
@@ -106,7 +153,7 @@
             between 1 and 512 bits. Elliptic curve algorithms don't need
             this parameter.
           
    
-
    
+          
    
             The key size does not need to be specified if using a default
             algorithm.  The default key size is 1024 bits for zone signing
             keys (ZSKs) and 2048 bits for key signing keys (KSKs,
@@ -115,9 +162,10 @@
             then there is no default key size, and the -b
             must be used.
           
    
-
    
+        
 
    -n nametype
    
-
    
+
    
+          
    
             Specifies the owner type of the key.  The value of
             nametype must either be ZONE (for a DNSSEC
             zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with
@@ -125,37 +173,44 @@
             USER (for a key associated with a user(KEY)) or OTHER (DNSKEY).
             These values are case insensitive.  Defaults to ZONE for DNSKEY
 	    generation.
-          
    
+          
    
+        
 
    -3
    
-
    
+
    
+          
    
 	    Use an NSEC3-capable algorithm to generate a DNSSEC key.
             If this option is used and no algorithm is explicitly
             set on the command line, NSEC3RSASHA1 will be used by
             default. Note that RSASHA256, RSASHA512, ECCGOST,
 	    ECDSAP256SHA256 and ECDSAP384SHA384 algorithms
 	    are NSEC3-capable.
-          
    
+          
    
+        
 
    -C
    
-
    
+
    
+          
    
 	    Compatibility mode:  generates an old-style key, without
-	    any metadata.  By default, dnssec-keygen
+	    any metadata.  By default, dnssec-keygen
 	    will include the key's creation date in the metadata stored
 	    with the private key, and other dates may be set there as well
 	    (publication date, activation date, etc).  Keys that include
 	    this data may be incompatible with older versions of BIND; the
 	    -C option suppresses them.
-          
    
+          
    
+        
 
    -c class
    
-
    
+
    
+          
    
             Indicates that the DNS record containing the key should have
             the specified class.  If not specified, class IN is used.
-          
    
+          
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             Specifies the cryptographic hardware to use, when applicable.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -163,39 +218,52 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -f flag
    
-
    
+
    
+          
    
             Set the specified flag in the flag field of the KEY/DNSKEY record.
             The only recognized flags are KSK (Key Signing Key) and REVOKE.
-          
    
+          
    
+        
 
    -G
    
-
    
+
    
+          
    
             Generate a key, but do not publish it or sign with it.  This
             option is incompatible with -P and -A.
-          
    
+          
    
+        
 
    -g generator
    
-
    
+
    
+          
    
             If generating a Diffie Hellman key, use this generator.
             Allowed values are 2 and 5.  If no generator
             is specified, a known prime from RFC 2539 will be used
             if possible; otherwise the default is 2.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Prints a short summary of the options and arguments to
-            dnssec-keygen.
-          
    
+            dnssec-keygen.
+          
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which the key files are to be written.
-          
    
+          
    
+        
 
    -k
    
-
    
+
    
+          
    
             Deprecated in favor of -T KEY.
-          
    
+          
    
+        
 
    -L ttl
    
-
    
+
    
+          
    
             Sets the default TTL to use for this key when it is converted
             into a DNSKEY RR.  If the key is imported into a zone,
             this is the TTL that will be used for it, unless there was
@@ -204,19 +272,23 @@
             is no existing DNSKEY RRset, the TTL will default to the
             SOA TTL. Setting the default TTL to 0
             or none is the same as leaving it unset.
-          
    
+          
    
+        
 
    -p protocol
    
-
    
+
    
+          
    
             Sets the protocol value for the generated key.  The protocol
             is a number between 0 and 255.  The default is 3 (DNSSEC).
             Other possible values for this argument are listed in
             RFC 2535 and its successors.
-          
    
+          
    
+        
 
    -q
    
-
    
+
    
+          
    
             Quiet mode: Suppresses unnecessary output, including
             progress indication.  Without this option, when
-            dnssec-keygen is run interactively
+            dnssec-keygen is run interactively
             to generate an RSA or DSA key pair, it will print a string
             of symbols to stderr indicating the
             progress of the key generation.  A '.' indicates that a
@@ -225,9 +297,11 @@
             round of the Miller-Rabin primality test; a space
             means that the number has passed all the tests and is
             a satisfactory key.
-          
    
+          
    
+        
 
    -r randomdev
    
-
    
+
    
+          
    
             Specifies the source of randomness.  If the operating
             system does not provide a /dev/random
             or equivalent device, the default source of randomness
@@ -237,9 +311,11 @@
             data to be used instead of the default.  The special value
             keyboard indicates that keyboard
             input should be used.
-          
    
+          
    
+        
 
    -S key
    
-
    
+
    
+          
    
             Create a new key which is an explicit successor to an
             existing key.  The name, algorithm, size, and type of the
             key will be set to match the existing key.  The activation
@@ -247,16 +323,19 @@
             the existing one.  The publication date will be set to the
             activation date minus the prepublication interval, which
             defaults to 30 days.
-          
    
+          
    
+        
 
    -s strength
    
-
    
+
    
+          
    
             Specifies the strength value of the key.  The strength is
             a number between 0 and 15, and currently has no defined
             purpose in DNSSEC.
-          
    
+          
    
+        
 
    -T rrtype
    
 
    
-
    
+          
    
             Specifies the resource record type to use for the key.
             rrtype must be either DNSKEY or KEY.  The
             default is DNSKEY when using a DNSSEC algorithm, but it can be
@@ -268,27 +347,36 @@
             Using any TSIG algorithm (HMAC-* or DH) forces this option
             to KEY.
           
    
-
    
+        
 
    -t type
    
-
    
+
    
+          
    
             Indicates the use of the key.  type must be
             one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF.  The default
             is AUTHCONF.  AUTH refers to the ability to authenticate
             data, and CONF the ability to encrypt data.
-          
    
+          
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    
-
    
-
    
-
    TIMING OPTIONS
    
-
    
+  
    
+
+  
    
+
    TIMING OPTIONS
    
+    
+
+    
    
       Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
       If the argument begins with a '+' or '-', it is interpreted as
       an offset from the present time.  For convenience, if such an offset
@@ -299,44 +387,55 @@
       is computed in seconds.  To explicitly prevent a date from being
       set, use 'none' or 'never'.
     
    
-
    
+
+    
    
 
    -P date/offset
    
-
    
+
    
+          
    
             Sets the date on which a key is to be published to the zone.
             After that date, the key will be included in the zone but will
             not be used to sign it.  If not set, and if the -G option has
             not been used, the default is "now".
-          
    
+          
    
+        
 
    -A date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be activated.  After that
             date, the key will be included in the zone and used to sign
             it.  If not set, and if the -G option has not been used, the
             default is "now".  If set, if and -P is not set, then
             the publication date will be set to the activation date
             minus the prepublication interval.
-          
    
+          
    
+        
 
    -R date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be revoked.  After that
             date, the key will be flagged as revoked.  It will be included
             in the zone and will be used to sign it.
-          
    
+          
    
+        
 
    -I date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be retired.  After that
             date, the key will still be included in the zone, but it
             will not be used to sign it.
-          
    
+          
    
+        
 
    -D date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be deleted.  After that
             date, the key will no longer be included in the zone.  (It
             may remain in the key repository, however.)
-          
    
+          
    
+        
 
    -i interval
    
 
    
-
    
+          
    
             Sets the prepublication interval for a key.  If set, then
             the publication and activation dates must be separated by at least
             this much time.  If the activation date is specified but the
@@ -345,42 +444,51 @@
             the publication date is specified but activation date isn't,
             then activation will be set to this much time after publication.
           
    
-
    
+          
    
             If the key is being created as an explicit successor to another
             key, then the default prepublication interval is 30 days; 
             otherwise it is zero.
           
    
-
    
+          
    
             As with date offsets, if the argument is followed by one of
             the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
             interval is measured in years, months, weeks, days, hours,
             or minutes, respectively.  Without a suffix, the interval is
             measured in seconds.
           
    
-
    
+        
 
    
-
    
-
    
-
    GENERATED KEYS
    
-
    
-      When dnssec-keygen completes
+  
    
+
+
+  
    
+
    GENERATED KEYS
    
+    
+    
    
+      When dnssec-keygen completes
       successfully,
       it prints a string of the form Knnnn.+aaa+iiiii
       to the standard output.  This is an identification string for
       the key it has generated.
     
    
-
      
-
    • nnnn is the key name.
-        
      • 
-
    • aaa is the numeric representation
+    
        
+
      • 
+        
        nnnn is the key name.
+        
        
+      
        • 
+
      • 
+        
        aaa is the numeric representation
           of the
           algorithm.
-        
        • 
-
      • iiiii is the key identifier (or
+        
        
+      
        • 
+
      • 
+        
        iiiii is the key identifier (or
           footprint).
-        
        • 
+        
        
+      
 
      
-
      dnssec-keygen 
+    
      dnssec-keygen 
       creates two files, with names based
       on the printed string.  Knnnn.+aaa+iiiii.key
       contains the public key, and
@@ -388,59 +496,61 @@
       private
       key.
     
      
-
      
+    
      
       The .key file contains a DNS KEY record
       that
       can be inserted into a zone file (directly or with a $INCLUDE
       statement).
     
      
-
      
+    
      
       The .private file contains
       algorithm-specific
       fields.  For obvious security reasons, this file does not have
       general read permission.
     
      
-
      
+    
      
       Both .key and .private
       files are generated for symmetric encryption algorithms such as
       HMAC-MD5, even though the public and private key are equivalent.
     
      
-
    
-
    
-
    EXAMPLE
    
-
    
+  
    
+
+  
    
+
    EXAMPLE
    
+    
+    
    
       To generate a 768-bit DSA key for the domain
       example.com, the following command would be
       issued:
     
    
-
    dnssec-keygen -a DSA -b 768 -n ZONE example.com
+    
    dnssec-keygen -a DSA -b 768 -n ZONE example.com
     
    
-
    
+    
    
       The command would print a string of the form:
     
    
-
    Kexample.com.+003+26160
+    
    Kexample.com.+003+26160
     
    
-
    
-      In this example, dnssec-keygen creates
+    
    
+      In this example, dnssec-keygen creates
       the files Kexample.com.+003+26160.key
       and
       Kexample.com.+003+26160.private.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 2539,
       RFC 2845,
       RFC 4034.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -461,6 +571,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-revoke.html b/doc/arm/man.dnssec-revoke.html
index a1a09875bf..50f9fa1a09 100644
--- a/doc/arm/man.dnssec-revoke.html
+++ b/doc/arm/man.dnssec-revoke.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-revoke
-
-
+
+
 
 
 
@@ -39,54 +38,90 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-revoke — Set the REVOKED bit on a DNSSEC key
    
+
    
+    dnssec-revoke
+     — Set the REVOKED bit on a DNSSEC key
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-revoke  [-hr] [-v level] [-V] [-K directory] [-E engine] [-f] [-R] {keyfile}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-revoke
+    
    
+      dnssec-revoke 
+       [-hr]
+       [-v level]
+       [-V]
+       [-K directory]
+       [-E engine]
+       [-f]
+       [-R]
+       {keyfile}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-revoke
       reads a DNSSEC key file, sets the REVOKED bit on the key as defined
       in RFC 5011, and creates a new pair of key files containing the
       now-revoked key.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -h
    
-
    
+
    
+	  
    
 	    Emit usage message and exit.
-	  
    
+	  
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which the key files are to reside.
-          
    
+          
    
+        
 
    -r
    
-
    
+
    
+	  
    
 	    After writing the new keyset files remove the original keyset
 	    files.
-	  
    
+	  
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             Specifies the cryptographic hardware to use, when applicable.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -94,32 +129,36 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -f
    
-
    
-            Force overwrite: Causes dnssec-revoke to
+
    
+          
    
+            Force overwrite: Causes dnssec-revoke to
             write the new key pair even if a file already exists matching
             the algorithm and key ID of the revoked key.
-          
    
+          
    
+        
 
    -R
    
-
    
+
    
+          
    
 	    Print the key tag of the key with the REVOKE bit set but do
 	    not revoke the key.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 5011.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -140,6 +179,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-settime.html b/doc/arm/man.dnssec-settime.html
index 6dc76f2c65..89ea5a16d7 100644
--- a/doc/arm/man.dnssec-settime.html
+++ b/doc/arm/man.dnssec-settime.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-settime
-
-
+
+
 
 
 
@@ -39,33 +38,61 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-settime — Set the key timing metadata for a DNSSEC key
    
+
    
+    dnssec-settime
+     — Set the key timing metadata for a DNSSEC key
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-settime  [-f] [-K directory] [-L ttl] [-P date/offset] [-A date/offset] [-R date/offset] [-I date/offset] [-D date/offset] [-h] [-V] [-v level] [-E engine] {keyfile}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-settime
+    
    
+      dnssec-settime 
+       [-f]
+       [-K directory]
+       [-L ttl]
+       [-P date/offset]
+       [-A date/offset]
+       [-R date/offset]
+       [-I date/offset]
+       [-D date/offset]
+       [-h]
+       [-V]
+       [-v level]
+       [-E engine]
+       {keyfile}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-settime
       reads a DNSSEC private key file and sets the key timing metadata
       as specified by the -P, -A,
       -R, -I, and -D
       options.  The metadata can then be used by
-      dnssec-signzone or other signing software to
+      dnssec-signzone or other signing software to
       determine when a key is to be published, whether it should be
       used for signing a zone, etc.
     
    
-
    
+    
    
       If none of these options is set on the command line,
-      then dnssec-settime simply prints the key timing
+      then dnssec-settime simply prints the key timing
       metadata already stored in the key.
     
    
-
    
+    
    
       When key metadata fields are changed, both files of a key
       pair (Knnnn.+aaa+iiiii.key and
       Knnnn.+aaa+iiiii.private) are regenerated.
@@ -74,27 +101,35 @@
       file.  The private file's permissions are always set to be
       inaccessible to anyone other than the owner (mode 0600).
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -f
    
-
    
+
    
+	  
    
 	    Force an update of an old-format key with no metadata fields.
-            Without this option, dnssec-settime will
+            Without this option, dnssec-settime will
             fail when attempting to update a legacy key.  With this option,
             the key will be recreated in the new format, but with the
             original key data retained.  The key's creation date will be
             set to the present time.  If no other values are specified, 
             then the key's publication and activation dates will also 
             be set to the present time.
-	  
    
+	  
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Sets the directory in which the key files are to reside.
-          
    
+          
    
+        
 
    -L ttl
    
-
    
+
    
+          
    
             Sets the default TTL to use for this key when it is converted
             into a DNSKEY RR.  If the key is imported into a zone,
             this is the TTL that will be used for it, unless there was
@@ -103,25 +138,32 @@
             is no existing DNSKEY RRset, the TTL will default to the
             SOA TTL. Setting the default TTL to 0
             or none removes it from the key.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+	  
    
 	    Emit usage message and exit.
-	  
    
+	  
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             Specifies the cryptographic hardware to use, when applicable.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -129,12 +171,14 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    
-
    
-
    
-
    TIMING OPTIONS
    
-
    
+  
    
+
+  
    
+
    TIMING OPTIONS
    
+    
+    
    
       Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS.
       If the argument begins with a '+' or '-', it is interpreted as
       an offset from the present time.  For convenience, if such an offset
@@ -144,39 +188,51 @@
       days, hours, or minutes, respectively.  Without a suffix, the offset
       is computed in seconds.  To unset a date, use 'none' or 'never'.
     
    
-
    
+
+    
    
 
    -P date/offset
    
-
    
+
    
+          
    
             Sets the date on which a key is to be published to the zone.
             After that date, the key will be included in the zone but will
             not be used to sign it.
-          
    
+          
    
+        
 
    -A date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be activated.  After that
             date, the key will be included in the zone and used to sign
             it.
-          
    
+          
    
+        
 
    -R date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be revoked.  After that
             date, the key will be flagged as revoked.  It will be included
             in the zone and will be used to sign it.
-          
    
+          
    
+        
 
    -I date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be retired.  After that
             date, the key will still be included in the zone, but it
             will not be used to sign it.
-          
    
+          
    
+        
 
    -D date/offset
    
-
    
+
    
+          
    
             Sets the date on which the key is to be deleted.  After that
             date, the key will no longer be included in the zone.  (It
             may remain in the key repository, however.)
-          
    
+          
    
+        
 
    -S predecessor key
    
-
    
+
    
+          
    
             Select a key for which the key being modified will be an
             explicit successor.  The name, algorithm, size, and type of the
             predecessor key must exactly match those of the key being
@@ -184,10 +240,11 @@
             to the inactivation date of the predecessor.  The publication
             date will be set to the activation date minus the prepublication
             interval, which defaults to 30 days.
-          
    
+          
    
+        
 
    -i interval
    
 
    
-
    
+          
    
             Sets the prepublication interval for a key.  If set, then
             the publication and activation dates must be separated by at least
             this much time.  If the activation date is specified but the
@@ -196,34 +253,40 @@
             the publication date is specified but activation date isn't,
             then activation will be set to this much time after publication.
           
    
-
    
+          
    
             If the key is being set to be an explicit successor to another
             key, then the default prepublication interval is 30 days; 
             otherwise it is zero.
           
    
-
    
+          
    
             As with date offsets, if the argument is followed by one of
             the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the
             interval is measured in years, months, weeks, days, hours,
             or minutes, respectively.  Without a suffix, the interval is
             measured in seconds.
           
    
-
    
+        
 
    
-
    
-
    
-
    PRINTING OPTIONS
    
-
    
-      dnssec-settime can also be used to print the
+  
    
+
+  
    
+
    PRINTING OPTIONS
    
+    
+    
    
+      dnssec-settime can also be used to print the
       timing metadata associated with a key.
     
    
-
    
+
+    
    
 
    -u
    
-
    
+
    
+	  
    
 	    Print times in UNIX epoch format.
-	  
    
+	  
    
+        
 
    -p C/P/A/R/I/D/all
    
-
    
+
    
+	  
    
 	    Print a specific metadata value or set of metadata values.
             The -p option may be followed by one or more
             of the following letters to indicate which value or values to print:
@@ -234,22 +297,25 @@
             I for the inactivation date, or
             D for the deletion date.
             To print all of the metadata, use -p all.
-	  
    
+	  
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
+      
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 5011.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -270,6 +336,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-signzone.html b/doc/arm/man.dnssec-signzone.html
index e4308b32ab..850802d6a1 100644
--- a/doc/arm/man.dnssec-signzone.html
+++ b/doc/arm/man.dnssec-signzone.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-signzone
-
-
+
+
 
 
 
@@ -39,19 +38,74 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-signzone — DNSSEC zone signing tool
    
+
    
+    dnssec-signzone
+     — DNSSEC zone signing tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-signzone  [-a] [-c class] [-d directory] [-D] [-E engine] [-e end-time] [-f output-file] [-g] [-h] [-K directory] [-k key] [-L serial] [-l domain] [-M domain] [-i interval] [-I input-format] [-j jitter] [-N soa-serial-format] [-o origin] [-O output-format] [-P] [-p] [-Q] [-R] [-r randomdev] [-S] [-s start-time] [-T ttl] [-t] [-u] [-v level] [-V] [-X extended end-time] [-x] [-z] [-3 salt] [-H iterations] [-A] {zonefile} [key...]
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-signzone
+    
    
+      dnssec-signzone 
+       [-a]
+       [-c class]
+       [-d directory]
+       [-D]
+       [-E engine]
+       [-e end-time]
+       [-f output-file]
+       [-g]
+       [-h]
+       [-K directory]
+       [-k key]
+       [-L serial]
+       [-l domain]
+       [-M domain]
+       [-i interval]
+       [-I input-format]
+       [-j jitter]
+       [-N soa-serial-format]
+       [-o origin]
+       [-O output-format]
+       [-P]
+       [-p]
+       [-Q]
+       [-R]
+       [-r randomdev]
+       [-S]
+       [-s start-time]
+       [-T ttl]
+       [-t]
+       [-u]
+       [-v level]
+       [-V]
+       [-X extended end-time]
+       [-x]
+       [-z]
+       [-3 salt]
+       [-H iterations]
+       [-A]
+       {zonefile}
+       [key...]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-signzone
       signs a zone.  It generates
       NSEC and RRSIG records and produces a signed version of the
       zone. The security status of delegations from the signed zone
@@ -59,51 +113,64 @@
       determined by the presence or absence of a
       keyset file for each child zone.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -a
    
-
    
+
    
+          
    
             Verify all generated signatures.
-          
    
+          
    
+        
 
    -c class
    
-
    
+
    
+          
    
             Specifies the DNS class of the zone.
-          
    
+          
    
+        
 
    -C
    
-
    
+
    
+          
    
             Compatibility mode: Generate a
             keyset-zonename
             file in addition to
             dsset-zonename
             when signing a zone, for use by older versions of
-            dnssec-signzone.
-          
    
+            dnssec-signzone.
+          
    
+        
 
    -d directory
    
-
    
+
    
+          
    
             Look for dsset- or
             keyset- files in directory.
-          
    
+          
    
+        
 
    -D
    
-
    
+
    
+          
    
 	    Output only those record types automatically managed by
-	    dnssec-signzone, i.e. RRSIG, NSEC,
+	    dnssec-signzone, i.e. RRSIG, NSEC,
 	    NSEC3 and NSEC3PARAM records. If smart signing
 	    (-S) is used, DNSKEY records are also
 	    included. The resulting file can be included in the original
-	    zone file with $INCLUDE. This option
+	    zone file with $INCLUDE. This option
 	    cannot be combined with -O raw, 
             -O map, or serial number updating.
-          
    
+          
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             When applicable, specifies the hardware to use for
             cryptographic operations, such as a secure key store used
             for signing.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -111,30 +178,39 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -g
    
-
    
+
    
+          
    
             Generate DS records for child zones from
             dsset- or keyset-
             file.  Existing DS records will be removed.
-          
    
+          
    
+        
 
    -K directory
    
-
    
+
    
+          
    
             Key repository: Specify a directory to search for DNSSEC keys.
             If not specified, defaults to the current directory.
-          
    
+          
    
+        
 
    -k key
    
-
    
+
    
+          
    
             Treat specified key as a key signing key ignoring any
             key flags.  This option may be specified multiple times.
-          
    
+          
    
+        
 
    -l domain
    
-
    
+
    
+          
    
             Generate a DLV set in addition to the key (DNSKEY) and DS sets.
             The domain is appended to the name of the records.
-          
    
+          
    
+        
 
    -M maxttl
    
-
    
+
    
+          
    
             Sets the maximum TTL for the signed zone.
             Any TTL higher than maxttl in the
             input zone will be reduced to maxttl
@@ -147,9 +223,11 @@
             max-zone-ttl in named.conf.
             (Note: This option is incompatible with -D,
             because it modifies non-DNSSEC data in the output zone.)
-          
    
+          
    
+        
 
    -s start-time
    
-
    
+
    
+          
    
             Specify the date and time when the generated RRSIG records
             become valid.  This can be either an absolute or relative
             time.  An absolute start time is indicated by a number
@@ -158,9 +236,11 @@
             indicated by +N, which is N seconds from the current time.
             If no start-time is specified, the current
             time minus 1 hour (to allow for clock skew) is used.
-          
    
+          
    
+        
 
    -e end-time
    
-
    
+
    
+          
    
             Specify the date and time when the generated RRSIG records
             expire.  As with start-time, an absolute
             time is indicated in YYYYMMDDHHMMSS notation.  A time relative
@@ -170,10 +250,11 @@
             specified, 30 days from the start time is used as a default.
             end-time must be later than
             start-time.
-          
    
+          
    
+        
 
    -X extended end-time
    
 
    
-
    
+          
    
             Specify the date and time when the generated RRSIG records
             for the DNSKEY RRset will expire.  This is to be used in cases
             when the DNSKEY signatures need to persist longer than
@@ -181,7 +262,7 @@
             of the KSK is kept offline and the KSK signature is to be
             refreshed manually.
           
    
-
    
+          
    
             As with start-time, an absolute
             time is indicated in YYYYMMDDHHMMSS notation.  A time relative
             to the start time is indicated with +N, which is N seconds from
@@ -192,28 +273,34 @@
             30 days from the start time.) extended end-time
             must be later than start-time.
           
    
-
    
+        
 
    -f output-file
    
-
    
+
    
+          
    
             The name of the output file containing the signed zone.  The
             default is to append .signed to
             the input filename.  If output-file is
             set to "-", then the signed zone is
             written to the standard output, with a default output
             format of "full".
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Prints a short summary of the options and arguments to
-            dnssec-signzone.
-          
    
+            dnssec-signzone.
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    -i interval
    
 
    
-
    
+          
    
             When a previously-signed zone is passed as input, records
             may be resigned.  The interval option
             specifies the cycle interval as an offset from the current
@@ -221,32 +308,34 @@
             cycle interval, it is retained.  Otherwise, it is considered
             to be expiring soon, and it will be replaced.
           
    
-
    
+          
    
             The default cycle interval is one quarter of the difference
             between the signature end and start times.  So if neither
             end-time or start-time
-            are specified, dnssec-signzone
+            are specified, dnssec-signzone
             generates
             signatures that are valid for 30 days, with a cycle
             interval of 7.5 days.  Therefore, if any existing RRSIG records
             are due to expire in less than 7.5 days, they would be
             replaced.
           
    
-
    
+        
 
    -I input-format
    
-
    
+
    
+          
    
             The format of the input zone file.
-	    Possible formats are "text" (default),
-	    "raw", and "map".
+	    Possible formats are "text" (default),
+	    "raw", and "map".
 	    This option is primarily intended to be used for dynamic
             signed zones so that the dumped zone file in a non-text
             format containing updates can be signed directly.
 	    The use of this option does not make much sense for
 	    non-dynamic zones.
-          
    
+          
    
+        
 
    -j jitter
    
 
    
-
    
+          
    
             When signing a zone with a fixed signature lifetime, all
             RRSIG records issued at the time of signing expires
             simultaneously.  If the zone is incrementally signed, i.e.
@@ -257,121 +346,142 @@
             expire time, thus spreading incremental signature
             regeneration over time.
           
    
-
    
+          
    
             Signature lifetime jitter also to some extent benefits
             validators and servers by spreading out cache expiration,
             i.e. if large numbers of RRSIGs don't expire at the same time
             from all caches there will be less congestion than if all
             validators need to refetch at mostly the same time.
           
    
-
    
+        
 
    -L serial
    
-
    
+
    
+          
    
             When writing a signed zone to "raw" or "map" format, set the
             "source serial" value in the header to the specified serial
             number.  (This is expected to be used primarily for testing
             purposes.)
-          
    
+          
    
+        
 
    -n ncpus
    
-
    
+
    
+          
    
             Specifies the number of threads to use.  By default, one
             thread is started for each detected CPU.
-          
    
+          
    
+        
 
    -N soa-serial-format
    
 
    
-
    
+          
    
             The SOA serial number format of the signed zone.
-	    Possible formats are "keep" (default),
-            "increment", "unixtime",
-            and "date".
+	    Possible formats are "keep" (default),
+            "increment", "unixtime",
+            and "date".
           
    
-
    
-
    "keep"
    
-
    Do not modify the SOA serial number.
    
-
    "increment"
    
-
    Increment the SOA serial number using RFC 1982
-                      arithmetics.
    
-
    "unixtime"
    
-
    Set the SOA serial number to the number of seconds
-	        since epoch.
    
-
    "date"
    
-
    Set the SOA serial number to today's date in
-                YYYYMMDDNN format.
    
+
+          
    
+
    "keep"
    
+
    
+                
    Do not modify the SOA serial number.
    
+	      
    
+
    "increment"
    
+
    
+                
    Increment the SOA serial number using RFC 1982
+                      arithmetics.
    
+	      
    
+
    "unixtime"
    
+
    
+                
    Set the SOA serial number to the number of seconds
+	        since epoch.
    
+	      
    
+
    "date"
    
+
    
+                
    Set the SOA serial number to today's date in
+                YYYYMMDDNN format.
    
+	      
    
 
    
-
    
+
+        
 
    -o origin
    
-
    
+
    
+          
    
             The zone origin.  If not specified, the name of the zone file
             is assumed to be the origin.
-          
    
+          
    
+        
 
    -O output-format
    
-
    
+
    
+          
    
             The format of the output file containing the signed zone.
-	    Possible formats are "text" (default),
+	    Possible formats are "text" (default),
             which is the standard textual representation of the zone;
-	    "full", which is text output in a
+	    "full", which is text output in a
             format suitable for processing by external scripts;
-            and "map", "raw",
-            and "raw=N", which store the zone in
-            binary formats for rapid loading by named.
-            "raw=N" specifies the format version of
+            and "map", "raw",
+            and "raw=N", which store the zone in
+            binary formats for rapid loading by named.
+            "raw=N" specifies the format version of
             the raw zone file: if N is 0, the raw file can be read by
-            any version of named; if N is 1, the file
+            any version of named; if N is 1, the file
             can be read by release 9.9.0 or higher; the default is 1.
-          
    
+          
    
+        
 
    -p
    
-
    
+
    
+          
    
             Use pseudo-random data when signing the zone.  This is faster,
             but less secure, than using real random data.  This option
             may be useful when signing large zones or when the entropy
             source is limited.
-          
    
+          
    
+        
 
    -P
    
 
    
-
    
+          
    
 	    Disable post sign verification tests.
           
    
-
    
+          
    
 	    The post sign verification test ensures that for each algorithm
 	    in use there is at least one non revoked self signed KSK key,
 	    that all revoked KSK keys are self signed, and that all records
 	    in the zone are signed by the algorithm.
 	    This option skips these tests.
           
    
-
    
+        
 
    -Q
    
 
    
-
    
+          
    
 	    Remove signatures from keys that are no longer active.
           
    
-
    
+          
    
             Normally, when a previously-signed zone is passed as input
             to the signer, and a DNSKEY record has been removed and
             replaced with a new one, signatures from the old key 
             that are still within their validity period are retained.
 	    This allows the zone to continue to validate with cached
 	    copies of the old DNSKEY RRset.  The -Q
-            forces dnssec-signzone to remove
+            forces dnssec-signzone to remove
             signatures from keys that are no longer active. This
             enables ZSK rollover using the procedure described in
             RFC 4641, section 4.2.1.1 ("Pre-Publish Key Rollover").
           
    
-
    
+        
 
    -R
    
 
    
-
    
+          
    
 	    Remove signatures from keys that are no longer published.
           
    
-
    
+          
    
             This option is similar to -Q, except it
-            forces dnssec-signzone to signatures from
+            forces dnssec-signzone to signatures from
             keys that are no longer published. This enables ZSK rollover
             using the procedure described in RFC 4641, section 4.2.1.2
             ("Double Signature Zone Signing Key Rollover").
           
    
-
    
+        
 
    -r randomdev
    
-
    
+
    
+          
    
             Specifies the source of randomness.  If the operating
             system does not provide a /dev/random
             or equivalent device, the default source of randomness
@@ -381,53 +491,65 @@
             data to be used instead of the default.  The special value
             keyboard indicates that keyboard
             input should be used.
-          
    
+          
    
+        
 
    -S
    
 
    
-
    
-            Smart signing: Instructs dnssec-signzone to
+          
    
+            Smart signing: Instructs dnssec-signzone to
             search the key repository for keys that match the zone being
             signed, and to include them in the zone if appropriate.
           
    
-
    
+          
    
             When a key is found, its timing metadata is examined to
             determine how it should be used, according to the following
             rules.  Each successive rule takes priority over the prior
             ones:
           
    
-
    
+          
    
 
    
-
    
+
    
+                
    
                   If no timing metadata has been set for the key, the key is
                   published in the zone and used to sign the zone.
-                
    
+                
    
+	      
    
 
    
-
    
+
    
+                
    
                   If the key's publication date is set and is in the past, the
                   key is published in the zone.
-                
    
+                
    
+	      
 
    
-
    
+
    
+                
    
                   If the key's activation date is set and in the past, the
                   key is published (regardless of publication date) and
                   used to sign the zone.  
-                
    
+                
    
+	      
 
    
-
    
+
    
+                
    
                   If the key's revocation date is set and in the past, and the
                   key is published, then the key is revoked, and the revoked key
                   is used to sign the zone.
-                
    
+                
    
+	      
 
    
-
    
+
    
+                
    
                   If either of the key's unpublication or deletion dates are set
                   and in the past, the key is NOT published or used to sign the
                   zone, regardless of any other metadata.
-                
    
+                
    
+	      
 
    
-
+        
 
    -T ttl
    
-
    
+
    
+          
    
             Specifies a TTL to be used for new DNSKEY records imported
             into the zone from the key repository.  If not
             specified, the default is the TTL value from the zone's SOA
@@ -439,100 +561,121 @@
             them, or if any of the imported DNSKEY records had a default
             TTL value.  In the event of a a conflict between TTL values in
             imported keys, the shortest one is used.
-          
    
+          
    
+        
 
    -t
    
-
    
+
    
+          
    
             Print statistics at completion.
-          
    
+          
    
+        
 
    -u
    
-
    
+
    
+          
    
             Update NSEC/NSEC3 chain when re-signing a previously signed
             zone.  With this option, a zone signed with NSEC can be
             switched to NSEC3, or a zone signed with NSEC3 can
             be switch to NSEC or to NSEC3 with different parameters.
-            Without this option, dnssec-signzone will
+            Without this option, dnssec-signzone will
             retain the existing chain when re-signing.
-          
    
+          
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -x
    
-
    
+
    
+          
    
             Only sign the DNSKEY RRset with key-signing keys, and omit
             signatures from zone-signing keys.  (This is similar to the
-            dnssec-dnskey-kskonly yes; zone option in
-            named.)
-          
    
+            dnssec-dnskey-kskonly yes; zone option in
+            named.)
+          
    
+        
 
    -z
    
-
    
+
    
+          
    
             Ignore KSK flag on key when determining what to sign.  This
             causes KSK-flagged keys to sign all records, not just the
             DNSKEY RRset.  (This is similar to the
-            update-check-ksk no; zone option in
-            named.)
-          
    
+            update-check-ksk no; zone option in
+            named.)
+          
    
+        
 
    -3 salt
    
-
    
+
    
+          
    
             Generate an NSEC3 chain with the given hex encoded salt.
 	    A dash (salt) can
 	    be used to indicate that no salt is to be used when generating		    the NSEC3 chain.
-          
    
+          
    
+        
 
    -H iterations
    
-
    
+
    
+          
    
 	    When generating an NSEC3 chain, use this many iterations.  The
 	    default is 10.
-          
    
+          
    
+        
 
    -A
    
 
    
-
    
+          
    
 	    When generating an NSEC3 chain set the OPTOUT flag on all
 	    NSEC3 records and do not generate NSEC3 records for insecure
 	    delegations.
           
    
-
    
+          
    
 	    Using this option twice (i.e., -AA)
 	    turns the OPTOUT flag off for all records.  This is useful
 	    when using the -u option to modify an NSEC3
 	    chain which previously had OPTOUT set.
           
    
-
    
+        
 
    zonefile
    
-
    
+
    
+          
    
             The file containing the zone to be signed.
-          
    
+          
    
+        
 
    key
    
-
    
+
    
+          
    
 	    Specify which keys should be used to sign the zone.  If
 	    no keys are specified, then the zone will be examined
 	    for DNSKEY records at the zone apex.  If these are found and
 	    there are matching private keys, in the current directory,
 	    then these will be used for signing.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    EXAMPLE
    
-
    
+  
    
+
+  
    
+
    EXAMPLE
    
+    
+    
    
       The following command signs the example.com
-      zone with the DSA key generated by dnssec-keygen
-      (Kexample.com.+003+17247).  Because the -S option
+      zone with the DSA key generated by dnssec-keygen
+      (Kexample.com.+003+17247).  Because the -S option
       is not being used, the zone's keys must be in the master file
       (db.example.com).  This invocation looks
       for dsset files, in the current directory,
-      so that DS records can be imported from them (-g).
+      so that DS records can be imported from them (-g).
     
    
 
    % dnssec-signzone -g -o example.com db.example.com \
 Kexample.com.+003+17247
 db.example.com.signed
 %
    
-
    
-      In the above example, dnssec-signzone creates
+    
    
+      In the above example, dnssec-signzone creates
       the file db.example.com.signed.  This
       file should be referenced in a zone statement in a
       named.conf file.
     
    
-
    
+    
    
       This example re-signs a previously signed zone with default parameters.
       The private keys are assumed to be in the current directory.
     
    
@@ -540,19 +683,19 @@ db.example.com.signed
 % dnssec-signzone -o example.com db.example.com
 db.example.com.signed
 %
    
-
-
    
-
    SEE ALSO
    
-
    dnssec-keygen(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        dnssec-keygen(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 4033, RFC 4641.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
+
 
 
    
 
    
@@ -573,6 +716,6 @@ db.example.com.signed
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnssec-verify.html b/doc/arm/man.dnssec-verify.html
index 302b44fcb6..a9e7472863 100644
--- a/doc/arm/man.dnssec-verify.html
+++ b/doc/arm/man.dnssec-verify.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnssec-verify
-
-
+
+
 
 
-
+
 
 
 
    
@@ -33,43 +32,72 @@
 
 Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnssec-verify — DNSSEC zone verification tool
    
+
    
+    dnssec-verify
+     — DNSSEC zone verification tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    dnssec-verify  [-c class] [-E engine] [-I input-format] [-o origin] [-v level] [-V] [-x] [-z] {zonefile}
    
-
    
-
    
-
    DESCRIPTION
    
-
    dnssec-verify
+    
    
+      dnssec-verify 
+       [-c class]
+       [-E engine]
+       [-I input-format]
+       [-o origin]
+       [-v level]
+       [-V]
+       [-x]
+       [-z]
+       {zonefile}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    dnssec-verify
       verifies that a zone is fully signed for each algorithm found
       in the DNSKEY RRset for the zone, and that the NSEC / NSEC3
       chains are complete.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -c class
    
-
    
+
    
+          
    
             Specifies the DNS class of the zone.
-          
    
+          
    
+        
 
    -E engine
    
 
    
-
    
+          
    
             Specifies the cryptographic hardware to use, when applicable.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -77,43 +105,53 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -I input-format
    
-
    
+
    
+          
    
             The format of the input zone file.
-	    Possible formats are "text" (default)
-	    and "raw".
+	    Possible formats are "text" (default)
+	    and "raw".
 	    This option is primarily intended to be used for dynamic
             signed zones so that the dumped zone file in a non-text
             format containing updates can be verified independently.
 	    The use of this option does not make much sense for
 	    non-dynamic zones.
-          
    
+          
    
+        
 
    -o origin
    
-
    
+
    
+          
    
             The zone origin.  If not specified, the name of the zone file
             is assumed to be the origin.
-          
    
+          
    
+        
 
    -v level
    
-
    
+
    
+          
    
             Sets the debugging level.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+	  
    
 	    Prints version information.
-	  
    
+	  
    
+        
 
    -x
    
-
    
+
    
+          
    
             Only verify that the DNSKEY RRset is signed with key-signing
             keys.  Without this flag, it is assumed that the DNSKEY RRset
             will be signed by all active keys.  When this flag is set,
             it will not be an error if the DNSKEY RRset is not signed
             by zone-signing keys.  This corresponds to the -x
-            option in dnssec-signzone.
-          
    
+            option in dnssec-signzone.
+          
    
+        
 
    -z
    
 
    
-
    
+	  
    
 	    Ignore the KSK flag on the keys when determining whether
             the zone if correctly signed.  Without this flag it is
 	    assumed that there will be a non-revoked, self-signed
@@ -121,35 +159,37 @@
 	    that RRsets other than DNSKEY RRset will be signed with
             a different DNSKEY without the KSK flag set.
 	  
    
-
    
+	  
    
 	    With this flag set, we only require that for each algorithm,
             there will be at least one non-revoked, self-signed DNSKEY,
             regardless of the KSK flag state, and that other RRsets
 	    will be signed by a non-revoked key for the same algorithm
             that includes the self-signed key; the same key may be used
             for both purposes.  This corresponds to the -z
-            option in dnssec-signzone.
+            option in dnssec-signzone.
 	  
    
-
    
+	
 
    zonefile
    
-
    
+
    
+          
    
             The file containing the zone to be signed.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
-      dnssec-signzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+      
+        dnssec-signzone(8)
+      ,
       BIND 9 Administrator Reference Manual,
       RFC 4033.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -158,18 +198,18 @@
 
 Prev 
 Up
- Next
+ Next
 
 
 
 
 dnssec-signzone 
 Home
- named-checkconf
+ lwresd
 
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.dnstap-read.html b/doc/arm/man.dnstap-read.html
index 53e228ebeb..6977185f79 100644
--- a/doc/arm/man.dnstap-read.html
+++ b/doc/arm/man.dnstap-read.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 dnstap-read
-
-
+
+
 
 
 
@@ -39,60 +38,90 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    dnstap-read — print dnstap data in human-readable form
    
-
    
-
    
-
    Synopsis
    
-
    dnstap-read  [-m] [-p] [-y] {file}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      dnstap-read
-      reads dnstap data from a specified file
+    dnstap-read
+     — print dnstap data in human-readable form
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      dnstap-read 
+       [-m]
+       [-p]
+       [-y]
+       {file}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      dnstap-read
+      reads dnstap data from a specified file
       and prints it in a human-readable format.  By default,
-      dnstap data is printed in a short summary
+      dnstap data is printed in a short summary
       format, but if the -y option is specified,
       then a longer and more detailed YAML format is used instead.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -m
    
-
    
+
    
+          
    
             Trace memory allocations; used for debugging memory leaks.
-          
    
+          
    
+        
 
    -p
    
-
    
-            After printing the dnstap data, print
+
    
+          
    
+            After printing the dnstap data, print
             the text form of the DNS message that was encapsulated in the
-            dnstap frame.
-          
    
+            dnstap frame.
+          
    
+        
 
    -y
    
-
    
-            Print dnstap data in a detailed YAML
+
    
+          
    
+            Print dnstap data in a detailed YAML
             format. Implies -p.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
-      named(8),
-      nsupdate(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+      
+        named(8)
+      ,
+      
+        nsupdate(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -113,6 +142,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.genrandom.html b/doc/arm/man.genrandom.html
index f1c4dd1a2e..b41621edb4 100644
--- a/doc/arm/man.genrandom.html
+++ b/doc/arm/man.genrandom.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 genrandom
-
-
+
+
 
 
 
@@ -39,55 +38,83 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    genrandom — generate a file containing random data
    
-
    
-
    
-
    Synopsis
    
-
    genrandom  [-n number] {size} {filename}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      genrandom
+    genrandom
+     — generate a file containing random data
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      genrandom 
+       [-n number]
+       {size}
+       {filename}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      genrandom
       generates a file or a set of files containing a specified quantity
       of pseudo-random data, which can be used as a source of entropy for
       other commands on systems with no random device.
     
    
-
    
-
    
-
    ARGUMENTS
    
-
    
+  
    
+
+  
    
+
    ARGUMENTS
    
+    
+    
    
 
    -n number
    
-
    
+
    
+          
    
             In place of generating one file, generates number
             (from 2 to 9) files, appending number to the name.
-          
    
+          
    
+        
 
    size
    
-
    
+
    
+          
    
             The size of the file, in kilobytes, to generate.
-          
    
+          
    
+        
 
    filename
    
-
    
+
    
+          
    
             The file name into which random data should be written.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
-      rand(3),
-      arc4random(3)
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+      
+        rand(3)
+      ,
+      
+        arc4random(3)
+      
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -108,6 +135,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.host.html b/doc/arm/man.host.html
index f12853dc40..f4bf100518 100644
--- a/doc/arm/man.host.html
+++ b/doc/arm/man.host.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 host
-
-
+
+
 
 
 
@@ -39,58 +38,92 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    host — DNS lookup utility
    
+
    
+    host
+     — DNS lookup utility
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    host  [-aCdlnrsTwv] [-c class] [-N ndots] [-R number] [-t type] [-W wait] [-m flag] [-4] [-6] [-v] [-V] {name} [server]
    
-
    
-
    
-
    DESCRIPTION
    
-
    host
+    
    
+      host 
+       [-aCdlnrsTwv]
+       [-c class]
+       [-N ndots]
+       [-R number]
+       [-t type]
+       [-W wait]
+       [-m flag]
+       [-4]
+       [-6]
+       [-v]
+       [-V]
+       {name}
+       [server]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+
+    
    host
       is a simple utility for performing DNS lookups.
       It is normally used to convert names to IP addresses and vice versa.
       When no arguments or options are given,
-      host
+      host
       prints a short summary of its command line arguments and options.
     
    
-
    name is the domain name that is to be
+
+    
    name is the domain name that is to be
       looked
       up.  It can also be a dotted-decimal IPv4 address or a colon-delimited
-      IPv6 address, in which case host will by
+      IPv6 address, in which case host will by
       default
       perform a reverse lookup for that address.
       server is an optional argument which
       is either
-      the name or IP address of the name server that host
+      the name or IP address of the name server that host
       should query instead of the server or servers listed in
       /etc/resolv.conf.
     
    
-
    
+
+    
    
       The -a (all) option is equivalent to setting the
-      -v option and asking host to make
+      -v option and asking host to make
       a query of type ANY.
     
    
-
    
-      When the -C option is used, host
+
+    
    
+      When the -C option is used, host
       will attempt to display the SOA records for zone
       name from all the listed
       authoritative name
       servers for that zone.  The list of name servers is defined by the NS
       records that are found for the zone.
     
    
-
    
+
+    
    
       The -c option instructs to make a DNS query of class
       class.  This can be used to lookup
       Hesiod or
       Chaosnet class resource records.  The default class is IN (Internet).
     
    
-
    
-      Verbose output is generated by host when
+
+    
    
+      Verbose output is generated by host when
       the
       -d or -v option is used.  The two
       options are equivalent.  They have been provided for backwards
@@ -100,21 +133,24 @@
       debug option in
       /etc/resolv.conf.
     
    
-
    
+
+    
    
       List mode is selected by the -l option.  This makes
-      host perform a zone transfer for zone
+      host perform a zone transfer for zone
       name.  Transfer the zone printing out
       the NS, PTR
       and address records (A/AAAA).  If combined with -a
       all records will be printed.
     
    
-
    
+
+    
    
       The -i
       option specifies that reverse lookups of IPv6 addresses should
       use the IP6.INT domain as defined in RFC1886.
       The default is to use IP6.ARPA.
     
    
-
    
+
+    
    
       The -N option sets the number of dots that have to be
       in name for it to be considered
       absolute.  The
@@ -126,11 +162,12 @@
       or domain directive in
       /etc/resolv.conf.
     
    
-
    
+
+    
    
       The number of UDP retries for a lookup can be changed with the
       -R option.  number
       indicates
-      how many times host will repeat a query
+      how many times host will repeat a query
       that does
       not get answered.  If
       number is negative or zero, the
@@ -139,105 +176,124 @@
       the value of the attempts option in
       /etc/resolv.conf, if set.
     
    
-
    
+
+    
    
       Non-recursive queries can be made via the -r option.
       Setting this option clears the RD — recursion
-      desired — bit in the query which host makes.
+      desired — bit in the query which host makes.
       This should mean that the name server receiving the query will not
       attempt to resolve name.  The
-      -r option enables host
+      -r option enables host
       to mimic
       the behavior of a name server by making non-recursive queries and
       expecting to receive answers to those queries that are usually
       referrals to other name servers.
     
    
-
    
-      By default, host uses UDP when making
+
+    
    
+      By default, host uses UDP when making
       queries.  The
       -T option makes it use a TCP connection when querying
       the name server.  TCP will be automatically selected for queries that
       require it, such as zone transfer (AXFR) requests.
     
    
-
    
-      The -4 option forces host to only
+
+    
    
+      The -4 option forces host to only
       use IPv4 query transport.  The -6 option forces
-      host to only use IPv6 query transport.
+      host to only use IPv6 query transport.
     
    
-
    
+
+    
    
       The -t option is used to select the query type.
       type can be any recognized query
       type: CNAME,
       NS, SOA, SIG, KEY, AXFR, etc.  When no query type is specified,
-      host automatically selects an appropriate
+      host automatically selects an appropriate
       query
       type.  By default, it looks for A, AAAA, and MX records, but if the
       -C option was given, queries will be made for SOA
       records, and if name is a
       dotted-decimal IPv4
-      address or colon-delimited IPv6 address, host will
+      address or colon-delimited IPv6 address, host will
       query for PTR records.  If a query type of IXFR is chosen the starting
       serial number can be specified by appending an equal followed by the
       starting serial number (e.g. -t IXFR=12345678).
     
    
-
    
+
+    
    
       The time to wait for a reply can be controlled through the
       -W and -w options.  The
-      -W option makes host
+      -W option makes host
       wait for
       wait seconds.  If wait
       is less than one, the wait interval is set to one second.  When the
-      -w option is used, host
+      -w option is used, host
       will
       effectively wait forever for a reply.  The time to wait for a response
       will be set to the number of seconds given by the hardware's maximum
-      value for an integer quantity.  By default, host
+      value for an integer quantity.  By default, host
       will wait for 5 seconds for UDP responses and 10 seconds for TCP
       connections.  These defaults can be overridden by the
       timeout option in
       /etc/resolv.conf.
     
    
-
    
-      The -s option tells host 
+
+    
    
+      The -s option tells host 
       not to send the query to the next nameserver
       if any server responds with a SERVFAIL response, which is the
       reverse of normal stub resolver behavior.
     
    
-
    
+
+    
    
       The -m can be used to set the memory usage debugging
       flags
       record, usage and
       trace.
     
    
-
    
-      The -V option causes host
+
+    
    
+      The -V option causes host
       to print the version number and exit.
     
    
-
    
-
    
-
    IDN SUPPORT
    
-
    
-      If host has been built with IDN (internationalized
+  
    
+
+  
    
+
    IDN SUPPORT
    
+    
+    
    
+      If host has been built with IDN (internationalized
       domain name) support, it can accept and display non-ASCII domain names. 
-      host appropriately converts character encoding of
+      host appropriately converts character encoding of
       domain name before sending a request to DNS server or displaying a
       reply from the server.
       If you'd like to turn off the IDN support for some reason, defines
       the IDN_DISABLE environment variable.
       The IDN support is disabled if the variable is set when
-      host runs.
+      host runs.
     
    
-
    
-
    
-
    FILES
    
-
    /etc/resolv.conf
+  
    
+
+  
    
+
    FILES
    
+
+    
    /etc/resolv.conf
     
    
-
    
-
    
-
    SEE ALSO
    
-
    dig(1),
-      named(8).
+  
    
+
+  
    
+
    SEE ALSO
    
+
+    
    
+        dig(1)
+      ,
+      
+        named(8)
+      .
     
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -256,6 +312,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.isc-hmac-fixup.html b/doc/arm/man.isc-hmac-fixup.html
index a615dcc4dd..ef7a35db67 100644
--- a/doc/arm/man.isc-hmac-fixup.html
+++ b/doc/arm/man.isc-hmac-fixup.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 isc-hmac-fixup
-
-
+
+
 
 
-
+
 
 
 
    
@@ -33,25 +32,42 @@
 
 Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    isc-hmac-fixup — fixes HMAC keys generated by older versions of BIND
    
-
    
-
    
-
    Synopsis
    
-
    isc-hmac-fixup  {algorithm} {secret}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
+    isc-hmac-fixup
+     — fixes HMAC keys generated by older versions of BIND
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      isc-hmac-fixup 
+       {algorithm}
+       {secret}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
       Versions of BIND 9 up to and including BIND 9.6 had a bug causing
       HMAC-SHA* TSIG keys which were longer than the digest length of the
       hash algorithm (i.e., SHA1 keys longer than 160 bits, SHA256 keys
@@ -59,14 +75,14 @@
       message authentication code that was incompatible with other DNS
       implementations.
     
    
-
    
+    
    
       This bug has been fixed in BIND 9.7.  However, the fix may
       cause incompatibility between older and newer versions of
-      BIND, when using long keys.  isc-hmac-fixup
+      BIND, when using long keys.  isc-hmac-fixup
       modifies those keys to restore compatibility.
     
    
-
    
-      To modify a key, run isc-hmac-fixup and
+    
    
+      To modify a key, run isc-hmac-fixup and
       specify the key's algorithm and secret on the command line.  If the
       secret is longer than the digest length of the algorithm (64 bytes
       for SHA1 through SHA256, or 128 bytes for SHA384 and SHA512), then a
@@ -74,30 +90,30 @@
       secret.  (If the secret did not require conversion, then it will be
       printed without modification.)
     
    
-
    
-
    
-
    SECURITY CONSIDERATIONS
    
-
    
-      Secrets that have been converted by isc-hmac-fixup
+  
    
+
+  
    
+
    SECURITY CONSIDERATIONS
    
+    
+    
    
+      Secrets that have been converted by isc-hmac-fixup
       are shortened, but as this is how the HMAC protocol works in
       operation anyway, it does not affect security.  RFC 2104 notes,
       "Keys longer than [the digest length] are acceptable but the
       extra length would not significantly increase the function
       strength."
     
    
-
    
-
    
-
    SEE ALSO
    
-
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
       BIND 9 Administrator Reference Manual,
       RFC 2104.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -106,18 +122,18 @@
 
 Prev 
 Up
- Next
+ Next
 
 
 
 
 genrandom 
 Home
- named-journalprint
+ nsec3hash
 
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.lwresd.html b/doc/arm/man.lwresd.html
index 8877b038b9..6582762d0a 100644
--- a/doc/arm/man.lwresd.html
+++ b/doc/arm/man.lwresd.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 lwresd
-
-
+
+
 
-
-
+
+
 
 
 
    
@@ -31,112 +30,165 @@
 lwresd
 
 
-Prev 
+Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    lwresd — lightweight resolver daemon
    
+
    
+    lwresd
+     — lightweight resolver daemon
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    lwresd  [-c config-file] [-C config-file] [-d debug-level] [-f] [-g] [-i pid-file] [-m flag] [-n #cpus] [-P port] [-p port] [-s] [-t directory] [-u user] [-v] [-4] [-6]
    
-
    
-
    
-
    DESCRIPTION
    
-
    lwresd
+    
    
+      lwresd 
+       [-c config-file]
+       [-C config-file]
+       [-d debug-level]
+       [-f]
+       [-g]
+       [-i pid-file]
+       [-m flag]
+       [-n #cpus]
+       [-P port]
+       [-p port]
+       [-s]
+       [-t directory]
+       [-u user]
+       [-v]
+       [-4]
+       [-6]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+
+    
    lwresd
       is the daemon providing name lookup
       services to clients that use the BIND 9 lightweight resolver
       library.  It is essentially a stripped-down, caching-only name
       server that answers queries using the BIND 9 lightweight
       resolver protocol rather than the DNS protocol.
     
    
-
    lwresd 
+
+    
    lwresd 
       listens for resolver queries on a
       UDP port on the IPv4 loopback interface, 127.0.0.1.  This
-      means that lwresd can only be used by
+      means that lwresd can only be used by
       processes running on the local machine.  By default, UDP port
       number 921 is used for lightweight resolver requests and
       responses.
     
    
-
    
+    
    
       Incoming lightweight resolver requests are decoded by the
       server which then resolves them using the DNS protocol.  When
-      the DNS lookup completes, lwresd encodes
+      the DNS lookup completes, lwresd encodes
       the answers in the lightweight resolver format and returns
       them to the client that made the request.
     
    
-
    
+    
    
       If /etc/resolv.conf contains any
-      nameserver entries, lwresd
+      nameserver entries, lwresd
       sends recursive DNS queries to those servers.  This is similar
       to the use of forwarders in a caching name server.  If no
       nameserver entries are present, or if
-      forwarding fails, lwresd resolves the
+      forwarding fails, lwresd resolves the
       queries autonomously starting at the root name servers, using
       a built-in list of root server hints.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -4
    
-
    
+
    
+          
    
             Use IPv4 only even if the host machine is capable of IPv6.
             -4 and -6 are mutually
             exclusive.
-          
    
+          
    
+        
 
    -6
    
-
    
+
    
+          
    
             Use IPv6 only even if the host machine is capable of IPv4.
             -4 and -6 are mutually
             exclusive.
-          
    
+          
    
+        
 
    -c config-file
    
-
    
+
    
+          
    
             Use config-file as the
             configuration file instead of the default,
             /etc/lwresd.conf.
 	    
 	    -c can not be used with -C.
-          
    
+          
    
+        
 
    -C config-file
    
-
    
+
    
+          
    
             Use config-file as the
             configuration file instead of the default,
             /etc/resolv.conf.
 	    -C can not be used with -c.
-          
    
+          
    
+        
 
    -d debug-level
    
-
    
+
    
+          
    
             Set the daemon's debug level to debug-level.
-            Debugging traces from lwresd become
+            Debugging traces from lwresd become
             		more verbose as the debug level increases.
-          
    
+          
    
+        
 
    -f
    
-
    
+
    
+          
    
             Run the server in the foreground (i.e. do not daemonize).
-          
    
+          
    
+        
 
    -g
    
-
    
+
    
+          
    
             Run the server in the foreground and force all logging
             to stderr.
-          
    
+          
    
+        
 
    -i pid-file
    
-
    
+
    
+          
    
             Use pid-file as the
             PID file instead of the default,
             /var/run/lwresd/lwresd.pid.
-          
    
+          
    
+        
 
    -m flag
    
-
    
+
    
+          
    
             Turn on memory usage debugging flags.  Possible flags are
             usage,
             trace,
@@ -145,54 +197,61 @@
             mctx.  
             These correspond to the ISC_MEM_DEBUGXXXX flags described in
             <isc/mem.h>.
-          
    
+          
    
+        
 
    -n #cpus
    
-
    
+
    
+          
    
             Create #cpus worker threads
             to take advantage of multiple CPUs.  If not specified,
-            lwresd will try to determine the
+            lwresd will try to determine the
             number of CPUs present and create one thread per CPU.
             If it is unable to determine the number of CPUs, a
             single worker thread will be created.
-          
    
+          
    
+        
 
    -P port
    
-
    
+
    
+          
    
             Listen for lightweight resolver queries on port
             port.  If
             		not specified, the default is port 921.
-          
    
+          
    
+        
 
    -p port
    
-
    
+
    
+          
    
             Send DNS lookups to port port.  If not
             specified, the default is port 53.  This provides a
             way of testing the lightweight resolver daemon with a
             name server that listens for queries on a non-standard
             port number.
-          
    
+          
    
+        
 
    -s
    
 
    
-
    
+          
    
             Write memory usage statistics to stdout
             on exit.
           
    
-
    
+          
    
 
    Note
    
-
    
+            
    
               This option is mainly of interest to BIND 9 developers
               and may be removed or changed in a future release.
             
    
-
    
-
    
+          
    
+        
 
    -t directory
    
 
    
-
    Chroot
+          
    Chroot
 	    to directory after
             processing the command line arguments, but before
             reading the configuration file.
           
    
-
    
+          
    
 
    Warning
    
-
    
+            
    
               This option should be used in conjunction with the
               -u option, as chrooting a process
               running as root doesn't enhance security on most
@@ -200,65 +259,82 @@
               defined allows a process with root privileges to
               escape a chroot jail.
             
    
-
    
-
    
+          
    
+        
 
    -u user
    
-
    Setuid
+
    
+          
    Setuid
 	    to user after completing
             privileged operations, such as creating sockets that
             listen on privileged ports.
-          
    
+          
    
+        
 
    -v
    
-
    
+
    
+          
    
             Report the version number and exit.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    FILES
    
-
    
+
+  
    
+
+  
    
+
    FILES
    
+    
+
+    
    
 
    /etc/resolv.conf
    
-
    
+
    
+          
    
             The default configuration file.
-          
    
+          
    
+        
 
    /var/run/lwresd.pid
    
-
    
+
    
+          
    
             The default process-id file.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    named(8),
-      lwres(3),
-      resolver(5).
+
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        named(8)
+      ,
+      
+        lwres(3)
+      ,
+      
+        resolver(5)
+      .
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
 
+Prev 
-
+dnssec-verify 
-
    
 
    
 
-Prev 
 Up Next
+ Next
 
 
    
 
    
 
-named.conf 
 Home named-journalprint
+ named
 
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named-checkconf.html b/doc/arm/man.named-checkconf.html
index 964e158083..cc41170ffa 100644
--- a/doc/arm/man.named-checkconf.html
+++ b/doc/arm/man.named-checkconf.html
@@ -14,15 +14,14 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named-checkconf
-
-
+
+
 
-
+
 
 
 
@@ -31,7 +30,7 @@
 named-checkconf
 
 
-Prev 
+Prev 
 Manual pages
  Next
 
@@ -39,61 +38,96 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
+
+  
    
 
    Name
    
-
    named-checkconf — named configuration file syntax checking tool
    
+
    
+    named-checkconf
+     — named configuration file syntax checking tool
+  
    
 
    
-
    
+
+  
    
 
    Synopsis
    
-
    named-checkconf  [-h] [-v] [-j] [-t directory] {filename} [-p] [-x] [-z]
    
-
    
-
    
-
    DESCRIPTION
    
-
    named-checkconf
+    
    
+      named-checkconf 
+       [-h]
+       [-v]
+       [-j]
+       [-t directory]
+       {filename}
+       [-p]
+       [-x]
+       [-z]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    named-checkconf
       checks the syntax, but not the semantics, of a
-      named configuration file.  The file is parsed
+      named configuration file.  The file is parsed
       and checked for syntax errors, along with all files included by it.
       If no file is specified, /etc/named.conf is read
       by default.
     
    
-
    
-      Note: files that named reads in separate
+    
    
+      Note: files that named reads in separate
       parser contexts, such as rndc.key and
       bind.keys, are not automatically read
-      by named-checkconf.  Configuration
-      errors in these files may cause named to
-      fail to run, even if named-checkconf was
-      successful.  named-checkconf can be run
+      by named-checkconf.  Configuration
+      errors in these files may cause named to
+      fail to run, even if named-checkconf was
+      successful.  named-checkconf can be run
       on these files explicitly, however.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -h
    
-
    
+
    
+          
    
             Print the usage summary and exit.
-          
    
+          
    
+        
 
    -t directory
    
-
    
+
    
+          
    
             Chroot to directory so that include
             directives in the configuration file are processed as if
-            run by a similarly chrooted named.
-          
    
+            run by a similarly chrooted named.
+          
    
+        
 
    -v
    
-
    
-            Print the version of the named-checkconf
+
    
+          
    
+            Print the version of the named-checkconf
             program and exit.
-          
    
+          
    
+        
 
    -p
    
-
    
+
    
+          
    
 	    Print out the named.conf and included files
 	    in canonical form if no errors were detected.
-          
    
+          
    
+        
 
    -x
    
-
    
+
    
+          
    
 	    When printing the configuration files in canonical
             form, obscure shared secrets by replacing them with
             strings of question marks ('?'). This allows the
@@ -101,62 +135,73 @@
             files to be shared — for example, when submitting
             bug reports — without compromising private data.
             This option cannot be used without -p.
-          
    
+          
    
+        
 
    -z
    
-
    
+
    
+          
    
 	    Perform a test load of all master zones found in
 	    named.conf.
-          
    
+          
    
+        
 
    -j
    
-
    
+
    
+          
    
             When loading a zonefile read the journal if it exists.
-          
    
+          
    
+        
 
    filename
    
-
    
+
    
+          
    
             The name of the configuration file to be checked.  If not
             specified, it defaults to /etc/named.conf.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    RETURN VALUES
    
-
    named-checkconf
+
+  
    
+
+  
    
+
    RETURN VALUES
    
+    
+    
    named-checkconf
       returns an exit status of 1 if
       errors were detected and 0 otherwise.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    named(8),
-      named-checkzone(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        named(8)
+      ,
+      
+        named-checkzone(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
 
    
 
    
 
    
 
+Prev 
+named.conf 
    
 
    
 
-Prev 
 Up
  Next
 
 
    
 
    
 
-dnssec-verify 
 Home
  named-checkzone
 
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named-checkzone.html b/doc/arm/man.named-checkzone.html
index 46b4a0fe10..ba80bbb07e 100644
--- a/doc/arm/man.named-checkzone.html
+++ b/doc/arm/man.named-checkzone.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named-checkzone
-
-
+
+
 
 
-
+
 
 
 
    
@@ -33,297 +32,425 @@
 
 Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
+
+  
    
 
    Name
    
-
    named-checkzone, named-compilezone — zone file validity checking or converting tool
    
+
    
+    named-checkzone, 
+    named-compilezone
+     — zone file validity checking or converting tool
+  
    
 
    
-
    
+
+  
    
 
    Synopsis
    
-
    named-checkzone  [-d] [-h] [-j] [-q] [-v] [-c class] [-f format] [-F format] [-J filename] [-i mode] [-k mode] [-m mode] [-M mode] [-n mode] [-l ttl] [-L serial] [-o filename] [-r mode] [-s style] [-S mode] [-t directory] [-T mode] [-w directory] [-D] [-W mode] {zonename} {filename}
    
-
    named-compilezone  [-d] [-j] [-q] [-v] [-c class] [-C mode] [-f format] [-F format] [-J filename] [-i mode] [-k mode] [-m mode] [-n mode] [-l ttl] [-L serial] [-r mode] [-s style] [-t directory] [-T mode] [-w directory] [-D] [-W mode] {-o filename} {zonename} {filename}
    
-
    
-
    
-
    DESCRIPTION
    
-
    named-checkzone
+    
    
+      named-checkzone 
+       [-d]
+       [-h]
+       [-j]
+       [-q]
+       [-v]
+       [-c class]
+       [-f format]
+       [-F format]
+       [-J filename]
+       [-i mode]
+       [-k mode]
+       [-m mode]
+       [-M mode]
+       [-n mode]
+       [-l ttl]
+       [-L serial]
+       [-o filename]
+       [-r mode]
+       [-s style]
+       [-S mode]
+       [-t directory]
+       [-T mode]
+       [-w directory]
+       [-D]
+       [-W mode]
+       {zonename}
+       {filename}
+    
    
+    
    
+      named-compilezone 
+       [-d]
+       [-j]
+       [-q]
+       [-v]
+       [-c class]
+       [-C mode]
+       [-f format]
+       [-F format]
+       [-J filename]
+       [-i mode]
+       [-k mode]
+       [-m mode]
+       [-n mode]
+       [-l ttl]
+       [-L serial]
+       [-r mode]
+       [-s style]
+       [-t directory]
+       [-T mode]
+       [-w directory]
+       [-D]
+       [-W mode]
+       {-o filename}
+       {zonename}
+       {filename}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    named-checkzone
       checks the syntax and integrity of a zone file.  It performs the
-      same checks as named does when loading a
-      zone.  This makes named-checkzone useful for
+      same checks as named does when loading a
+      zone.  This makes named-checkzone useful for
       checking zone files before configuring them into a name server.
     
    
-
    
-        named-compilezone is similar to
-	named-checkzone, but it always dumps the
+    
    
+        named-compilezone is similar to
+	named-checkzone, but it always dumps the
         zone contents to a specified file in a specified format.
 	Additionally, it applies stricter check levels by default,
         since the dump output will be used as an actual zone file
-	loaded by named.
+	loaded by named.
 	When manually specified otherwise, the check levels must at
         least be as strict as those specified in the
-	named configuration file.
+	named configuration file.
      
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -d
    
-
    
+
    
+          
    
             Enable debugging.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Print the usage summary and exit.
-          
    
+          
    
+        
 
    -q
    
-
    
+
    
+          
    
             Quiet mode - exit code only.
-          
    
+          
    
+        
 
    -v
    
-
    
-            Print the version of the named-checkzone
+
    
+          
    
+            Print the version of the named-checkzone
             program and exit.
-          
    
+          
    
+        
 
    -j
    
-
    
+
    
+          
    
             When loading a zone file, read the journal if it exists.
             The journal file name is assumed to be the zone file name
 	    appended with the string .jnl.
-          
    
+          
    
+        
 
    -J filename
    
-
    
+
    
+          
    
             When loading the zone file read the journal from the given
             file, if it exists. (Implies -j.)
-          
    
+          
    
+        
 
    -c class
    
-
    
+
    
+          
    
             Specify the class of the zone.  If not specified, "IN" is assumed.
-          
    
+          
    
+        
 
    -i mode
    
 
    
-
    
+	  
    
 	      Perform post-load zone integrity checks.  Possible modes are
-	      "full" (default),
-	      "full-sibling",
-	      "local",
-	      "local-sibling" and
-	      "none".
+	      "full" (default),
+	      "full-sibling",
+	      "local",
+	      "local-sibling" and
+	      "none".
 	  
    
-
    
-	      Mode "full" checks that MX records
+	  
    
+	      Mode "full" checks that MX records
 	      refer to A or AAAA record (both in-zone and out-of-zone
-	      hostnames).  Mode "local" only
+	      hostnames).  Mode "local" only
 	      checks MX records which refer to in-zone hostnames.
 	  
    
-
    
-	      Mode "full" checks that SRV records
+	  
    
+	      Mode "full" checks that SRV records
 	      refer to A or AAAA record (both in-zone and out-of-zone
-	      hostnames).  Mode "local" only
+	      hostnames).  Mode "local" only
 	      checks SRV records which refer to in-zone hostnames.
 	  
    
-
    
-	      Mode "full" checks that delegation NS
+	  
    
+	      Mode "full" checks that delegation NS
 	      records refer to A or AAAA record (both in-zone and out-of-zone
 	      hostnames).  It also checks that glue address records
 	      in the zone match those advertised by the child.
-	      Mode "local" only checks NS records which
+	      Mode "local" only checks NS records which
 	      refer to in-zone hostnames or that some required glue exists,
 	      that is when the nameserver is in a child zone.
 	  
    
-
    
-	      Mode "full-sibling" and
-	      "local-sibling" disable sibling glue
-	      checks but are otherwise the same as "full"
-	      and "local" respectively.
+	  
    
+	      Mode "full-sibling" and
+	      "local-sibling" disable sibling glue
+	      checks but are otherwise the same as "full"
+	      and "local" respectively.
 	  
    
-
    
-	      Mode "none" disables the checks.
+	  
    
+	      Mode "none" disables the checks.
 	  
    
-
    
+	
 
    -f format
    
-
    
+
    
+	  
    
 	    Specify the format of the zone file.
-	    Possible formats are "text" (default),
-	    "raw", and "map".
-	  
    
+	    Possible formats are "text" (default),
+	    "raw", and "map".
+	  
    
+	
 
    -F format
    
 
    
-
    
+	  
    
 	    Specify the format of the output file specified.
-	    For named-checkzone,
+	    For named-checkzone,
 	    this does not cause any effects unless it dumps the zone
 	    contents.
 	  
    
-
    
-	    Possible formats are "text" (default),
+	  
    
+	    Possible formats are "text" (default),
 	    which is the standard textual representation of the zone,
-	    and "map", "raw",
-            and "raw=N", which store the zone in a
-            binary format for rapid loading by named.
-            "raw=N" specifies the format version of
+	    and "map", "raw",
+            and "raw=N", which store the zone in a
+            binary format for rapid loading by named.
+            "raw=N" specifies the format version of
             the raw zone file: if N is 0, the raw file can be read by
-            any version of named; if N is 1, the file
+            any version of named; if N is 1, the file
             can be read by release 9.9.0 or higher; the default is 1.
 	  
    
-
    
+	
 
    -k mode
    
-
    
-            Perform "check-names" checks with the
+
    
+          
    
+            Perform "check-names" checks with the
 	    specified failure mode.
-            Possible modes are "fail"
-	    (default for named-compilezone),
-            "warn"
-	    (default for named-checkzone) and
-            "ignore".
-          
    
+            Possible modes are "fail"
+	    (default for named-compilezone),
+            "warn"
+	    (default for named-checkzone) and
+            "ignore".
+          
    
+        
 
    -l ttl
    
-
    
+
    
+          
    
             Sets a maximum permissible TTL for the input file.
             Any record with a TTL higher than this value will cause
             the zone to be rejected.  This is similar to using the
-            max-zone-ttl option in
+            max-zone-ttl option in
             named.conf.
-          
    
+          
    
+        
 
    -L serial
    
-
    
+
    
+          
    
             When compiling a zone to "raw" or "map" format, set the
             "source serial" value in the header to the specified serial
             number.  (This is expected to be used primarily for testing
             purposes.)
-          
    
+          
    
+        
 
    -m mode
    
-
    
+
    
+          
    
             Specify whether MX records should be checked to see if they
-            are addresses.  Possible modes are "fail",
-            "warn" (default) and
-            "ignore".
-          
    
+            are addresses.  Possible modes are "fail",
+            "warn" (default) and
+            "ignore".
+          
    
+        
 
    -M mode
    
-
    
+
    
+	  
    
 	    Check if a MX record refers to a CNAME.
-            Possible modes are "fail",
-            "warn" (default) and
-            "ignore".
-	  
    
+            Possible modes are "fail",
+            "warn" (default) and
+            "ignore".
+	  
    
+        
 
    -n mode
    
-
    
+
    
+          
    
             Specify whether NS records should be checked to see if they
             are addresses.
-	    Possible modes are "fail"
-	    (default for named-compilezone),
-            "warn"
-	    (default for named-checkzone) and
-            "ignore".
-          
    
+	    Possible modes are "fail"
+	    (default for named-compilezone),
+            "warn"
+	    (default for named-checkzone) and
+            "ignore".
+          
    
+        
 
    -o filename
    
-
    
+
    
+          
    
             Write zone output to filename.
 	    If filename is - then
 	    write to standard out.
-	    This is mandatory for named-compilezone.
-          
    
+	    This is mandatory for named-compilezone.
+          
    
+        
 
    -r mode
    
-
    
+
    
+	  
    
             Check for records that are treated as different by DNSSEC but
 	    are semantically equal in plain DNS.  
-            Possible modes are "fail",
-            "warn" (default) and
-            "ignore".
-	  
    
+            Possible modes are "fail",
+            "warn" (default) and
+            "ignore".
+	  
    
+        
 
    -s style
    
-
    
+
    
+	  
    
 	    Specify the style of the dumped zone file.
-	    Possible styles are "full" (default)
-	    and "relative".
+	    Possible styles are "full" (default)
+	    and "relative".
 	    The full format is most suitable for processing
 	    automatically by a separate script.
 	    On the other hand, the relative format is more
 	    human-readable and is thus suitable for editing by hand.
-	    For named-checkzone
+	    For named-checkzone
 	    this does not cause any effects unless it dumps the zone
 	    contents.
 	    It also does not have any meaning if the output format
 	    is not text.
-	  
    
+	  
    
+	
 
    -S mode
    
-
    
+
    
+	  
    
 	    Check if a SRV record refers to a CNAME.
-            Possible modes are "fail",
-            "warn" (default) and
-            "ignore".
-	  
    
+            Possible modes are "fail",
+            "warn" (default) and
+            "ignore".
+	  
    
+        
 
    -t directory
    
-
    
+
    
+          
    
             Chroot to directory so that
             include
             directives in the configuration file are processed as if
-            run by a similarly chrooted named.
-          
    
+            run by a similarly chrooted named.
+          
    
+        
 
    -T mode
    
-
    
+
    
+	  
    
 	    Check if Sender Policy Framework (SPF) records exist
 	    and issues a warning if an SPF-formatted TXT record is
-	    not also present.  Possible modes are "warn"
-	    (default), "ignore".
-	  
    
+	    not also present.  Possible modes are "warn"
+	    (default), "ignore".
+	  
    
+	
 
    -w directory
    
-
    
+
    
+          
    
             chdir to directory so that
             relative
             filenames in master file $INCLUDE directives work.  This
             is similar to the directory clause in
             named.conf.
-          
    
+          
    
+        
 
    -D
    
-
    
+
    
+          
    
             Dump zone file in canonical format.
-	    This is always enabled for named-compilezone.
-          
    
+	    This is always enabled for named-compilezone.
+          
    
+        
 
    -W mode
    
-
    
+
    
+          
    
             Specify whether to check for non-terminal wildcards.
             Non-terminal wildcards are almost always the result of a
             failure to understand the wildcard matching algorithm (RFC 1034).
-            Possible modes are "warn" (default)
+            Possible modes are "warn" (default)
             and
-            "ignore".
-          
    
+            "ignore".
+          
    
+        
 
    zonename
    
-
    
+
    
+          
    
             The domain name of the zone being checked.
-          
    
+          
    
+        
 
    filename
    
-
    
+
    
+          
    
             The name of the zone file.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    RETURN VALUES
    
-
    named-checkzone
+
+  
    
+
+  
    
+
    RETURN VALUES
    
+    
+    
    named-checkzone
       returns an exit status of 1 if
       errors were detected and 0 otherwise.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    named(8),
-      named-checkconf(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        named(8)
+      ,
+      
+        named-checkconf(8)  
+      ,
       RFC 1035,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -332,18 +459,18 @@
 
 Prev 
 Up
- Next
+ Next
 
 
 
 
 named-checkconf 
 Home
- named
+ named-journalprint
 
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named-journalprint.html b/doc/arm/man.named-journalprint.html
index 60d6c883f8..04445593f8 100644
--- a/doc/arm/man.named-journalprint.html
+++ b/doc/arm/man.named-journalprint.html
@@ -14,15 +14,14 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named-journalprint
-
-
+
+
 
-
+
 
 
 
@@ -31,7 +30,7 @@
 named-journalprint
 
 
-Prev 
+Prev 
 Manual pages
  Next
 
@@ -39,27 +38,43 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    named-journalprint — print zone journal in human-readable form
    
-
    
-
    
-
    Synopsis
    
-
    named-journalprint  {journal}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      named-journalprint
+    named-journalprint
+     — print zone journal in human-readable form
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      named-journalprint 
+       {journal}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      named-journalprint
       prints the contents of a zone journal file in a human-readable
       form. 
     
    
-
    
-      Journal files are automatically created by named 
+    
    
+      Journal files are automatically created by named 
       when changes are made to dynamic zones (e.g., by
-      nsupdate).  They record each addition
+      nsupdate).  They record each addition
       or deletion of a resource record, in binary format, allowing the
       changes to be re-applied to the zone when the server is
       restarted after a shutdown or crash.  By default, the name of
@@ -67,47 +82,49 @@
       .jnl to the name of the corresponding
       zone file.
     
    
-
    
-      named-journalprint converts the contents of a given
+    
    
+      named-journalprint converts the contents of a given
       journal file into a human-readable text format.  Each line begins
       with "add" or "del", to indicate whether the record was added or
       deleted, and continues with the resource record in master-file
       format.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    
-      named(8),
-      nsupdate(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+      
+        named(8)
+      ,
+      
+        nsupdate(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
 
+Prev 
+named-checkzone 
    
 
    
 
-Prev 
 Up
  Next
 
 
    
 
    
 
-isc-hmac-fixup 
 Home
  named-rrchecker
 
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named-rrchecker.html b/doc/arm/man.named-rrchecker.html
index 6504b6548d..0bf60fa201 100644
--- a/doc/arm/man.named-rrchecker.html
+++ b/doc/arm/man.named-rrchecker.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named-rrchecker
-
-
+
+
 
 
-
+
 
 
 
    
@@ -33,58 +32,83 @@
 
 Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+  
+  
    
 
    Name
    
-
    named-rrchecker — A syntax checker for individual DNS resource records
    
+
    
+    named-rrchecker
+     — A syntax checker for individual DNS resource records
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    named-rrchecker  [-h] [-o origin] [-p] [-u] [-C] [-T] [-P]
    
-
    
-
    
-
    DESCRIPTION
    
-
    named-rrchecker
+    
    
+      named-rrchecker 
+       [-h]
+       [-o origin]
+       [-p]
+       [-u]
+       [-C]
+       [-T]
+       [-P]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    named-rrchecker
      read a individual DNS resource record from standard input and checks if it
      is syntactically correct.
     
    
-
    
+    
    
       The -h prints out the help menu.
     
    
-
    
+    
    
       The -o origin
       option specifies a origin to be used when interpreting the record.
     
    
-
    
+    
    
       The -p prints out the resulting record in canonical
       form.  If there is no canonical form defined then the record will be
       printed in unknown record format.
     
    
-
    
+    
    
       The -u prints out the resulting record in unknown record
       form.
     
    
-
    
+    
    
       The -C, -T and -P
       print out the known class, standard type and private type mnemonics
       respectively.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
       RFC 1034,
       RFC 1035,
-      named(8)
+      
+        named(8)
+      
     
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -93,18 +117,18 @@
 
 Prev 
 Up
- Next
+ Next
 
 
 
 
 named-journalprint 
 Home
- nsec3hash
+ nsupdate
 
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named.conf.html b/doc/arm/man.named.conf.html
index 4b100c7cc6..45082331a2 100644
--- a/doc/arm/man.named.conf.html
+++ b/doc/arm/man.named.conf.html
@@ -14,16 +14,15 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named.conf
-
-
+
+
 
 
-
+
 
 
 
    
@@ -33,69 +32,92 @@
 
 Prev 
 Manual pages
- Next
+ Next
 
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    named.conf — configuration file for named
    
+
    
+    named.conf
+     — configuration file for named
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    named.conf 
    
-
    
-
    
-
    DESCRIPTION
    
-
    named.conf is the configuration file
+    
    
+      named.conf 
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    named.conf is the configuration file
       for
-      named.  Statements are enclosed
+      named.  Statements are enclosed
       in braces and terminated with a semi-colon.  Clauses in
       the statements are also semi-colon terminated.  The usual
       comment styles are supported:
     
    
-
    
+    
    
       C style: /* */
     
    
-
    
+    
    
       C++ style: // to end of line
     
    
-
    
+    
    
       Unix style: # to end of line
     
    
-
    
-
    
-
    ACL
    
-

    
+  
    
+
+  
    
+
    ACL
    
+    
+    

    
 acl string { address_match_element; ... };
    
 
    
 
    
-
    
-
    
-
    KEY
    
-

    
+  
    
+
+  
    
+
    KEY
    
+    
+    

    
 key domain_name {
    
 	algorithm string;
    
 	secret string;
    
 };
    
 
    
-
    
-
    
-
    MASTERS
    
-

    
+  
    
+
+  
    
+
    MASTERS
    
+    
+    

    
 masters string [ port integer ] {
    
 	( masters | ipv4_address [port integer] |
    
 	ipv6_address [port integer] ) [ key string ]; ...
    
 };
    
 
    
-
    
-
    
-
    SERVER
    
-

    
+  
    
+
+  
    
+
    SERVER
    
+    
+    

    
 server ( ipv4_address[/prefixlen] | ipv6_address[/prefixlen] ) {
    
 	bogus boolean;
    
 	edns boolean;
    
@@ -115,26 +137,32 @@ server
 	support-ixfr boolean; // obsolete
    
 };
    
 
    
-
    
-
    
-
    TRUSTED-KEYS
    
-

    
+  
    
+
+  
    
+
    TRUSTED-KEYS
    
+    
+    

    
 trusted-keys {
    
 	domain_name flags protocol algorithm key; ...
    
 };
    
 
    
-
    
-
    
-
    MANAGED-KEYS
    
-

    
+  
    
+
+  
    
+
    MANAGED-KEYS
    
+    
+    

    
 managed-keys {
    
 	domain_name initial-key flags protocol algorithm key; ...
    
 };
    
 
    
-
    
-
    
-
    CONTROLS
    
-

    
+  
    
+
+  
    
+
    CONTROLS
    
+    
+    

    
 controls {
    
 	inet ( ipv4_address | ipv6_address | * )
    
 		[ port ( integer | * ) ]
    
@@ -143,10 +171,12 @@ controls
 	unix unsupported; // not implemented
    
 };
    
 
    
-
    
-
    
-
    LOGGING
    
-

    
+  
    
+
+  
    
+
    LOGGING
    
+    
+    

    
 logging {
    
 	channel string {
    
 		file log_file;
    
@@ -161,10 +191,12 @@ logging
 	category string { string; ... };
    
 };
    
 
    
-
    
-
    
-
    LWRES
    
-

    
+  
    
+
+  
    
+
    LWRES
    
+    
+    

    
 lwres {
    
 	listen-on [ port integer ] {
    
 		( ipv4_address | ipv6_address ) [ port integer ]; ...
    
@@ -176,10 +208,12 @@ lwres
 	lwres-clients integer;
    
 };
    
 
    
-
    
-
    
-
    OPTIONS
    
-

    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+    

    
 options {
    
 	avoid-v4-udp-ports { port; ... };
    
 	avoid-v6-udp-ports { port; ... };
    
@@ -390,10 +424,12 @@ options
 	use-id-pool boolean; // obsolete
    
 };
    
 
    
-
    
-
    
-
    VIEW
    
-

    
+  
    
+
+  
    
+
    VIEW
    
+    
+    

    
 view string optional_class {
    
 	match-clients { address_match_element; ... };
    
 	match-destinations { address_match_element; ... };
    
@@ -559,10 +595,12 @@ view
 	max-ixfr-log-size size; // obsolete
    
 };
    
 
    
-
    
-
    
-
    ZONE
    
-

    
+  
    
+
+  
    
+
    ZONE
    
+    
+    

    
 zone string optional_class {
    
 	type ( master | slave | stub | hint | redirect |
    
 		forward | delegation-only );
    
@@ -656,20 +694,31 @@ zone
 	pubkey integer integer integer quoted_string; // obsolete
    
 };
    
 
    
-
    
-
    
-
    FILES
    
-
    /etc/named.conf
+  
    
+
+  
    
+
    FILES
    
+    
+    
    /etc/named.conf
     
    
-
    
-
    
-
    SEE ALSO
    
-
    named(8),
-      named-checkconf(8),
-      rndc(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+	named(8)
+      ,
+      
+	named-checkconf(8)
+      ,
+      
+	rndc(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -678,18 +727,18 @@ zone
 
 Prev 
 Up
- Next
+ Next
 
 
 
 
 named 
 Home
- lwresd
+ named-checkconf
 
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.named.html b/doc/arm/man.named.html
index 80b3d8535b..1ba6274df3 100644
--- a/doc/arm/man.named.html
+++ b/doc/arm/man.named.html
@@ -14,15 +14,14 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 named
-
-
+
+
 
-
+
 
 
 
@@ -31,7 +30,7 @@
 named
 
 
-Prev 
+Prev 
 Manual pages
  Next
 
@@ -39,48 +38,93 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    named — Internet domain name server
    
+
    
+    named
+     — Internet domain name server
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    named  [-4] [-6] [-c config-file] [-d debug-level] [-D string] [-E engine-name] [-f] [-g] [-L logfile] [-M option] [-m flag] [-n #cpus] [-p port] [-s] [-S #max-socks] [-t directory] [-U #listeners] [-u user] [-v] [-V] [-X lock-file] [-x cache-file]
    
-
    
-
    
-
    DESCRIPTION
    
-
    named
+    
    
+      named 
+       [-4]
+       [-6]
+       [-c config-file]
+       [-d debug-level]
+       [-D string]
+       [-E engine-name]
+       [-f]
+       [-g]
+       [-L logfile]
+       [-M option]
+       [-m flag]
+       [-n #cpus]
+       [-p port]
+       [-s]
+       [-S #max-socks]
+       [-t directory]
+       [-U #listeners]
+       [-u user]
+       [-v]
+       [-V]
+       [-X lock-file]
+       [-x cache-file]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    named
       is a Domain Name System (DNS) server,
       part of the BIND 9 distribution from ISC.  For more
       information on the DNS, see RFCs 1033, 1034, and 1035.
     
    
-
    
-      When invoked without arguments, named
+    
    
+      When invoked without arguments, named
       will
       read the default configuration file
       /etc/named.conf, read any initial
       data, and listen for queries.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -4
    
-
    
+
    
+          
    
             Use IPv4 only even if the host machine is capable of IPv6.
             -4 and -6 are mutually
             exclusive.
-          
    
+          
    
+        
 
    -6
    
-
    
+
    
+          
    
             Use IPv6 only even if the host machine is capable of IPv4.
             -4 and -6 are mutually
             exclusive.
-          
    
+          
    
+        
 
    -c config-file
    
-
    
+
    
+          
    
             Use config-file as the
             configuration file instead of the default,
             /etc/named.conf.  To
@@ -90,28 +134,33 @@
             directory option in the configuration
             file, config-file should be
             an absolute pathname.
-          
    
+          
    
+        
 
    -d debug-level
    
-
    
+
    
+          
    
             Set the daemon's debug level to debug-level.
-            Debugging traces from named become
+            Debugging traces from named become
             more verbose as the debug level increases.
-          
    
+          
    
+        
 
    -D string
    
-
    
-	    Specifies a string that is used to identify a instance of
-	    named in a process listing.  The contents
-	    of string are
-	    not examined.
-          
    
+
    
+          
    
+            Specifies a string that is used to identify a instance of
+            named in a process listing.  The contents
+            of string are
+            not examined.
+          
    
+        
    
 
    -E engine-name
    
 
    
-
    
+          
    
             When applicable, specifies the hardware to use for
             cryptographic operations, such as a secure key store used
             for signing.
           
    
-
    
+          
    
             When BIND is built with OpenSSL PKCS#11 support, this defaults
             to the string "pkcs11", which identifies an OpenSSL engine
             that can drive a cryptographic accelerator or hardware service
@@ -119,105 +168,119 @@
             (--enable-native-pkcs11), it defaults to the path of the PKCS#11
             provider library specified via "--with-pkcs11".
           
    
-
    
+        
 
    -f
    
-
    
+
    
+          
    
             Run the server in the foreground (i.e. do not daemonize).
-          
    
+          
    
+        
 
    -g
    
-
    
+
    
+          
    
             Run the server in the foreground and force all logging
             to stderr.
-          
    
+          
    
+        
 
    -L logfile
    
-
    
+
    
+          
    
             Log to the file logfile by default
             instead of the system log.
-          
    
+          
    
+        
 
    -M option
    
-
    
-	    Sets the default memory context options.  Currently
-	    the only supported option is
-	    external,
-	    which causes the internal memory manager to be bypassed
-	    in favor of system-provided memory allocation functions.
-          
    
+
    
+          
    
+            Sets the default memory context options.  Currently
+            the only supported option is
+            external,
+            which causes the internal memory manager to be bypassed
+            in favor of system-provided memory allocation functions.
+          
    
+        
    
 
    -m flag
    
-
    
-	    Turn on memory usage debugging flags.  Possible flags are
-	    usage,
-	    trace,
-	    record,
-	    size, and
-	    mctx.
-	    These correspond to the ISC_MEM_DEBUGXXXX flags described in
-	    <isc/mem.h>.
-          
    
+
    
+          
    
+            Turn on memory usage debugging flags.  Possible flags are
+            usage,
+            trace,
+            record,
+            size, and
+            mctx.
+            These correspond to the ISC_MEM_DEBUGXXXX flags described in
+            <isc/mem.h>.
+          
    
+        
    
 
    -n #cpus
    
-
    
+
    
+          
    
             Create #cpus worker threads
             to take advantage of multiple CPUs.  If not specified,
-            named will try to determine the
+            named will try to determine the
             number of CPUs present and create one thread per CPU.
             If it is unable to determine the number of CPUs, a
             single worker thread will be created.
-          
    
+          
    
+        
 
    -p port
    
-
    
+
    
+          
    
             Listen for queries on port port.  If not
             specified, the default is port 53.
-          
    
+          
    
+        
 
    -s
    
 
    
-
    
+          
    
             Write memory usage statistics to stdout on exit.
           
    
-
    
+          
    
 
    Note
    
-
    
+            
    
               This option is mainly of interest to BIND 9 developers
               and may be removed or changed in a future release.
             
    
-
    
-
    
+          
    
+        
 
    -S #max-socks
    
 
    
-
    
-	    Allow named to use up to
-	    #max-socks sockets.
+          
    
+            Allow named to use up to
+            #max-socks sockets.
             The default value is 4096 on systems built with default
             configuration options, and 21000 on systems built with
             "configure --with-tuning=large".
-	  
    
-
    
+          
    
+          
    
 
    Warning
    
-
    
+            
    
               This option should be unnecessary for the vast majority
               of users.
-	      The use of this option could even be harmful because the
+              The use of this option could even be harmful because the
               specified value may exceed the limitation of the
               underlying system API.
-	      It is therefore set only when the default configuration
+              It is therefore set only when the default configuration
               causes exhaustion of file descriptors and the
               operational environment is known to support the
               specified number of sockets.
-	      Note also that the actual maximum number is normally a little
+              Note also that the actual maximum number is normally a little
               fewer than the specified value because
-	      named reserves some file descriptors
-	      for its internal use.
+              named reserves some file descriptors
+              for its internal use.
             
    
-
    
-
    
+          
    
+        
 
    -t directory
    
 
    
-
    Chroot
-	    to directory after
+          
    Chroot
+            to directory after
             processing the command line arguments, but before
             reading the configuration file.
           
    
-
    
+          
    
 
    Warning
    
-
    
+            
    
               This option should be used in conjunction with the
               -u option, as chrooting a process
               running as root doesn't enhance security on most
@@ -225,168 +288,214 @@
               defined allows a process with root privileges to
               escape a chroot jail.
             
    
-
    
-
    
+          
    
+        
 
    -U #listeners
    
-
    
+
    
+          
    
             Use #listeners
             worker threads to listen for incoming UDP packets on each
-            address.  If not specified, named will
+            address.  If not specified, named will
             calculate a default value based on the number of detected
-            CPUs: 1 for 1 CPU, 2 for 2-4 CPUs, and the number of
-            detected CPUs divided by 2 for values higher than 4.
+            CPUs: 1 for 1 CPU, and the number of detected CPUs
+            minus one for machines with more than 1 CPU. This cannot
+            be increased to a value higher than the number of CPUs.
             If -n has been set to a higher value than
             the number of detected CPUs, then -U may
             be increased as high as that value, but no higher.
-          
    
+            On Windows, the number of UDP listeners is hardwired to 1
+            and this option has no effect.
+          
    
+        
 
    -u user
    
 
    
-
    Setuid
-	    to user after completing
+          
    Setuid
+            to user after completing
             privileged operations, such as creating sockets that
             listen on privileged ports.
           
    
-
    
+          
    
 
    Note
    
-
    
-              On Linux, named uses the kernel's
-              		capability mechanism to drop all root privileges
+            
    
+              On Linux, named uses the kernel's
+                        capability mechanism to drop all root privileges
               except the ability to bind(2) to
               a
               privileged port and set process resource limits.
               Unfortunately, this means that the -u
-              option only works when named is
+              option only works when named is
               run
               on kernel 2.2.18 or later, or kernel 2.3.99-pre3 or
               later, since previous kernels did not allow privileges
               to be retained after setuid(2).
             
    
-
    
-
    
+          
    
+        
 
    -v
    
-
    
+
    
+          
    
             Report the version number and exit.
-          
    
+          
    
+        
 
    -V
    
-
    
+
    
+          
    
             Report the version number and build options, and exit.
-          
    
+          
    
+        
 
    -X lock-file
    
-
    
+
    
+          
    
             Acquire a lock on the specified file at runtime; this
-            helps to prevent duplicate named instances
+            helps to prevent duplicate named instances
             from running simultaneously.
-            Use of this option overrides the lock-file
+            Use of this option overrides the lock-file
             option in named.conf.
             If set to none, the lock file check
             is disabled.
-          
    
+          
    
+        
 
    -x cache-file
    
 
    
-
    
+          
    
             Load data from cache-file into the
             cache of the default view.
           
    
-
    
+          
    
 
    Warning
    
-
    
+            
    
               This option must not be used.  It is only of interest
               to BIND 9 developers and may be removed or changed in a
               future release.
             
    
-
    
-
    
+          
    
+        
 
    
-
    
-
    
-
    SIGNALS
    
-
    
+
+  
    
+
+  
    
+
    SIGNALS
    
+    
+    
    
       In routine operation, signals should not be used to control
-      the nameserver; rndc should be used
+      the nameserver; rndc should be used
       instead.
     
    
-
    
+
+    
    
 
    SIGHUP
    
-
    
+
    
+          
    
             Force a reload of the server.
-          
    
+          
    
+        
 
    SIGINT, SIGTERM
    
-
    
+
    
+          
    
             Shut down the server.
-          
    
+          
    
+        
 
    
-
    
+
+    
    
       The result of sending any other signals to the server is undefined.
     
    
-
    
-
    
-
    CONFIGURATION
    
-
    
-      The named configuration file is too complex
+
+  
    
+
+  
    
+
    CONFIGURATION
    
+    
+    
    
+      The named configuration file is too complex
       to describe in detail here.  A complete description is provided
       in the
       BIND 9 Administrator Reference Manual.
     
    
-
    
-      named inherits the umask
+
+    
    
+      named inherits the umask
       (file creation mode mask) from the parent process. If files
-      created by named, such as journal files,
+      created by named, such as journal files,
       need to have custom permissions, the umask
       should be set explicitly in the script used to start the
-      named process.
+      named process.
     
    
-
    
-
    
-
    FILES
    
-
    
+
+  
    
+
+  
    
+
    FILES
    
+    
+
+    
    
 
    /etc/named.conf
    
-
    
+
    
+          
    
             The default configuration file.
-          
    
+          
    
+        
 
    /var/run/named/named.pid
    
-
    
+
    
+          
    
             The default process-id file.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    RFC 1033,
+
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    RFC 1033,
       RFC 1034,
       RFC 1035,
-      named-checkconf(8),
-      named-checkzone(8),
-      rndc(8),
-      lwresd(8),
-      named.conf(5),
+      
+        named-checkconf
+        (8)
+      ,
+      
+        named-checkzone
+        (8)
+      ,
+      
+        rndc
+        (8)
+      ,
+      
+        lwresd
+        (8)
+      ,
+      
+        named.conf
+        (5)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
 
+Prev 
+lwresd 
    
 
    
 
-Prev 
 Up
  Next
 
 
    
 
    
 
-named-checkzone 
 Home
  named.conf
 
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.nsec3hash.html b/doc/arm/man.nsec3hash.html
index 652f9b79dd..7c0c5c142a 100644
--- a/doc/arm/man.nsec3hash.html
+++ b/doc/arm/man.nsec3hash.html
@@ -14,15 +14,14 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 nsec3hash
-
-
+
+
 
-
+
 
 
 
    
@@ -30,85 +29,112 @@
 nsec3hash
 
 
-Prev 
+Prev 
 Manual pages
  
 
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    nsec3hash — generate NSEC3 hash
    
-
    
-
    
-
    Synopsis
    
-
    nsec3hash  {salt} {algorithm} {iterations} {domain}
    
-
    
-
    
-
    DESCRIPTION
    
 
    
-      nsec3hash generates an NSEC3 hash based on
+    nsec3hash
+     — generate NSEC3 hash
+  
    
+
    
+
+  
+
+  
    
+
    Synopsis
    
+    
    
+      nsec3hash 
+       {salt}
+       {algorithm}
+       {iterations}
+       {domain}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    
+      nsec3hash generates an NSEC3 hash based on
       a set of NSEC3 parameters.  This can be used to check the validity
       of NSEC3 records in a signed zone.
     
    
-
    
-
    
-
    ARGUMENTS
    
-
    
+  
    
+
+  
    
+
    ARGUMENTS
    
+    
+    
    
 
    salt
    
-
    
+
    
+          
    
             The salt provided to the hash algorithm.
-          
    
+          
    
+        
 
    algorithm
    
-
    
+
    
+          
    
             A number indicating the hash algorithm.  Currently the
             only supported hash algorithm for NSEC3 is SHA-1, which is
             indicated by the number 1; consequently "1" is the only
             useful value for this argument.
-          
    
+          
    
+        
 
    iterations
    
-
    
+
    
+          
    
             The number of additional times the hash should be performed.
-          
    
+          
    
+        
 
    domain
    
-
    
+
    
+          
    
             The domain name to be hashed.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
       BIND 9 Administrator Reference Manual,
       RFC 5155.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
 
+Prev 
+isc-hmac-fixup 
    
 
    
 
-Prev 
 Up
  
 
    
 
    
 
-named-rrchecker 
 Home
  
 
    
 
    
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.nsupdate.html b/doc/arm/man.nsupdate.html
index 60462428c3..ffe426c79b 100644
--- a/doc/arm/man.nsupdate.html
+++ b/doc/arm/man.nsupdate.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 nsupdate
-
-
+
+
 
 
 
@@ -39,19 +38,52 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+  
    
 
    Name
    
-
    nsupdate — Dynamic DNS update utility
    
+
    
+    nsupdate
+     — Dynamic DNS update utility
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    nsupdate  [-d] [-D] [-L level] [[-g] |  [-o] |  [-l] |  [-y [hmac:]keyname:secret] |  [-k keyfile]] [-t timeout] [-u udptimeout] [-r udpretries] [-R randomdev] [-v] [-T] [-P] [-V] [filename]
    
-
    
-
    
-
    DESCRIPTION
    
-
    nsupdate
+    
    
+      nsupdate 
+       [-d]
+       [-D]
+       [-L level]
+       [
+	[-g]
+	 |  [-o]
+	 |  [-l]
+	 |  [-y [hmac:]keyname:secret]
+	 |  [-k keyfile]
+      ]
+       [-t timeout]
+       [-u udptimeout]
+       [-r udpretries]
+       [-R randomdev]
+       [-v]
+       [-T]
+       [-P]
+       [-V]
+       [filename]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    nsupdate
       is used to submit Dynamic DNS Update requests as defined in RFC 2136
       to a name server.
       This allows resource records to be added or removed from a zone
@@ -60,114 +92,134 @@
       one
       resource record.
     
    
-
    
+    
    
       Zones that are under dynamic control via
-      nsupdate
+      nsupdate
       or a DHCP server should not be edited by hand.
       Manual edits could
       conflict with dynamic updates and cause data to be lost.
     
    
-
    
+    
    
       The resource records that are dynamically added or removed with
-      nsupdate
+      nsupdate
       have to be in the same zone.
       Requests are sent to the zone's master server.
       This is identified by the MNAME field of the zone's SOA record.
     
    
-
    
+    
    
       Transaction signatures can be used to authenticate the Dynamic
       DNS updates.  These use the TSIG resource record type described
       in RFC 2845 or the SIG(0) record described in RFC 2535 and
       RFC 2931 or GSS-TSIG as described in RFC 3645.
     
    
-
    
+    
    
       TSIG relies on
       a shared secret that should only be known to
-      nsupdate and the name server.
+      nsupdate and the name server.
       For instance, suitable key and
       server statements would be added to
       /etc/named.conf so that the name server
       can associate the appropriate secret key and algorithm with
       the IP address of the client application that will be using
-      TSIG authentication. You can use ddns-confgen
+      TSIG authentication. You can use ddns-confgen
       to generate suitable configuration fragments.
-      nsupdate
+      nsupdate
       uses the -y or -k options
       to provide the TSIG shared secret.  These options are mutually exclusive.
     
    
-
    
+    
    
       SIG(0) uses public key cryptography.
       To use a SIG(0) key, the public key must be stored in a KEY
       record in a zone served by the name server.
     
    
-
    
+    
    
       GSS-TSIG uses Kerberos credentials.  Standard GSS-TSIG mode
       is switched on with the -g flag.  A
       non-standards-compliant variant of GSS-TSIG used by Windows
       2000 can be switched on with the -o flag.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -d
    
-
    
+
    
+	  
    
 	    Debug mode. This provides tracing information about the
 	    update requests that are made and the replies received
 	    from the name server.
-	  
    
+	  
    
+	
 
    -D
    
-
    
+
    
+	  
    
 	    Extra debug mode.
-	  
    
+	  
    
+	
 
    -k keyfile
    
-
    
+
    
+	  
    
 	    The file containing the TSIG authentication key.
 	    Keyfiles may be in two formats: a single file containing
-	    a named.conf-format key
+	    a named.conf-format key
 	    statement, which may be generated automatically by
-	    ddns-confgen, or a pair of files whose names are
+	    ddns-confgen, or a pair of files whose names are
 	    of the format K{name}.+157.+{random}.key and
 	    K{name}.+157.+{random}.private, which can be
-	    generated by dnssec-keygen.
+	    generated by dnssec-keygen.
 	    The -k may also be used to specify a SIG(0) key used
 	    to authenticate Dynamic DNS update requests.  In this case, the key
 	    specified is not an HMAC-MD5 key.
-	  
    
+	  
    
+	
 
    -l
    
-
    
+
    
+	  
    
 	    Local-host only mode. This sets the server address to
-	    localhost (disabling the server so that the server
+	    localhost (disabling the server so that the server
 	    address cannot be overridden).  Connections to the local server will
 	    use a TSIG key found in /var/run/named/session.key,
-	    which is automatically generated by named if any
-	    local master zone has set update-policy to
-	    local.  The location of this key file can be
+	    which is automatically generated by named if any
+	    local master zone has set update-policy to
+	    local.  The location of this key file can be
 	    overridden with the -k option.
-	  
    
+	  
    
+	
 
    -L level
    
-
    
+
    
+	  
    
 	    Set the logging debug level.  If zero, logging is disabled.
-	  
    
+	  
    
+	
 
    -p port
    
-
    
+
    
+	  
    
 	    Set the port to use for connections to a name server. The
 	    default is 53.
-	  
    
+	  
    
+	
 
    -P
    
-
    
+
    
+	  
    
 	    Print the list of private BIND-specific resource record
 	    types whose format is understood
-	    by nsupdate. See also
+	    by nsupdate. See also
 	    the -T option.
-	  
    
+	  
    
+	
 
    -r udpretries
    
-
    
+
    
+	  
    
 	    The number of UDP retries. The default is 3. If zero, only
 	    one update request will be made.
-	  
    
+	  
    
+	
 
    -R randomdev
    
-
    
+
    
+	
    
 	  Where to obtain randomness. If the operating system
 	  does not provide a /dev/random or
 	  equivalent device, the default source of randomness is keyboard
@@ -176,51 +228,60 @@
 	  instead of the default.  The special value
 	  keyboard indicates that keyboard input
 	  should be used.  This option may be specified multiple times.
-	
    
+	
    
+	
 
    -t timeout
    
-
    
+
    
+	  
    
 	    The maximum time an update request can take before it is
 	    aborted. The default is 300 seconds. Zero can be used to
 	    disable the timeout.
-	  
    
+	  
    
+	
 
    -T
    
 
    
-
    
+	  
    
 	    Print the list of IANA standard resource record types
-	    whose format is understood by nsupdate.
-	    nsupdate will exit after the lists are
+	    whose format is understood by nsupdate.
+	    nsupdate will exit after the lists are
 	    printed. The -T option can be combined
 	    with the -P option.
 	  
    
-
    
+	  
    
 	    Other types can be entered using "TYPEXXXXX" where "XXXXX" is the
 	    decimal value of the type with no leading zeros.  The rdata,
 	    if present, will be parsed using the UNKNOWN rdata format,
 	    (<backslash> <hash> <space> <length>
 	    <space> <hexstring>).
 	  
    
-
    
+	
 
    -u udptimeout
    
-
    
+
    
+	  
    
 	    The UDP retry interval. The default is 3 seconds. If zero,
 	    the interval will be computed from the timeout interval and
 	    number of UDP retries.
-	  
    
+	  
    
+	
 
    -v
    
-
    
+
    
+	  
    
 	    Use TCP even for small update requests.
-	    By default, nsupdate
+	    By default, nsupdate
 	    uses UDP to send update requests to the name server unless they are too
 	    large to fit in a UDP request in which case TCP will be used.
 	    TCP may be preferable when a batch of update requests is made.
-	  
    
+	  
    
+	
 
    -V
    
-
    
+
    
+	  
    
 	    Print the version number and exit.
-	  
    
+	  
    
+	
 
    -y [hmac:]keyname:secret
    
 
    
-
    
+	  
    
 	    Literal TSIG authentication key.
 	    keyname is the name of the key, and
 	    secret is the base64 encoded shared secret.
@@ -231,19 +292,23 @@
 	    hmac-sha512.  If hmac
 	    is not specified, the default is hmac-md5.
 	  
    
-
    
+	  
    
 	    NOTE: Use of the -y option is discouraged because the
 	    shared secret is supplied as a command line argument in clear text.
 	    This may be visible in the output from
-	    ps(1)
+	    
+	      ps(1)
+	    
 	    or in a history file maintained by the user's shell.
 	  
    
-
    
+	
 
    
-
    
-
    
-
    INPUT FORMAT
    
-
    nsupdate
+  
    
+
+  
    
+
    INPUT FORMAT
    
+    
+    
    nsupdate
       reads input from
       filename
       or standard input.
@@ -257,30 +322,31 @@
       Updates will be rejected if the tests for the prerequisite conditions
       fail.
     
    
-
    
+    
    
       Every update request consists of zero or more prerequisites
       and zero or more updates.
       This allows a suitably authenticated update request to proceed if some
       specified resource records are present or missing from the zone.
-      A blank input line (or the send command)
+      A blank input line (or the send command)
       causes the
       accumulated commands to be sent as one Dynamic DNS update request to the
       name server.
     
    
-
    
+    
    
       The command formats and their meaning are as follows:
       
    
-
    
+
    
 
    
-	      server
+	      server
 	       {servername}
 	       [port]
 	    
    
-
    
+
    
+	    
    
 	      Sends all dynamic update requests to the name server
 	      servername.
 	      When no server statement is provided,
-	      nsupdate
+	      nsupdate
 	      will send updates to the master server of the correct zone.
 	      The MNAME field of that zone's SOA record will identify the
 	      master
@@ -292,131 +358,155 @@
 	      If no port number is specified, the default DNS port number of
 	      53 is
 	      used.
-	    
    
+	    
    
+	  
 
    
-	      local
+	      local
 	       {address}
 	       [port]
 	    
    
-
    
+
    
+	    
    
 	      Sends all dynamic update requests using the local
 	      address.
 
 	      When no local statement is provided,
-	      nsupdate
+	      nsupdate
 	      will send updates using an address and port chosen by the
 	      system.
 	      port
 	      can additionally be used to make requests come from a specific
 	      port.
 	      If no port number is specified, the system will assign one.
-	    
    
+	    
    
+	  
 
    
-	      zone
+	      zone
 	       {zonename}
 	    
    
-
    
+
    
+	    
    
 	      Specifies that all updates are to be made to the zone
 	      zonename.
 	      If no
 	      zone
 	      statement is provided,
-	      nsupdate
+	      nsupdate
 	      will attempt determine the correct zone to update based on the
 	      rest of the input.
-	    
    
+	    
    
+	  
 
    
-	      class
+	      class
 	       {classname}
 	    
    
-
    
+
    
+	    
    
 	      Specify the default class.
 	      If no class is specified, the
 	      default class is
 	      IN.
-	    
    
+	    
    
+	  
 
    
-	      ttl
+	      ttl
 	       {seconds}
 	    
    
-
    
+
    
+	    
    
 	      Specify the default time to live for records to be added.
 	      The value none will clear the default
 	      ttl.
-	    
    
+	    
    
+	  
 
    
-	      key
+	      key
 	       [hmac:] {keyname}
 	       {secret}
 	    
    
-
    
+
    
+	    
    
 	      Specifies that all updates are to be TSIG-signed using the
 	      keyname secret pair.
 	      If hmac is specified, then it sets the
 	      signing algorithm in use; the default is
-	      hmac-md5.  The key
+	      hmac-md5.  The key
 	      command overrides any key specified on the command line via
 	      -y or -k.
-	    
    
+	    
    
+	  
 
    
-	    gsstsig
+	    gsstsig
 	  
    
-
    
+
    
+	    
    
 	      Use GSS-TSIG to sign the updated.  This is equivalent to
 	      specifying -g on the command line.
-	    
    
+	    
    
+	  
 
    
-	    oldgsstsig
+	    oldgsstsig
 	  
    
-
    
+
    
+	    
    
 	      Use the Windows 2000 version of GSS-TSIG to sign the updated.
 	      This is equivalent to specifying -o on the
 	      command line.
-	    
    
+	    
    
+	  
 
    
-	    realm
+	    realm
 	     {[realm_name]}
 	  
    
-
    
+
    
+	    
    
 	      When using GSS-TSIG use realm_name rather
 	      than the default realm in krb5.conf.  If no
 	      realm is specified the saved realm is cleared.
-	    
    
+	    
    
+	  
 
    
-	    check-names
+	    check-names
 	     {[yes_or_no]}
 	  
    
-
    
+
    
+	    
    
 	      Turn on or off check-names processing on records to
 	      be added.  Check-names has no effect on prerequisites
 	      or records to be deleted.  By default check-names
 	      processing is on.  If check-names processing fails
 	      the record will not be added to the UPDATE message.
-	    
    
+	    
    
+	  
 
    
-	      [prereq] nxdomain
+	      [prereq] nxdomain
 	       {domain-name}
 	    
    
-
    
+
    
+	    
    
 	      Requires that no resource record of any type exists with name
 	      domain-name.
-	    
    
+	    
    
+	  
 
    
-	      [prereq] yxdomain
+	      [prereq] yxdomain
 	       {domain-name}
 	    
    
-
    
+
    
+	    
    
 	      Requires that
 	      domain-name
 	      exists (has as at least one resource record, of any type).
-	    
    
+	    
    
+	  
 
    
-	      [prereq] nxrrset
+	      [prereq] nxrrset
 	       {domain-name}
 	       [class]
 	       {type}
 	    
    
-
    
+
    
+	    
    
 	      Requires that no resource record exists of the specified
 	      type,
 	      class
@@ -425,14 +515,16 @@
 	      If
 	      class
 	      is omitted, IN (internet) is assumed.
-	    
    
+	    
    
+	  
 
    
-	      [prereq] yxrrset
+	      [prereq] yxrrset
 	       {domain-name}
 	       [class]
 	       {type}
 	    
    
-
    
+
    
+	    
    
 	      This requires that a resource record of the specified
 	      type,
 	      class
@@ -442,15 +534,17 @@
 	      If
 	      class
 	      is omitted, IN (internet) is assumed.
-	    
    
+	    
    
+	  
 
    
-	      [prereq] yxrrset
+	      [prereq] yxrrset
 	       {domain-name}
 	       [class]
 	       {type}
 	       {data...}
 	    
    
-
    
+
    
+	    
    
 	      The
 	      data
 	      from each set of prerequisites of this form
@@ -471,15 +565,17 @@
 	      are written in the standard text representation of the resource
 	      record's
 	      RDATA.
-	    
    
+	    
    
+	  
 
    
-	      [update] del[ete]
+	      [update] del[ete]
 	       {domain-name}
 	       [ttl]
 	       [class]
 	       [type [data...]]
 	    
    
-
    
+
    
+	    
    
 	      Deletes any resource records named
 	      domain-name.
 	      If
@@ -492,73 +588,92 @@
 	      is not supplied.  The
 	      ttl
 	      is ignored, and is only allowed for compatibility.
-	    
    
+	    
    
+	  
 
    
-	      [update] add
+	      [update] add
 	       {domain-name}
 	       {ttl}
 	       [class]
 	       {type}
 	       {data...}
 	    
    
-
    
+
    
+	    
    
 	      Adds a new resource record with the specified
 	      ttl,
 	      class
 	      and
 	      data.
-	    
    
+	    
    
+	  
 
    
-	      show
+	      show
 	    
    
-
    
+
    
+	    
    
 	      Displays the current message, containing all of the
 	      prerequisites and
 	      updates specified since the last send.
-	    
    
+	    
    
+	  
 
    
-	      send
+	      send
 	    
    
-
    
+
    
+	    
    
 	      Sends the current message.  This is equivalent to entering a
 	      blank line.
-	    
    
+	    
    
+	  
 
    
-	      answer
+	      answer
 	    
    
-
    
+
    
+	    
    
 	      Displays the answer.
-	    
    
+	    
    
+	  
 
    
-	      debug
+	      debug
 	    
    
-
    
+
    
+	    
    
 	      Turn on debugging.
-	    
    
+	    
    
+	  
 
    
-	      version
+	      version
 	    
    
-
    
+
    
+	    
    
 	      Print version number.
-	    
    
+	    
    
+	  
 
    
-	      help
+	      help
 	    
    
-
    
+
    
+	    
    
 	      Print a list of commands.
-	    
    
+	    
    
+	  
 
    
 
    
     
    
-
    
+
+    
    
       Lines beginning with a semicolon are comments and are ignored.
     
    
-
    
-
    
-
    EXAMPLES
    
-
    
+
+  
    
+
+  
    
+
    EXAMPLES
    
+    
+    
    
       The examples below show how
-      nsupdate
+      nsupdate
       could be used to insert and delete resource records from the
       example.com
       zone.
@@ -577,7 +692,7 @@
 
    
 
    
     
    
-
    
+    
    
       Any A records for
       oldhost.example.com
       are deleted.
@@ -594,7 +709,7 @@
 
    
 
    
     
    
-
    
+    
    
       The prerequisite condition gets the name server to check that there
       are no resource records of any type for
       nickname.example.com.
@@ -607,33 +722,50 @@
       (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
       RRSIG, DNSKEY and NSEC records.)
     
    
-
-
    
-
    FILES
    
-
    
+  
    
+
+  
    
+
    FILES
    
+    
+
+    
    
 
    /etc/resolv.conf
    
-
    
+
    
+	  
    
 	    used to identify default name server
-	  
    
+	  
    
+	
 
    /var/run/named/session.key
    
-
    
+
    
+	  
    
 	    sets the default TSIG key for use in local-only mode
-	  
    
+	  
    
+	
 
    K{name}.+157.+{random}.key
    
-
    
+
    
+	  
    
 	    base-64 encoding of HMAC-MD5 key created by
-	    dnssec-keygen(8).
-	  
    
+	    
+	      dnssec-keygen(8)
+	    .
+	  
    
+	
 
    K{name}.+157.+{random}.private
    
-
    
+
    
+	  
    
 	    base-64 encoding of HMAC-MD5 key created by
-	    dnssec-keygen(8).
-	  
    
+	    
+	      dnssec-keygen(8)
+	    .
+	  
    
+	
 
    
-
    
-
    
-
    SEE ALSO
    
-
    
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
       RFC 2136,
       RFC 3007,
       RFC 2104,
@@ -641,20 +773,29 @@
       RFC 1034,
       RFC 2535,
       RFC 2931,
-      named(8),
-      ddns-confgen(8),
-      dnssec-keygen(8).
+      
+	named(8)
+      ,
+      
+	ddns-confgen(8)
+      ,
+      
+	dnssec-keygen(8)
+      .
     
    
-
    
-
    
-
    BUGS
    
-
    
+  
    
+
+  
    
+
    BUGS
    
+    
+    
    
       The TSIG key is redundantly stored in two separate files.
       This is a consequence of nsupdate using the DST library
       for its cryptographic operations, and may change in future
       releases.
     
    
-
    
+  
    
+
 
 
    
 
    
@@ -675,6 +816,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html
index 798c364163..3adcda6219 100644
--- a/doc/arm/man.rndc-confgen.html
+++ b/doc/arm/man.rndc-confgen.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 rndc-confgen
-
-
+
+
 
 
 
@@ -39,108 +38,151 @@
 
 
    
 
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    rndc-confgen — rndc key generation tool
    
+
    
+    rndc-confgen
+     — rndc key generation tool
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    rndc-confgen  [-a] [-A algorithm] [-b keysize] [-c keyfile] [-h] [-k keyname] [-p port] [-r randomfile] [-s address] [-t chrootdir] [-u user]
    
-
    
-
    
-
    DESCRIPTION
    
-
    rndc-confgen
+    
    
+      rndc-confgen 
+       [-a]
+       [-A algorithm]
+       [-b keysize]
+       [-c keyfile]
+       [-h]
+       [-k keyname]
+       [-p port]
+       [-r randomfile]
+       [-s address]
+       [-t chrootdir]
+       [-u user]
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    rndc-confgen
       generates configuration files
-      for rndc.  It can be used as a
+      for rndc.  It can be used as a
       convenient alternative to writing the
       rndc.conf file
-      and the corresponding controls
-      and key
+      and the corresponding controls
+      and key
       statements in named.conf by hand.
-      Alternatively, it can be run with the -a
+      Alternatively, it can be run with the -a
       option to set up a rndc.key file and
       avoid the need for a rndc.conf file
-      and a controls statement altogether.
+      and a controls statement altogether.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -a
    
 
    
-
    
-            Do automatic rndc configuration.
+          
    
+            Do automatic rndc configuration.
             This creates a file rndc.key
             in /etc (or whatever
             sysconfdir
             was specified as when BIND was
             built)
-            that is read by both rndc
-            and named on startup.  The
+            that is read by both rndc
+            and named on startup.  The
             rndc.key file defines a default
             command channel and authentication key allowing
-            rndc to communicate with
-            named on the local host
+            rndc to communicate with
+            named on the local host
             with no further configuration.
           
    
-
    
-            Running rndc-confgen -a allows
-            BIND 9 and rndc to be used as
+          
    
+            Running rndc-confgen -a allows
+            BIND 9 and rndc to be used as
             drop-in
-            replacements for BIND 8 and ndc,
+            replacements for BIND 8 and ndc,
             with no changes to the existing BIND 8
             named.conf file.
           
    
-
    
+          
    
             If a more elaborate configuration than that
-            generated by rndc-confgen -a
+            generated by rndc-confgen -a
             is required, for example if rndc is to be used remotely,
-            you should run rndc-confgen without
+            you should run rndc-confgen without
             the
-            -a option and set up a
+            -a option and set up a
             rndc.conf and
             named.conf
             as directed.
           
    
-
    
+        
 
    -A algorithm
    
-
    
+
    
+          
    
             Specifies the algorithm to use for the TSIG key.  Available
             choices are: hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256,
             hmac-sha384 and hmac-sha512.  The default is hmac-md5.
-          
    
+          
    
+        
 
    -b keysize
    
-
    
+
    
+          
    
             Specifies the size of the authentication key in bits.
             Must be between 1 and 512 bits; the default is the
             hash size.
-          
    
+          
    
+        
 
    -c keyfile
    
-
    
-            Used with the -a option to specify
+
    
+          
    
+            Used with the -a option to specify
             an alternate location for rndc.key.
-          
    
+          
    
+        
 
    -h
    
-
    
+
    
+          
    
             Prints a short summary of the options and arguments to
-            rndc-confgen.
-          
    
+            rndc-confgen.
+          
    
+        
 
    -k keyname
    
-
    
+
    
+          
    
             Specifies the key name of the rndc authentication key.
             This must be a valid domain name.
             The default is rndc-key.
-          
    
+          
    
+        
 
    -p port
    
-
    
-            Specifies the command channel port where named
-            listens for connections from rndc.
+
    
+          
    
+            Specifies the command channel port where named
+            listens for connections from rndc.
             The default is 953.
-          
    
+          
    
+        
 
    -r randomfile
    
-
    
+
    
+          
    
             Specifies a source of random data for generating the
             authorization.  If the operating
             system does not provide a /dev/random
@@ -151,64 +193,77 @@
             data to be used instead of the default.  The special value
             keyboard indicates that keyboard
             input should be used.
-          
    
+          
    
+        
 
    -s address
    
-
    
-            Specifies the IP address where named
+
    
+          
    
+            Specifies the IP address where named
             listens for command channel connections from
-            rndc.  The default is the loopback
+            rndc.  The default is the loopback
             address 127.0.0.1.
-          
    
+          
    
+        
 
    -t chrootdir
    
-
    
-            Used with the -a option to specify
-            a directory where named will run
+
    
+          
    
+            Used with the -a option to specify
+            a directory where named will run
             chrooted.  An additional copy of the rndc.key
             will be written relative to this directory so that
-            it will be found by the chrooted named.
-          
    
+            it will be found by the chrooted named.
+          
    
+        
 
    -u user
    
-
    
-            Used with the -a option to set the
+
    
+          
    
+            Used with the -a option to set the
             owner
             of the rndc.key file generated.
             If
-            -t is also specified only the file
+            -t is also specified only the file
             in
             the chroot area has its owner changed.
-          
    
+          
    
+        
 
    
-
    
-
    
-
    EXAMPLES
    
-
    
-      To allow rndc to be used with
+  
    
+
+  
    
+
    EXAMPLES
    
+    
+    
    
+      To allow rndc to be used with
       no manual configuration, run
     
    
-
    rndc-confgen -a
+    
    rndc-confgen -a
     
    
-
    
+    
    
       To print a sample rndc.conf file and
-      corresponding controls and key
+      corresponding controls and key
       statements to be manually inserted into named.conf,
       run
     
    
-
    rndc-confgen
+    
    rndc-confgen
     
    
-
    
-
    
-
    SEE ALSO
    
-
    rndc(8),
-      rndc.conf(5),
-      named(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        rndc(8)
+      ,
+      
+        rndc.conf(5)
+      ,
+      
+        named(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -229,6 +284,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.rndc.conf.html b/doc/arm/man.rndc.conf.html
index 9508eca5b2..8de79cfd51 100644
--- a/doc/arm/man.rndc.conf.html
+++ b/doc/arm/man.rndc.conf.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 rndc.conf
-
-
+
+
 
 
 
@@ -39,46 +38,61 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    rndc.conf — rndc configuration file
    
+
    
+    rndc.conf
+     — rndc configuration file
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    rndc.conf 
    
-
    
-
    
-
    DESCRIPTION
    
-
    rndc.conf is the configuration file
-      for rndc, the BIND 9 name server control
+    
    
+      rndc.conf 
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    rndc.conf is the configuration file
+      for rndc, the BIND 9 name server control
       utility.  This file has a similar structure and syntax to
       named.conf.  Statements are enclosed
       in braces and terminated with a semi-colon.  Clauses in
       the statements are also semi-colon terminated.  The usual
       comment styles are supported:
     
    
-
    
+    
    
       C style: /* */
     
    
-
    
+    
    
       C++ style: // to end of line
     
    
-
    
+    
    
       Unix style: # to end of line
     
    
-
    rndc.conf is much simpler than
+    
    rndc.conf is much simpler than
       named.conf.  The file uses three
       statements: an options statement, a server statement
       and a key statement.
     
    
-
    
+    
    
       The options statement contains five clauses.
       The default-server clause is followed by the
       name or address of a name server.  This host will be used when
       no name server is given as an argument to
-      rndc.  The default-key
+      rndc.  The default-key
       clause is followed by the name of a key which is identified by
       a key statement.  If no
       keyid is provided on the rndc command line,
@@ -96,7 +110,7 @@
       can be used to set the IPv4 and IPv6 source addresses
       respectively.
     
    
-
    
+    
    
       After the server keyword, the server
       statement includes a string which is the hostname or address
       for a name server.  The statement has three possible clauses:
@@ -110,34 +124,37 @@
       of supplied then these will be used to specify the IPv4 and IPv6
       source addresses respectively.
     
    
-
    
+    
    
       The key statement begins with an identifying
       string, the name of the key.  The statement has two clauses.
       algorithm identifies the authentication algorithm
-      for rndc to use; currently only HMAC-MD5
+      for rndc to use; currently only HMAC-MD5
       (for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256
       (default), HMAC-SHA384 and HMAC-SHA512 are
       supported.  This is followed by a secret clause which contains
       the base-64 encoding of the algorithm's authentication key.  The
       base-64 string is enclosed in double quotes.
     
    
-
    
+    
    
       There are two common ways to generate the base-64 string for the
-      secret.  The BIND 9 program rndc-confgen
+      secret.  The BIND 9 program rndc-confgen
       can
       be used to generate a random key, or the
-      mmencode program, also known as
-      mimencode, can be used to generate a
+      mmencode program, also known as
+      mimencode, can be used to generate a
       base-64
-      string from known input.  mmencode does
+      string from known input.  mmencode does
       not
       ship with BIND 9 but is available on many systems.  See the
       EXAMPLE section for sample command lines for each.
     
    
-
    
-
    
-
    EXAMPLE
    
-
    +  
    
+
+  
    
+
    EXAMPLE
    
+    
+
+    
           options {
         default-server  localhost;
         default-key     samplekey;
@@ -145,14 +162,14 @@
 
    
 
    
     
    
-
    +    
           server localhost {
         key             samplekey;
       };
 
    
 
    
     
    
-
    +    
           server testserver {
         key		testkey;
         addresses	{ localhost port 5353; };
@@ -160,7 +177,7 @@
 
    
 
    
     
    
-
    +    
           key samplekey {
         algorithm       hmac-sha256;
         secret          "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
@@ -168,7 +185,7 @@
 
    
 
    
     
    
-
    +    
           key testkey {
         algorithm	hmac-sha256;
         secret		"R3HI8P6BKw9ZwXwN3VZKuQ==";
@@ -176,8 +193,9 @@
     
    
 
    
     
    
-
    
-      In the above example, rndc will by
+
+    
    
+      In the above example, rndc will by
       default use
       the server at localhost (127.0.0.1) and the key called samplekey.
       Commands to the localhost server will use the samplekey key, which
@@ -186,16 +204,16 @@
       uses the HMAC-SHA256 algorithm and its secret clause contains the
       base-64 encoding of the HMAC-SHA256 secret enclosed in double quotes.
     
    
-
    
-      If rndc -s testserver is used then rndc will
+    
    
+      If rndc -s testserver is used then rndc will
       connect to server on localhost port 5353 using the key testkey.
     
    
-
    
-      To generate a random secret with rndc-confgen:
+    
    
+      To generate a random secret with rndc-confgen:
     
    
-
    rndc-confgen
+    
    rndc-confgen
     
    
-
    
+    
    
       A complete rndc.conf file, including
       the
       randomly generated key, will be written to the standard
@@ -203,35 +221,41 @@
       controls statements for
       named.conf are also printed.
     
    
-
    
-      To generate a base-64 secret with mmencode:
+    
    
+      To generate a base-64 secret with mmencode:
     
    
-
    echo "known plaintext for a secret" | mmencode
+    
    echo "known plaintext for a secret" | mmencode
     
    
-
    
-
    
-
    NAME SERVER CONFIGURATION
    
-
    
+  
    
+
+  
    
+
    NAME SERVER CONFIGURATION
    
+    
+    
    
       The name server must be configured to accept rndc connections and
       to recognize the key specified in the rndc.conf
       file, using the controls statement in named.conf.
       See the sections on the controls statement in the
       BIND 9 Administrator Reference Manual for details.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    rndc(8),
-      rndc-confgen(8),
-      mmencode(1),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+        rndc(8)
+      ,
+      
+        rndc-confgen(8)
+      ,
+      
+        mmencode(1)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -252,6 +276,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/man.rndc.html b/doc/arm/man.rndc.html
index d4a3951a89..d397fd4895 100644
--- a/doc/arm/man.rndc.html
+++ b/doc/arm/man.rndc.html
@@ -14,13 +14,12 @@
  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  - PERFORMANCE OF THIS SOFTWARE.
 -->
-
 
 
 
 rndc
-
-
+
+
 
 
 
@@ -39,32 +38,57 @@
 
 
    
 
    
-
    
+
    
 
    
-
    
+  
+  
+
+  
+
+  
    
 
    Name
    
-
    rndc — name server control utility
    
+
    
+    rndc
+     — name server control utility
+  
    
 
    
-
    
+
+  
+
+  
    
 
    Synopsis
    
-
    rndc  [-b source-address] [-c config-file] [-k key-file] [-s server] [-p port] [-q] [-r] [-V] [-y key_id] {command}
    
-
    
-
    
-
    DESCRIPTION
    
-
    rndc
+    
    
+      rndc 
+       [-b source-address]
+       [-c config-file]
+       [-k key-file]
+       [-s server]
+       [-p port]
+       [-q]
+       [-r]
+       [-V]
+       [-y key_id]
+       {command}
+    
    
+  
    
+
+  
    
+
    DESCRIPTION
    
+    
+    
    rndc
       controls the operation of a name
-      server.  It supersedes the ndc utility
+      server.  It supersedes the ndc utility
       that was provided in old BIND releases.  If
-      rndc is invoked with no command line
+      rndc is invoked with no command line
       options or arguments, it prints a short summary of the
       supported commands and the available options and their
       arguments.
     
    
-
    rndc
+    
    rndc
       communicates with the name server over a TCP connection, sending
       commands authenticated with digital signatures.  In the current
       versions of
-      rndc and named,
+      rndc and named,
       the only supported authentication algorithms are HMAC-MD5
       (for compatibility), HMAC-SHA1, HMAC-SHA224, HMAC-SHA256
       (default), HMAC-SHA384 and HMAC-SHA512.
@@ -74,30 +98,38 @@
       over the channel must be signed by a key_id known to the
       server.
     
    
-
    rndc
+    
    rndc
       reads a configuration file to
       determine how to contact the name server and decide what
       algorithm and key it should use.
     
    
-
    
-
    
-
    OPTIONS
    
-
    
+  
    
+
+  
    
+
    OPTIONS
    
+    
+
+    
    
 
    -b source-address
    
-
    
+
    
+	  
    
 	    Use source-address
 	    as the source address for the connection to the server.
 	    Multiple instances are permitted to allow setting of both
 	    the IPv4 and IPv6 source addresses.
-	  
    
+	  
    
+	
 
    -c config-file
    
-
    
+
    
+	  
    
 	    Use config-file
 	    as the configuration file instead of the default,
 	    /etc/rndc.conf.
-	  
    
+	  
    
+	
 
    -k key-file
    
-
    
+
    
+	  
    
 	    Use key-file
 	    as the key file instead of the default,
 	    /etc/rndc.key.  The key in
@@ -105,48 +137,60 @@
 	    authenticate
 	    commands sent to the server if the config-file
 	    does not exist.
-	  
    
+	  
    
+	
 
    -s server
    
-
    server is
+
    
+	  
    server is
 	    the name or address of the server which matches a
 	    server statement in the configuration file for
-	    rndc.  If no server is supplied on the
+	    rndc.  If no server is supplied on the
 	    command line, the host named by the default-server clause
-	    in the options statement of the rndc
+	    in the options statement of the rndc
 	    configuration file will be used.
-	  
    
+	  
    
+	
 
    -p port
    
-
    
+
    
+	  
    
 	    Send commands to TCP port
 	    port
 	    instead
 	    of BIND 9's default control channel port, 953.
-	  
    
+	  
    
+	
 
    -q
    
-
    
+
    
+	  
    
 	    Quiet mode: Message text returned by the server
 	    will not be printed except when there is an error.
-	  
    
+	  
    
+	
 
    -r
    
-
    
-	    Instructs rndc to print the result code
-	    returned by named after executing the
+
    
+	  
    
+	    Instructs rndc to print the result code
+	    returned by named after executing the
 	    requested command (e.g., ISC_R_SUCCESS, ISC_R_FAILURE, etc).
-	  
    
+	  
    
+	
 
    -V
    
-
    
+
    
+	  
    
 	    Enable verbose logging.
-	  
    
+	  
    
+	
 
    -y key_id
    
-
    
+
    
+	  
    
 	    Use the key key_id
 	    from the configuration file.
 	    key_id
 	    must be
-	    known by named with the same algorithm and secret string
+	    known by named with the same algorithm and secret string
 	    in order for control message validation to succeed.
 	    If no key_id
-	    is specified, rndc will first look
+	    is specified, rndc will first look
 	    for a key clause in the server statement of the server
 	    being used, or if no server statement is present for that
 	    host, then the default-key clause of the options statement.
@@ -154,32 +198,36 @@
 	    which are used to send authenticated control commands
 	    to name servers.  It should therefore not have general read
 	    or write access.
-	  
    
+	  
    
+	
 
    
-
    
-
    
-
    COMMANDS
    
-
    
-      A list of commands supported by rndc can
-      be seen by running rndc without arguments.
+  
    
+
+  
    
+
    COMMANDS
    
+    
+    
    
+      A list of commands supported by rndc can
+      be seen by running rndc without arguments.
     
    
-
    
+    
    
       Currently supported commands are:
     
    
-
    
+
+    
    
 
    addzone zone [class [view]] configuration 
    
 
    
-
    
+	  
    
 	    Add a zone while the server is running.  This
 	    command requires the
-	    allow-new-zones option to be set
+	    allow-new-zones option to be set
 	    to yes.  The
 	    configuration string
 	    specified on the command line is the zone
 	    configuration text that would ordinarily be
 	    placed in named.conf.
 	  
    
-
    
+	  
    
 	    The configuration is saved in a file called
 	    name.nzf,
 	    where name is the
@@ -187,33 +235,33 @@
 	    that are incompatible with use as a file name, a
 	    cryptographic hash generated from the name
 	    of the view.
-	    When named is
+	    When named is
 	    restarted, the file will be loaded into the view
 	    configuration, so that zones that were added
 	    can persist after a restart.
 	  
    
-
    
-	    This sample addzone command
+	  
    
+	    This sample addzone command
 	    would add the zone example.com
 	    to the default view:
 	  
    
-
    
+	  
    
 $ rndc addzone example.com '{ type master; file "example.com.db"; };'
 	  
    
-
    
+	  
    
 	    (Note the brackets and semi-colon around the zone
 	    configuration text.)
 	  
    
-
    
-	    See also rndc delzone and rndc modzone.
+	  
    
+	    See also rndc delzone and rndc modzone.
 	  
    
-
    
+	
 
    delzone [-clean] zone [class [view]] 
    
 
    
-
    
+	  
    
 	    Delete a zone while the server is running.
 	  
    
-
    
+	  
    
 	    If the -clean argument is specified,
 	    the zone's master file (and journal file, if any)
 	    will be deleted along with the zone.  Without the
@@ -221,11 +269,11 @@
 	    be cleaned up by hand.  (If the zone is of
 	    type "slave" or "stub", the files needing to
 	    be cleaned up will be reported in the output
-	    of the rndc delzone command.)
+	    of the rndc delzone command.)
 	  
    
-
    
+	  
    
 	    If the zone was originally added via
-	    rndc addzone, then it will be
+	    rndc addzone, then it will be
 	    removed permanently. However, if it was originally
 	    configured in named.conf, then
 	    that original configuration is still in place; when
@@ -233,39 +281,47 @@
 	    come back. To remove it permanently, it must also be
 	    removed from named.conf
 	  
    
-
    
-	    See also rndc addzone and rndc modzone.
+	  
    
+	    See also rndc addzone and rndc modzone.
 	  
    
-
    
+	
 
    dumpdb [-all|-cache|-zone|-adb|-bad|-fail] [view ...]
    
-
    
+
    
+	  
    
 	    Dump the server's caches (default) and/or zones to
 	    the
 	    dump file for the specified views.  If no view is
 	    specified, all
 	    views are dumped.
-	    (See the dump-file option in
+	    (See the dump-file option in
 	    the BIND 9 Administrator Reference Manual.)
-	  
    
+	  
    
+	
 
    flush
    
-
    
+
    
+	  
    
 	    Flushes the server's cache.
-	  
    
+	  
    
+	
 
    flushname name [view] 
    
-
    
+
    
+	  
    
 	    Flushes the given name from the view's DNS cache
 	    and, if applicable, from the view's nameserver address
 	    database, bad server cache and SERVFAIL cache.
-	  
    
+	  
    
+	
 
    flushtree name [view] 
    
-
    
+
    
+	  
    
 	    Flushes the given name, and all of its subdomains,
 	    from the view's DNS cache, address database,
 	    bad server cache, and SERVFAIL cache.
-	  
    
+	  
    
+	
 
    freeze [zone [class [view]]]
    
 
    
-
    
+	  
    
 	    Suspend updates to a dynamic zone.  If no zone is
 	    specified, then all zones are suspended.  This allows
 	    manual edits to be made to a zone normally updated by
@@ -274,48 +330,49 @@
 	    All dynamic update attempts will be refused while
 	    the zone is frozen.
 	  
    
-
    
-	    See also rndc thaw.
+	  
    
+	    See also rndc thaw.
 	  
    
-
    
+	
 
    halt [-p]
    
 
    
-
    
+	  
    
 	    Stop the server immediately.  Recent changes
 	    made through dynamic update or IXFR are not saved to
 	    the master files, but will be rolled forward from the
 	    journal files when the server is restarted.
-	    If -p is specified named's process id is returned.
-	    This allows an external process to determine when named
+	    If -p is specified named's process id is returned.
+	    This allows an external process to determine when named
 	    had completed halting.
 	  
    
-
    
-	    See also rndc stop.
+	  
    
+	    See also rndc stop.
 	  
    
-
    
+	
 
    loadkeys zone [class [view]]
    
 
    
-
    
+	  
    
 	    Fetch all DNSSEC keys for the given zone
 	    from the key directory.  If they are within
 	    their publication period, merge them into the
-	    zone's DNSKEY RRset.  Unlike rndc
+	    zone's DNSKEY RRset.  Unlike rndc
 	    sign, however, the zone is not
 	    immediately re-signed by the new keys, but is
 	    allowed to incrementally re-sign over time.
 	  
    
-
    
+	  
    
 	    This command requires that the
-	    auto-dnssec zone option
+	    auto-dnssec zone option
 	    be set to maintain,
 	    and also requires the zone to be configured to
 	    allow dynamic DNS.
 	    (See "Dynamic Update Policies" in the Administrator
 	    Reference Manual for more details.)
 	  
    
-
    
+	
 
    managed-keys (status | refresh | sync) [class [view]]
    
-
    
+
    
+	  
    
 	    When run with the "status" keyword, print the current
 	    status of the managed-keys database for the specified
 	    view, or for all views if none is specified.  When run
@@ -325,23 +382,24 @@
 	    immediate dump of the managed-keys database to disk (in
 	    the file managed-keys.bind or
 	    (viewname.mkeys).
-	  
    
+	  
    
+	
 
    modzone zone [class [view]] configuration 
    
 
    
-
    
+	  
    
 	    Modify the configuration of a zone while the server
 	    is running.  This command requires the
-	    allow-new-zones option to be
+	    allow-new-zones option to be
 	    set to yes.  As with
-	    addzone, the
+	    addzone, the
 	    configuration string
 	    specified on the command line is the zone
 	    configuration text that would ordinarily be
 	    placed in named.conf.
 	  
    
-
    
+	  
    
 	    If the zone was originally added via
-	    rndc addzone, the configuration
+	    rndc addzone, the configuration
 	    changes will be recorded permanently and will still be
 	    in effect after the server is restarted or reconfigured.
 	    However, if it was originally configured in
@@ -352,30 +410,32 @@
 	    permanent, it must also be modified in
 	    named.conf
 	  
    
-
    
-	    See also rndc addzone and rndc delzone.
+	  
    
+	    See also rndc addzone and rndc delzone.
 	  
    
-
    
+	
 
    notify zone [class [view]]
    
-
    
+
    
+	  
    
 	    Resend NOTIFY messages for the zone.
-	  
    
+	  
    
+	
 
    notrace
    
 
    
-
    
+	  
    
 	    Sets the server's debugging level to 0.
 	  
    
-
    
-	    See also rndc trace.
+	  
    
+	    See also rndc trace.
 	  
    
-
    
+	
 
    nta
 	[( -d | -f | -r | -l duration)]
 	domain
 	[view]
 	
    
 
    
-
    
+	  
    
 	    Sets a DNSSEC negative trust anchor (NTA)
 	    for domain, with a lifetime of
 	    duration.  The default lifetime is
@@ -383,19 +443,19 @@
 	    nta-lifetime option, and defaults to
 	    one hour.  The lifetime cannot exceed one week.
 	  
    
-
    
+	  
    
 	    A negative trust anchor selectively disables
 	    DNSSEC validation for zones that are known to be
 	    failing because of misconfiguration rather than
 	    an attack.  When data to be validated is
 	    at or below an active NTA (and above any other
-	    configured trust anchors), named will
+	    configured trust anchors), named will
 	    abort the DNSSEC validation process and treat the data as
 	    insecure rather than bogus.  This continues until the
 	    NTA's lifetime is elapsed.
 	  
    
-
    
-	    NTAs persist across restarts of the named server.
+	  
    
+	    NTAs persist across restarts of the named server.
 	    The NTAs for a view are saved in a file called
 	    name.nta,
 	    where name is the
@@ -404,11 +464,11 @@
 	    cryptographic hash generated from the name
 	    of the view.
 	  
    
-
    
+	  
    
 	    An existing NTA can be removed by using the
 	    -remove option.
 	  
    
-
    
+	  
    
 	    An NTA's lifetime can be specified with the
 	    -lifetime option.  TTL-style
 	    suffixes can be used to specify the lifetime in
@@ -417,14 +477,14 @@
 	    new value.  Setting lifetime to zero
 	    is equivalent to -remove.
 	  
    
-
    
+	  
    
 	    If -dump is used, any other arguments
 	    are ignored, and a list of existing NTAs is printed
 	    (note that this may include NTAs that are expired but
 	    have not yet been cleaned up).
 	  
    
-
    
-	    Normally, named will periodically
+	  
    
+	    Normally, named will periodically
 	    test to see whether data below an NTA can now be
 	    validated (see the nta-recheck option
 	    in the Administrator Reference Manual for details).
@@ -435,127 +495,139 @@
 	    lifetime, regardless of whether data could be
 	    validated if the NTA were not present.
 	  
    
-
    
+	  
    
 	    All of these options can be shortened, i.e., to
 	    -l, -r, -d,
 	    and -f.
 	  
    
-
    
+	
 
    querylog [on|off] 
    
 
    
-
    
+	  
    
 	    Enable or disable query logging.  (For backward
 	    compatibility, this command can also be used without
 	    an argument to toggle query logging on and off.)
 	  
    
-
    
+	  
    
 	    Query logging can also be enabled
-	    by explicitly directing the queries
-	    category to a
-	    channel in the
-	    logging section of
+	    by explicitly directing the queries
+	    category to a
+	    channel in the
+	    logging section of
 	    named.conf or by specifying
-	    querylog yes; in the
-	    options section of
+	    querylog yes; in the
+	    options section of
 	    named.conf.
 	  
    
-
    
+	
 
    reconfig
    
-
    
+
    
+	  
    
 	    Reload the configuration file and load new zones,
 	    but do not reload existing zone files even if they
 	    have changed.
-	    This is faster than a full reload when there
+	    This is faster than a full reload when there
 	    is a large number of zones because it avoids the need
 	    to examine the
 	    modification times of the zones files.
-	  
    
+	  
    
+	
 
    recursing
    
-
    
-            Dump the list of queries named is currently
+
    
+          
    
+            Dump the list of queries named is currently
             recursing on, and the list of domains to which iterative
             queries are currently being sent.  (The second list includes
             the number of fetches currently active for the given domain,
             and how many have been passed or dropped because of the
             fetches-per-zone option.)
-          
    
+          
    
+        
 
    refresh zone [class [view]]
    
-
    
+
    
+	  
    
 	    Schedule zone maintenance for the given zone.
-	  
    
+	  
    
+	
 
    reload
    
-
    
+
    
+	  
    
 	    Reload configuration file and zones.
-	  
    
+	  
    
+	
 
    reload zone [class [view]]
    
-
    
+
    
+	  
    
 	    Reload the given zone.
-	  
    
+	  
    
+	
 
    retransfer zone [class [view]]
    
 
    
-
    
+	  
    
 	    Retransfer the given slave zone from the master server.
 	  
    
-
    
+	  
    
 	    If the zone is configured to use
-	    inline-signing, the signed
+	    inline-signing, the signed
 	    version of the zone is discarded; after the
 	    retransfer of the unsigned version is complete, the
 	    signed version will be regenerated with all new
 	    signatures.
 	  
    
-
    
+	
 
    scan
    
-
    
+
    
+	  
    
 	     Scan the list of available network interfaces
 	     for changes, without performing a full
-	     reconfig or waiting for the
-	     interface-interval timer.
-	  
    
+	     reconfig or waiting for the
+	     interface-interval timer.
+	  
    
+	
 
    secroots [-] [view ...]
    
 
    
-
    
+	  
    
 	    Dump the server's security roots and negative trust anchors
 	    for the specified views.  If no view is specified, all views
 	    are dumped.
 	  
    
-
    
+	  
    
 	    If the first argument is "-", then the output is
-	    returned via the rndc response channel
+	    returned via the rndc response channel
 	    and printed to the standard output.
 	    Otherwise, it is written to the secroots dump file, which
 	    defaults to named.secroots, but can be
 	    overridden via the secroots-file option in
 	    named.conf.
 	  
    
-
    
-	    See also rndc managed-keys.
+	  
    
+	    See also rndc managed-keys.
 	  
    
-
    
+	
 
    showzone zone [class [view]] 
    
 
    
-
    
+	  
    
 	    Print the configuration of a running zone.
 	  
    
-
    
-	    See also rndc zonestatus.
+	  
    
+	    See also rndc zonestatus.
 	  
    
-
    
+	
 
    sign zone [class [view]]
    
 
    
-
    
+	  
    
 	    Fetch all DNSSEC keys for the given zone
 	    from the key directory (see the
-	    key-directory option in
+	    key-directory option in
 	    the BIND 9 Administrator Reference Manual).  If they are within
 	    their publication period, merge them into the
 	    zone's DNSKEY RRset.  If the DNSKEY RRset
 	    is changed, then the zone is automatically
 	    re-signed with the new key set.
 	  
    
-
    
+	  
    
 	    This command requires that the
-	    auto-dnssec zone option be set
+	    auto-dnssec zone option be set
 	    to allow or
 	    maintain,
 	    and also requires the zone to be configured to
@@ -563,44 +635,44 @@
 	    (See "Dynamic Update Policies" in the Administrator
 	    Reference Manual for more details.)
 	  
    
-
    
-	    See also rndc loadkeys.
+	  
    
+	    See also rndc loadkeys.
 	  
    
-
    
+	
 
    signing [( -list | -clear keyid/algorithm | -clear all | -nsec3param ( parameters | none ) | -serial value ) ] zone [class [view]] 
    
 
    
-
    
+	  
    
 	    List, edit, or remove the DNSSEC signing state records
 	    for the specified zone.  The status of ongoing DNSSEC
 	    operations (such as signing or generating
 	    NSEC3 chains) is stored in the zone in the form
 	    of DNS resource records of type
-	    sig-signing-type. 
-	    rndc signing -list converts
+	    sig-signing-type. 
+	    rndc signing -list converts
 	    these records into a human-readable form,
 	    indicating which keys are currently signing
 	    or have finished signing the zone, and which NSEC3
 	    chains are being created or removed.
 	  
    
-
    
-	    rndc signing -clear can remove
+	  
    
+	    rndc signing -clear can remove
 	    a single key (specified in the same format that
-	    rndc signing -list uses to
+	    rndc signing -list uses to
 	    display it), or all keys.  In either case, only
 	    completed keys are removed; any record indicating
 	    that a key has not yet finished signing the zone
 	    will be retained.
 	  
    
-
    
-	    rndc signing -nsec3param sets
+	  
    
+	    rndc signing -nsec3param sets
 	    the NSEC3 parameters for a zone.  This is the
 	    only supported mechanism for using NSEC3 with
-	    inline-signing zones.
+	    inline-signing zones.
 	    Parameters are specified in the same format as
 	    an NSEC3PARAM resource record: hash algorithm,
 	    flags, iterations, and salt, in that order.
 	  
    
-
    
+	  
    
 	    Currently, the only defined value for hash algorithm 
 	    is 1, representing SHA-1.
 	    The flags may be set to
@@ -612,67 +684,73 @@
 	    salt is a string of data expressed
 	    in hexadecimal, a hyphen (`-') if no salt is
 	    to be used, or the keyword auto,
-	    which causes named to generate a
+	    which causes named to generate a
 	    random 64-bit salt.
 	  
    
-
    
+	  
    
 	    So, for example, to create an NSEC3 chain using
 	    the SHA-1 hash algorithm, no opt-out flag,
 	    10 iterations, and a salt value of "FFFF", use:
-	    rndc signing -nsec3param 1 0 10 FFFF zone.
+	    rndc signing -nsec3param 1 0 10 FFFF zone.
 	    To set the opt-out flag, 15 iterations, and no
 	    salt, use:
-	    rndc signing -nsec3param 1 1 15 - zone.
+	    rndc signing -nsec3param 1 1 15 - zone.
 	  
    
-
    
-	    rndc signing -nsec3param none
+	  
    
+	    rndc signing -nsec3param none
 	    removes an existing NSEC3 chain and replaces it
 	    with NSEC.
 	  
    
-
    
-	    rndc signing -serial value sets
+	  
    
+	    rndc signing -serial value sets
 	    the serial number of the zone to value.  If the value
 	    would cause the serial number to go backwards it will
 	    be rejected.  The primary use is to set the serial on
 	    inline signed zones.
 	  
    
-
    
+	
 
    stats
    
-
    
+
    
+	  
    
 	    Write server statistics to the statistics file.
-	    (See the statistics-file option in
+	    (See the statistics-file option in
 	    the BIND 9 Administrator Reference Manual.)
-	  
    
+	  
    
+	
 
    status
    
-
    
+
    
+	  
    
 	    Display status of the server.
-	    Note that the number of zones includes the internal bind/CH zone
-	    and the default ./IN
+	    Note that the number of zones includes the internal bind/CH zone
+	    and the default ./IN
 	    hint zone if there is not an
 	    explicit root zone configured.
-	  
    
+	  
    
+	
 
    stop [-p]
    
 
    
-
    
+	  
    
 	    Stop the server, making sure any recent changes
 	    made through dynamic update or IXFR are first saved to
 	    the master files of the updated zones.
-	    If -p is specified named's process id is returned.
-	    This allows an external process to determine when named
+	    If -p is specified named's process id is returned.
+	    This allows an external process to determine when named
 	    had completed stopping.
 	  
    
-
    See also rndc halt.
    
-
    
+	  
    See also rndc halt.
    
+	
 
    sync [-clean] [zone [class [view]]]
    
-
    
+
    
+	  
    
 	    Sync changes in the journal file for a dynamic zone
 	    to the master file.  If the "-clean" option is
 	    specified, the journal file is also removed.  If
 	    no zone is specified, then all zones are synced.
-	  
    
+	  
    
+	
 
    thaw [zone [class [view]]]
    
 
    
-
    
+	  
    
 	    Enable updates to a frozen dynamic zone.  If no
 	    zone is specified, then all frozen zones are
 	    enabled.  This causes the server to reload the zone
@@ -680,53 +758,61 @@
 	    load has completed.  After a zone is thawed,
 	    dynamic updates will no longer be refused.  If
 	    the zone has changed and the
-	    ixfr-from-differences option is
+	    ixfr-from-differences option is
 	    in use, then the journal file will be updated to
 	    reflect changes in the zone.  Otherwise, if the
 	    zone has changed, any existing journal file will be
 	    removed.
 	  
    
-
    See also rndc freeze.
    
-
    
+	  
    See also rndc freeze.
    
+	
 
    trace
    
-
    
+
    
+	  
    
 	    Increment the servers debugging level by one.
-	  
    
+	  
    
+	
 
    trace level
    
 
    
-
    
+	  
    
 	    Sets the server's debugging level to an explicit
 	    value.
 	  
    
-
    
-	    See also rndc notrace.
+	  
    
+	    See also rndc notrace.
 	  
    
-
    
+	
 
    tsig-delete keyname [view]
    
-
    
+
    
+	  
    
 	    Delete a given TKEY-negotiated key from the server.
 	    (This does not apply to statically configured TSIG
 	    keys.)
-	  
    
+	  
    
+	
 
    tsig-list
    
-
    
+
    
+	  
    
 	    List the names of all TSIG keys currently configured
-	    for use by named in each view.  The
+	    for use by named in each view.  The
 	    list both statically configured keys and dynamic
 	    TKEY-negotiated keys.
-	  
    
+	  
    
+	
 
    validation ( on | off | check ) [view ...] 
    
-
    
+
    
+	  
    
 	    Enable, disable, or check the current status of
 	    DNSSEC validation.
-	    Note dnssec-enable also needs to be
+	    Note dnssec-enable also needs to be
 	    set to yes or
 	    auto to be effective.
 	    It defaults to enabled.
-	  
    
+	  
    
+	
 
    zonestatus zone [class [view]]
    
 
    
-
    
+	  
    
 	    Displays the current status of the given zone,
 	    including the master file name and any include
 	    files from which it was loaded, when it was most
@@ -737,37 +823,47 @@
 	    management or inline signing, and the scheduled
 	    refresh or expiry times for the zone.
 	  
    
-
    
-	    See also rndc showzone.
+	  
    
+	    See also rndc showzone.
 	  
    
-
    
+	
 
    
-
    
-
    
-
    LIMITATIONS
    
-
    
+  
    
+
+  
    
+
    LIMITATIONS
    
+    
+    
    
       There is currently no way to provide the shared secret for a
       key_id without using the configuration file.
     
    
-
    
+    
    
       Several error messages could be clearer.
     
    
-
    
-
    
-
    SEE ALSO
    
-
    rndc.conf(5),
-      rndc-confgen(8),
-      named(8),
-      named.conf(5),
-      ndc(8),
+  
    
+
+  
    
+
    SEE ALSO
    
+    
+    
    
+	rndc.conf(5)
+      ,
+      
+	rndc-confgen(8)
+      ,
+      
+	named(8)
+      ,
+      
+	named.conf(5)
+      ,
+      
+	ndc(8)
+      ,
       BIND 9 Administrator Reference Manual.
     
    
-
    
-
    
-
    AUTHOR
    
-
    Internet Systems Consortium
-    
    
-
    
+  
    
+
 
    
 
    
 
    
@@ -788,6 +884,6 @@
 
 
 
    
-
    BIND 9.11.0pre-alpha
    
+
    BIND 9.11.0pre-alpha
    
 
 
diff --git a/doc/arm/managed-keys.xml b/doc/arm/managed-keys.xml
index a33b701d6f..361c25baa7 100644
--- a/doc/arm/managed-keys.xml
+++ b/doc/arm/managed-keys.xml
@@ -1,4 +1,3 @@
-
 
-
-
-
-
-  Dynamic Trust Anchor Management
+
+
    Dynamic Trust Anchor Management
+  
   BIND 9.7.0 introduces support for RFC 5011, dynamic trust
   anchor management. Using this feature allows 
   named to keep track of changes to critical
   DNSSEC keys without any need for the operator to make changes to
   configuration files.
-  
-    Validating Resolver
+  
    Validating Resolver
+    
     
     To configure a validating resolver to use RFC 5011 to
     maintain a trust anchor, configure the trust anchor using a 
     managed-keys statement. Information about
     this can be found in 
-    .
+    .
     
-  
-  
-    Authoritative Server
+  
    
+  
    Authoritative Server
+    
     To set up an authoritative zone for RFC 5011 trust anchor
     maintenance, generate two (or more) key signing keys (KSKs) for
     the zone. Sign the zone with one of them; this is the "active"
@@ -96,5 +93,5 @@ $ dnssec-signzone -S -K keys example.net
     It is expected that a future release of BIND 9 will
     address this problem in a different way, by storing revoked
     keys with their original unrevoked key IDs.
-  
-
+  
    
+
    
diff --git a/doc/arm/notes-wrapper.xml b/doc/arm/notes-wrapper.xml
index 9d31ef8b6d..f35964985e 100644
--- a/doc/arm/notes-wrapper.xml
+++ b/doc/arm/notes-wrapper.xml
@@ -1,8 +1,7 @@
-]>
+]>
 
-
-
    
-  
-  <xi:include href="notes.xml"/>
+<!-- Converted by db4-upgrade version 1.0 -->
+<article xmlns="http://docbook.org/ns/docbook" version="5.0"><info><title/></info>
+  
+  <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="notes.xml"/>
 </article>
-
-<!--
-  - Local variables:
-  - mode: sgml
-  - End:
- -->
diff --git a/doc/arm/notes.conf b/doc/arm/notes.conf
new file mode 100644
index 0000000000..f8dd8326f5
--- /dev/null
+++ b/doc/arm/notes.conf
@@ -0,0 +1,3 @@
+TexInputs: ../tex//
+TexStyle:  notestyle
+XslParam:  ../xsl/notes-param.xsl
diff --git a/doc/arm/notes.html b/doc/arm/notes.html
index c2670d314e..e023618aed 100644
--- a/doc/arm/notes.html
+++ b/doc/arm/notes.html
@@ -17,7 +17,893 @@
 <head>
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
 <title>
-
+
 
-
    <xi:include></xi:include>
    
+
    
+  
+  
    
+
    
+Release Notes for BIND Version 9.11.0pre-alpha
    
+  
+  
    
+
    
+Introduction
    
+    
+    
    
+      This document summarizes changes since the last production release
+      of BIND on the corresponding major release branch.
+    
    
+  
    
+  
    
+
    
+Download
    
+    
+    
    
+      The latest versions of BIND 9 software can always be found at
+      http://www.isc.org/downloads/.
+      There you will find additional information about each release,
+      source code, and pre-compiled versions for Microsoft Windows
+      operating systems.
+    
    
+  
    
+  
    
+
    
+Security Fixes
    
+    
+    
      
+
    • 
+	
      
+	  An incorrect boundary check in the OPENPGPKEY rdatatype
+	  could trigger an assertion failure. This flaw is disclosed
+	  in CVE-2015-5986. [RT #40286]
+	
      
+      
      • 
+
    • 
+	
      
+	  A buffer accounting error could trigger an assertion failure
+	  when parsing certain malformed DNSSEC keys.
+	
      
+	
      
+	  This flaw was discovered by Hanno Böck of the Fuzzing
+	  Project, and is disclosed in CVE-2015-5722. [RT #40212]
+	
      
+      
      • 
+
    • 
+	
      
+	  A specially crafted query could trigger an assertion failure
+	  in message.c.
+	
      
+	
      
+	  This flaw was discovered by Jonathan Foote, and is disclosed
+	  in CVE-2015-5477. [RT #40046]
+	
      
+      
      • 
+
    • 
+	
      
+	  On servers configured to perform DNSSEC validation, an
+	  assertion failure could be triggered on answers from
+	  a specially configured server.
+	
      
+	
      
+	  This flaw was discovered by Breno Silveira Soares, and is
+	  disclosed in CVE-2015-4620. [RT #39795]
+	
      
+      
      • 
+
    • 
+	
      
+	  On servers configured to perform DNSSEC validation using
+	  managed trust anchors (i.e., keys configured explicitly
+	  via managed-keys, or implicitly
+	  via dnssec-validation auto; or
+	  dnssec-lookaside auto;), revoking
+	  a trust anchor and sending a new untrusted replacement
+	  could cause named to crash with an
+	  assertion failure. This could occur in the event of a
+	  botched key rollover, or potentially as a result of a
+	  deliberate attack if the attacker was in position to
+	  monitor the victim's DNS traffic.
+	
      
+	
      
+	  This flaw was discovered by Jan-Piet Mens, and is
+	  disclosed in CVE-2015-1349. [RT #38344]
+	
      
+      
      • 
+
    • 
+	
      
+	  A flaw in delegation handling could be exploited to put
+	  named into an infinite loop, in which
+	  each lookup of a name server triggered additional lookups
+	  of more name servers.  This has been addressed by placing
+	  limits on the number of levels of recursion
+	  named will allow (default 7), and
+	  on the number of queries that it will send before
+	  terminating a recursive query (default 50).
+	
      
+	
      
+	  The recursion depth limit is configured via the
+	  max-recursion-depth option, and the query limit
+	  via the max-recursion-queries option.
+	
      
+	
      
+	  The flaw was discovered by Florian Maury of ANSSI, and is
+	  disclosed in CVE-2014-8500. [RT #37580]
+	
      
+      
      • 
+
    • 
+	
      
+	  Two separate problems were identified in BIND's GeoIP code that
+	  could lead to an assertion failure. One was triggered by use of
+	  both IPv4 and IPv6 address families, the other by referencing
+	  a GeoIP database in named.conf which was
+	  not installed. Both are covered by CVE-2014-8680. [RT #37672]
+	  [RT #37679]
+	
      
+	
      
+	  A less serious security flaw was also found in GeoIP: changes
+	  to the geoip-directory option in
+	  named.conf were ignored when running
+	  rndc reconfig. In theory, this could allow
+	  named to allow access to unintended clients.
+	
      
+      
      • 
+
    
+  
    
+  
    
+
    
+New Features
    
+    
+    
      
+
    • 
+	
      
+	  Added support for DynDB, a new interface for loading zone data
+	  from an external database, developed by Red Hat for the FreeIPA
+	  project.  (Thanks in particular to Adam Tkac and Petr
+	  Spacek of Red Hat for the contribution.)
+	
      
+	
      
+	  Unlike the existing DLZ and SDB interfaces, which provide a
+	  limited subset of database functionality within BIND —
+	  translating DNS queries into real-time database lookups with
+	  relatively poor performance and with no ability to handle
+	  DNSSEC-signed data — DynDB is able to fully implement
+	  and extend the database API used natively by BIND.
+	
      
+	
      
+	  A DynDB module could pre-load data from an external data
+	  source, then serve it with the same performance and
+	  functionality as conventional BIND zones, and with the
+	  ability to take advantage of database features not
+	  available in BIND, such as multi-master replication.
+	
      
+      
      • 
+
    • 
+	
      
+	  New quotas have been added to limit the queries that are
+	  sent by recursive resolvers to authoritative servers
+	  experiencing denial-of-service attacks. When configured,
+	  these options can both reduce the harm done to authoritative
+	  servers and also avoid the resource exhaustion that can be
+	  experienced by recursives when they are being used as a
+	  vehicle for such an attack.
+	
      
+	
        
+
      • 
+	    
        
+	      fetches-per-server limits the number of
+	      simultaneous queries that can be sent to any single
+	      authoritative server.  The configured value is a starting
+	      point; it is automatically adjusted downward if the server is
+	      partially or completely non-responsive. The algorithm used to
+	      adjust the quota can be configured via the
+	      fetch-quota-params option.
+	    
        
+	  
        • 
+
      • 
+	    
        
+	      fetches-per-zone limits the number of
+	      simultaneous queries that can be sent for names within a
+	      single domain.  (Note: Unlike "fetches-per-server", this
+	      value is not self-tuning.)
+	    
        
+	  
        • 
+
      
+	
      
+	  Statistics counters have also been added to track the number
+	  of queries affected by these quotas.
+	
      
+      
      • 
+
    • 
+	
      
+	  Added support for dnstap, a fast,
+	  flexible method for capturing and logging DNS traffic,
+	  developed by Robert Edmonds at Farsight Security, Inc.,
+	  whose assistance is gratefully acknowledged.
+	
      
+	
      
+	  To enable dnstap at compile time, 
+	  the fstrm and protobuf-c
+	  libraries must be available, and BIND must be configured with
+	  --enable-dnstap.
+	
      
+	
      
+	  A new utility dnstap-read has been added
+	  to allow dnstap data to be presented in
+	  a human-readable format.
+	
      
+	
      
+	  For more information on dnstap, see
+	  http://dnstap.info.
+	
      
+      
      • 
+
    • 
+	
      
+	  New statistics counters have been added to track traffic
+	  sizes, as specified in RSSAC002.  Query and response
+	  message sizes are broken up into ranges of histogram buckets:
+	  TCP and UDP queries of size 0-15, 16-31, ..., 272-288, and 288+,
+	  and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
+	  and 4096+.  These values can be accessed via the XML and JSON
+	  statistics channels at, for example,
+	  http://localhost:8888/xml/v3/traffic
+	  or
+	  http://localhost:8888/json/v1/traffic.
+	
      
+      
      • 
+
    • 
+	
      
+	  The serial number of a dynamically updatable zone can
+	  now be set using
+	  rndc signing -serial number zonename.
+	  This is particularly useful with inline-signing
+	  zones that have been reset.  Setting the serial number to a value
+	  larger than that on the slaves will trigger an AXFR-style
+	  transfer.
+	
      
+      
      • 
+
    • 
+	
      
+	  When answering recursive queries, SERVFAIL responses can now be
+	  cached by the server for a limited time; subsequent queries for
+	  the same query name and type will return another SERVFAIL until
+	  the cache times out.  This reduces the frequency of retries
+	  when a query is persistently failing, which can be a burden
+	  on recursive serviers.  The SERVFAIL cache timeout is controlled
+	  by servfail-ttl, which defaults to 10 seconds
+	  and has an upper limit of 30.
+	
      
+      
      • 
+
    • 
+	
      
+	  The new rndc nta command can now be used to
+	  set a "negative trust anchor" (NTA), disabling DNSSEC validation for
+	  a specific domain; this can be used when responses from a domain
+	  are known to be failing validation due to administrative error
+	  rather than because of a spoofing attack. NTAs are strictly
+	  temporary; by default they expire after one hour, but can be
+	  configured to last up to one week.  The default NTA lifetime
+	  can be changed by setting the nta-lifetime in
+	  named.conf. When added, NTAs are stored in a
+	  file (viewname.nta)
+	  in order to persist across restarts of the named server.
+	
      
+      
      • 
+
    • 
+	
      
+	  The EDNS Client Subnet (ECS) option is now supported for
+	  authoritative servers; if a query contains an ECS option then
+	  ACLs containing geoip or ecs
+	  elements can match against the the address encoded in the option.
+	  This can be used to select a view for a query, so that different
+	  answers can be provided depending on the client network.
+	
      
+      
      • 
+
    • 
+	
      
+	  The EDNS EXPIRE option has been implemented on the client
+	  side, allowing a slave server to set the expiration timer
+	  correctly when transferring zone data from another slave
+	  server.
+	
      
+      
      • 
+
    • 
+	
      
+	  A new masterfile-style zone option controls
+	  the formatting of text zone files:  When set to
+	  full, the zone file will dumped in
+	  single-line-per-record format.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +ednsopt can now be used to set
+	  arbitrary EDNS options in DNS requests.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +ednsflags can now be used to set
+	  yet-to-be-defined EDNS flags in DNS requests.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +[no]ednsnegotiation can now be used enable /
+	  disable EDNS version negotiation.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +header-only can now be used to send
+	  queries without a question section.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +ttlunits causes dig
+	  to print TTL values with time-unit suffixes: w, d, h, m, s for
+	  weeks, days, hours, minutes, and seconds.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +zflag can be used to set the last
+	  unassigned DNS header flag bit.  This bit in normally zero.
+	
      
+      
      • 
+
    • 
+	
      
+	  dig +dscp=value
+	  can now be used to set the DSCP code point in outgoing query
+	  packets.
+	
      
+      
      • 
+
    • 
+	
      
+	  serial-update-method can now be set to
+	  date. On update, the serial number will
+	  be set to the current date in YYYYMMDDNN format.
+	
      
+      
      • 
+
    • 
+	
      
+	  dnssec-signzone -N date also sets the serial
+	  number to YYYYMMDDNN.
+	
      
+      
      • 
+
    • 
+	
      
+	  named -L filename
+	  causes named to send log messages to the specified file by
+	  default instead of to the system log.
+	
      
+      
      • 
+
    • 
+	
      
+	  The rate limiter configured by the
+	  serial-query-rate option no longer covers
+	  NOTIFY messages; those are now separately controlled by
+	  notify-rate and
+	  startup-notify-rate (the latter of which
+	  controls the rate of NOTIFY messages sent when the server
+	  is first started up or reconfigured).
+	
      
+      
      • 
+
    • 
+	
      
+	  The default number of tasks and client objects available
+	  for serving lightweight resolver queries have been increased,
+	  and are now configurable via the new lwres-tasks
+	  and lwres-clients options in
+	  named.conf. [RT #35857]
+	
      
+      
      • 
+
    • 
+	
      
+	  Log output to files can now be buffered by specifying
+	  buffered yes; when creating a channel.
+	
      
+      
      • 
+
    • 
+	
      
+	  delv +tcp will exclusively use TCP when
+	  sending queries.
+	
      
+      
      • 
+
    • 
+	
      
+	  named will now check to see whether
+	  other name server processes are running before starting up.
+	  This is implemented in two ways: 1) by refusing to start
+	  if the configured network interfaces all return "address
+	  in use", and 2) by attempting to acquire a lock on a file
+	  specified by the lock-file option or
+	  the -X command line option.  The
+	  default lock file is
+	  /var/run/named/named.lock.
+	  Specifying none will disable the lock
+	  file check.
+	
      
+      
      • 
+
    • 
+	
      
+	  rndc delzone can now be applied to zones
+	  which were configured in named.conf;
+	  it is no longer restricted to zones which were added by
+	  rndc addzone.  (Note, however, that
+	  this does not edit named.conf; the zone
+	  must be removed from the configuration or it will return
+	  when named is restarted or reloaded.)
+	
      
+      
      • 
+
    • 
+	
      
+	  rndc modzone can be used to reconfigure
+	  a zone, using similar syntax to rndc addzone.
+	
      
+      
      • 
+
    • 
+	
      
+	  rndc showzone displays the current
+	  configuration for a specified zone.
+	
      
+      
      • 
+
    • 
+	
      
+	  Added server-side support for pipelined TCP queries.  Clients
+	  may continue sending queries via TCP while previous queries are
+	  processed in parallel.  Responses are sent when they are
+	  ready, not necessarily in the order in which the queries were
+	  received.
+	
      
+	
      
+	  To revert to the former behavior for a particular
+	  client address or range of addresses, specify the address prefix
+	  in the "keep-response-order" option.  To revert to the former
+	  behavior for all clients, use "keep-response-order { any; };".
+	
      
+      
      • 
+
    • 
+	
      
+	  The new mdig command is a version of
+	  dig that sends multiple pipelined
+	  queries and then waits for responses, instead of sending one
+	  query and waiting the response before sending the next. [RT #38261]
+	
      
+      
      • 
+
    • 
+	
      
+	  To enable better monitoring and troubleshooting of RFC 5011
+	  trust anchor management, the new rndc managed-keys
+	  can be used to check status of trust anchors or to force keys
+	  to be refreshed.  Also, the managed-keys data file now has
+	  easier-to-read comments. [RT #38458]
+	
      
+      
      • 
+
    • 
+	
      
+	  An --enable-querytrace configure switch is
+	  now available to enable very verbose query tracelogging. This
+	  option can only be set at compile time. This option has a
+	  negative performance impact and should be used only for
+	  debugging. [RT #37520]
+	
      
+      
      • 
+
    • 
+	
      
+	  A new tcp-only option can be specified
+	  in server statements to force
+	  named to connect to the specified
+	  server via TCP. [RT #37800]
+	
      
+      
      • 
+
    • 
+	
      
+	  The nxdomain-redirect option specifies
+	  a DNS namespace to use for NXDOMAIN redirection. When a
+	  recursive lookup returns NXDOMAIN, a second lookup is
+	  initiated with the specified name appended to the query
+	  name. This allows NXDOMAIN redirection data to be supplied
+	  by multiple zones configured on the server or by recursive
+	  queries to other servers. (The older method, using
+	  a single type redirect zone, has
+	  better average performance but is less flexible.) [RT #37989]
+	
      
+      
      • 
+
    • 
+	
      
+	  The following types have been implemented: CSYNC, NINFO, RKEY,
+	  SINK, TA, TALINK.
+	
      
+      
      • 
+
    
+  
    
+  
    
+
    
+Feature Changes
    
+    
+    
      
+
    • 
+	
      
+	  ACLs containing geoip asnum elements were
+	  not correctly matched unless the full organization name was
+	  specified in the ACL (as in
+	  geoip asnum "AS1234 Example, Inc.";).
+	  They can now match against the AS number alone (as in
+	  geoip asnum "AS1234";).
+	
      
+      
      • 
+
    • 
+	
      
+	  When using native PKCS#11 cryptography (i.e.,
+	  configure --enable-native-pkcs11) HSM PINs
+	  of up to 256 characters can now be used.
+	
      
+      
      • 
+
    • 
+	
      
+	  NXDOMAIN responses to queries of type DS are now cached separately
+	  from those for other types. This helps when using "grafted" zones
+	  of type forward, for which the parent zone does not contain a
+	  delegation, such as local top-level domains.  Previously a query
+	  of type DS for such a zone could cause the zone apex to be cached
+	  as NXDOMAIN, blocking all subsequent queries.  (Note: This
+	  change is only helpful when DNSSEC validation is not enabled.
+	  "Grafted" zones without a delegation in the parent are not a
+	  recommended configuration.)
+	
      
+      
      • 
+
    • 
+	
      
+	  Update forwarding performance has been improved by allowing
+	  a single TCP connection to be shared between multiple updates.
+	
      
+      
      • 
+
    • 
+	
      
+	  By default, nsupdate will now check
+	  the correctness of hostnames when adding records of type
+	  A, AAAA, MX, SOA, NS, SRV or PTR.  This behavior can be
+	  disabled with check-names no.
+	
      
+      
      • 
+
    • 
+	
      
+	  Added support for OPENPGPKEY type.
+	
      
+      
      • 
+
    • 
+	
      
+	  The names of the files used to store managed keys and added
+	  zones for each view are no longer based on the SHA256 hash
+	  of the view name, except when this is necessary because the
+	  view name contains characters that would be incompatible with use
+	  as a file name.  For views whose names do not contain forward
+	  slashes ('/'), backslashes ('\'), or capital letters - which
+	  could potentially cause namespace collision problems on
+	  case-insensitive filesystems - files will now be named
+	  after the view (for example, internal.mkeys
+	  or external.nzf).  However, to ensure
+	  consistent behavior when upgrading, if a file using the old
+	  name format is found to exist, it will continue to be used.
+	
      
+      
      • 
+
    • 
+	
      
+	  "rndc" can now return text output of arbitrary size to
+	  the caller. (Prior to this, certain commands such as
+	  "rndc tsig-list" and "rndc zonestatus" could return
+	  truncated output.)
+	
      
+      
      • 
+
    • 
+	
      
+	  Errors reported when running rndc addzone
+	  (e.g., when a zone file cannot be loaded) have been clarified
+	  to make it easier to diagnose problems.
+	
      
+      
      • 
+
    • 
+	
      
+	  When encountering an authoritative name server whose name is
+	  an alias pointing to another name, the resolver treats
+	  this as an error and skips to the next server. Previously
+	  this happened silently; now the error will be logged to
+	  the newly-created "cname" log category.
+	
      
+      
      • 
+
    • 
+	
      
+	  If named is not configured to validate the answer then
+	  allow fallback to plain DNS on timeout even when we know
+	  the server supports EDNS.  This will allow the server to
+	  potentially resolve signed queries when TCP is being
+	  blocked.
+	
      
+      
      • 
+
    • 
+	
      
+	  Large inline-signing changes should be less disruptive.
+	  Signature generation is now done incrementally; the number
+	  of signatures to be generated in each quantum is controlled
+	  by "sig-signing-signatures number;".
+	  [RT #37927]
+	
      
+      
      • 
+
    • 
+	
      
+	  The experimental SIT option (code point 65001) of BIND
+	  9.10.0 through BIND 9.10.2 has been replaced with the COOKIE
+	  option (code point 10). It is no longer experimental, and
+	  is sent by default, by both named and
+	  dig.
+	
      
+	
      
+	  The SIT-related named.conf options have been marked as
+	  obsolete, and are otherwise ignored.
+	
      
+      
      • 
+
    • 
+	
      
+	  When dig receives a truncated (TC=1)
+	  response or a BADCOOKIE response code from a server, it
+	  will automatically retry the query using the server COOKIE
+	  that was returned by the server in its initial response.
+	  [RT #39047]
+	
      
+      
      • 
+
    • 
+	
      
+	  A alternative NXDOMAIN redirect method (nxdomain-redirect)
+	  which allows the redirect information to be looked up from
+	  a namespace on the Internet rather than requiring a zone
+	  to be configured on the server is now available.
+	
      
+      
      • 
+
    • 
+	
      
+	  Retrieving the local port range from net.ipv4.ip_local_port_range
+	  on Linux is now supported.
+	
      
+      
      • 
+
    • 
+	
      
+	  Within the response-policy option, it is now
+	  possible to configure RPZ rewrite logging on a per-zone basis
+	  using the log clause.
+	
      
+      
      • 
+
    • 
+	
      
+	  The default preferred glue is now the address type of the
+	   transport the query was received over.
+	
      
+      
      • 
+
    • 
+	
      
+	  On machines with 2 or more processors (CPU), the default value
+	  for the number of UDP listeners has been changed to the number
+	  of detected processors minus one.
+	
      
+      
      • 
+
    
+  
    
+  
    
+
    
+Porting Changes
    
+    
+    
    • 
+	
      
+	  The Microsoft Windows install tool
+	  BINDInstall.exe which requires a
+	  non-free version of Visual Studio to be built, now uses two
+	  files (lists of flags and files) created by the Configure
+	  perl script with all the needed information which were
+	  previously compiled in the binary. Read
+	  win32utils/build.txt for more details.
+	  [RT #38915]
+	
      
+      
    
+  
    
+  
    
+
    
+Bug Fixes
    
+    
+    
      
+
    • 
+	
      
+	  dig, host and
+	  nslookup aborted when encountering
+	  a name which, after appending search list elements,
+	  exceeded 255 bytes. Such names are now skipped, but
+	  processing of other names will continue. [RT #36892]
+	
      
+      
      • 
+
    • 
+	
      
+	  The error message generated when
+	  named-checkzone or
+	  named-checkconf -z encounters a
+	  $TTL directive without a value has
+	  been clarified. [RT #37138]
+	
      
+      
      • 
+
    • 
+	
      
+	  Semicolon characters (;) included in TXT records were
+	  incorrectly escaped with a backslash when the record was
+	  displayed as text. This is actually only necessary when there
+	  are no quotation marks. [RT #37159]
+	
      
+      
      • 
+
    • 
+	
      
+	  When files opened for writing by named,
+	  such as zone journal files, were referenced more than once
+	  in named.conf, it could lead to file
+	  corruption as multiple threads wrote to the same file. This
+	  is now detected when loading named.conf
+	  and reported as an error. [RT #37172]
+	
      
+      
      • 
+
    • 
+	
      
+	  When checking for updates to trust anchors listed in
+	  managed-keys, named
+	  now revalidates keys based on the current set of
+	  active trust anchors, without relying on any cached
+	  record of previous validation. [RT #37506]
+	
      
+      
      • 
+
    • 
+	
      
+	  Large-system tuning
+	  (configure --with-tuning=large) caused
+	  problems on some platforms by setting a socket receive
+	  buffer size that was too large.  This is now detected and
+	  corrected at run time. [RT #37187]
+	
      
+      
      • 
+
    • 
+	
      
+	  When NXDOMAIN redirection is in use, queries for a name
+	  that is present in the redirection zone but a type that
+	  is not present will now return NOERROR instead of NXDOMAIN.
+	
      
+      
      • 
+
    • 
+	
      
+	  Due to an inadvertent removal of code in the previous
+	  release, when named encountered an
+	  authoritative name server which dropped all EDNS queries,
+	  it did not always try plain DNS. This has been corrected.
+	  [RT #37965]
+	
      
+      
      • 
+
    • 
+	
      
+	  A regression caused nsupdate to use the default recursive servers
+	  rather than the SOA MNAME server when sending the UPDATE.
+	
      
+      
      • 
+
    • 
+	
      
+	  Adjusted max-recursion-queries to accommodate the smaller
+	  initial packet sizes used in BIND 9.10 and higher when
+	  contacting authoritative servers for the first time.
+	
      
+      
      • 
+
    • 
+	
      
+	  Built-in "empty" zones did not correctly inherit the
+	  "allow-transfer" ACL from the options or view. [RT #38310]
+	
      
+      
      • 
+
    • 
+	
      
+	  Two leaks were fixed that could cause named
+	  processes to grow to very large sizes. [RT #38454]
+	
      
+      
      • 
+
    • 
+	
      
+	  Fixed some bugs in RFC 5011 trust anchor management,
+	  including a memory leak and a possible loss of state
+	  information. [RT #38458]
+	
      
+      
      • 
+
    • 
+	
      
+	  Asynchronous zone loads were not handled correctly when the
+	  zone load was already in progress; this could trigger a crash
+	  in zt.c. [RT #37573]
+	
      
+      
      • 
+
    • 
+	
      
+	  A race during shutdown or reconfiguration could
+	  cause an assertion failure in mem.c. [RT #38979]
+	
      
+      
      • 
+
    • 
+	
      
+	  Some answer formatting options didn't work correctly with
+	  dig +short. [RT #39291]
+	
      
+      
      • 
+
    • 
+	
      
+	  Several bugs have been fixed in the RPZ implementation:
+	
      
+	
        
+
      • 
+	    
        
+	      Policy zones that did not specifically require recursion
+	      could be treated as if they did; consequently, setting
+	      qname-wait-recurse no; was
+	      sometimes ineffective.  This has been corrected.
+	      In most configurations, behavioral changes due to this
+	      fix will not be noticeable. [RT #39229]
+	    
        
+	  
        • 
+
      • 
+	    
        
+	      The server could crash if policy zones were updated (e.g.
+	      via rndc reload or an incoming zone
+	      transfer) while RPZ processing was still ongoing for an
+	      active query. [RT #39415]
+	    
        
+	  
        • 
+
      • 
+	    
        
+	      On servers with one or more policy zones configured as
+	      slaves, if a policy zone updated during regular operation
+	      (rather than at startup) using a full zone reload, such as
+	      via AXFR, a bug could allow the RPZ summary data to fall out
+	      of sync, potentially leading to an assertion failure in
+	      rpz.c when further incremental updates were made to the
+	      zone, such as via IXFR. [RT #39567]
+	    
        
+	  
        • 
+
      • 
+	    
        
+	      The server could match a shorter prefix than what was
+	      available in CLIENT-IP policy triggers, and so, an
+	      unexpected action could be taken. This has been
+	      corrected. [RT #39481]
+	    
        
+	  
        • 
+
      • 
+	    
        
+	      The server could crash if a reload of an RPZ zone was
+	      initiated while another reload of the same zone was
+	      already in progress. [RT #39649]
+	    
        
+	  
        • 
+
      
+      
      • 
+
    
+  
    
+  
    
+
    
+End of Life
    
+    
+    
    
+      The end of life for BIND 9.11 is yet to be determined but
+      will not be before BIND 9.13.0 has been released for 6 months.
+      https://www.isc.org/downloads/software-support-policy/
+    
    
+  
    
+  
    
+
    
+Thank You
    
+    
+    
    
+      Thank you to everyone who assisted us in making this release possible.
+      If you would like to contribute to ISC to assist us in continuing to
+      make quality open source software, please visit our donations page at
+      http://www.isc.org/donate/.
+    
    
+  
    
+
    
+
    
 
diff --git a/doc/arm/notes.pdf b/doc/arm/notes.pdf
index f67d505cf3..5685bc7e8e 100644
Binary files a/doc/arm/notes.pdf and b/doc/arm/notes.pdf differ
diff --git a/doc/arm/notes.xml b/doc/arm/notes.xml
index 9899d2fdc9..08ee48b652 100644
--- a/doc/arm/notes.xml
+++ b/doc/arm/notes.xml
@@ -1,4 +1,8 @@
-
+
+
+
+]>
 
-
-
-  
-  
-    Introduction
+
+
    
+  
+  
    Introduction
+    
     
       This document summarizes changes since the last production release
       of BIND on the corresponding major release branch.
     
-  
-  
-    Download
+  
    
+  
    Download
+    
     
       The latest versions of BIND 9 software can always be found at
-      http://www.isc.org/downloads/.
+      http://www.isc.org/downloads/.
       There you will find additional information about each release,
       source code, and pre-compiled versions for Microsoft Windows
       operating systems.
     
-  
-  
-    Security Fixes
+  
    
+  
    Security Fixes
+    
     
       
 	
@@ -51,7 +54,7 @@
 	  when parsing certain malformed DNSSEC keys.
 	
 	
-	  This flaw was discovered by Hanno B쎶ck of the Fuzzing
+	  This flaw was discovered by Hanno Böck of the Fuzzing
 	  Project, and is disclosed in CVE-2015-5722. [RT #40212]
 	
       
@@ -134,16 +137,16 @@
 	
       
     
-  
-  
-    New Features
+  
    
+  
    New Features
+    
     
       
 	
 	  Added support for DynDB, a new interface for loading zone data
 	  from an external database, developed by Red Hat for the FreeIPA
 	  project.  (Thanks in particular to Adam Tkac and Petr
-	  Špaček of Red Hat for the contribution.)
+	  Spacek of Red Hat for the contribution.)
 	
 	
 	  Unlike the existing DLZ and SDB interfaces, which provide a
@@ -217,7 +220,7 @@
 	
 	
 	  For more information on dnstap, see
-	  http://dnstap.info.
+	  http://dnstap.info.
 	
       
       
@@ -229,11 +232,9 @@
 	  and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
 	  and 4096+.  These values can be accessed via the XML and JSON
 	  statistics channels at, for example,
-	  http://localhost:8888/xml/v3/traffic
+	  http://localhost:8888/xml/v3/traffic
 	  or
-	  http://localhost:8888/json/v1/traffic.
+	  http://localhost:8888/json/v1/traffic.
 	
       
       
@@ -503,9 +504,9 @@
 	
       
     
-  
-  
-    Feature Changes
+  
    
+  
    Feature Changes
+    
     
       
 	
@@ -671,9 +672,9 @@
 	
       
     
-  
-  
-    Porting Changes
+  
    
+  
    Porting Changes
+    
     
       
 	
@@ -688,9 +689,9 @@
 	
       
     
-  
-  
-    Bug Fixes
+  
    
+  
    Bug Fixes
+    
     
       
 	
@@ -865,24 +866,22 @@
 	
       
     
-  
-  
-    End of Life
+  
    
+  
    End of Life
+    
     
       The end of life for BIND 9.11 is yet to be determined but
       will not be before BIND 9.13.0 has been released for 6 months.
-      https://www.isc.org/downloads/software-support-policy/
+      https://www.isc.org/downloads/software-support-policy/
     
-  
-  
-    Thank You
+  
    
+  
    Thank You
+    
     
       Thank you to everyone who assisted us in making this release possible.
       If you would like to contribute to ISC to assist us in continuing to
       make quality open source software, please visit our donations page at
-      http://www.isc.org/donate/.
+      http://www.isc.org/donate/.
     
-  
-
+  
    
+
    
diff --git a/doc/arm/pkcs11.xml b/doc/arm/pkcs11.xml
index 4fd03aa00c..582c2e82a7 100644
--- a/doc/arm/pkcs11.xml
+++ b/doc/arm/pkcs11.xml
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-  PKCS#11 (Cryptoki) support
+
+
    PKCS#11 (Cryptoki) support
+  
   
     PKCS#11 (Public Key Cryptography Standard #11) defines a
     platform-independent API for the control of hardware security
@@ -49,16 +48,16 @@
     OpenSSL completely; BIND loads the provider library itself, and uses
     the PKCS#11 API to drive the HSM directly.
   
-  
-    Prerequisites
+  
    Prerequisites
+    
     
       See the documentation provided by your HSM vendor for
       information about installing, initializing, testing and
       troubleshooting the HSM.
     
-  
-  
-    Native PKCS#11
+  
    
+  
    Native PKCS#11
+    
     
       Native PKCS#11 mode will only work with an HSM capable of carrying
       out every cryptographic operation BIND 9 may
@@ -89,18 +88,18 @@ $ ./configure --enable-native-pkcs11 \
       dnssec-* tools, or the  in
       the pkcs11-* tools.)
     
-    
-      Building SoftHSMv2
+    
    Building SoftHSMv2
+      
       
 	SoftHSMv2, the latest development version of SoftHSM, is available
 	from
-	
+	
 	  https://github.com/opendnssec/SoftHSMv2
-	.
+	.
 	It is a software library developed by the OpenDNSSEC project
-	(
+	(
 	  http://www.opendnssec.org
-	)
+	)
 	which provides a PKCS#11 interface to a virtual HSM, implemented in
 	the form of a SQLite3 database on the local filesystem.  It provides
 	less security than a true HSM, but it allows you to experiment with
@@ -124,10 +123,10 @@ $  make 
 $  make install 
 $  /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 
       
-    
-  
-  
-    OpenSSL-based PKCS#11
+    
    
+  
    
+  
    OpenSSL-based PKCS#11
+    
     
       OpenSSL-based PKCS#11 mode uses a modified version of the
       OpenSSL library; stock OpenSSL does not fully support PKCS#11.
@@ -186,10 +185,10 @@ $  /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label s
       necessary to build OpenSSL with the patch in place, and configure
       it with the path to your HSM's PKCS#11 provider library.
     
-    
-      Patching OpenSSL
+    
    Patching OpenSSL
+      
       
-$ wget http://www.openssl.org/source/openssl-0.9.8zc.tar.gz
+$ wget http://www.openssl.org/source/openssl-0.9.8zc.tar.gz
   
       Extract the tarball:
       
@@ -216,10 +215,10 @@ $ patch -p1 -d openssl-0.9.8zc \
 	Later, when building BIND 9, the location of the custom-built
 	OpenSSL library will need to be specified via configure.
       
-    
-    
+    
    
+    
    Building OpenSSL for the AEP Keyper on Linux
       
-      Building OpenSSL for the AEP Keyper on Linux
+      
       
 	The AEP Keyper is a highly secure key storage device,
 	but does not provide hardware cryptographic acceleration. It
@@ -258,10 +257,10 @@ $ ./Configure linux-generic32 -m32 -pthread \
 	test" fails with "pthread_atfork() not found", you forgot to
 	add the -pthread above.
       
-    
-    
+    
    
+    
    Building OpenSSL for the SCA 6000 on Solaris
       
-      Building OpenSSL for the SCA 6000 on Solaris
+      
       
 	The SCA-6000 PKCS#11 provider is installed as a system
 	library, libpkcs11. It is a true crypto accelerator, up to 4
@@ -287,16 +286,16 @@ $ ./Configure solaris64-x86_64-cc \
 	make and 
 	make test.
       
-    
-    
+    
    
+    
    Building OpenSSL for SoftHSM
       
-      Building OpenSSL for SoftHSM
+      
       
 	SoftHSM (version 1) is a software library developed by the
 	OpenDNSSEC project
-	(
+	(
 	  http://www.opendnssec.org
-	)
+	)
 	which provides a
 	PKCS#11 interface to a virtual HSM, implemented in the form of
 	a SQLite3 database on the local filesystem.  SoftHSM uses
@@ -316,7 +315,7 @@ $  configure --prefix=/opt/pkcs11/usr 
 $  make 
 $  make install 
 $  export SOFTHSM_CONF=/opt/pkcs11/softhsm.conf 
-$  echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF 
+$  echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF 
 $  /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm 
 
       
@@ -336,7 +335,7 @@ $ ./Configure linux-x86_64 -pthread \
 	After configuring, run "make"
 	and "make test".
       
-    
+    
    
     
       Once you have built OpenSSL, run
       "apps/openssl engine pkcs11" to confirm
@@ -363,9 +362,9 @@ $ ./Configure linux-x86_64 -pthread \
       "make install" which will install the
       modified OpenSSL suite to /opt/pkcs11/usr.
     
-    
+    
    Configuring BIND 9 for Linux with the AEP Keyper
       
-      Configuring BIND 9 for Linux with the AEP Keyper
+      
       
 	To link with the PKCS#11 provider, threads must be
 	enabled in the BIND 9 build.
@@ -382,10 +381,10 @@ $ ./configure CC="gcc -m32" --enable-threads \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libpkcs11.so
 
-    
-    
+    
    
+    
    Configuring BIND 9 for Solaris with the SCA 6000
       
-      Configuring BIND 9 for Solaris with the SCA 6000
+      
       
 	To link with the PKCS#11 provider, threads must be
 	enabled in the BIND 9 build.
@@ -404,17 +403,17 @@ $ ./configure CC="cc -xarch=amd64" --enable-threads \
 	same as the --prefix argument to the OpenSSL
 	Configure).
       
-    
-    
+    
    
+    
    Configuring BIND 9 for SoftHSM
       
-      Configuring BIND 9 for SoftHSM
+      
       
 $ cd ../bind9
 $ ./configure --enable-threads \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libsofthsm.so
 
-    
+    
    
     
       After configuring, run
       "make",
@@ -425,9 +424,9 @@ $ ./configure --enable-threads \
       (Note: If "make test" fails in the "pkcs11" system test, you may
       have forgotten to set the SOFTHSM_CONF environment variable.)
     
-  
-  
-    PKCS#11 Tools
+  
    
+  
    PKCS#11 Tools
+    
     
       BIND 9 includes a minimal set of tools to operate the
       HSM, including 
@@ -447,9 +446,9 @@ $ ./configure --enable-threads \
       PKCS11_PROVIDER environment variable to specify the path to the
       provider.)
     
-  
-  
-    Using the HSM
+  
    
+  
    Using the HSM
+    
     
       For OpenSSL-based PKCS#11, we must first set up the runtime
       environment so the OpenSSL and PKCS#11 libraries can be loaded:
@@ -567,9 +566,9 @@ Zone signing complete:
 Algorithm: NSEC3RSASHA1: ZSKs: 1, KSKs: 1 active, 0 revoked, 0 stand-by
 example.net.signed
 
-  
-  
-    Specifying the engine on the command line
+  
    
+  
    Specifying the engine on the command line
+    
     
       When using OpenSSL-based PKCS#11, the "engine" to be used by
       OpenSSL can be specified in named and all of
@@ -598,9 +597,9 @@ $ dnssec-signzone -E '' -S example.net
       different meaning: it specifies the path to the PKCS#11 provider
       library.  This may be useful when testing a new provider library.
     
-  
-  
-    Running named with automatic zone re-signing
+  
    
+  
    Running named with automatic zone re-signing
+    
     
       If you want named to dynamically re-sign zones
       using HSM keys, and/or to to sign new records inserted via nsupdate,
@@ -644,5 +643,5 @@ $ dnssec-signzone -E '' -S example.net
 	do before configuring the system in this way.
       
     
-  
-
+  
    
+
    
diff --git a/doc/tex/.gitignore b/doc/tex/.gitignore
new file mode 100644
index 0000000000..764b6ada73
--- /dev/null
+++ b/doc/tex/.gitignore
@@ -0,0 +1 @@
+armstyle.sty
diff --git a/doc/arm/html-fixup.pl b/doc/tex/Makefile.in
similarity index 75%
rename from doc/arm/html-fixup.pl
rename to doc/tex/Makefile.in
index 2763813601..62a3742daa 100644
--- a/doc/arm/html-fixup.pl
+++ b/doc/tex/Makefile.in
@@ -1,6 +1,4 @@
-#!/usr/bin/perl -w
-#
-# Copyright (C) 2015  Internet Systems Consortium, Inc. ("ISC")
+# Copyright (C) 2005, 2007, 2012, 2014, 2015  Internet Systems Consortium, Inc. ("ISC")
 #
 # Permission to use, copy, modify, and/or distribute this software for any
 # purpose with or without fee is hereby granted, provided that the above
@@ -14,7 +12,14 @@
 # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
 # PERFORMANCE OF THIS SOFTWARE.
 
-while (<>) {
-    s/쎶/ö/;
-    print;
-}
+srcdir =	@srcdir@
+VPATH =		@srcdir@
+top_srcdir =	@top_srcdir@
+
+SUBDIRS =
+TARGETS =
+
+@BIND9_MAKE_RULES@
+
+distclean::
+	rm -f armstyle.sty
diff --git a/doc/tex/armstyle.sty.in b/doc/tex/armstyle.sty.in
new file mode 100644
index 0000000000..0aa766cdef
--- /dev/null
+++ b/doc/tex/armstyle.sty.in
@@ -0,0 +1,107 @@
+%%
+%% This style is derivated from the docbook one
+%%
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{armstyle}[]
+
+%% Just use the original package and pass the options
+\RequirePackageWithOptions{db2latex}
+
+% 2015-09-03 reed -- used with figure
+\usepackage{float}
+
+% For page layout
+\usepackage{geometry}
+
+% don't want date on the cover page
+\let\@date\@empty
+
+% get rid of "Chapter" on start of each chapter
+\def\@makechapterhead#1{%
+  \vspace*{50\p@}%
+  {\parindent \z@ \raggedright \normalfont
+    \ifnum \c@secnumdepth >\m@ne
+      \if@mainmatter
+        \Huge\bfseries\sffamily \thechapter\space\space\space\space%
+      \fi
+    \fi
+    \interlinepenalty\@M
+    \Huge \bfseries \sffamily #1\par\nobreak
+    \vskip 40\p@
+  }}
+
+% for use of \titleformat
+\usepackage{titlesec}
+
+\titleformat*{\section}{\Large\bfseries\scshape\sffamily}
+\titleformat*{\subsection}{\large\bfseries\sffamily}
+
+% Contents font too ; note I don't know what last parts of this are for
+\titleformat{\chapter}{\Huge\bfseries\sffamily}{\thechapter}{1em}{} \vspace{6pt}
+
+% font for the Index headline also
+\titleformat{\index}{\Huge\bfseries\sffamily}{Index}{1em}{} \vspace{6pt}
+
+% following two lines for no indenting paragraphs and spacing between
+\setlength\parskip{\medskipamount}
+\setlength\parindent{0pt}
+
+% fancy footers
+\pagestyle{fancy}
+\fancyfoot[ce,co]{\thepage}
+\fancyfoot[le,ro]{@BIND9_VERSIONSHORT@}
+\renewcommand{\headrulewidth}{0.4 pt}
+\fancypagestyle{plain}{%
+  \fancyhf{}%
+  \fancyfoot[ce,co]{\thepage}%
+  \fancyfoot[le,ro]{@BIND9_VERSIONSHORT@}
+  \renewcommand{\headrulewidth}{0 pt}
+}
+\fancypagestyle{empty}{%
+  \fancyhf{}%
+  \renewcommand{\headrulewidth}{0 pt}
+  \renewcommand{\footrulewidth}{0 pt}
+}
+
+% custom title and copyright pages
+\def\maketitle{
+  \thispagestyle{empty}
+  \null\vfil
+  \vskip 60pt
+  \begin{center}%
+    { %\LARGE
+      \Huge
+      \bfseries
+      \DBKtitle \\
+       \par
+    }
+    \vskip 3em%
+    { %\large
+      \Large
+      \lineskip .75em%
+      @BIND9_VERSIONSTRING@
+      \par
+    }
+    \vfil\null
+    % Not sure exactly how much to trim logo, but given that
+    % this is a centered environment, we need not be too precise
+    % so long as the image is centered in the input PDF, we
+    % trim enough for it to fit on page, and we do not trim
+    % so much that we clip out part of the graphic itself.
+    % This seems to work, anyway.
+    \includegraphics[trim=400 400 400 400,scale=2.5]{isc-logo}
+  \end{center}\par
+  \newpage
+  \thispagestyle{empty}
+  \vfill
+  \DBKcopyright \\
+  \vfill\null
+  \begin{center}
+    Internet Systems Consortium \\
+    950 Charter Street \\
+    Redwood City, California \\
+    USA \\
+    https://www.isc.org/
+  \end{center}
+  \vfil\null
+}
diff --git a/doc/tex/notestyle.sty b/doc/tex/notestyle.sty
new file mode 100644
index 0000000000..6ae2d0caf4
--- /dev/null
+++ b/doc/tex/notestyle.sty
@@ -0,0 +1,17 @@
+%%
+%% This style is derivated from the docbook one
+%%
+\NeedsTeXFormat{LaTeX2e}
+\ProvidesPackage{notestyle}[]
+
+%% Just use the original package and pass the options
+\RequirePackageWithOptions{db2latex}
+
+%% My Cover Page
+\def\maketitle{%
+}
+
+%% Suppress header
+\fancyhead{}
+\renewcommand{\headrulewidth}{0pt}
+\renewcommand{\footrulewidth}{0pt}
diff --git a/doc/xsl/Makefile.in b/doc/xsl/Makefile.in
index e77194c1ad..ed925ca41c 100644
--- a/doc/xsl/Makefile.in
+++ b/doc/xsl/Makefile.in
@@ -23,5 +23,4 @@ TARGETS =
 
 distclean::
 	rm -f isc-docbook-chunk.xsl isc-docbook-html.xsl \
-	      isc-docbook-latex.xsl isc-manpage.xsl \
-	      isc-notes-html.xsl isc-notes-latex.xsl
+	      isc-manpage.xsl isc-notes-html.xsl 
diff --git a/doc/xsl/arm-param.xsl b/doc/xsl/arm-param.xsl
new file mode 100644
index 0000000000..89feb5bf66
--- /dev/null
+++ b/doc/xsl/arm-param.xsl
@@ -0,0 +1,123 @@
+
+
+
+  
+  
+    
+    
+    
+
+    
+      
+      
+      
+    
+  
+
+  
+  
+
+  
+  
+  
+
+  
+  2
+
+  
+  
+
+  
+  
+
+  
+  
+  
+    
+      
+  
+  
+        
+      
+    
+    
+  
+
+  
+  book
+
+  
+  
+  
+  nohyperlink,colorlinks,linkcolor=black,urlcolor=black
+
+  
+  1
+
+  
+  2
+
+  
+  1
+
+  
+  
+  
+  
+   
+  
+  
+   
+  
+  
+   
+  
+
+  
+    
+      
+    
+    \textsf{
+    
+    }
+  
+
+  
+
+  
+  default
+
+  
+  qanda
+
+  
+  5
+  0
+
+  
+  
+  
+   \\
+
+  
+    
+    \def\DBKtitle{
+    
+    }

+
+    \def\DBKcopyright{
+    
+    }

+  
+
+
diff --git a/doc/xsl/copyright.xsl b/doc/xsl/copyright.xsl
index 395f89a111..2a6b35385e 100644
--- a/doc/xsl/copyright.xsl
+++ b/doc/xsl/copyright.xsl
@@ -14,11 +14,12 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-
-
 
 
-
+
 
   
     
@@ -52,20 +53,20 @@
   
     
       
-	
+        
 	  Copyright (C) 
 	  
-	    
+	    
 	  
 	   
-	  
+	  
+          
 	  

 	
 	
       
     
   
-
 
 
 
 
-
-
  
 
-
+
 
   
   
@@ -44,6 +44,10 @@
 
   
    - 
+  
+
+  
+  
 
   
   
@@ -52,8 +56,6 @@
       
     
     

-     $Id$ 
-    

   
 
   
diff --git a/doc/xsl/isc-docbook-html.xsl.in b/doc/xsl/isc-docbook-html.xsl.in
index 6efd5dd433..8b91a29fc2 100644
--- a/doc/xsl/isc-docbook-html.xsl.in
+++ b/doc/xsl/isc-docbook-html.xsl.in
@@ -14,11 +14,11 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-
-
  
 
-
+
 
   
   
@@ -37,6 +37,10 @@
 
   
    - 
+  
+
+  
+  
 
   
   
@@ -45,8 +49,6 @@
       
     
     

-     $Id$ 
-    

   
 
   
diff --git a/doc/xsl/isc-docbook-latex-mappings.xml b/doc/xsl/isc-docbook-latex-mappings.xml
deleted file mode 100644
index 97c7cef810..0000000000
--- a/doc/xsl/isc-docbook-latex-mappings.xml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
-
-
-
-
-  
-    
-      % 

-      % -------------------------------------------------------------

-      % Refentry 

-      % -------------------------------------------------------------

-      \section{%title%}

-      \label{%id%}\hypertarget{%id%}{}%

-    
-  
-
diff --git a/doc/xsl/isc-docbook-latex.xsl.in b/doc/xsl/isc-docbook-latex.xsl.in
deleted file mode 100644
index a9c32621a6..0000000000
--- a/doc/xsl/isc-docbook-latex.xsl.in
+++ /dev/null
@@ -1,205 +0,0 @@
-
-
-
-
-
-
-
-
-  
-  
-
-  
-  
-
-  
-  
-  
-
-  
-  
-  10pt,twoside,openright
-
-  
-  
-  
-
-  
-  
-
-  
-  ansi
-
-  
-  
-
-  
-  
-    
-    
-      , 
-    
-  
-
-  
-  
-
-  
-  % 
-
-  
-  
-    
-    
-  
-
-  
-  
-    
-     \par 
-  
-
-  
-  
-    [
-    
-    ]
-  
-
-  
-  
-    
-      \begin{titlepage}
-        \null\vfil
-        \vskip 60pt
-        \begin{center}%
-          { %\LARGE
-	    \Huge
-	    \bfseries
-            
-	    
-	      
-	    
-            
-            \par}%
-          \vskip 3em%
-          { %\large
-	    \Large
-            \lineskip .75em%
-            
-	    
-	      
-	    
-            
-            \par}
-          %\vskip 1.5em%
-	  \vfil
-	  % Not sure exactly how much to trim logo, but given that
-	  % this is a centered environment, we need not be too precise
-	  % so long as the image is centered in the input PDF, we
-	  % trim enough for it to fit on page, and we do not trim
-	  % so much that we clip out part of the graphic itself.
-	  % This seems to work, anyway.
-	  \includegraphics[trim=400 400 400 400,scale=2.5]{isc-logo}
-        \end{center}\par
-        \vfil\null
-      \end{titlepage}
-    
-    

-  
-
-  
-  
-    
-      \pagestyle{fancy}
-      \fancyfoot[ce,co]{\thepage}
-      \fancyfoot[le,ro]{@BIND9_VERSIONSTRING@}
-      \renewcommand{\headrulewidth}{0.4 pt}
-      \fancypagestyle{plain}{%
-        \fancyhf{}%
-        \fancyfoot[ce,co]{\thepage}%
-        \fancyfoot[le,ro]{@BIND9_VERSIONSTRING@}%
-        \renewcommand{\headrulewidth}{0 pt}
-      }
-    
-  
-
-  
-  
-    \thispagestyle{empty}

-    
-    \begin{center}

-    
-    \end{center}

-    
-      \begin{center}
-      
-      \end{center}

-    
-    
-      \vfill
-      \begin{center}
-      Internet Systems Consortium \\
-      950 Charter Street \\
-      Redwood City, California \\
-      USA \\
-      http://www.isc.org/
-      \end{center}
-    
-    
-      \newpage
-      \pagenumbering{roman}
-      \tableofcontents
-      \newpage
-      \pagenumbering{arabic}
-    
-  
-
-  
-  
-    \mbox{
-    
-    }
-  
-
-
-
-
diff --git a/doc/xsl/isc-docbook-text.xsl b/doc/xsl/isc-docbook-text.xsl
index abca9eaafc..79a945013e 100644
--- a/doc/xsl/isc-docbook-text.xsl
+++ b/doc/xsl/isc-docbook-text.xsl
@@ -14,8 +14,6 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-
-
  
 
 
 
-
-
 
 
-
+
 
   
-  
-  
+  
+
   
   
 
   
   .\" 
+  
 
   
-  
+  
 
   
   ansi
@@ -40,8 +41,6 @@
 
   
   
-    .\"

-    .\" $Id$

     .\"

     .hy 0

     .ad l

diff --git a/doc/xsl/isc-notes-html.xsl.in b/doc/xsl/isc-notes-html.xsl.in
index a9b7e29e75..f5b42f9f01 100644
--- a/doc/xsl/isc-notes-html.xsl.in
+++ b/doc/xsl/isc-notes-html.xsl.in
@@ -16,7 +16,9 @@
 
  
 
-
+
 
   
   
@@ -35,6 +37,10 @@
 
   
    - 
+  
+
+  
+  
 
   
   
diff --git a/doc/xsl/isc-notes-latex.xsl.in b/doc/xsl/isc-notes-latex.xsl.in
deleted file mode 100644
index 721471ccaf..0000000000
--- a/doc/xsl/isc-notes-latex.xsl.in
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
-
-
-
-
-  
-  
-
-  
-  
-
-  
-  
-  
-
-  
-  
-  10pt,twoside,openright
-
-  
-  
-  
-
-  
-  
-
-  
-  ansi
-
-  
-  
-
-  
-  
-    
-    
-      , 
-    
-  
-
-  
-  
-  
-  
-
-  
-  
-  
-
-  
-  a4paper,10pt,twoside,openright
-
-  
-  
-    
-     \par 
-  
-
-  
-  
-    [
-    
-    ]
-  
-
-  
-  
-    \mbox{
-    
-    }
-  
-
-
-
-
diff --git a/doc/xsl/notes-param.xsl b/doc/xsl/notes-param.xsl
new file mode 100644
index 0000000000..8701a6e70d
--- /dev/null
+++ b/doc/xsl/notes-param.xsl
@@ -0,0 +1,28 @@
+
+
+
+
+
+
+
+
diff --git a/doc/xsl/pre-latex.xsl b/doc/xsl/pre-latex.xsl
index 9473556c6a..81d82c5056 100644
--- a/doc/xsl/pre-latex.xsl
+++ b/doc/xsl/pre-latex.xsl
@@ -21,7 +21,9 @@
   - There's probably a better way to do this, but this will work for now.
   --> 
 
-
+
 
   
 
diff --git a/isc-config.sh.docbook b/isc-config.sh.docbook
index dcf2120a79..7a411cc210 100644
--- a/isc-config.sh.docbook
+++ b/isc-config.sh.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
+
+
+  
+    2009-02-18
+  
   
-    February 18, 2009
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -42,19 +43,19 @@
   
 
   
-    
+    
       isc-config.sh
-      
-      
-      
-      
-      
+      
+      
+      
+      
+      
       libraries
     
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     isc-config.sh
 	prints information related to the installed version of ISC BIND,
 	such as the compiler and linker flags required to compile
@@ -74,10 +75,10 @@
 	(Some libraries require other libraries, so are implied.)
     
 
-  
+  
 
-  
-    OPTIONS
+  OPTIONS
+    
 
     
 
@@ -136,25 +137,15 @@
 
     
 
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     isc-config.sh
       returns an exit status of 1 if
       invoked with invalid arguments or no arguments at all.
       It returns 0 if information was successfully printed.
     
-  
+  
 
-  
-    AUTHOR
-    Internet Systems Consortium
-    
-  
-
-
+
diff --git a/lib/lwres/man/lwres.docbook b/lib/lwres/man/lwres.docbook
index 26723e5f0c..2988ac2d0d 100644
--- a/lib/lwres/man/lwres.docbook
+++ b/lib/lwres/man/lwres.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -55,8 +55,8 @@
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       The BIND 9 lightweight resolver library is a simple, name service
       independent stub resolver library.  It provides hostname-to-address
@@ -69,10 +69,10 @@
       The library and resolver daemon communicate using a simple
       UDP-based protocol.
     
-  
+  
 
-  
-    OVERVIEW
+  OVERVIEW
+    
     
       The lwresd library implements multiple name service APIs.
       The standard
@@ -124,9 +124,9 @@
       resolver daemon.  The use of this low-level API in clients
       and servers is outlined in the following sections.
     
-  
-  
-    CLIENT-SIDE LOW-LEVEL API CALL FLOW
+  
+  CLIENT-SIDE LOW-LEVEL API CALL FLOW
+    
     
       When a client program wishes to make an lwres request using the
       native low-level API, it typically performs the following
@@ -137,23 +137,23 @@
       called pkt below.
     
     
-      (2) Set pkt.recvlength to the maximum length
+      (2) Set pkt.recvlength to the maximum length
       we will accept.
       This is done so the receiver of our packets knows how large our receive
       buffer is.  The "default" is a constant in
       lwres.h: LWRES_RECVLENGTH = 4096.
     
     
-      (3) Set pkt.serial
+      (3) Set pkt.serial
       to a unique serial number.  This value is echoed
       back to the application by the remote server.
     
     
-      (4) Set pkt.pktflags.  Usually this is set to
+      (4) Set pkt.pktflags.  Usually this is set to
       0.
     
     
-      (5) Set pkt.result to 0.
+      (5) Set pkt.result to 0.
     
     
       (6) Call lwres_*request_render(),
@@ -172,9 +172,9 @@
       (9) Verify that the opcode and serial match a request, and process the
       packet specific information contained in the body.
     
-  
-  
-    SERVER-SIDE LOW-LEVEL API CALL FLOW
+  
+  SERVER-SIDE LOW-LEVEL API CALL FLOW
+    
     
       When implementing the server side of the lightweight resolver
       protocol using the lwres library, a sequence of actions like the
@@ -197,12 +197,12 @@
       (2) Process the request in the data specific type.
     
     
-      (3) Set the pkt.result,
-      pkt.recvlength as above.  All other fields
+      (3) Set the pkt.result,
+      pkt.recvlength as above.  All other fields
       can
       be left untouched since they were filled in by the *_parse() call
       above.  If using lwres_*response_render(),
-      pkt.pktflags will be set up
+      pkt.pktflags will be set up
       properly.  Otherwise, the LWRES_LWPACKETFLAG_RESPONSE bit should be
       set.
     
@@ -213,10 +213,10 @@
     
       (5) Send the resulting packet to the client.
     
-    
-  
-  
-    SEE ALSO
+    
+  
+  SEE ALSO
+    
     
         lwres_gethostent3
       ,
@@ -258,9 +258,5 @@
       .
 
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_buffer.docbook b/lib/lwres/man/lwres_buffer.docbook
index 17ccbf549f..1377ae66ce 100644
--- a/lib/lwres/man/lwres_buffer.docbook
+++ b/lib/lwres/man/lwres_buffer.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -199,9 +200,9 @@ void
 
   
 
-  
+  DESCRIPTION
 
-    DESCRIPTION
+    
     
       These functions provide bounds checked access to a region of memory
       where data is being read or written.
@@ -302,23 +303,23 @@ void
       checks for underflow.
       These functions do not allocate or deallocate memory.
       They just change the value of
-      used.
+      used.
     
     
       A buffer is re-initialised by
       lwres_buffer_clear().
       The function sets
-      used,
-      current
+      used,
+      current
       and
-      active
+      active
       to zero.
     
     lwres_buffer_first
       makes the consumed region of buffer
       *p
       empty by setting
-      current
+      current
       to zero (the start of the buffer).
     
     lwres_buffer_forward()
@@ -386,9 +387,5 @@ void
       to
       base.
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_config.docbook b/lib/lwres/man/lwres_config.docbook
index 5af37eaf7c..0ad795f3a2 100644
--- a/lib/lwres/man/lwres_config.docbook
+++ b/lib/lwres/man/lwres_config.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
+
+
+  
+    2007-06-18
+  
   
-
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -92,8 +92,8 @@ lwres_conf_t *
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_conf_init()
       creates an empty
@@ -128,10 +128,10 @@ lwres_conf_t *
       FILE
       fp.
     
-  
-  
+  
+  RETURN VALUES
 
-    RETURN VALUES
+    
 
     lwres_conf_parse()
       returns LWRES_R_SUCCESS
@@ -150,9 +150,9 @@ lwres_conf_t *
       If this happens, the function returns
       LWRES_R_FAILURE.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         stdio3
       ,
@@ -160,14 +160,10 @@ lwres_conf_t *
         resolver5
       .
     
-  
-  
-    FILES
+  
+  FILES
+    
     /etc/resolv.conf
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_context.docbook b/lib/lwres/man/lwres_context.docbook
index e0a45eecf3..e100c6579d 100644
--- a/lib/lwres/man/lwres_context.docbook
+++ b/lib/lwres/man/lwres_context.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -115,8 +117,8 @@ void *
       
 
   
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_context_create()
       creates a lwres_context_t structure for use in
@@ -212,10 +214,10 @@ void *
       written to this receive buffer is returned in
       *recvd_len.
     
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
 
     lwres_context_create()
       returns LWRES_R_NOMEMORY if memory for
@@ -239,9 +241,9 @@ void *
       lwres_context_sendrecv()
       times out waiting for a response.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres_conf_init3
       ,
@@ -254,9 +256,5 @@ void *
         free3
       .
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_gabn.docbook b/lib/lwres/man/lwres_gabn.docbook
index 8743696c12..3f7fc8d475 100644
--- a/lib/lwres/man/lwres_gabn.docbook
+++ b/lib/lwres/man/lwres_gabn.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -109,8 +111,8 @@ void
       
 
   
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       These are low-level routines for creating and parsing
       lightweight resolver name-to-address lookup request and
@@ -207,9 +209,9 @@ typedef struct {
       Any memory associated with ancillary buffers and strings for
       those structures is also discarded.
     
-  
-  
-    RETURN VALUES
+  
+  RETURN VALUES
+    
     
       The getaddrbyname opcode functions
       lwres_gabnrequest_render(),
@@ -240,21 +242,17 @@ typedef struct {
       These functions will return
       LWRES_R_FAILURE
       if
-      pktflags
+      pktflags
       in the packet header structure
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres_packet3
       
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_gai_strerror.docbook b/lib/lwres/man/lwres_gai_strerror.docbook
index a9314d3199..61636fa025 100644
--- a/lib/lwres/man/lwres_gai_strerror.docbook
+++ b/lib/lwres/man/lwres_gai_strerror.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -62,8 +62,8 @@ char *
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_gai_strerror()
       returns an error message corresponding to an error code returned by
@@ -172,10 +172,10 @@ char *
       used by
       lwres_getaddrinfo().
     
-  
+  
 
-  
-    SEE ALSO
+  SEE ALSO
+    
     
         strerror3
       ,
@@ -192,9 +192,5 @@ char *
         RFC2133
       .
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_getaddrinfo.docbook b/lib/lwres/man/lwres_getaddrinfo.docbook
index 76927fd822..a7cdc0938a 100644
--- a/lib/lwres/man/lwres_getaddrinfo.docbook
+++ b/lib/lwres/man/lwres_getaddrinfo.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -92,8 +94,8 @@ struct  addrinfo {
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_getaddrinfo()
       is used to get a list of IP addresses and port numbers for host
@@ -316,10 +318,10 @@ struct  addrinfo {
       lwres_getaddrinfo().
     
 
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
 
     lwres_getaddrinfo()
       returns zero on success or one of the error codes listed in
@@ -331,9 +333,9 @@ struct  addrinfo {
       lwres_getaddrinfo() returns
       EAI_NONAME.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres3
       ,
@@ -379,9 +381,5 @@ struct  addrinfo {
       .
     
 
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_gethostent.docbook b/lib/lwres/man/lwres_gethostent.docbook
index 487fb7f9ea..8dd999ffa3 100644
--- a/lib/lwres/man/lwres_gethostent.docbook
+++ b/lib/lwres/man/lwres_gethostent.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -146,8 +148,8 @@ void
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       These functions provide hostname-to-address and
       address-to-hostname lookups by means of the lightweight resolver.
@@ -306,10 +308,10 @@ struct  hostent {
       struct hostent() it created.
     
 
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     
       The functions
       lwres_gethostbyname(),
@@ -391,9 +393,9 @@ struct  hostent {
       errno to ERANGE.
     
 
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         gethostent3
       ,
@@ -406,10 +408,10 @@ struct  hostent {
         lwres_hstrerror3
       
     
-  
+  
 
-  
-    BUGS
+  BUGS
+    
     lwres_gethostbyname(),
       lwres_gethostbyname2(),
       lwres_gethostbyaddr()
@@ -431,9 +433,5 @@ struct  hostent {
       NIS,
       consequently the above functions don't, either.
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_getipnode.docbook b/lib/lwres/man/lwres_getipnode.docbook
index 44b628b558..06e358ccdf 100644
--- a/lib/lwres/man/lwres_getipnode.docbook
+++ b/lib/lwres/man/lwres_getipnode.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -82,8 +82,8 @@ void
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     
       These functions perform thread safe, protocol independent
@@ -236,9 +236,9 @@ struct  hostent {
       h_aliases is freed, as is the memory for
       the hostent structure itself.
     
-  
-  
-    RETURN VALUES
+  
+  RETURN VALUES
+    
     
       If an error occurs,
       lwres_getipnodebyname()
@@ -296,9 +296,9 @@ struct  hostent {
       
       translates these error codes to suitable error messages.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         RFC2553
       ,
@@ -323,9 +323,5 @@ struct  hostent {
         lwres_hstrerror3
       .
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_getnameinfo.docbook b/lib/lwres/man/lwres_getnameinfo.docbook
index 34a72cb884..92fd66f0b6 100644
--- a/lib/lwres/man/lwres_getnameinfo.docbook
+++ b/lib/lwres/man/lwres_getnameinfo.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -69,8 +69,8 @@ int
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     
        This function is equivalent to the
@@ -158,16 +158,16 @@ int
         
       
     
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     lwres_getnameinfo()
       returns 0 on success or a non-zero error code if an error occurs.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         RFC2133
       ,
@@ -187,9 +187,9 @@ int
         lwres_net_ntop3
       .
     
-  
-  
-    BUGS
+  
+  BUGS
+    
     
       RFC2133 fails to define what the nonzero return values of
       
@@ -197,9 +197,5 @@ int
       
       are.
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_getrrsetbyname.docbook b/lib/lwres/man/lwres_getrrsetbyname.docbook
index aceb5a1f9f..0cea4f6951 100644
--- a/lib/lwres/man/lwres_getrrsetbyname.docbook
+++ b/lib/lwres/man/lwres_getrrsetbyname.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -97,8 +97,8 @@ struct  rrsetinfo {
     
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     lwres_getrrsetbyname()
       gets a set of resource records associated with a
       hostname, class,
@@ -143,10 +143,10 @@ struct  rrsetinfo {
       rrset created by a call to
       lwres_getrrsetbyname().
     
-    
-  
-  
-    RETURN VALUES
+    
+  
+  RETURN VALUES
+    
     lwres_getrrsetbyname()
       returns zero on success, and one of the following error codes if
       an error occurred:
@@ -200,24 +200,20 @@ struct  rrsetinfo {
         
           
           
-            
+            
           
         
 
       
 
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres3
       .
     
 
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_gnba.docbook b/lib/lwres/man/lwres_gnba.docbook
index ebb7487b03..098ec2bbc1 100644
--- a/lib/lwres/man/lwres_gnba.docbook
+++ b/lib/lwres/man/lwres_gnba.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -121,8 +123,8 @@ void
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       These are low-level routines for creating and parsing
       lightweight resolver address-to-name lookup request and
@@ -207,10 +209,10 @@ typedef struct {
       ancillary buffers and strings for those structures is also
       discarded.
     
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     
       The getnamebyaddr opcode functions
       lwres_gnbarequest_render(),
@@ -241,21 +243,17 @@ typedef struct {
       These functions will return
       LWRES_R_FAILURE
       if
-      pktflags
+      pktflags
       in the packet header structure
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres_packet3
       .
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_hstrerror.docbook b/lib/lwres/man/lwres_hstrerror.docbook
index d091b347da..0786194046 100644
--- a/lib/lwres/man/lwres_hstrerror.docbook
+++ b/lib/lwres/man/lwres_hstrerror.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -68,8 +68,8 @@ const char *
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_herror()
       prints the string s on
@@ -121,10 +121,10 @@ const char *
         
       
     
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     
       The string Unknown resolver error is returned by
       lwres_hstrerror()
@@ -132,9 +132,9 @@ const char *
       lwres_h_errno
       is not a valid error code.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         herror3
       ,
@@ -144,9 +144,5 @@ const char *
       .
     
 
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_inetntop.docbook b/lib/lwres/man/lwres_inetntop.docbook
index b2d170f297..6bc33cd063 100644
--- a/lib/lwres/man/lwres_inetntop.docbook
+++ b/lib/lwres/man/lwres_inetntop.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -64,8 +66,8 @@ const char *
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_net_ntop()
       converts an IP address of protocol family
@@ -84,9 +86,9 @@ const char *
       ASCII representation of the address.
     
 
-  
-  
-    RETURN VALUES
+  
+  RETURN VALUES
+    
 
     
       If successful, the function returns dst:
@@ -99,9 +101,9 @@ const char *
       supported.
     
 
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         RFC1884
       ,
@@ -112,9 +114,5 @@ const char *
         errno3
       .
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_noop.docbook b/lib/lwres/man/lwres_noop.docbook
index 8f40990b47..751ab69109 100644
--- a/lib/lwres/man/lwres_noop.docbook
+++ b/lib/lwres/man/lwres_noop.docbook
@@ -1,6 +1,5 @@
-]>
+]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -110,8 +112,8 @@ void
       
 
   
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       These are low-level routines for creating and parsing
       lightweight resolver no-op request and response messages.
@@ -201,9 +203,9 @@ typedef struct {
       structp.
     
 
-  
-  
-    RETURN VALUES
+  
+  RETURN VALUES
+    
     
       The no-op opcode functions
       lwres_nooprequest_render(),
@@ -240,16 +242,12 @@ typedef struct {
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres_packet3
       
     
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_packet.docbook b/lib/lwres/man/lwres_packet.docbook
index b946263502..7e4a80ecc3 100644
--- a/lib/lwres/man/lwres_packet.docbook
+++ b/lib/lwres/man/lwres_packet.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -69,8 +69,8 @@ lwres_result_t
       
 
   
-  
-    DESCRIPTION
+  DESCRIPTION
+    
     
       These functions rely on a
       struct lwres_lwpacket
@@ -268,10 +268,10 @@ struct lwres_lwpacket {
       lwres_lwpacket_t.
     
 
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     
       Successful calls to
       lwres_lwpacket_renderheader() and
@@ -283,9 +283,5 @@ struct lwres_lwpacket {
       return LWRES_R_UNEXPECTEDEND.
     
 
-  
-
+  
+
diff --git a/lib/lwres/man/lwres_resutil.docbook b/lib/lwres/man/lwres_resutil.docbook
index 0a0c4704aa..4fa3733ecf 100644
--- a/lib/lwres/man/lwres_resutil.docbook
+++ b/lib/lwres/man/lwres_resutil.docbook
@@ -1,6 +1,3 @@
-]>
 
-
-
-
+
+
+  
+    2007-06-18
+  
   
-    June 18, 2007
+    ISC
+    Internet Systems Consortium, Inc.
   
 
   
@@ -92,8 +92,8 @@ lwres_result_t
 
   
 
-  
-    DESCRIPTION
+  DESCRIPTION
+    
 
     lwres_string_parse()
       retrieves a DNS-encoded string starting the current pointer of
@@ -176,10 +176,10 @@ typedef struct {
       function call is made available through
       *structp.
     
-  
+  
 
-  
-    RETURN VALUES
+  RETURN VALUES
+    
     
       Successful calls to
       lwres_string_parse()
@@ -218,9 +218,9 @@ typedef struct {
       small.
     
 
-  
-  
-    SEE ALSO
+  
+  SEE ALSO
+    
     
         lwres_buffer3
       ,
@@ -230,9 +230,5 @@ typedef struct {
       .
     
 
-  
-
+  
+
diff --git a/make/rules.in b/make/rules.in
index 1a8e9ac917..f95d2bd49d 100644
--- a/make/rules.in
+++ b/make/rules.in
@@ -311,6 +311,7 @@ XSLTPROC =		@XSLTPROC@ --novalid --xinclude --nonet
 PERL =			@PERL@
 LATEX =			@LATEX@
 PDFLATEX =		@PDFLATEX@
+DBLATEX =		@DBLATEX@
 W3M =			@W3M@
 
 ###