From 50f00fc38602de835fbf5f8fe1c6429df3788b37 Mon Sep 17 00:00:00 2001 From: Tinderbox User Date: Wed, 7 Oct 2015 04:17:56 +0000 Subject: [PATCH] regen v9_9 --- bin/check/named-checkconf.8 | 4 +- bin/check/named-checkconf.html | 133 +- bin/check/named-checkzone.8 | 6 +- bin/check/named-checkzone.html | 289 +- bin/confgen/ddns-confgen.8 | 4 +- bin/confgen/ddns-confgen.html | 127 +- bin/confgen/rndc-confgen.8 | 4 +- bin/confgen/rndc-confgen.html | 158 +- bin/dig/dig.1 | 8 +- bin/dig/dig.html | 590 ++-- bin/dig/host.1 | 7 +- bin/dig/host.html | 139 +- bin/dig/nslookup.1 | 5 +- bin/dig/nslookup.html | 292 +- bin/dnssec/dnssec-dsfromkey.8 | 8 +- bin/dnssec/dnssec-dsfromkey.html | 220 +- bin/dnssec/dnssec-importkey.8 | 6 +- bin/dnssec/dnssec-importkey.html | 159 +- bin/dnssec/dnssec-keyfromlabel.8 | 4 +- bin/dnssec/dnssec-keyfromlabel.html | 297 +- bin/dnssec/dnssec-keygen.8 | 4 +- bin/dnssec/dnssec-keygen.html | 342 +-- bin/dnssec/dnssec-revoke.8 | 4 +- bin/dnssec/dnssec-revoke.html | 116 +- bin/dnssec/dnssec-settime.8 | 4 +- bin/dnssec/dnssec-settime.html | 206 +- bin/dnssec/dnssec-signzone.8 | 4 +- bin/dnssec/dnssec-signzone.html | 409 +-- bin/dnssec/dnssec-verify.8 | 4 +- bin/dnssec/dnssec-verify.html | 120 +- bin/named/lwresd.8 | 34 +- bin/named/lwresd.html | 222 +- bin/named/named.8 | 79 +- bin/named/named.conf.5 | 4 +- bin/named/named.conf.html | 194 +- bin/named/named.html | 307 +- bin/nsupdate/nsupdate.1 | 7 +- bin/nsupdate/nsupdate.html | 398 +-- bin/python/dnssec-checkds.8 | 6 +- bin/python/dnssec-checkds.html | 107 +- bin/python/dnssec-coverage.8 | 4 +- bin/python/dnssec-coverage.html | 126 +- bin/rndc/rndc.8 | 7 +- bin/rndc/rndc.conf.5 | 4 +- bin/rndc/rndc.conf.html | 118 +- bin/rndc/rndc.html | 362 +-- bin/tools/arpaname.1 | 4 +- bin/tools/arpaname.html | 48 +- bin/tools/genrandom.8 | 4 +- bin/tools/genrandom.html | 87 +- bin/tools/isc-hmac-fixup.8 | 4 +- bin/tools/isc-hmac-fixup.html | 64 +- bin/tools/named-journalprint.8 | 4 +- bin/tools/named-journalprint.html | 61 +- bin/tools/nsec3hash.8 | 4 +- bin/tools/nsec3hash.html | 86 +- doc/arm/Bv9ARM.ch01.html | 256 +- doc/arm/Bv9ARM.ch02.html | 76 +- doc/arm/Bv9ARM.ch03.html | 287 +- doc/arm/Bv9ARM.ch04.html | 1104 +++----- doc/arm/Bv9ARM.ch05.html | 48 +- doc/arm/Bv9ARM.ch06.html | 3413 +++++++++-------------- doc/arm/Bv9ARM.ch07.html | 93 +- doc/arm/Bv9ARM.ch08.html | 73 +- doc/arm/Bv9ARM.ch09.html | 236 +- doc/arm/Bv9ARM.ch10.html | 45 +- doc/arm/Bv9ARM.ch11.html | 965 ++----- doc/arm/Bv9ARM.ch12.html | 281 +- doc/arm/Bv9ARM.ch13.html | 36 +- doc/arm/Bv9ARM.html | 236 +- doc/arm/man.arpaname.html | 48 +- doc/arm/man.ddns-confgen.html | 127 +- doc/arm/man.dig.html | 590 ++-- doc/arm/man.dnssec-checkds.html | 107 +- doc/arm/man.dnssec-coverage.html | 126 +- doc/arm/man.dnssec-dsfromkey.html | 220 +- doc/arm/man.dnssec-importkey.html | 159 +- doc/arm/man.dnssec-keyfromlabel.html | 297 +- doc/arm/man.dnssec-keygen.html | 342 +-- doc/arm/man.dnssec-revoke.html | 116 +- doc/arm/man.dnssec-settime.html | 206 +- doc/arm/man.dnssec-signzone.html | 409 +-- doc/arm/man.dnssec-verify.html | 120 +- doc/arm/man.genrandom.html | 87 +- doc/arm/man.host.html | 139 +- doc/arm/man.isc-hmac-fixup.html | 64 +- doc/arm/man.lwresd.html | 222 +- doc/arm/man.named-checkconf.html | 133 +- doc/arm/man.named-checkzone.html | 289 +- doc/arm/man.named-journalprint.html | 61 +- doc/arm/man.named.conf.html | 194 +- doc/arm/man.named.html | 307 +- doc/arm/man.nsec3hash.html | 86 +- doc/arm/man.nsupdate.html | 398 +-- doc/arm/man.rndc-confgen.html | 158 +- doc/arm/man.rndc.conf.html | 118 +- doc/arm/man.rndc.html | 362 +-- doc/arm/notes.html | 226 +- isc-config.sh.1 | 4 +- isc-config.sh.html | 99 +- lib/lwres/man/lwres.3 | 5 +- lib/lwres/man/lwres.html | 149 +- lib/lwres/man/lwres_buffer.3 | 8 +- lib/lwres/man/lwres_buffer.html | 131 +- lib/lwres/man/lwres_config.3 | 8 +- lib/lwres/man/lwres_config.html | 99 +- lib/lwres/man/lwres_context.3 | 5 +- lib/lwres/man/lwres_context.html | 119 +- lib/lwres/man/lwres_gabn.3 | 8 +- lib/lwres/man/lwres_gabn.html | 93 +- lib/lwres/man/lwres_gai_strerror.3 | 5 +- lib/lwres/man/lwres_gai_strerror.html | 134 +- lib/lwres/man/lwres_getaddrinfo.3 | 8 +- lib/lwres/man/lwres_getaddrinfo.html | 183 +- lib/lwres/man/lwres_gethostent.3 | 5 +- lib/lwres/man/lwres_gethostent.html | 201 +- lib/lwres/man/lwres_getipnode.3 | 5 +- lib/lwres/man/lwres_getipnode.html | 189 +- lib/lwres/man/lwres_getnameinfo.3 | 8 +- lib/lwres/man/lwres_getnameinfo.html | 137 +- lib/lwres/man/lwres_getrrsetbyname.3 | 5 +- lib/lwres/man/lwres_getrrsetbyname.html | 111 +- lib/lwres/man/lwres_gnba.3 | 8 +- lib/lwres/man/lwres_gnba.html | 99 +- lib/lwres/man/lwres_hstrerror.3 | 5 +- lib/lwres/man/lwres_hstrerror.html | 103 +- lib/lwres/man/lwres_inetntop.3 | 5 +- lib/lwres/man/lwres_inetntop.html | 73 +- lib/lwres/man/lwres_noop.3 | 8 +- lib/lwres/man/lwres_noop.html | 96 +- lib/lwres/man/lwres_packet.3 | 8 +- lib/lwres/man/lwres_packet.html | 144 +- lib/lwres/man/lwres_resutil.3 | 5 +- lib/lwres/man/lwres_resutil.html | 103 +- 134 files changed, 7369 insertions(+), 13885 deletions(-) diff --git a/bin/check/named-checkconf.8 b/bin/check/named-checkconf.8 index 83090ea287..cab8e22f8a 100644 --- a/bin/check/named-checkconf.8 +++ b/bin/check/named-checkconf.8 @@ -18,7 +18,7 @@ '\" t .\" Title: named-checkconf .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-01-10 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" named-checkconf \- named configuration file syntax checking tool .SH "SYNOPSIS" -.HP 16 +.HP \w'\fBnamed\-checkconf\fR\ 'u \fBnamed\-checkconf\fR [\fB\-h\fR] [\fB\-v\fR] [\fB\-j\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] {filename} [\fB\-p\fR] [\fB\-x\fR] [\fB\-z\fR] .SH "DESCRIPTION" .PP diff --git a/bin/check/named-checkconf.html b/bin/check/named-checkconf.html index eb0c8da1fb..89524ab0db 100644 --- a/bin/check/named-checkconf.html +++ b/bin/check/named-checkconf.html @@ -18,51 +18,28 @@ named-checkconf - + -
+
- - - - - - - -
+

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 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 parser contexts, such as rndc.key and bind.keys, are not automatically read @@ -72,44 +49,32 @@ 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. -

-
+

-v
-
-

+

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 @@ -117,52 +82,36 @@ 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.

-
+
diff --git a/bin/check/named-checkzone.8 b/bin/check/named-checkzone.8 index f226293616..3f8ca0550d 100644 --- a/bin/check/named-checkzone.8 +++ b/bin/check/named-checkzone.8 @@ -18,7 +18,7 @@ '\" t .\" Title: named-checkzone .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-04-29 .\" Manual: BIND9 .\" Source: ISC @@ -47,9 +47,9 @@ .SH "NAME" named-checkzone, named-compilezone \- zone file validity checking or converting tool .SH "SYNOPSIS" -.HP 16 +.HP \w'\fBnamed\-checkzone\fR\ 'u \fBnamed\-checkzone\fR [\fB\-d\fR] [\fB\-h\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-M\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-o\ \fR\fB\fIfilename\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-S\ \fR\fB\fImode\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {zonename} {filename} -.HP 18 +.HP \w'\fBnamed\-compilezone\fR\ 'u \fBnamed\-compilezone\fR [\fB\-d\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-C\ \fR\fB\fImode\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {\fB\-o\ \fR\fB\fIfilename\fR\fR} {zonename} {filename} .SH "DESCRIPTION" .PP diff --git a/bin/check/named-checkzone.html b/bin/check/named-checkzone.html index c51c349675..1008abf545 100644 --- a/bin/check/named-checkzone.html +++ b/bin/check/named-checkzone.html @@ -18,94 +18,28 @@ named-checkzone - + -
+
- - - - - - - -
+

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] - [-i mode] - [-k mode] - [-m mode] - [-M mode] - [-n mode] - [-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] - [-i mode] - [-k mode] - [-m mode] - [-n mode] - [-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] [-i mode] [-k mode] [-m mode] [-M mode] [-n mode] [-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] [-i mode] [-k mode] [-m mode] [-n mode] [-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 checking zone files before configuring them into a name server.

-

+

named-compilezone is similar to named-checkzone, but it always dumps the zone contents to a specified file in a specified format. @@ -116,53 +50,38 @@ least be as strict as those specified in the 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 program and exit. -

-
+

-j
-
-

+

When loading the zone file read the journal if it exists. -

-
+

-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", @@ -170,19 +89,19 @@ "local-sibling" and "none".

-

+

Mode "full" checks that MX records refer to A or AAAA record (both in-zone and out-of-zone hostnames). Mode "local" only checks MX records which refer to in-zone hostnames.

-

+

Mode "full" checks that SRV records refer to A or AAAA record (both in-zone and out-of-zone hostnames). Mode "local" only checks SRV records which refer to in-zone hostnames.

-

+

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 @@ -191,33 +110,31 @@ 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 "none" disables the checks.

-
+
-f format
-
-

+

Specify the format of the zone file. Possible formats are "text" (default) and "raw". -

-
+

-F format
-

+

Specify the format of the output file specified. For named-checkzone, this does not cause any effects unless it dumps the zone contents.

-

+

Possible formats are "text" (default) and "raw" or "raw=N", which store the zone in a binary format for rapid loading @@ -227,10 +144,9 @@ 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 specified failure mode. Possible modes are "fail" @@ -238,37 +154,29 @@ "warn" (default for named-checkzone) and "ignore". -

-
+

-L serial
-
-

+

When compiling a zone to 'raw' 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". -

-
+

-M mode
-
-

+

Check if a MX record refers to a CNAME. 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" @@ -276,30 +184,24 @@ "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. -

-
+

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

-
+

-s style
-
-

+

Specify the style of the dumped zone file. Possible styles are "full" (default) and "relative". @@ -312,101 +214,74 @@ 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". -

-
+

-t directory
-
-

+

Chroot to directory so that include directives in the configuration file are processed as if 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". -

-
+

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

-
+

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

-
- +
diff --git a/bin/confgen/ddns-confgen.8 b/bin/confgen/ddns-confgen.8 index e5ba45e698..aa40e4edc7 100644 --- a/bin/confgen/ddns-confgen.8 +++ b/bin/confgen/ddns-confgen.8 @@ -17,7 +17,7 @@ '\" t .\" Title: ddns-confgen .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-09-18 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" ddns-confgen \- ddns key generation tool .SH "SYNOPSIS" -.HP 13 +.HP \w'\fBddns\-confgen\fR\ 'u \fBddns\-confgen\fR [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-h\fR] [\fB\-k\ \fR\fB\fIkeyname\fR\fR] [\fB\-r\ \fR\fB\fIrandomfile\fR\fR] [\-s\ \fIname\fR | \-z\ \fIzone\fR] [\fB\-q\fR] [name] .SH "DESCRIPTION" .PP diff --git a/bin/confgen/ddns-confgen.html b/bin/confgen/ddns-confgen.html index e8e0f9dd26..6d07957873 100644 --- a/bin/confgen/ddns-confgen.html +++ b/bin/confgen/ddns-confgen.html @@ -17,46 +17,21 @@ ddns-confgen - + -
+
- - - - - -
+

Name

-

- ddns-confgen - — ddns key generation tool -

+

ddns-confgen — ddns key generation tool

- - - -
+

Synopsis

-

- ddns-confgen - [-a algorithm] - [-h] - [-k keyname] - [-r randomfile] - [ - -s name - | -z zone - ] - [-q] - [name] -

-
- -
-

DESCRIPTION

- -

ddns-confgen +

ddns-confgen [-a algorithm] [-h] [-k keyname] [-r randomfile] [ -s name | -z zone ] [-q] [name]

+
+
+

DESCRIPTION

+

ddns-confgen generates a key for use by nsupdate and named. It simplifies configuration of dynamic zones by generating a key and providing the @@ -64,8 +39,7 @@ syntax that will be needed to use it, including an example update-policy statement.

- -

+

If a domain name is specified on the command line, it will be used in the name of the generated key and in the sample named.conf syntax. For example, @@ -74,39 +48,30 @@ named.conf command that could be used in the zone definition for "example.com".

- -

+

Note that named itself can configure a local DDNS key for use with nsupdate -l. ddns-confgen is only needed when a more elaborate configuration is required: for instance, 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. -

-
+

-h
-
-

+

Prints a short summary of the options and arguments to ddns-confgen. -

-
+

-k keyname
-
-

+

Specifies the key name of the DDNS authentication key. The default is ddns-key when neither the -s nor -z option is @@ -116,18 +81,14 @@ ddns-key.example.com. The key name must have the format of a valid domain name, consisting of letters, digits, hyphens and periods. -

-
+

-q
-
-

+

Quiet mode: Print only the key, with no explanatory text or usage examples. -

-
+

-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 @@ -137,11 +98,9 @@ instead of the default. The special value keyboard indicates that keyboard input should be used. -

-
+

-s name
-
-

+

Single host mode: The example named.conf text shows how to set an update policy for the specified name @@ -151,11 +110,9 @@ 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
-
-

+

zone mode: The example named.conf text shows how to set an update policy for the specified zone @@ -163,26 +120,16 @@ 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.

-
- +
diff --git a/bin/confgen/rndc-confgen.8 b/bin/confgen/rndc-confgen.8 index 496b63ca70..85d3151004 100644 --- a/bin/confgen/rndc-confgen.8 +++ b/bin/confgen/rndc-confgen.8 @@ -18,7 +18,7 @@ '\" t .\" Title: rndc-confgen .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-06-15 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" rndc-confgen \- rndc key generation tool .SH "SYNOPSIS" -.HP 13 +.HP \w'\fBrndc\-confgen\fR\ 'u \fBrndc\-confgen\fR [\fB\-a\fR] [\fB\-b\ \fR\fB\fIkeysize\fR\fR] [\fB\-c\ \fR\fB\fIkeyfile\fR\fR] [\fB\-h\fR] [\fB\-k\ \fR\fB\fIkeyname\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-r\ \fR\fB\fIrandomfile\fR\fR] [\fB\-s\ \fR\fB\fIaddress\fR\fR] [\fB\-t\ \fR\fB\fIchrootdir\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] .SH "DESCRIPTION" .PP diff --git a/bin/confgen/rndc-confgen.html b/bin/confgen/rndc-confgen.html index 489866c541..a5c02451dc 100644 --- a/bin/confgen/rndc-confgen.html +++ b/bin/confgen/rndc-confgen.html @@ -18,46 +18,21 @@ rndc-confgen - + -
+
- - - - - -
+

Name

-

- rndc-confgen - — rndc key generation tool -

+

rndc-confgen — rndc key generation tool

- - - -
+

Synopsis

-

- rndc-confgen - [-a] - [-b keysize] - [-c keyfile] - [-h] - [-k keyname] - [-p port] - [-r randomfile] - [-s address] - [-t chrootdir] - [-u user] -

-
- -
-

DESCRIPTION

- -

rndc-confgen +

rndc-confgen [-a] [-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 convenient alternative to writing the @@ -70,17 +45,13 @@ avoid the need for a rndc.conf file and a controls statement altogether.

- -
- -
-

OPTIONS

- - -
+
+
+

OPTIONS

+
-a
-

+

Do automatic rndc configuration. This creates a file rndc.key in /etc (or whatever @@ -95,7 +66,7 @@ named on the local host with no further configuration.

-

+

Running rndc-confgen -a allows BIND 9 and rndc to be used as drop-in @@ -103,7 +74,7 @@ with no changes to the existing BIND 8 named.conf file.

-

+

If a more elaborate configuration than that generated by rndc-confgen -a is required, for example if rndc is to be used remotely, @@ -114,47 +85,36 @@ named.conf as directed.

-
+
-b keysize
-
-

+

Specifies the size of the authentication key in bits. Must be between 1 and 512 bits; the default is 128. -

-
+

-c keyfile
-
-

+

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

-
+

-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. 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 @@ -165,30 +125,24 @@ 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 listens for command channel connections from 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 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. -

-
+

-u user
-
-

+

Used with the -a option to set the owner of the rndc.key file generated. @@ -196,45 +150,33 @@ -t is also specified only the file in the chroot area has its owner changed. -

-
+

-
- -
-

EXAMPLES

- -

+

+
+

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

-
- +
diff --git a/bin/dig/dig.1 b/bin/dig/dig.1 index 7b4938b5e7..380dba1012 100644 --- a/bin/dig/dig.1 +++ b/bin/dig/dig.1 @@ -18,7 +18,7 @@ '\" t .\" Title: dig .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-12 .\" Manual: BIND9 .\" Source: ISC @@ -47,11 +47,11 @@ .SH "NAME" dig \- DNS lookup utility .SH "SYNOPSIS" -.HP 4 +.HP \w'\fBdig\fR\ 'u \fBdig\fR [@server] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-f\ \fR\fB\fIfilename\fR\fR] [\fB\-k\ \fR\fB\fIfilename\fR\fR] [\fB\-m\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-q\ \fR\fB\fIname\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIname:key\fR\fR] [\fB\-4\fR] [\fB\-6\fR] [name] [type] [class] [queryopt...] -.HP 4 +.HP \w'\fBdig\fR\ 'u \fBdig\fR [\fB\-h\fR] -.HP 4 +.HP \w'\fBdig\fR\ 'u \fBdig\fR [global\-queryopt...] [query...] .SH "DESCRIPTION" .PP diff --git a/bin/dig/dig.html b/bin/dig/dig.html index 808b25df60..2ea4828347 100644 --- a/bin/dig/dig.html +++ b/bin/dig/dig.html @@ -18,66 +18,23 @@ dig - + -
+
- - - - - - -
+

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 @@ -86,8 +43,7 @@ clarity of output. Other lookup tools tend to have less functionality than dig.

- -

+

Although dig is normally used with command-line arguments, it also has a batch mode of operation for reading lookup @@ -98,42 +54,34 @@ from the command line.

- -

+

Unless it is told to query a specific name server, 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 host.

- -

+

When no command line arguments or options are given, dig will perform an NS query for "." (the root).

- -

+

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

- - -

+

+
+

SIMPLE USAGE

+

A typical invocation of dig looks like: 

 dig @server name type
@@ -141,10 +89,10 @@ 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 @@ -152,7 +100,7 @@ dig resolves that name before querying that name server.

-

+

If no server argument is provided, dig consults /etc/resolv.conf; if an @@ -165,16 +113,13 @@ 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 @@ -182,109 +127,81 @@ type argument is supplied, 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 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. -

-
+

-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) - . + 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 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 @@ -296,17 +213,13 @@ 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 @@ -321,11 +234,10 @@ 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. @@ -336,34 +248,28 @@ 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 @@ -377,29 +283,22 @@ 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 @@ -409,161 +308,123 @@ 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]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 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]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 /etc/resolv.conf, and enable search list processing as if the +search option were given. -

-
+

+[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]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]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 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 @@ -575,123 +436,97 @@ 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 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]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 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 @@ -700,30 +535,24 @@ +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]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. -

-
+

+time=T
-
-

+

Sets the timeout for a query to T seconds. The default @@ -731,18 +560,15 @@ 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, @@ -750,67 +576,62 @@ 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 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 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]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". -

-
+

-
- -
-

MULTIPLE QUERIES

- - -

+

+
+

MULTIPLE QUERIES

+

The BIND 9 implementation of dig supports specifying multiple queries on the command line (in addition to @@ -818,8 +639,7 @@ 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 @@ -827,8 +647,7 @@ 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 @@ -855,13 +674,10 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr will not print the initial query when it looks up the NS records for 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. dig appropriately converts character encoding of @@ -872,39 +688,27 @@ 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

- -

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

-
+
diff --git a/bin/dig/host.1 b/bin/dig/host.1 index 12707ccaa8..f654d97763 100644 --- a/bin/dig/host.1 +++ b/bin/dig/host.1 @@ -18,7 +18,7 @@ '\" t .\" Title: host .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-01-20 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" host \- DNS lookup utility .SH "SYNOPSIS" -.HP 5 +.HP \w'\fBhost\fR\ 'u \fBhost\fR [\fB\-aCdlnrsTwv\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-N\ \fR\fB\fIndots\fR\fR] [\fB\-R\ \fR\fB\fInumber\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-W\ \fR\fB\fIwait\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-4\fR] [\fB\-6\fR] [\fB\-v\fR] [\fB\-V\fR] {name} [server] .SH "DESCRIPTION" .PP @@ -198,8 +198,7 @@ will effectively wait forever for a reply\&. The time to wait for a response wil The \fB\-s\fR option tells -\fBhost\fR -\fInot\fR +\fBhost\fR\fInot\fR 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\&. .PP The diff --git a/bin/dig/host.html b/bin/dig/host.html index 97653cabf9..3b4aea9a6e 100644 --- a/bin/dig/host.html +++ b/bin/dig/host.html @@ -18,58 +18,28 @@ host - + -
+
- - - - - -
+

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 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 @@ -81,14 +51,12 @@ 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 a query of type ANY.

- -

+

When the -C option is used, host will attempt to display the SOA records for zone name from all the listed @@ -96,15 +64,13 @@ 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 the -d or -v option is used. The two @@ -113,8 +79,7 @@ switched on debugging traces and -v enabled verbose output.

- -

+

List mode is selected by the -l option. This makes host perform a zone transfer for zone name. Transfer the zone printing out @@ -122,15 +87,13 @@ 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 @@ -142,8 +105,7 @@ or domain directive in /etc/resolv.conf.

- -

+

The number of UDP retries for a lookup can be changed with the -R option. number indicates @@ -154,8 +116,7 @@ number of retries will default to 1.

- -

+

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. @@ -167,22 +128,19 @@ expecting to receive answers to those queries that are usually referrals to other name servers.

- -

+

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 use IPv4 query transport. The -6 option forces 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, @@ -198,8 +156,7 @@ 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 @@ -212,31 +169,26 @@ will be set to the number of seconds given by the hardware's maximum value for an integer quantity.

- -

+

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 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. host appropriately converts character encoding of @@ -247,26 +199,17 @@ The IDN support is disabled if the variable is set when host runs.

-
- -
-

FILES

- -

/etc/resolv.conf +

+
+

FILES

+

/etc/resolv.conf

-
- -
-

SEE ALSO

- -

- dig(1) - , - - named(8) - . +

+
+

SEE ALSO

+

dig(1), + named(8).

-
- +
diff --git a/bin/dig/nslookup.1 b/bin/dig/nslookup.1 index 15f39cedea..ee9106b4fe 100644 --- a/bin/dig/nslookup.1 +++ b/bin/dig/nslookup.1 @@ -17,7 +17,7 @@ '\" t .\" Title: nslookup .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-01-24 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" nslookup \- query Internet name servers interactively .SH "SYNOPSIS" -.HP 9 +.HP \w'\fBnslookup\fR\ 'u \fBnslookup\fR [\fB\-option\fR] [name\ |\ \-] [server] .SH "DESCRIPTION" .PP @@ -93,7 +93,6 @@ nslookup \-query=hinfo \-timeout=10 .if n \{\ .RE .\} -.sp .PP The \fB\-version\fR diff --git a/bin/dig/nslookup.html b/bin/dig/nslookup.html index 573f25506c..ec8d16eaf9 100644 --- a/bin/dig/nslookup.html +++ b/bin/dig/nslookup.html @@ -17,39 +17,21 @@ nslookup - + -
-
- - - - - -
+
+
+

Name

-

- nslookup - — query Internet name servers interactively -

+

nslookup — query Internet name servers interactively

- - - -
+

Synopsis

-

- nslookup - [-option] - [name | -] - [server] -

-
- -
-

DESCRIPTION

- -

Nslookup +

nslookup [-option] [name | -] [server]

+
+
+

DESCRIPTION

+

Nslookup is a program to query Internet domain name servers. Nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query name servers for information about various hosts and @@ -58,37 +40,29 @@ used to print just the name and requested information for a host or domain.

-
- -
-

ARGUMENTS

- -

+

+
+

ARGUMENTS

+

Interactive mode is entered in the following cases:

    -
  1. -

    +

  2. when no arguments are given (the default name server will be used) -

    -
    3. -
  3. -

    +

    4. +

  4. when the first argument is a hyphen (-) and the second argument is the host name or Internet address of a name server. -

    -
    5. +

- -

+

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

- -

+

Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. For example, to change the default query type to host information, and the initial @@ -101,291 +75,239 @@ nslookup -query=hinfo -timeout=10

-

+

The -version option causes nslookup to print the version number and immediately exits.

- -
- -
-

INTERACTIVE COMMANDS

- -
+
+
+

INTERACTIVE COMMANDS

+
host [server]
-

+

Look up information for host using the current default server or using server, if specified. If host is an Internet address and the query type is A or PTR, the name of the host is returned. If host is a name and does not have a trailing period, the search list is used to qualify the name.

- -

+

To look up a host not in the current domain, append a period to the name.

-
+
server domain
-
-

-
+

lserver domain
-
-

+

Change the default server to domain; lserver uses the initial server to look up information about domain, while server uses the current default server. If an authoritative answer can't be found, the names of servers that might have the answer are returned. -

-
+

root
-
-

+

not implemented -

-
+

finger
-
-

+

not implemented -

-
+

ls
-
-

+

not implemented -

-
+

view
-
-

+

not implemented -

-
+

help
-
-

+

not implemented -

-
+

?
-
-

+

not implemented -

-
+

exit
-
-

+

Exits the program. -

-
+

set keyword[=value]
-

+

This command is used to change state information that affects the lookups. Valid keywords are:

-
+
all
-
-

+

Prints the current values of the frequently used options to set. Information about the current default server and host is also printed. -

-
+

class=value
-

+

Change the query class to one of:

-
+
IN
-
-

+

the Internet class -

-
+

CH
-
-

+

the Chaos class -

-
+

HS
-
-

+

the Hesiod class -

-
+

ANY
-
-

+

wildcard -

-
+

The class specifies the protocol group of the information.

-

+

(Default = IN; abbreviation = cl)

- +
[no]debug
-

+

Turn on or off the display of the full response packet and any intermediate response packets when searching.

-

+

(Default = nodebug; abbreviation = [no]deb)

-
+
[no]d2
-

+

Turn debugging mode on or off. This displays more about what nslookup is doing.

-

+

(Default = nod2)

-
+
domain=name
-
-

+

Sets the search list to name. -

-
+

[no]search
-

+

If the lookup request contains at least one period but doesn't end with a trailing period, append the domain names in the domain search list to the request until an answer is received.

-

+

(Default = search)

-
+
port=value
-

+

Change the default TCP/UDP name server port to value.

-

+

(Default = 53; abbreviation = po)

-
+
querytype=value
-
-

-
+

type=value
-

+

Change the type of the information query.

-

+

(Default = A; abbreviations = q, ty)

-
+
[no]recurse
-

+

Tell the name server to query other servers if it does not have the information.

-

+

(Default = recurse; abbreviation = [no]rec)

-
+
ndots=number
-
-

+

Set the number of dots (label separators) in a domain that will disable searching. Absolute names always stop searching. -

-
+

retry=number
-
-

+

Set the number of retries to number. -

-
+

timeout=number
-
-

+

Change the initial timeout interval for waiting for a reply to number seconds. -

-
+

[no]vc
-

+

Always use a virtual circuit when sending requests to the server.

-

+

(Default = novc)

-
+
[no]fail
-

+

Try the next nameserver if a nameserver responds with SERVFAIL or a referral (nofail) or terminate query (fail) on such a response.

-

+

(Default = nofail)

-
+

- +
-
- -
-

FILES

- -

/etc/resolv.conf +

+
+

FILES

+

/etc/resolv.conf

-
- -
-

SEE ALSO

- -

- dig(1) - , - - host(1) - , - - named(8) - . +

+
+

SEE ALSO

+

dig(1), + host(1), + named(8).

-
+
diff --git a/bin/dnssec/dnssec-dsfromkey.8 b/bin/dnssec/dnssec-dsfromkey.8 index 3721cb847f..5f6312177c 100644 --- a/bin/dnssec/dnssec-dsfromkey.8 +++ b/bin/dnssec/dnssec-dsfromkey.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-dsfromkey .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2012-05-17 .\" Manual: BIND9 .\" Source: ISC @@ -46,11 +46,11 @@ .SH "NAME" dnssec-dsfromkey \- DNSSEC DS RR generation tool .SH "SYNOPSIS" -.HP 17 +.HP \w'\fBdnssec\-dsfromkey\fR\ 'u \fBdnssec\-dsfromkey\fR [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-1\fR] [\fB\-2\fR] [\fB\-a\ \fR\fB\fIalg\fR\fR] [\fB\-C\fR] [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-T\ \fR\fB\fITTL\fR\fR] {keyfile} -.HP 17 +.HP \w'\fBdnssec\-dsfromkey\fR\ 'u \fBdnssec\-dsfromkey\fR {\-s} [\fB\-1\fR] [\fB\-2\fR] [\fB\-a\ \fR\fB\fIalg\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-s\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-T\ \fR\fB\fITTL\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-A\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] {dnsname} -.HP 17 +.HP \w'\fBdnssec\-dsfromkey\fR\ 'u \fBdnssec\-dsfromkey\fR [\fB\-h\fR] [\fB\-V\fR] .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-dsfromkey.html b/bin/dnssec/dnssec-dsfromkey.html index cffa0f35a6..dc06420a27 100644 --- a/bin/dnssec/dnssec-dsfromkey.html +++ b/bin/dnssec/dnssec-dsfromkey.html @@ -17,246 +17,162 @@ dnssec-dsfromkey - + -
+
- - - - - -
+

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 command as input, as in:

-

+

dig dnskey example.com | dnssec-dsfromkey -f - example.com

-
+
-A
-
-

+

Include ZSK's 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.

-
- +
diff --git a/bin/dnssec/dnssec-importkey.8 b/bin/dnssec/dnssec-importkey.8 index a2aa82142c..bdbcdade29 100644 --- a/bin/dnssec/dnssec-importkey.8 +++ b/bin/dnssec/dnssec-importkey.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-importkey .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-07 .\" Manual: BIND9 .\" Source: ISC @@ -46,9 +46,9 @@ .SH "NAME" dnssec-importkey \- Import DNSKEY records from external systems so they can be managed\&. .SH "SYNOPSIS" -.HP 17 +.HP \w'\fBdnssec\-importkey\fR\ 'u \fBdnssec\-importkey\fR [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-h\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] {\fBkeyfile\fR} -.HP 17 +.HP \w'\fBdnssec\-importkey\fR\ 'u \fBdnssec\-importkey\fR {\fB\-f\ \fR\fB\fIfilename\fR\fR} [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-h\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fBdnsname\fR] .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-importkey.html b/bin/dnssec/dnssec-importkey.html index bf1a013b0f..5417a5415b 100644 --- a/bin/dnssec/dnssec-importkey.html +++ b/bin/dnssec/dnssec-importkey.html @@ -18,56 +18,22 @@ dnssec-importkey - + -
+
- - - - - -
+

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 @@ -75,7 +41,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 @@ -84,68 +50,53 @@ 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 @@ -156,51 +107,37 @@ 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.

-
- +
diff --git a/bin/dnssec/dnssec-keyfromlabel.8 b/bin/dnssec/dnssec-keyfromlabel.8 index 3135f9d8ea..9e108fcfc0 100644 --- a/bin/dnssec/dnssec-keyfromlabel.8 +++ b/bin/dnssec/dnssec-keyfromlabel.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-keyfromlabel .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-27 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" dnssec-keyfromlabel \- DNSSEC key generation tool .SH "SYNOPSIS" -.HP 20 +.HP \w'\fBdnssec\-keyfromlabel\fR\ 'u \fBdnssec\-keyfromlabel\fR {\-l\ \fIlabel\fR} [\fB\-3\fR] [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\ \fR\fB\fIflag\fR\fR] [\fB\-G\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-k\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-n\ \fR\fB\fInametype\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-p\ \fR\fB\fIprotocol\fR\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-y\fR] {name} .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-keyfromlabel.html b/bin/dnssec/dnssec-keyfromlabel.html index 3fc18f6291..ead6b22036 100644 --- a/bin/dnssec/dnssec-keyfromlabel.html +++ b/bin/dnssec/dnssec-keyfromlabel.html @@ -17,60 +17,21 @@ dnssec-keyfromlabel - + -
+
- - - - - -
+

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 @@ -78,80 +39,68 @@ 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 name of the crypto hardware (OpenSSL engine). When compiled with PKCS#11 support it defaults to "pkcs11". -

-
+

-l label
-
-

+

Specifies the label of the key pair in the crypto hardware. The label may be preceded by an optional OpenSSL engine name, separated by a colon, as in "pkcs11:keylabel". -

-
+

-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 will include the key's creation date in the metadata stored @@ -159,71 +108,53 @@ (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. -

-
+

-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 @@ -231,47 +162,35 @@ 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 @@ -282,53 +201,42 @@ 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 @@ -337,82 +245,67 @@ 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

- -

+

+
+

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.

-
- +
diff --git a/bin/dnssec/dnssec-keygen.8 b/bin/dnssec/dnssec-keygen.8 index 709a29fcad..acbbbbd0e6 100644 --- a/bin/dnssec/dnssec-keygen.8 +++ b/bin/dnssec/dnssec-keygen.8 @@ -18,7 +18,7 @@ '\" t .\" Title: dnssec-keygen .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-07 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" dnssec-keygen \- DNSSEC key generation tool .SH "SYNOPSIS" -.HP 14 +.HP \w'\fBdnssec\-keygen\fR\ 'u \fBdnssec\-keygen\fR [\fB\-a\ \fR\fB\fIalgorithm\fR\fR] [\fB\-b\ \fR\fB\fIkeysize\fR\fR] [\fB\-n\ \fR\fB\fInametype\fR\fR] [\fB\-3\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-C\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\ \fR\fB\fIflag\fR\fR] [\fB\-G\fR] [\fB\-g\ \fR\fB\fIgenerator\fR\fR] [\fB\-h\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-k\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-p\ \fR\fB\fIprotocol\fR\fR] [\fB\-q\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-r\ \fR\fB\fIrandomdev\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-s\ \fR\fB\fIstrength\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-z\fR] {name} .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-keygen.html b/bin/dnssec/dnssec-keygen.html index 2653958c0a..a1143c7ebb 100644 --- a/bin/dnssec/dnssec-keygen.html +++ b/bin/dnssec/dnssec-keygen.html @@ -18,86 +18,38 @@ dnssec-keygen - + -
+
- - - - - -
+

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, @@ -107,26 +59,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 @@ -135,7 +87,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 (ZSK's) and 2048 bits for key signing keys (KSK's, @@ -144,10 +96,9 @@ 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 @@ -155,22 +106,18 @@ 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 will include the key's creation date in the metadata stored @@ -178,69 +125,51 @@ (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
-
-

+

Uses a crypto hardware (OpenSSL engine) for random number and, when supported, key generation. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine. -

-
+

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

-
+

-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 @@ -249,20 +178,16 @@ 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 @@ -274,11 +199,9 @@ 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 @@ -288,11 +211,9 @@ 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 @@ -300,19 +221,16 @@ 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 @@ -324,36 +242,27 @@ 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 @@ -364,55 +273,44 @@ 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 @@ -421,51 +319,42 @@ 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

- -

+

+
+

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 @@ -473,60 +362,53 @@ 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 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.

-
- +
diff --git a/bin/dnssec/dnssec-revoke.8 b/bin/dnssec/dnssec-revoke.8 index 99cb8f7b71..15ac846aaa 100644 --- a/bin/dnssec/dnssec-revoke.8 +++ b/bin/dnssec/dnssec-revoke.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-revoke .\" Author: [FIXME: author] [see http://docbook.sf.net/el/author] -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2011-10-20 .\" Manual: BIND9 .\" Source: BIND9 @@ -46,7 +46,7 @@ .SH "NAME" dnssec-revoke \- Set the REVOKED bit on a DNSSEC key .SH "SYNOPSIS" -.HP 14 +.HP \w'\fBdnssec\-revoke\fR\ 'u \fBdnssec\-revoke\fR [\fB\-hr\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-f\fR] [\fB\-R\fR] {keyfile} .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-revoke.html b/bin/dnssec/dnssec-revoke.html index 92f53ad384..58bbdae415 100644 --- a/bin/dnssec/dnssec-revoke.html +++ b/bin/dnssec/dnssec-revoke.html @@ -17,120 +17,74 @@ dnssec-revoke - + -
+
- - - - -
+

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

+

Use the given OpenSSL engine. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine. -

-
+

-f
-
-

+

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.

-
- +
diff --git a/bin/dnssec/dnssec-settime.8 b/bin/dnssec/dnssec-settime.8 index 793ac03f50..37951ad2e0 100644 --- a/bin/dnssec/dnssec-settime.8 +++ b/bin/dnssec/dnssec-settime.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-settime .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-07 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" dnssec-settime \- Set the key timing metadata for a DNSSEC key .SH "SYNOPSIS" -.HP 15 +.HP \w'\fBdnssec\-settime\fR\ 'u \fBdnssec\-settime\fR [\fB\-f\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-h\fR] [\fB\-V\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] {keyfile} .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-settime.html b/bin/dnssec/dnssec-settime.html index 9ce6b40ef7..03fbe8e7e0 100644 --- a/bin/dnssec/dnssec-settime.html +++ b/bin/dnssec/dnssec-settime.html @@ -17,49 +17,21 @@ dnssec-settime - + -
+
- - - - - -
+

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 @@ -68,12 +40,12 @@ 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 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. @@ -82,16 +54,12 @@ 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 fail when attempting to update a legacy key. With this option, @@ -100,17 +68,13 @@ 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 @@ -119,40 +83,29 @@ 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
-
-

+

Use the given OpenSSL engine. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine. -

-
+

-
- -
-

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 @@ -162,51 +115,39 @@ 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 @@ -214,11 +155,10 @@ 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 @@ -227,40 +167,34 @@ 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

- -

+

+
+

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: @@ -271,24 +205,16 @@ 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.

-
- +
diff --git a/bin/dnssec/dnssec-signzone.8 b/bin/dnssec/dnssec-signzone.8 index ddddd84881..214bb55123 100644 --- a/bin/dnssec/dnssec-signzone.8 +++ b/bin/dnssec/dnssec-signzone.8 @@ -18,7 +18,7 @@ '\" t .\" Title: dnssec-signzone .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-12-11 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" dnssec-signzone \- DNSSEC zone signing tool .SH "SYNOPSIS" -.HP 16 +.HP \w'\fBdnssec\-signzone\fR\ 'u \fBdnssec\-signzone\fR [\fB\-a\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-d\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-e\ \fR\fB\fIend\-time\fR\fR] [\fB\-f\ \fR\fB\fIoutput\-file\fR\fR] [\fB\-g\fR] [\fB\-h\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-k\ \fR\fB\fIkey\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-I\ \fR\fB\fIinput\-format\fR\fR] [\fB\-j\ \fR\fB\fIjitter\fR\fR] [\fB\-N\ \fR\fB\fIsoa\-serial\-format\fR\fR] [\fB\-o\ \fR\fB\fIorigin\fR\fR] [\fB\-O\ \fR\fB\fIoutput\-format\fR\fR] [\fB\-P\fR] [\fB\-p\fR] [\fB\-R\fR] [\fB\-r\ \fR\fB\fIrandomdev\fR\fR] [\fB\-S\fR] [\fB\-s\ \fR\fB\fIstart\-time\fR\fR] [\fB\-T\ \fR\fB\fIttl\fR\fR] [\fB\-t\fR] [\fB\-u\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-X\ \fR\fB\fIextended\ end\-time\fR\fR] [\fB\-x\fR] [\fB\-z\fR] [\fB\-3\ \fR\fB\fIsalt\fR\fR] [\fB\-H\ \fR\fB\fIiterations\fR\fR] [\fB\-A\fR] {zonefile} [key...] .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-signzone.html b/bin/dnssec/dnssec-signzone.html index 85f8b0899a..f6540cd9cb 100644 --- a/bin/dnssec/dnssec-signzone.html +++ b/bin/dnssec/dnssec-signzone.html @@ -18,74 +18,21 @@ dnssec-signzone - + -
+
- - - - - -
+

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] - [-i interval] - [-I input-format] - [-j jitter] - [-N soa-serial-format] - [-o origin] - [-O output-format] - [-P] - [-p] - [-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] [-i interval] [-I input-format] [-j jitter] [-N soa-serial-format] [-o origin] [-O output-format] [-P] [-p] [-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 @@ -93,46 +40,34 @@ 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. -

-
+

-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, NSEC3 and NSEC3PARAM records. If smart signing @@ -141,49 +76,37 @@ zone file with $INCLUDE. This option cannot be combined with -O raw or serial number updating. -

-
+

-E engine
-
-

+

Uses a crypto hardware (OpenSSL engine) for the crypto operations it supports, for instance signing with private keys from a secure key store. When compiled with PKCS#11 support it defaults to pkcs11; the empty name resets it to no engine. -

-
+

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

-
+

-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 @@ -192,11 +115,9 @@ 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 @@ -206,11 +127,10 @@ 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 @@ -218,7 +138,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 @@ -229,34 +149,28 @@ 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. -

-
+

-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 @@ -264,7 +178,7 @@ 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 @@ -275,10 +189,9 @@ 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) and "raw". @@ -287,11 +200,10 @@ 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. @@ -302,66 +214,51 @@ 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' 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" and "unixtime".

- -
+
"keep"
-
-

Do not modify the SOA serial number.

-
+

Do not modify the SOA serial number.

"increment"
-
-

Increment the SOA serial number using RFC 1982 - arithmetics.

-
+

Increment the SOA serial number using RFC 1982 + arithmetics.

"unixtime"
-
-

Set the SOA serial number to the number of seconds - since epoch.

-
+

Set the SOA serial number to the number of seconds + since epoch.

- -
+
-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) "full", which is text output in a @@ -373,36 +270,33 @@ is 0, the raw file can be read by 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 @@ -414,23 +308,22 @@ 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 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 @@ -440,65 +333,53 @@ 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 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 @@ -510,102 +391,81 @@ 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 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.) -

-
+

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

-
+

-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 @@ -618,13 +478,13 @@ Kexample.com.+003+17247 db.example.com.signed % -

+

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.

@@ -632,18 +492,13 @@ 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.

-
- +
diff --git a/bin/dnssec/dnssec-verify.8 b/bin/dnssec/dnssec-verify.8 index 7264eedd3f..ab0f66de60 100644 --- a/bin/dnssec/dnssec-verify.8 +++ b/bin/dnssec/dnssec-verify.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-verify .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2012-06-26 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" dnssec-verify \- DNSSEC zone verification tool .SH "SYNOPSIS" -.HP 14 +.HP \w'\fBdnssec\-verify\fR\ 'u \fBdnssec\-verify\fR [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] [\fB\-I\ \fR\fB\fIinput\-format\fR\fR] [\fB\-o\ \fR\fB\fIorigin\fR\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-V\fR] [\fB\-x\fR] [\fB\-z\fR] {zonefile} .SH "DESCRIPTION" .PP diff --git a/bin/dnssec/dnssec-verify.html b/bin/dnssec/dnssec-verify.html index 38732ce585..b973634e05 100644 --- a/bin/dnssec/dnssec-verify.html +++ b/bin/dnssec/dnssec-verify.html @@ -17,65 +17,35 @@ dnssec-verify - + -
+
- - - - - -
+

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

-
+

-I input-format
-
-

+

The format of the input zone file. Possible formats are "text" (default) and "raw". @@ -84,41 +54,32 @@ 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. -

-
+

-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 @@ -126,7 +87,7 @@ 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 @@ -135,27 +96,20 @@ for both purposes. This corresponds to the -z 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.

-
- +
diff --git a/bin/named/lwresd.8 b/bin/named/lwresd.8 index 951472d4f3..5c209ea057 100644 --- a/bin/named/lwresd.8 +++ b/bin/named/lwresd.8 @@ -18,7 +18,7 @@ '\" t .\" Title: lwresd .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-01-20 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" lwresd \- lightweight resolver daemon .SH "SYNOPSIS" -.HP 7 +.HP \w'\fBlwresd\fR\ 'u \fBlwresd\fR [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-C\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-i\ \fR\fB\fIpid\-file\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-n\ \fR\fB\fI#cpus\fR\fR] [\fB\-P\ \fR\fB\fIport\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-s\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] [\fB\-v\fR] [\fB\-4\fR] [\fB\-6\fR] .SH "DESCRIPTION" .PP @@ -180,9 +180,20 @@ Send DNS lookups to port Write memory usage statistics to stdout on exit\&. -.RS -.B "Note:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&. +.sp .5v .RE .RE .PP @@ -191,13 +202,24 @@ This option is mainly of interest to BIND 9 developers and may be removed or cha Chroot to \fIdirectory\fR after processing the command line arguments, but before reading the configuration file\&. -.RS -.B "Warning:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBWarning\fR +.ps -1 +.br This option should be used in conjunction with the \fB\-u\fR option, as chrooting a process running as root doesn\*(Aqt enhance security on most systems; the way \fBchroot(2)\fR is defined allows a process with root privileges to escape a chroot jail\&. +.sp .5v .RE .RE .PP diff --git a/bin/named/lwresd.html b/bin/named/lwresd.html index 841bc9891a..5438acf78a 100644 --- a/bin/named/lwresd.html +++ b/bin/named/lwresd.html @@ -18,61 +18,28 @@ lwresd - + -
+
- - - - - -
+

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 @@ -80,14 +47,14 @@ 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 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 sends recursive DNS queries to those servers. This is similar @@ -97,80 +64,60 @@ 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 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, @@ -179,61 +126,54 @@ 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 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 @@ -241,61 +181,39 @@ 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).

-
- +
diff --git a/bin/named/named.8 b/bin/named/named.8 index e493d0af09..23e35e580e 100644 --- a/bin/named/named.8 +++ b/bin/named/named.8 @@ -18,7 +18,7 @@ '\" t .\" Title: named .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-02-20 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" named \- Internet domain name server .SH "SYNOPSIS" -.HP 6 +.HP \w'\fBnamed\fR\ 'u \fBnamed\fR [\fB\-4\fR] [\fB\-6\fR] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR] [\fB\-E\ \fR\fB\fIengine\-name\fR\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-M\ \fR\fB\fIoption\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-n\ \fR\fB\fI#cpus\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-s\fR] [\fB\-S\ \fR\fB\fI#max\-socks\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-U\ \fR\fB\fI#listeners\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] [\fB\-v\fR] [\fB\-V\fR] [\fB\-x\ \fR\fB\fIcache\-file\fR\fR] .SH "DESCRIPTION" .PP @@ -153,9 +153,20 @@ Listen for queries on port Write memory usage statistics to stdout on exit\&. -.RS -.B "Note:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&. +.sp .5v .RE .RE .PP @@ -166,11 +177,22 @@ Allow to use up to \fI#max\-socks\fR sockets\&. -.RS -.B "Warning:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBWarning\fR +.ps -1 +.br This option should be unnecessary for the vast majority of users\&. 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 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 fewer than the specified value because \fBnamed\fR reserves some file descriptors for its internal use\&. +.sp .5v .RE .RE .PP @@ -179,13 +201,24 @@ reserves some file descriptors for its internal use\&. Chroot to \fIdirectory\fR after processing the command line arguments, but before reading the configuration file\&. -.RS -.B "Warning:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBWarning\fR +.ps -1 +.br This option should be used in conjunction with the \fB\-u\fR option, as chrooting a process running as root doesn\*(Aqt enhance security on most systems; the way \fBchroot(2)\fR is defined allows a process with root privileges to escape a chroot jail\&. +.sp .5v .RE .RE .PP @@ -207,8 +240,18 @@ may be increased as high as that value, but no higher\&. On Windows, the number Setuid to \fIuser\fR after completing privileged operations, such as creating sockets that listen on privileged ports\&. -.RS -.B "Note:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBNote\fR +.ps -1 +.br On Linux, \fBnamed\fR uses the kernel\*(Aqs capability mechanism to drop all root privileges except the ability to @@ -219,6 +262,7 @@ option only works when \fBnamed\fR 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 \fBsetuid(2)\fR\&. +.sp .5v .RE .RE .PP @@ -237,9 +281,20 @@ Report the version number and build options, and exit\&. Load data from \fIcache\-file\fR into the cache of the default view\&. -.RS -.B "Warning:" +.if n \{\ +.sp +.\} +.RS 4 +.it 1 an-trap +.nr an-no-space-flag 1 +.nr an-break-flag 1 +.br +.ps +1 +\fBWarning\fR +.ps -1 +.br 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\&. +.sp .5v .RE .RE .SH "SIGNALS" diff --git a/bin/named/named.conf.5 b/bin/named/named.conf.5 index b45d5646ec..a1bc83aeac 100644 --- a/bin/named/named.conf.5 +++ b/bin/named/named.conf.5 @@ -17,7 +17,7 @@ '\" t .\" Title: named.conf .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-01-08 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" named.conf \- configuration file for named .SH "SYNOPSIS" -.HP 11 +.HP \w'\fBnamed\&.conf\fR\ 'u \fBnamed\&.conf\fR .SH "DESCRIPTION" .PP diff --git a/bin/named/named.conf.html b/bin/named/named.conf.html index 9d7fdf4fc0..0f32dfc559 100644 --- a/bin/named/named.conf.html +++ b/bin/named/named.conf.html @@ -17,88 +17,65 @@ named.conf - + -
+
- - - - - -
+

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 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;
@@ -117,32 +94,26 @@ 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 | * ) ]
@@ -151,12 +122,10 @@ controls unix unsupported; // not implemented
};

-
- -
-

LOGGING

- -


+

+
+

LOGGING

+


logging {
channel string {
file log_file;
@@ -171,12 +140,10 @@ logging category string { string; ... };
};

-
- -
-

LWRES

- -


+

+
+

LWRES

+


lwres {
listen-on [ port integer ] {
( ipv4_address | ipv6_address ) [ port integer ]; ...
@@ -186,12 +153,10 @@ lwres ndots integer;
};

-
- -
-

OPTIONS

- -


+

+
+

OPTIONS

+


options {
avoid-v4-udp-ports { port; ... };
avoid-v6-udp-ports { port; ... };
@@ -393,12 +358,10 @@ options use-id-pool boolean; // obsolete
};

-
- -
-

VIEW

- -


+

+
+

VIEW

+


view string optional_class {
match-clients { address_match_element; ... };
match-destinations { address_match_element; ... };
@@ -559,12 +522,10 @@ view max-ixfr-log-size size; // obsolete
};

-
- -
-

ZONE

- -


+

+
+

ZONE

+


zone string optional_class {
type ( master | slave | stub | hint | redirect |
forward | delegation-only );
@@ -658,30 +619,19 @@ 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.

-
- +
diff --git a/bin/named/named.html b/bin/named/named.html index a6ecf1753b..04a6b19530 100644 --- a/bin/named/named.html +++ b/bin/named/named.html @@ -18,92 +18,50 @@ named - + -
+
- - - - - -
+

Name

-

- named - — Internet domain name server -

+

named — Internet domain name server

- - - -
+

Synopsis

-

- named - [-4] - [-6] - [-c config-file] - [-d debug-level] - [-E engine-name] - [-f] - [-g] - [-M option] - [-m flag] - [-n #cpus] - [-p port] - [-s] - [-S #max-socks] - [-t directory] - [-U #listeners] - [-u user] - [-v] - [-V] - [-x cache-file] -

-
- -
-

DESCRIPTION

- -

named +

named [-4] [-6] [-c config-file] [-d debug-level] [-E engine-name] [-f] [-g] [-M option] [-m flag] [-n #cpus] [-p port] [-s] [-S #max-socks] [-t directory] [-U #listeners] [-u user] [-v] [-V] [-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 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 @@ -113,52 +71,40 @@ 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 more verbose as the debug level increases. -

-
+

-E engine-name
-
-

+

Use a crypto hardware (OpenSSL engine) for the crypto operations it supports, for instance re-signing with private keys from a secure key store. When compiled with PKCS#11 support engine-name defaults to pkcs11, the empty name resets it to no engine. -

-
+

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

-
+

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

-
+

-m flag
-
-

+

Turn on memory usage debugging flags. Possible flags are usage, trace, @@ -167,48 +113,43 @@ 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 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.

-
+

Warning

-

+

This option should be unnecessary for the vast majority of users. The use of this option could even be harmful because the @@ -223,18 +164,18 @@ named reserves some file descriptors for its internal use.

-
-
+
+
-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 @@ -242,11 +183,10 @@ 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 @@ -259,18 +199,17 @@ 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 +

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 except the ability to bind(2) to @@ -283,80 +222,63 @@ 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 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 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

- -

+

+
+

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 (file creation mode mask) from the parent process. If files created by named, such as journal files, @@ -364,59 +286,32 @@ should be set explicitly in the script used to start the 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.

-
- +
diff --git a/bin/nsupdate/nsupdate.1 b/bin/nsupdate/nsupdate.1 index f3552005f2..f5669ccec6 100644 --- a/bin/nsupdate/nsupdate.1 +++ b/bin/nsupdate/nsupdate.1 @@ -18,7 +18,7 @@ '\" t .\" Title: nsupdate .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2014-04-18 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" nsupdate \- Dynamic DNS update utility .SH "SYNOPSIS" -.HP 9 +.HP \w'\fBnsupdate\fR\ 'u \fBnsupdate\fR [\fB\-d\fR] [\fB\-D\fR] [\fB\-L\ \fR\fB\fIlevel\fR\fR] [[\fB\-g\fR] | [\fB\-o\fR] | [\fB\-l\fR] | [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIkeyname:secret\fR\fR] | [\fB\-k\ \fR\fB\fIkeyfile\fR\fR]] [\fB\-t\ \fR\fB\fItimeout\fR\fR] [\fB\-u\ \fR\fB\fIudptimeout\fR\fR] [\fB\-r\ \fR\fB\fIudpretries\fR\fR] [\fB\-R\ \fR\fB\fIrandomdev\fR\fR] [\fB\-v\fR] [\fB\-V\fR] [filename] .SH "DESCRIPTION" .PP @@ -267,8 +267,7 @@ will clear the default ttl\&. \fBkey\fR [hmac:] {keyname} {secret} .RS 4 Specifies that all updates are to be TSIG\-signed using the -\fIkeyname\fR -\fIsecret\fR +\fIkeyname\fR\fIsecret\fR pair\&. If \fIhmac\fR is specified, then it sets the signing algorithm in use; the default is diff --git a/bin/nsupdate/nsupdate.html b/bin/nsupdate/nsupdate.html index a0eac74425..7f1c8c2294 100644 --- a/bin/nsupdate/nsupdate.html +++ b/bin/nsupdate/nsupdate.html @@ -18,51 +18,21 @@ nsupdate - + -
+
- - - -
+

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] - [-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] [-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 @@ -71,27 +41,27 @@ one resource record.

-

+

Zones that are under dynamic control via 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 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. @@ -106,41 +76,33 @@ 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 @@ -152,11 +114,9 @@ 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 address cannot be overridden). Connections to the local server will @@ -165,31 +125,23 @@ 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. -

-
+

-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 @@ -198,43 +150,34 @@ 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. -

-
+

-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 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. @@ -245,23 +188,19 @@ 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. @@ -275,7 +214,7 @@ 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 @@ -285,17 +224,16 @@ 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 {servername} [port]
-
-

+

Sends all dynamic update requests to the name server servername. When no server statement is provided, @@ -311,15 +249,13 @@ If no port number is specified, the default DNS port number of 53 is used. -

-
+

local {address} [port]
-
-

+

Sends all dynamic update requests using the local address. @@ -331,14 +267,12 @@ can additionally be used to make requests come from a specific port. If no port number is specified, the system will assign one. -

-
+

zone {zonename}
-
-

+

Specifies that all updates are to be made to the zone zonename. If no @@ -347,38 +281,32 @@ nsupdate will attempt determine the correct zone to update based on the rest of the input. -

-
+

class {classname}
-
-

+

Specify the default class. If no class is specified, the default class is IN. -

-
+

ttl {seconds}
-
-

+

Specify the default time to live for records to be added. The value none will clear the default ttl. -

-
+

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 @@ -386,67 +314,55 @@ hmac-md5. The key command overrides any key specified on the command line via -y or -k. -

-
+

gsstsig
-
-

+

Use GSS-TSIG to sign the updated. This is equivalent to specifying -g on the commandline. -

-
+

oldgsstsig
-
-

+

Use the Windows 2000 version of GSS-TSIG to sign the updated. This is equivalent to specifying -o on the commandline. -

-
+

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

-
+

[prereq] nxdomain {domain-name}
-
-

+

Requires that no resource record of any type exists with name domain-name. -

-
+

[prereq] yxdomain {domain-name}
-
-

+

Requires that domain-name exists (has as at least one resource record, of any type). -

-
+

[prereq] nxrrset {domain-name} [class] {type}
-
-

+

Requires that no resource record exists of the specified type, class @@ -455,16 +371,14 @@ If class is omitted, IN (internet) is assumed. -

-
+

[prereq] yxrrset {domain-name} [class] {type}
-
-

+

This requires that a resource record of the specified type, class @@ -474,8 +388,7 @@ If class is omitted, IN (internet) is assumed. -

-
+

[prereq] yxrrset {domain-name} @@ -483,8 +396,7 @@ {type} {data...}
-
-

+

The data from each set of prerequisites of this form @@ -505,8 +417,7 @@ are written in the standard text representation of the resource record's RDATA. -

-
+

[update] del[ete] {domain-name} @@ -514,8 +425,7 @@ [class] [type [data...]]
-
-

+

Deletes any resource records named domain-name. If @@ -528,8 +438,7 @@ is not supplied. The ttl is ignored, and is only allowed for compatibility. -

-
+

[update] add {domain-name} @@ -538,80 +447,62 @@ {type} {data...}
-
-

+

Adds a new resource record with the specified ttl, class and data. -

-
+

show
-
-

+

Displays the current message, containing all of the prerequisites and updates specified since the last send. -

-
+

send
-
-

+

Sends the current message. This is equivalent to entering a blank line. -

-
+

answer
-
-

+

Displays the answer. -

-
+

debug
-
-

+

Turn on debugging. -

-
+

version
-
-

+

Print version number. -

-
+

help
-
-

+

Print a list of commands. -

-
+

- -

+

Lines beginning with a semicolon are comments and are ignored.

- -
- -
-

EXAMPLES

- -

+

+
+

EXAMPLES

+

The examples below show how nsupdate could be used to insert and delete resource records from the @@ -632,7 +523,7 @@

-

+

Any A records for oldhost.example.com are deleted. @@ -649,7 +540,7 @@

-

+

The prerequisite condition gets the name server to check that there are no resource records of any type for nickname.example.com. @@ -662,50 +553,33 @@ (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, @@ -713,27 +587,19 @@ 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.

-
+
diff --git a/bin/python/dnssec-checkds.8 b/bin/python/dnssec-checkds.8 index 75ecb7d46a..ac771f7102 100644 --- a/bin/python/dnssec-checkds.8 +++ b/bin/python/dnssec-checkds.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-checkds .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-01-02 .\" Manual: BIND9 .\" Source: ISC @@ -46,9 +46,9 @@ .SH "NAME" dnssec-checkds \- A DNSSEC delegation consistency checking tool\&. .SH "SYNOPSIS" -.HP 15 +.HP \w'\fBdnssec\-checkds\fR\ 'u \fBdnssec\-checkds\fR [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIdig\ path\fR\fR] [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR] {zone} -.HP 17 +.HP \w'\fBdnssec\-dsfromkey\fR\ 'u \fBdnssec\-dsfromkey\fR [\fB\-l\ \fR\fB\fIdomain\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIdig\ path\fR\fR] [\fB\-D\ \fR\fB\fIdsfromkey\ path\fR\fR] {zone} .SH "DESCRIPTION" .PP diff --git a/bin/python/dnssec-checkds.html b/bin/python/dnssec-checkds.html index 42f57cba8b..556a21ce15 100644 --- a/bin/python/dnssec-checkds.html +++ b/bin/python/dnssec-checkds.html @@ -17,109 +17,62 @@ dnssec-checkds - + -
+
- - - - - -
+

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 -

-
+

-d dig path
-
-

+

Specifies a path to a dig binary. Used for testing. -

-
+

-D dsfromkey path
-
-

+

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

-
- +
diff --git a/bin/python/dnssec-coverage.8 b/bin/python/dnssec-coverage.8 index 880adf0f50..890ff64e50 100644 --- a/bin/python/dnssec-coverage.8 +++ b/bin/python/dnssec-coverage.8 @@ -17,7 +17,7 @@ '\" t .\" Title: dnssec-coverage .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-03-21 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" dnssec-coverage \- checks future DNSKEY coverage for a zone .SH "SYNOPSIS" -.HP 16 +.HP \w'\fBdnssec\-coverage\fR\ 'u \fBdnssec\-coverage\fR [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-f\ \fR\fB\fIfile\fR\fR] [\fB\-d\ \fR\fB\fIDNSKEY\ TTL\fR\fR] [\fB\-m\ \fR\fB\fImax\ TTL\fR\fR] [\fB\-r\ \fR\fB\fIinterval\fR\fR] [\fB\-c\ \fR\fB\fIcompilezone\ path\fR\fR] [zone] .SH "DESCRIPTION" .PP diff --git a/bin/python/dnssec-coverage.html b/bin/python/dnssec-coverage.html index f3796d7005..e7df69ba4e 100644 --- a/bin/python/dnssec-coverage.html +++ b/bin/python/dnssec-coverage.html @@ -18,48 +18,26 @@ dnssec-coverage - + -
+
- - - - - -
+

Name

-

- dnssec-coverage - — checks future DNSKEY coverage for a zone -

+

dnssec-coverage — checks future DNSKEY coverage for a zone

- - - -
+

Synopsis

-

- dnssec-coverage - [-K directory] - [-f file] - [-d DNSKEY TTL] - [-m max TTL] - [-r interval] - [-c compilezone path] - [zone] -

-
- -
-

DESCRIPTION

- -

dnssec-coverage +

dnssec-coverage [-K directory] [-f file] [-d DNSKEY TTL] [-m max TTL] [-r interval] [-c compilezone path] [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., @@ -72,40 +50,33 @@ 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

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

-
+

-K directory
-
-

+

Sets the directory in which keys can be found. Defaults to the current working directory. -

-
+

-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 @@ -114,21 +85,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 @@ -138,12 +109,12 @@ 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 @@ -151,10 +122,10 @@ 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 @@ -164,40 +135,27 @@ 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.

-
+
-c compilezone path
-
-

+

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)

-
- +
diff --git a/bin/rndc/rndc.8 b/bin/rndc/rndc.8 index ce98e532d8..bbdda2a97b 100644 --- a/bin/rndc/rndc.8 +++ b/bin/rndc/rndc.8 @@ -18,7 +18,7 @@ '\" t .\" Title: rndc .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-12-04 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" rndc \- name server control utility .SH "SYNOPSIS" -.HP 5 +.HP \w'\fBrndc\fR\ 'u \fBrndc\fR [\fB\-b\ \fR\fB\fIsource\-address\fR\fR] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-k\ \fR\fB\fIkey\-file\fR\fR] [\fB\-s\ \fR\fB\fIserver\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-V\fR] [\fB\-y\ \fR\fB\fIkey_id\fR\fR] {command} .SH "DESCRIPTION" .PP @@ -255,8 +255,7 @@ See also Enable or disable query logging\&. (For backward compatibility, this command can also be used without an argument to toggle query logging on and off\&.) .sp Query logging can also be enabled by explicitly directing the -\fBqueries\fR -\fBcategory\fR +\fBqueries\fR\fBcategory\fR to a \fBchannel\fR in the diff --git a/bin/rndc/rndc.conf.5 b/bin/rndc/rndc.conf.5 index e02104b1bf..1bb0ab6a8c 100644 --- a/bin/rndc/rndc.conf.5 +++ b/bin/rndc/rndc.conf.5 @@ -18,7 +18,7 @@ '\" t .\" Title: rndc.conf .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2007-06-18 .\" Manual: BIND9 .\" Source: ISC @@ -47,7 +47,7 @@ .SH "NAME" rndc.conf \- rndc configuration file .SH "SYNOPSIS" -.HP 10 +.HP \w'\fBrndc\&.conf\fR\ 'u \fBrndc\&.conf\fR .SH "DESCRIPTION" .PP diff --git a/bin/rndc/rndc.conf.html b/bin/rndc/rndc.conf.html index bec43f9ff4..46fab08554 100644 --- a/bin/rndc/rndc.conf.html +++ b/bin/rndc/rndc.conf.html @@ -18,36 +18,21 @@ rndc.conf - + -
+
- - - - - -
+

Name

-

- rndc.conf - — rndc configuration file -

+

rndc.conf — rndc configuration file

- - - -
+

Synopsis

-

- rndc.conf -

-
- -
-

DESCRIPTION

- -

rndc.conf is the configuration file +

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 @@ -55,21 +40,21 @@ 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 @@ -92,7 +77,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: @@ -106,7 +91,7 @@ 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 encryption algorithm @@ -116,7 +101,7 @@ the base-64 encoding of the algorithm's encryption 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 can @@ -129,13 +114,10 @@ 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;
@@ -143,14 +125,14 @@

- 
+
       server localhost {
         key             samplekey;
       };
 

 

     

-    
+
       server testserver {
         key		testkey;
         addresses	{ localhost port 5353; };
@@ -158,7 +140,7 @@
 

 

     

-    
+
       key samplekey {
         algorithm       hmac-md5;
         secret          "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
@@ -166,7 +148,7 @@
 

 

     

-    
+
       key testkey {
         algorithm	hmac-md5;
         secret		"R3HI8P6BKw9ZwXwN3VZKuQ==";
@@ -174,8 +156,7 @@
     

 

     

-
-    

+

       In the above example, rndc will by
       default use
       the server at localhost (127.0.0.1) and the key called samplekey.
@@ -185,16 +166,16 @@
       uses the HMAC-MD5 algorithm and its secret clause contains the
       base-64 encoding of the HMAC-MD5 secret enclosed in double quotes.
     

-    

+

       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:
     

-    
rndc-confgen
+
rndc-confgen
     

-    

+

       A complete rndc.conf file, including
       the
       randomly generated key, will be written to the standard
@@ -202,40 +183,29 @@
       controls statements for
       named.conf are also printed.
     

-    

+

       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.

-
- +
diff --git a/bin/rndc/rndc.html b/bin/rndc/rndc.html index 98bea825b7..7bc342ae23 100644 --- a/bin/rndc/rndc.html +++ b/bin/rndc/rndc.html @@ -18,44 +18,21 @@ rndc - + -
+
- - - - - -
+

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] - [-V] - [-y key_id] - {command} -

-
- -
-

DESCRIPTION

- -

rndc +

rndc [-b source-address] [-c config-file] [-k key-file] [-s server] [-p port] [-V] [-y key_id] {command}

+
+
+

DESCRIPTION

+

rndc controls the operation of a name server. It supersedes the ndc utility that was provided in old BIND releases. If @@ -64,7 +41,7 @@ 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 @@ -76,38 +53,30 @@ 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 @@ -115,37 +84,29 @@ 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 command line, the host named by the default-server clause 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. -

-
+

-V
-
-

+

Enable verbose logging. -

-
+

-y key_id
-
-

+

Use the key key_id from the configuration file. key_id @@ -161,26 +122,22 @@ which are used to send authenticated control commands to name servers. It should therefore not have general read or write access. -

-
+

-
- -
-

COMMANDS

- -

+

+
+

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 @@ -190,7 +147,7 @@ configuration text that would ordinarily be placed in named.conf.

-

+

The configuration is saved in a file called hash.nzf, where hash is a @@ -200,37 +157,36 @@ configuration, so that zones that were added can persist after a restart.

-

+

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.

-
+
delzone zone [class [view]]
-

+

Delete a zone while the server is running. Only zones that were originally added via rndc addzone can be deleted in this manner.

-

+

See also rndc addzone

-
+
dumpdb [-all|-cache|-zone|-adb|-bad] [view ...]
-
-

+

Dump the server's caches (default) and/or zones to the dump file for the specified views. If no view is @@ -238,34 +194,27 @@ views are dumped. (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 or bad-server cache. -

-
+

flushtree name [view]
-
-

+

Flushes the given name, and all of its subdomains, from the view's DNS cache. Note that this does not affect he server's address database or bad-server 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,13 +223,13 @@ All dynamic update attempts will be refused while the zone is frozen.

-

+

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 @@ -289,13 +238,13 @@ This allows an external process to determine when named had completed halting.

-

+

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 @@ -304,7 +253,7 @@ 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 be set to maintain, @@ -313,30 +262,28 @@ (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)

-
+
notify zone [class [view]]
-
-

+

Resend NOTIFY messages for the zone. -

-
+

notrace
-

+

Sets the server's debugging level to 0.

-

+

See also rndc trace.

-
+
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 @@ -347,10 +294,9 @@ 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. @@ -358,43 +304,34 @@ 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 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 version of the zone is discarded; after the @@ -402,19 +339,17 @@ signed version will be regenerated with all new signatures.

-
+
secroots [view ...]
-
-

+

Dump the server's security roots to the secroots file for the specified views. If no view is specified, security roots for all views are dumped. -

-
+

sign zone [class [view]]
-

+

Fetch all DNSSEC keys for the given zone from the key directory (see the key-directory option in @@ -424,7 +359,7 @@ 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 to allow or @@ -434,13 +369,13 @@ (See "Dynamic Update Policies" in the Administrator Reference Manual for more details.)

-

+

See also rndc loadkeys.

-
+
signing [( -list | -clear keyid/algorithm | -clear all | -nsec3param ( parameters | none ) ) ] 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 @@ -453,7 +388,7 @@ or have finished signing the zone, and which NSEC3 chains are being created or removed.

-

+

rndc signing -clear can remove a single key (specified in the same format that rndc signing -list uses to @@ -462,7 +397,7 @@ that a key has not yet finished signing the zone will be retained.

-

+

rndc signing -nsec3param sets the NSEC3 parameters for a zone. This is the only supported mechanism for using NSEC3 with @@ -471,7 +406,7 @@ 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 @@ -484,7 +419,7 @@ in hexadecimal, or a hyphen (`-') if no salt is to be used.

-

+

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: @@ -493,33 +428,29 @@ salt, use: rndc signing -nsec3param 1 1 15 - zone.

-

+

rndc signing -nsec3param none removes an existing NSEC3 chain and replaces it with NSEC.

-
+
stats
-
-

+

Write server statistics to the statistics file. (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 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. @@ -527,20 +458,18 @@ 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 @@ -554,88 +483,65 @@ 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.

-
+
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 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 set to yes or auto to be effective. It defaults to enabled. -

-
+

-
- -
-

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.

-
- +
diff --git a/bin/tools/arpaname.1 b/bin/tools/arpaname.1 index a04d567ac4..d5bb1b5af7 100644 --- a/bin/tools/arpaname.1 +++ b/bin/tools/arpaname.1 @@ -17,7 +17,7 @@ '\" t .\" Title: arpaname .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-03-03 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" arpaname \- translate IP addresses to the corresponding ARPA names .SH "SYNOPSIS" -.HP 9 +.HP \w'\fBarpaname\fR\ 'u \fBarpaname\fR {\fIipaddress\ \fR...} .SH "DESCRIPTION" .PP diff --git a/bin/tools/arpaname.html b/bin/tools/arpaname.html index 899706ec82..b54ddd1614 100644 --- a/bin/tools/arpaname.html +++ b/bin/tools/arpaname.html @@ -17,48 +17,30 @@ arpaname - + -
+
- - - - -
+

Name

-

- arpaname - — translate IP addresses to the corresponding ARPA names -

+

arpaname — translate IP addresses to the corresponding ARPA names

- - - -
+

Synopsis

-

- arpaname - {ipaddress ...} -

-
- -
-

DESCRIPTION

- -

+

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.

-
- +
diff --git a/bin/tools/genrandom.8 b/bin/tools/genrandom.8 index 4dec0f005b..d51956b326 100644 --- a/bin/tools/genrandom.8 +++ b/bin/tools/genrandom.8 @@ -17,7 +17,7 @@ '\" t .\" Title: genrandom .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2011-08-08 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" genrandom \- generate a file containing random data .SH "SYNOPSIS" -.HP 10 +.HP \w'\fBgenrandom\fR\ 'u \fBgenrandom\fR [\fB\-n\ \fR\fB\fInumber\fR\fR] {\fIsize\fR} {\fIfilename\fR} .SH "DESCRIPTION" .PP diff --git a/bin/tools/genrandom.html b/bin/tools/genrandom.html index 952f2dd198..f61f57a38f 100644 --- a/bin/tools/genrandom.html +++ b/bin/tools/genrandom.html @@ -17,84 +17,51 @@ genrandom - + -
+
- - - - - -
+

Name

-

- genrandom - — generate a file containing random data -

+

genrandom — generate a file containing random data

- - - -
+

Synopsis

-

- genrandom - [-n number] - {size} - {filename} -

-
- -
-

DESCRIPTION

- -

+

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)

-
- +
diff --git a/bin/tools/isc-hmac-fixup.8 b/bin/tools/isc-hmac-fixup.8 index 4bb67a3803..0f60791043 100644 --- a/bin/tools/isc-hmac-fixup.8 +++ b/bin/tools/isc-hmac-fixup.8 @@ -17,7 +17,7 @@ '\" t .\" Title: isc-hmac-fixup .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2013-04-28 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" isc-hmac-fixup \- fixes HMAC keys generated by older versions of BIND .SH "SYNOPSIS" -.HP 15 +.HP \w'\fBisc\-hmac\-fixup\fR\ 'u \fBisc\-hmac\-fixup\fR {\fIalgorithm\fR} {\fIsecret\fR} .SH "DESCRIPTION" .PP diff --git a/bin/tools/isc-hmac-fixup.html b/bin/tools/isc-hmac-fixup.html index 24e2539abf..5bd25586fe 100644 --- a/bin/tools/isc-hmac-fixup.html +++ b/bin/tools/isc-hmac-fixup.html @@ -17,38 +17,21 @@ isc-hmac-fixup - + -
+
- - - - - -
+

Name

-

- isc-hmac-fixup - — fixes HMAC keys generated by older versions of BIND -

+

isc-hmac-fixup — fixes HMAC keys generated by older versions of BIND

- - - -
+

Synopsis

-

- isc-hmac-fixup - {algorithm} - {secret} -

-
- -
-

DESCRIPTION

- -

+

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 @@ -56,13 +39,13 @@ 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 modifies those keys to restore compatibility.

-

+

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 @@ -71,12 +54,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 operation anyway, it does not affect security. RFC 2104 notes, @@ -84,16 +65,13 @@ extra length would not significantly increase the function strength."

-
- -
-

SEE ALSO

- -

+

+
+

SEE ALSO

+

BIND 9 Administrator Reference Manual, RFC 2104.

-
- +
diff --git a/bin/tools/named-journalprint.8 b/bin/tools/named-journalprint.8 index 1972b18dee..8363739c01 100644 --- a/bin/tools/named-journalprint.8 +++ b/bin/tools/named-journalprint.8 @@ -17,7 +17,7 @@ '\" t .\" Title: named-journalprint .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-12-04 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" named-journalprint \- print zone journal in human\-readable form .SH "SYNOPSIS" -.HP 19 +.HP \w'\fBnamed\-journalprint\fR\ 'u \fBnamed\-journalprint\fR {\fIjournal\fR} .SH "DESCRIPTION" .PP diff --git a/bin/tools/named-journalprint.html b/bin/tools/named-journalprint.html index f9145322c5..eee59983f8 100644 --- a/bin/tools/named-journalprint.html +++ b/bin/tools/named-journalprint.html @@ -17,42 +17,26 @@ named-journalprint - + -
+
- - - - - -
+

Name

-

- named-journalprint - — print zone journal in human-readable form -

+

named-journalprint — print zone journal in human-readable form

- - - -
+

Synopsis

-

- named-journalprint - {journal} -

-
- -
-

DESCRIPTION

- -

+

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 when changes are made to dynamic zones (e.g., by nsupdate). They record each addition @@ -63,28 +47,21 @@ .jnl to the name of the corresponding zone file.

-

+

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.

-
- +
diff --git a/bin/tools/nsec3hash.8 b/bin/tools/nsec3hash.8 index d71fea045d..39ff3b48f4 100644 --- a/bin/tools/nsec3hash.8 +++ b/bin/tools/nsec3hash.8 @@ -17,7 +17,7 @@ '\" t .\" Title: nsec3hash .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.76.1 +.\" Generator: DocBook XSL Stylesheets v1.78.1 .\" Date: 2009-03-02 .\" Manual: BIND9 .\" Source: ISC @@ -46,7 +46,7 @@ .SH "NAME" nsec3hash \- generate NSEC3 hash .SH "SYNOPSIS" -.HP 10 +.HP \w'\fBnsec3hash\fR\ 'u \fBnsec3hash\fR {\fIsalt\fR} {\fIalgorithm\fR} {\fIiterations\fR} {\fIdomain\fR} .SH "DESCRIPTION" .PP diff --git a/bin/tools/nsec3hash.html b/bin/tools/nsec3hash.html index 7de7718e28..e5de8fca9a 100644 --- a/bin/tools/nsec3hash.html +++ b/bin/tools/nsec3hash.html @@ -17,88 +17,56 @@ nsec3hash - + -
+
- - - - - -
+

Name

-

- nsec3hash - — generate NSEC3 hash -

+

nsec3hash — generate NSEC3 hash

- - - -
+

Synopsis

-

- nsec3hash - {salt} - {algorithm} - {iterations} - {domain} -

-
- -
-

DESCRIPTION

- -

+

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.

-
- +
diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index 6d2dc127bd..d3a608e8b2 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -18,7 +18,7 @@ Chapter 1. Introduction - + @@ -38,28 +38,27 @@
-
-

-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,13 +68,10 @@ 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 @@ -84,14 +80,12 @@ BIND version 9 software package for system administrators.

-

This version of the manual corresponds to BIND version 9.9.

-
- -
+<para>This version of the manual corresponds to BIND version 9.9.</para> +
+

-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 @@ -116,19 +110,15 @@ 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:

- -
- +
@@ -185,14 +175,11 @@ -
-
- -

+

+

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

-
- +
@@ -247,37 +234,31 @@ -
-
+

-
-
+
+

-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. @@ -288,14 +269,11 @@ 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 @@ -306,8 +284,7 @@ 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, @@ -319,8 +296,7 @@ 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 @@ -328,32 +304,27 @@ 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”.

- -

+

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

-
- -
+
+

-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 @@ -365,8 +336,7 @@ 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 @@ -388,8 +358,7 @@ 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 @@ -399,14 +368,11 @@ 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. @@ -414,20 +380,16 @@ 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”).

- -
+

-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 @@ -438,19 +400,16 @@ 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 @@ -462,14 +421,11 @@ 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. @@ -480,8 +436,7 @@ 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 @@ -492,8 +447,7 @@ 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 @@ -501,19 +455,12 @@ 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 @@ -525,27 +472,22 @@ 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 @@ -553,8 +495,7 @@ 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 @@ -568,23 +509,18 @@ 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. @@ -599,11 +535,9 @@ does not need to be reachable from the Internet at large and can be placed inside a firewall.

- -
-
- -
+
+
+
diff --git a/doc/arm/Bv9ARM.ch02.html b/doc/arm/Bv9ARM.ch02.html index 8bd7a36950..60bd85321f 100644 --- a/doc/arm/Bv9ARM.ch02.html +++ b/doc/arm/Bv9ARM.ch02.html @@ -18,7 +18,7 @@ Chapter 2. BIND Resource Requirements - + @@ -38,33 +38,29 @@
-
-

-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 @@ -73,25 +69,22 @@ 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 option can be used to limit the amount of memory used by the cache, @@ -110,14 +103,11 @@ 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 @@ -130,13 +120,11 @@ 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 @@ -146,8 +134,8 @@ directory of the BIND 9 source distribution.

-
-
+
+
diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index d052caf28c..03d28207d5 100644 --- a/doc/arm/Bv9ARM.ch03.html +++ b/doc/arm/Bv9ARM.ch03.html @@ -18,7 +18,7 @@ Chapter 3. Name Server Configuration - + @@ -38,41 +38,37 @@
-
-

-Chapter 3. Name Server Configuration

+
+

+Chapter 3. Name Server Configuration

Table of Contents

-
+
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 @@ -81,7 +77,6 @@ suitable firewall rules.

- 
 // Two corporate subnets we wish to allow queries from.
 acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
@@ -99,19 +94,15 @@ 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
@@ -150,31 +141,23 @@ 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:

- -
- +
@@ -288,55 +271,47 @@ 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.

- -
- -
+
+

-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 line tools for manually querying name servers. They differ in style and output format.

- -
+
dig
-

+

The domain information groper (dig) is the most versatile and complete of these lookup tools. It has two modes: simple interactive @@ -346,31 +321,22 @@ zone "eng.example.com" { accessible from the command line.

-

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

-

+

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

+

The usual simple use of dig will take the form

-

+

dig @server domain query-type query-class

-

+

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

-
+
host
-

+

The host utility emphasizes simplicity and ease of use. By default, it converts @@ -378,29 +344,16 @@ zone "eng.example.com" { 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 page.

-
+
nslookup
-

nslookup +

nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query name servers for information about various @@ -409,15 +362,8 @@ 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 @@ -425,7 +371,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. @@ -433,77 +379,56 @@ 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.

-
+
-
- -
+
+

Administrative Tools

- -

+

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

-
+
named-checkconf
-

+

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
-

+

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
-

+

The remote name daemon control (rndc) program allows the system @@ -518,21 +443,11 @@ zone "eng.example.com" { 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 +

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, since all communication with the server is authenticated with @@ -556,8 +471,7 @@ zone "eng.example.com" { the section called “controls Statement Definition and Usage”.

- -

+

The format of the configuration file is similar to that of named.conf, but limited to @@ -569,8 +483,7 @@ zone "eng.example.com" { be shared. The order of statements is not significant.

- -

+

The options statement has three clauses: default-server, default-key, @@ -588,8 +501,7 @@ zone "eng.example.com" { port is given on the command line or in a server statement.

- -

+

The key statement defines a key to be used by rndc when authenticating @@ -612,8 +524,7 @@ zone "eng.example.com" { has any meaning. The secret is a base-64 encoded string as specified in RFC 3548.

- -

+

The server statement associates a key defined using the key @@ -629,11 +540,9 @@ zone "eng.example.com" { connect to on the server.

- -

+

A sample minimal configuration file is as follows:

- 
 key rndc_key {
      algorithm "hmac-md5";
@@ -645,36 +554,30 @@ 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 program will conveniently create a rndc.conf @@ -689,24 +592,19 @@ controls { 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.

-
- +
@@ -744,11 +642,10 @@ controls { -
-
-
-
-
+
+
+
+
diff --git a/doc/arm/Bv9ARM.ch04.html b/doc/arm/Bv9ARM.ch04.html index 17d6341e8c..3d1de562a4 100644 --- a/doc/arm/Bv9ARM.ch04.html +++ b/doc/arm/Bv9ARM.ch04.html @@ -18,7 +18,7 @@ Chapter 4. Advanced DNS Features - + @@ -38,88 +38,83 @@
-
-

-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
+
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)
+
TKEY
+
SIG(0)
DNSSEC
-
Generating Keys
-
Signing the Zone
-
Configuring Servers
+
Generating Keys
+
Signing the Zone
+
Configuring Servers
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
-
Validating Resolver
-
Authoritative Server
+
Validating Resolver
+
Authoritative Server
PKCS #11 (Cryptoki) support
-
Prerequisites
-
Building BIND 9 with PKCS#11
-
PKCS #11 Tools
-
Using the HSM
-
Specifying the engine on the command line
-
Running named with automatic zone re-signing
+
Prerequisites
+
Building BIND 9 with PKCS#11
+
PKCS #11 Tools
+
Using the HSM
+
Specifying the engine on the command line
+
Running named with automatic zone re-signing
-
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 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 @@ -127,8 +122,7 @@ 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 @@ -136,36 +130,29 @@ 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.

- -

+

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.

- -

+

Dynamic updates using Kerberos signed requests can be made using the TKEY/GSS protocol by setting either the tkey-gssapi-keytab option, or alternatively @@ -175,21 +162,17 @@ 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. @@ -199,8 +182,7 @@ 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 @@ -213,29 +195,25 @@ 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.

- -

+

If you have to make changes to a dynamic zone manually, the following procedure will work: Disable dynamic updates to the zone using @@ -246,8 +224,7 @@ rndc thaw zone to reload the changed zone and re-enable dynamic updates.

- -

+

rndc sync zone will update the zone file with changes from the journal file without stopping dynamic updates; this may be useful for viewing @@ -255,24 +232,18 @@ file after updating the zone file, use 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.

- -

+

When acting as a master, BIND 9 supports IXFR for those zones where the necessary change history information is available. These @@ -283,27 +254,24 @@ 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.

-
- -
+
+

-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 @@ -317,18 +285,17 @@ 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 @@ -336,14 +303,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 @@ -351,7 +318,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 @@ -360,20 +327,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 @@ -382,11 +349,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 @@ -394,72 +361,57 @@ 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”.

      - -

      +

      Internal DNS server config:

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

      +

      External (bastion host) DNS server config:

      - 
       acl internals { 172.16.72.0/24; 192.168.1.0/24; };
 
@@ -560,41 +510,36 @@ 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. @@ -604,137 +549,124 @@ nameserver 172.16.72.4 -y command line options or inline by use 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 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 @@ -743,31 +675,25 @@ server 10.1.2.3 { This has been extended to allow TSIG keys also. The above key would be denoted key host1-host2.

-

+

An example of an allow-update directive would be:

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

+

This allows dynamic updates to succeed only if the request 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.

- - -
+
+

-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 @@ -775,8 +701,7 @@ 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 @@ -789,15 +714,12 @@ 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 @@ -812,8 +734,7 @@ allow-update { key host1-host2. ;}; used to delete shared secrets that it had previously generated.

- -

+

The TKEY process is initiated by a client or server by sending a signed TKEY @@ -830,14 +751,11 @@ allow-update { key host1-host2. ;}; 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) @@ -845,37 +763,30 @@ 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.

- - -
+
+

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 @@ -888,8 +799,7 @@ 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 @@ -898,24 +808,19 @@ 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

- - -

+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 @@ -926,17 +831,14 @@ allow-update { key host1-host2. ;}; 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 @@ -952,36 +854,29 @@ 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 to get a key pair from a crypto hardware and build the key 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.

- - -
+
+

-Signing the Zone

- - -

+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 @@ -991,19 +886,16 @@ 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 @@ -1011,38 +903,31 @@ 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

- - -

+Configuring Servers

+

To enable named to respond appropriately to DNS requests from DNSSEC aware clients, 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 must be set to yes, and the dnssec-validation options must be set to yes or auto.

- -

+

If dnssec-validation is set to auto, then a default trust anchor for the DNS root zone will be used. @@ -1054,8 +939,7 @@ allow-update { key host1-host2. ;}; will not occur. The default setting is yes.

- -

+

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 @@ -1063,27 +947,23 @@ allow-update { key host1-host2. ;}; 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 automatically kept up to date via RFC 5011 trust anchor maintenance.

- -

+

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 @@ -1093,7 +973,6 @@ allow-update { key host1-host2. ;}; is immune to compromises in the DNSSEC components of the security of parent zones.

- 
 managed-keys {
         /* Root Key */
@@ -1146,69 +1025,59 @@ 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 +

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 @@ -1216,7 +1085,7 @@ options { 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;
@@ -1224,35 +1093,32 @@ options {
                 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:

-  
+

+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
   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=
@@ -1260,32 +1126,29 @@ options {
         > 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
   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 
+

+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: 
   allow or 
   maintain.

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

-  

+

   
   auto-dnssec maintain includes the above
   functionality, but will also automatically adjust the zone's
@@ -1293,7 +1156,7 @@ options {
   (See dnssec-keygen(8) and
   dnssec-settime(8) for more information.) 
   

-  

+

   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,
@@ -1303,21 +1166,21 @@ options {
   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
   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
   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
@@ -1327,28 +1190,25 @@ options {
   the zone is signed and the NSEC3 chain is completed, the NSEC3PARAM
   record will appear in the zone.
   

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

-  

+

     

 


 

@@ -1359,15 +1219,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.

-  

+

     

 


 

@@ -1378,20 +1238,14 @@ 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
+

+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
   DNSKEY RRs via dynamic update. 
@@ -1399,24 +1253,21 @@ options {
   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
   by the old key after the update completes.

-  

-

-Automatic key rollovers

-    
-  

-  
When a new key reaches its activation date (as set by
+

+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
@@ -1429,69 +1280,51 @@ 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,
   and associated NSEC3PARAM records will be removed automatically.
   This will take place after the update request completes.

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

-  

-

-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

-    
-  

-  

+

+NSEC3 and OPTOUT

+

   named only supports creating new NSEC3 chains
   where all the NSEC3 records in the zone have the same OPTOUT
   state. 
@@ -1502,39 +1335,33 @@ options {
   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 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 this can be found in 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 KSK's 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 @@ -1543,7 +1370,7 @@ 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 @@ -1551,88 +1378,82 @@ options { the future, " 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 
+
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 ID's exactly 128 apart, and one is
+
If two keys have ID's exactly 128 apart, and one is
     revoked, then the two key ID's will collide, causing several
     problems. To prevent this, 
     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 ID's.

-  
 
-
-    

+

+

 

 PKCS #11 (Cryptoki) support

-  
-  
PKCS #11 (Public Key Cryptography Standard #11) defines a
+
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 two HSMs: The Sun SCA 6000
+
BIND 9 is known to work with two HSMs: The Sun SCA 6000
   cryptographic acceleration board, tested under Solaris x86, and
   the AEP Keyper network-attached key storage device, tested with
   Debian Linux, Solaris x86 and Windows Server 2003.

-  

+

 

-Prerequisites

-    
-    
See the HSM vendor documentation for information about
+Prerequisites

+
See the HSM vendor documentation for information about
     installing, initializing, testing and troubleshooting the
     HSM.

-    
BIND 9 uses OpenSSL for cryptography, but stock OpenSSL
+
BIND 9 uses OpenSSL for cryptography, but stock OpenSSL
     does not yet fully support PKCS #11. However, a PKCS #11 engine
     for OpenSSL is available from the OpenSolaris project. It has
     been modified by ISC to work with with BIND 9, and to provide
     new features such as PIN management and key by
     reference.

-    
The patched OpenSSL depends on a "PKCS #11 provider".
+
The patched OpenSSL depends on a "PKCS #11 provider".
     This is a shared library object, providing a low-level PKCS #11
     interface to the HSM hardware. It is dynamically loaded by
     OpenSSL at runtime. The PKCS #11 provider comes from the HSM
     vendor, and is specific to the HSM to be controlled.

-    
There are two "flavors" of PKCS #11 support provided by
+
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
+
      
+
    • 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
+        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
         are not necessarily any faster at cryptography than the
@@ -1641,10 +1462,9 @@ $ dnssec-signzone -S -K keys example.net<
         functions that require access to the secured private key,
         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.
      
-      
      • 
+        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
@@ -1652,104 +1472,98 @@ $ dnssec-signzone -S -K keys example.net<
       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 at the time of the BIND release
       are 0.9.8y, 1.0.0k and 1.0.1e.
       ISC will provide an updated patch as new versions of OpenSSL
       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 this patch in place and inform
     it of the path to the HSM-specific PKCS #11 provider
     library.
    
-    
    Obtain OpenSSL 0.9.8s:
    
-    
    -$ wget http://www.openssl.org/source/openssl-0.9.8s.tar.gz
+
    Obtain OpenSSL 0.9.8s:
    
+
    +$ wget http://www.openssl.org/source/openssl-0.9.8s.tar.gz
 
    
-    
    Extract the tarball:
    
-    
    +
    Extract the tarball:
    
+
     $ tar zxf openssl-0.9.8s.tar.gz
 
    
-    
    Apply the patch from the BIND 9 release:
    
-    
    +
    Apply the patch from the BIND 9 release:
    
+
     $ patch -p1 -d openssl-0.9.8s \
             < bind9/bin/pkcs11/openssl-0.9.8s-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
+
    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.
    
-    
    
+
    
 
    
-Building OpenSSL for the AEP Keyper on Linux
    
-      
-      
-      
    The AEP Keyper is a highly secure key storage device,
+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
+
    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
+
    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
+
    Finally, the Keyper library requires threads, so we
       must specify -pthread.
    
-      
    +
     $ cd openssl-0.9.8s
 $ ./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"
+
    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
    
-      
-      
-      
    The SCA-6000 PKCS #11 provider is installed as a system
+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
+
In this example, we are building on Solaris x86 on an
       AMD64 system.

-      
+
 $ cd openssl-0.9.8s
 $ ./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
+
(For a 32-bit build, use "solaris-x86-cc" and
       /usr/lib/libpkcs11.so.)

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

-    
-    

+

+

 

-Building OpenSSL for SoftHSM

-      
-      
-      
SoftHSM is a software library provided by the OpenDNSSEC
+Building OpenSSL for SoftHSM

+
SoftHSM is a software library provided by the OpenDNSSEC
       project (http://www.opendnssec.org) which provides a PKCS#11
       interface to a virtual HSM, implemented in the form of encrypted
       data on the local filesystem.  It uses the Botan library for
@@ -1757,11 +1571,11 @@ $ ./Configure solaris64-x86_64-cc \
       than a true HSM, it can provide more secure key storage than
       traditional key files, and can allow you to experiment with
       PKCS#11 when an HSM is not available.

-      
The SoftHSM cryptographic store must be installed and
+
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.0 
 $  configure --prefix=/opt/pkcs11/usr 
 $  make 
@@ -1770,144 +1584,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
+
SoftHSM can perform all cryptographic operations, but
       since it only uses your system CPU, there is no need to use it
       for anything but signing.  Therefore, we choose the 'sign-only'
       flavor when building OpenSSL.

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

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

-    
-    
Once you have built OpenSSL, run
+
+
Once you have built OpenSSL, run
     "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
+
Next, run
     "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 ]”.

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

-  
-  

+

+

 

-Building BIND 9 with PKCS#11

-    
-    
When building BIND 9, the location of the custom-built
+Building BIND 9 with PKCS#11

+
When building BIND 9, the location of the custom-built
     OpenSSL library must be specified via configure.

-    

+

 

-Configuring BIND 9 for Linux with the AEP Keyper

-      
-      
-      
To link with the PKCS #11 provider, threads must be
+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
+
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

-      
-      
-      
To link with the PKCS #11 provider, threads must be
+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".)

-      
If configure complains about OpenSSL not working, you
+
(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/libpkcs11.so
 

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

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

-  
-  

+

+

 

-PKCS #11 Tools

-    
-    
BIND 9 includes a minimal set of tools to operate the
+PKCS #11 Tools

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

-    
In UNIX/Linux builds, these tools are built only if BIND
+
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
     PKCS #11 provider, then the tools will be built but the
     provider will be left undefined. Use the -m option or the
     PKCS11_PROVIDER environment variable to specify the path to the
     provider.)

-  
-  

+

+

 

-Using the HSM

-    
-    
First, we must set up the runtime environment so the
+Using the HSM

+
First, we must 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}
 

-    
When operating an AEP Keyper, it is also necessary to
+
When operating an AEP Keyper, it is also necessary to
     specify the location of the "machine" file, which stores
     information about the Keyper for use by PKCS #11 provider
     library. If the machine file is in 
     /opt/Keyper/PKCS11Provider/machine,
     use:

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

-    
-    
These environment variables must be set whenever running
+
These environment variables must be set whenever running
     any tool that uses the HSM, including 
     pkcs11-keygen, 
     pkcs11-list, 
@@ -1917,58 +1721,58 @@ $ export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11P
     dnssec-keygen(which will use the HSM for
     random number generation), and 
     named.

-    
We can now create and use keys in the HSM. In this case,
+
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
+
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
+
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
     public key data, plus an identifier for the private key which
     remains stored within the HSM. The HSM handles signing with the
     private key.

-    
If you wish to generate a second key in the HSM for use
+
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:

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

-    
Alternatively, you may prefer to generate a conventional
+
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
+
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
     frequent key-signing operation. The zone-signing key can be
     rolled more frequently, if you wish, to compensate for a
     reduction in key security.

-    
Now you can sign the zone. (Note: If not using the -S
+
Now you can sign the zone. (Note: If not using the -S
     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:
@@ -1977,12 +1781,11 @@ 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

-    
-    
The OpenSSL engine can be specified in 
+Specifying the engine on the command line

+
The OpenSSL engine 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
@@ -1990,32 +1793,31 @@ example.net.signed
     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 —
+
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 
+
This causes 
     dnssec-signzone to run as if it were compiled
     without the --with-pkcs11 option.

-  
-  

+

+

 

-Running named with automatic zone re-signing

-    
-    
If you want 
+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. This can be 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
+
The location of the openssl.cnf file can be overridden by
     setting the OPENSSL_CONF environment variable before running
     named.

-    
Sample openssl.cnf:

-    
+
Sample openssl.cnf:

+
         openssl_conf = openssl_def
         [ openssl_def ]
         engines = engine_section
@@ -2024,36 +1826,29 @@ $ dnssec-signzone -E '' -S example.net<PLACE PIN HERE>
 

-    
This will also allow the dnssec-* tools to access the HSM
+
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.)

-
-    

+

 
Warning

-      
Placing the HSM's PIN in a text file in
+
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
       OpenSSL in this way.

-    

-  

-  
-  
 
-
-    

+

+
+

 

-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
@@ -2063,8 +1858,7 @@ $ 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
@@ -2079,41 +1873,33 @@ $ 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)”.
       

-
-      

+

 

-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
@@ -2122,16 +1908,14 @@ 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. )
 

-
-      
-    
-  
+
+
+
 

 

 
diff --git a/doc/arm/Bv9ARM.ch05.html b/doc/arm/Bv9ARM.ch05.html
index 3cca06b036..a3a4c367ff 100644
--- a/doc/arm/Bv9ARM.ch05.html
+++ b/doc/arm/Bv9ARM.ch05.html
@@ -18,7 +18,7 @@
 Chapter 5. The BIND 9 Lightweight Resolver
-
+
@@ -38,34 +38,32 @@
 

 
 
 
 
 

 

 

-

-

-Chapter 5. The BIND 9 Lightweight Resolver

+

+

+Chapter 5. The BIND 9 Lightweight Resolver

 

 
Table of Contents

-

-
The Lightweight Resolver Library

+

+
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
@@ -73,21 +71,18 @@
         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
         local
         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.
@@ -96,14 +91,12 @@
         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
         caching-only name server that responds to requests using the
         lightweight
@@ -116,7 +109,7 @@
         autonomously if
         none are specified.
       

-      

+

         The lwresd daemon may also be
         configured with a
         named.conf style configuration file,
@@ -126,9 +119,8 @@
         be configured to act as a lightweight resolver daemon using the
         lwres statement in named.conf.
       

-
-    

-  
+
+
 

 

 
diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html
index 17b0d092c1..6495cb42bf 100644
--- a/doc/arm/Bv9ARM.ch06.html
+++ b/doc/arm/Bv9ARM.ch06.html
@@ -18,7 +18,7 @@
 Chapter 6. BIND 9 Configuration Reference
-
+
@@ -38,67 +38,67 @@
 

 
 
 
 
 

 

 

-

-

-Chapter 6. BIND 9 Configuration Reference

+

+

+Chapter 6. BIND 9 Configuration Reference

 

 
Table of Contents

-

+

 
Configuration File Elements

 

 
Address Match Lists

-
Comment Syntax

+
Comment Syntax

 

 
Configuration File Grammar

 

-
acl Statement Grammar

+
acl Statement Grammar

 
acl Statement Definition and
           Usage

-
controls Statement Grammar

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

 
options Statement Definition and
           Usage

 
server Statement Grammar

 
server Statement Definition and
             Usage

 
statistics-channels Statement Grammar

-
statistics-channels Statement Definition and
+
statistics-channels Statement Definition and
             Usage

 
trusted-keys Statement Grammar

-
trusted-keys Statement Definition
+
trusted-keys Statement Definition
             and Usage

-
managed-keys Statement Grammar

+
managed-keys Statement Grammar

 
managed-keys Statement Definition
             and Usage

 
view Statement Grammar

-
view Statement Definition and Usage

+
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

+
Discussion of MX Records

 
Setting TTLs

-
Inverse Mapping in IPv4

-
Other Zone File Directives

-
BIND Master File Extension: the  $GENERATE Directive

+
Inverse Mapping in IPv4

+
Other Zone File Directives

+
BIND Master File Extension: the  $GENERATE Directive

 
Additional File Formats

 

 
BIND9 Statistics

@@ -108,9 +108,7 @@
 

 

 

-    
-
-    

+

       BIND 9 configuration is broadly similar
       to BIND 8; however, there are a few new
       areas
@@ -120,23 +118,20 @@
       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:
       

-      

-        
+
@@ -494,88 +489,67 @@
               
-

 
 
 

 
 

-      

-      

+

+

 

 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
             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)
      • 
 
    • 
-              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 name of an address match list defined with
                 the acl statement
-              
-            
      • 
-
    • 
-              a nested address match list enclosed in braces
-            
      • 
+              
+
    • 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.
           
    
-
-          
    
+
    
             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
@@ -594,8 +568,7 @@
             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
@@ -611,28 +584,22 @@
             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 */

 

@@ -644,26 +611,25 @@
 # 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.
@@ -674,15 +640,14 @@
 

 
           

-
-          

+

             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
@@ -692,15 +657,14 @@
 

 
           

-          

+

             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
@@ -710,26 +674,22 @@
 

 
           

-
-          

+

 
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
@@ -737,13 +697,10 @@
         statements contain a block of sub-statements, which are also
         terminated with a semicolon.
       

-
-      

+

         The following statements are supported:
       

-
-      

-        
+
@@ -902,45 +859,34 @@
               
-

 
 
 

 
 

-      

-
-      

+

+

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

-
-      

+

 

-acl Statement Grammar

-        
-
+acl Statement Grammar

 
acl acl-name {
     address_match_list
 };
 

-
-      
-      

+

+

 

 acl Statement Definition and
           Usage

-        
-
-        

+

           The acl statement assigns a symbolic
           name to an address match list. It gets its name from a primary
           use of address match lists: Access Control Lists (ACLs).
         

-
-        

+

           The following ACLs are built-in:
         

-
-        

-          
+
@@ -1000,15 +946,11 @@
                 
-

 
 
 

 
 

-        

-
-      

-      

+

+
+

 

-controls Statement Grammar

-        
-
+controls Statement Grammar

 
controls {
    [ inet ( ip_addr | * ) [ port ip_port ]
                 allow {  address_match_list  }
@@ -1019,24 +961,19 @@
    [ unix ...; ]
 };
 

-
-      
-
-      

+

+

 

 controls Statement Definition and
           Usage

-        
-
-        

+

           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
           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
@@ -1049,13 +986,11 @@
           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.
         

-
-        

+

           The ability to issue commands over the control channel is
           restricted by the allow and
           keys clauses.
@@ -1065,8 +1000,7 @@
           elements of the address_match_list
           are ignored.
         

-
-        

+

           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,
@@ -1075,8 +1009,7 @@
           (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.
@@ -1085,8 +1018,7 @@
           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
           control channel listening on the loopback address 127.0.0.1
@@ -1100,8 +1032,7 @@
           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
@@ -1114,8 +1045,7 @@
           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
@@ -1136,27 +1066,22 @@
           readable by a group
           that contains the users who should have access.
         

-
-        

+

           To disable the command channel, use an empty
           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
@@ -1166,35 +1091,27 @@
           others. For example, the statement could include private keys
           that are readable only by the name server.
         

-
-      

-      

+

+

 

-key Statement Grammar

-        
-
+key Statement Grammar

 
key key_id {
     algorithm algorithm_id;
     secret secret_string;
 };
 

-
-      
-
-      

+

+

 

-key Statement Definition and Usage

-        
-
-        

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

-
-        

+

           The key statement can occur at the
           top level
           of the configuration file or inside a view
@@ -1205,8 +1122,7 @@
           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
@@ -1215,8 +1131,7 @@
           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.  Named
           supports hmac-md5,
@@ -1230,13 +1145,10 @@
           to be used by the algorithm, and is treated as a base-64
           encoded string.
         

-
-      
-      

+

+

 

-logging Statement Grammar

-        
-
+logging Statement Grammar

 
logging {
    [ channel channel_name {
      ( file path_name
@@ -1257,16 +1169,12 @@
    ...
 };
 

-
-      
-
-      

+

+

 

-logging Statement Definition and
+logging Statement Definition and
           Usage

-        
-
-        

+

           The logging statement configures a
           wide
           variety of logging options for the name server. Its channel phrase
@@ -1274,20 +1182,18 @@
           a name that can then be used with the category phrase
           to select how various classes of messages are logged.
         

-        

+

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

-
 
logging {
      category default { default_syslog; default_debug; };
      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
@@ -1298,18 +1204,14 @@
           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
@@ -1320,14 +1222,12 @@
             category name
             and/or severity level (the default is not to include any).
           

-
-          

+

             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 channel
             to a disk file.  It can include limitations
@@ -1335,8 +1235,7 @@
             versions
             of the file will be saved each time the file is opened.
           

-
-          

+

             If you use the versions log file
             option, then
             named will retain that many backup
@@ -1359,8 +1258,7 @@
             existing
             log file is simply appended.
           

-
-          

+

             The size option for files is used
             to limit log
             growth. If the file ever exceeds the size, then named will
@@ -1376,20 +1274,17 @@
             the
             file.
           

-
-          

+

             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
             directs the
             channel to the system log.  Its argument is a
@@ -1411,10 +1306,10 @@
             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
             "priorities", except that they can also be used if you are writing
             straight to a file rather than using syslog.
@@ -1423,7 +1318,7 @@
             levels
             will be accepted.
           

-          

+

             If you are using syslog, then the syslog.conf priorities
             will also determine what eventually passes through. For example,
             defining a channel facility and severity as daemon and debug but
@@ -1435,8 +1330,7 @@
             then syslogd would
             print all messages it received from the channel.
           

-
-          

+

             The stderr destination clause
             directs the
             channel to the server's standard error stream.  This is intended
@@ -1445,8 +1339,7 @@
             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
@@ -1460,21 +1353,19 @@ 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
             severity use the
             server's global debug level to determine what messages to print.
           

-          

+

             If print-time has been turned on,
             then
             the date and time will be logged. print-time may
@@ -1492,18 +1383,15 @@ notrace. All debugging messages in the server have a debug
             three print- options
             are on:
           

-
-          

+

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

-
-          

+

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

-
 
channel default_syslog {
     // send to syslog's daemon facility
     syslog daemon;
@@ -1531,8 +1419,7 @@ channel null {
    null;
 };
 

-
-          

+

             The default_debug channel has the
             special
             property that it only produces output when the server's debug
@@ -1540,8 +1427,7 @@ channel null {
             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
@@ -1551,21 +1437,17 @@ channel null {
             to capture this output, you must run the server with the "-g"
             option and redirect standard error to a file.
           

-
-          

+

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

-        
-
-        

+

+

 

 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
@@ -1574,16 +1456,13 @@ channel null {
             instead. If you don't specify a default category, the following
             "default default" is used:
           

-
 
category default { default_syslog; default_debug; };
 

-
-          

+

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

-
 
channel my_security_channel {
     file "my_security_file";
     severity info;
@@ -1593,22 +1472,18 @@ category security {
     default_syslog;
     default_debug;
 };

-
-          

+

             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.
           

-          

-  
+
@@ -1968,14 +1843,12 @@ category notify { null; };
 	
-

 
 
 

 
 

+

 

-        
-        

+

 

-The query-errors Category

-          
-          

+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
@@ -1983,15 +1856,14 @@ category notify { null; };
             Messages of this category are therefore only logged
             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.
@@ -1999,13 +1871,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:
           

-          

+

 
             

 
@@ -2016,14 +1888,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
@@ -2033,7 +1905,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.
@@ -2043,9 +1915,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
             The meaning of the other fields is summarized in the
             following table.
           

-
-          

-            
+
@@ -2184,16 +2054,15 @@ 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.
@@ -2202,19 +2071,15 @@ 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

-        
-
-        

+lwres Statement Grammar

+

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

-
 
lwres {
     [ listen-on { ip_addr [port ip_port] ;
                 [ ip_addr [port ip_port] ; ... ] }; ]
@@ -2223,14 +2088,11 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     [ ndots number; ]
 };
 

-
-      
-      

+

+

 

-lwres Statement Definition and Usage

-        
-
-        

+lwres Statement Definition and Usage

+

           The lwres statement configures the
           name
           server to also act as a lightweight resolver server. (See
@@ -2238,8 +2100,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           lwres statements configuring
           lightweight resolver servers with different properties.
         

-
-        

+

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

-
-        

+

           The view statement binds this
           instance of a
           lightweight resolver daemon to a view in the DNS namespace, so that
@@ -2262,8 +2122,7 @@ 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 in
@@ -2271,8 +2130,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           list of domains
           which are appended to relative names in queries.
         

-
-        

+

           The ndots statement is equivalent to
           the
           ndots statement in
@@ -2281,41 +2139,32 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           number of dots in a relative domain name that should result in an
           exact match lookup before search path elements are appended.
         

-      
-      

+

+

 

-masters Statement Grammar

-        
-
+masters Statement Grammar

 
 masters name [port ip_port] { ( 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.
         

-      

-
-      

+

+

 

-options Statement Grammar

-        
-
-        

+options Statement Grammar

+

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

-
 
options {
     [ attach-cache cache_name; ]
     [ version version_string; ]
@@ -2553,16 +2402,12 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     ; ]
 };
 

-
-      
-
-      

+

+

 

 options Statement Definition and
           Usage

-        
-
-        

+

           The options statement sets up global
           options
           to be used by BIND. This statement
@@ -2571,11 +2416,10 @@ badresp:1,adberr:0,findfail:0,valfail:0]
           statement, an options block with each option set to its default will
           be used.
         

-
-        

+

 
attach-cache

 

-                

+

                   Allows multiple views to share a single cache
                   database.
                   Each view has its own cache database by default, but
@@ -2584,15 +2428,13 @@ 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
                   statements, in which case it overrides the
                   global attach-cache option.
                 

-
-                

+

                   The cache_name specifies
                   the cache to be shared.
                   When the named server configures
@@ -2602,16 +2444,14 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   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
                   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.
@@ -2620,7 +2460,6 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   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
@@ -2635,8 +2474,7 @@ 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
@@ -2651,8 +2489,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   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.
@@ -2664,10 +2501,9 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                   configuration differences in different views do
                   not cause disruption with a shared cache.
                 

-              

+
 
directory

-

-              

+

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

-            

+              

 
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
@@ -2693,16 +2527,15 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 bind.keys,
                 rndc.key or
                 session.key.)
-              

-            

+              

 
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,
                 then managed keys for the server will be tracked in a single
                 file called managed-keys.bind.
@@ -2711,30 +2544,25 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 of the view name, followed by the extension
                 .mkeys.
               

-            

+
 
named-xfer

-

-              

+

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

-            

+              

 
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

-

-              

+

                 The security credential with which the server should
                 authenticate keys requested by the GSS-TSIG protocol.
                 Currently only Kerberos 5 authentication is available
@@ -2747,11 +2575,9 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 To use GSS-TSIG, tkey-domain must
                 also be set if a specific keytab is not set with
                 tkey-gssapi-keytab.
-              

-            

+              

 
tkey-domain

-

-              

+

                 The domain appended to the names of all shared keys
                 generated with TKEY.  When a
                 client requests a TKEY exchange,
@@ -2767,11 +2593,9 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 "_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

-

-              

+

                 The Diffie-Hellman key used by the server
                 to generate shared keys with clients using the Diffie-Hellman
                 mode
@@ -2780,34 +2604,26 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 public and private keys from files in the working directory.
                 In
                 most cases, the keyname should be the server's host name.
-              

-            

+              

 
cache-file

-

-              

+

                 This is for testing only.  Do not use.
-              

-            

+              

 
dump-file

-

-              

+

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

-            

+              

 
memstatistics-file

-

-              

+

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

-            

+              

 
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.
@@ -2819,52 +2635,42 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 is a keyword, not a filename, and therefore is not enclosed
                 in
                 double quotes.
-              

-            

+              

 
recursing-file

-

-              

+

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

-            

+              

 
statistics-file

-

-              

+

                 The pathname of the file the server appends statistics
                 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

-

-              

+

                 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.
                 If not specified, the default is
                 /etc/bind.keys.
-              

-            

+              

 
secroots-file

-

-              

+

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

-            

+              

 
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
@@ -2874,27 +2680,21 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 update-policy statement's
                 local option for more
                 information about this feature.)
-              

-            

+              

 
session-keyname

-

-              

+

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

-            

+              

 
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

-

-              

+

                 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
@@ -2902,11 +2702,9 @@ 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.
-              

-            

+              

 
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
@@ -2923,36 +2721,33 @@ badresp:1,adberr:0,findfail:0,valfail:0]
                 effect during
                 the initial configuration load at server startup time and
                 is ignored on subsequent reloads.
-              

-            

+              

 
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
 

 

-              

+

                 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
@@ -2968,36 +2763,32 @@ 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 the specified DNSSEC algorithms at and below the
                 specified name.
                 Multiple disable-algorithms
                 statements are allowed.
                 Only the most specific will be applied.
-              

-            

+              

 
dnssec-lookaside

 

-              

+

                 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
@@ -3009,18 +2800,18 @@ options {
                 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
                 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
                 no, then dnssec-lookaside
                 is not used.
               

-              

+

                 The default DLV key is stored in the file
                 bind.keys;
                 named will load that key at
@@ -3029,25 +2820,24 @@ options {
                 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
                 to be recompiled with a new key when the DLV key expires.)
               

-              

+

                 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

-

-              

+

                 Specify hierarchies which must be or may not be secure
                 (signed and validated).  If yes,
                 then named will only accept answers if
@@ -3057,11 +2847,10 @@ options {
                 trusted-keys or
                 managed-keys statement, or
                 dnssec-lookaside must be active.
-              

-            

+              

 
dns64

 

-              

+

                 This directive instructs named to
                 return mapped IPv4 addresses to AAAA queries when
                 there are no AAAA records.  It is intended to be
@@ -3069,11 +2858,11 @@ options {
                 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
@@ -3083,20 +2872,20 @@ options {
                 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
                 clients are affected by this directive.  If not defined,
                 it defaults to any;.
               

-              

+

                 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
@@ -3107,7 +2896,7 @@ options {
                 name owns.  If not defined, exclude
                 defaults to none.
               

-              

+

                 A optional suffix can also
                 be defined to set the bits trailing the mapped
                 IPv4 address bits.  By default these bits are
@@ -3115,13 +2904,13 @@ options {
                 matching the prefix and mapped IPv4 address
                 must be zero.
               

-              

+

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

-              

+

                 If break-dnssec is set to
                 yes the DNS64 synthesis will
                 happen even if the result, if validated, would
@@ -3140,10 +2929,9 @@ options {
                 suffix ::;
         };
 

-            
+
 
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
@@ -3156,11 +2944,10 @@ options {
                   the minimum is 1 (1 minute), and the
                   maximum is 1440 (24 hours); any higher
                   value is silently reduced.
-                

-            

+                

 
dnssec-update-mode

 

-                

+

                   If this option is set to its default value of
                   maintain in a zone of type
                   master which is DNSSEC-signed
@@ -3173,13 +2960,13 @@ options {
                   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
                   changed records, but scheduled maintenance of
                   signatures is disabled.
                 

-                

+

                   With either of these settings, named
                   will reject updates to a DNSSEC-signed zone when the
                   signing keys are inactive or unavailable to
@@ -3188,21 +2975,21 @@ options {
                   signing and allow DNSSEC data to be submitted into a zone
                   via dynamic update; this is not yet implemented.)
                 

-            

+
 
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
                 SOA serial number will be incremented by one each time
                 the zone is updated.
               

-              

+

                 When set to
                 serial-update-method unixtime;, the
                 SOA serial number will be set to the number of seconds
@@ -3210,10 +2997,10 @@ options {
                 already greater than or equal to that value, in which
                 case it is simply incremented by one.
               

-            

+
 
zone-statistics

 

-              

+

                 If full, the server will collect
                 statistical data on all zones (unless specifically
                 turned off on a per-zone basis by specifying
@@ -3225,7 +3012,7 @@ options {
                 current serial number, but not query type
                 counters).
               

-              

+

                 These statistics may be accessed via the
                 statistics-channel or
                 using rndc stats, which
@@ -3233,7 +3020,7 @@ options {
                 in the statistics-file.  See
                 also the section called “The Statistics File”.
               

-              

+

                 For backward compatibility with earlier versions
                 of BIND 9, the zone-statistics
                 option can also accept yes
@@ -3241,27 +3028,21 @@ options {
                 effect as full and
                 terse, respectively.
               

-            

+
 
-
-        

+

 

 Boolean Options

-          
-
-          

+

 
allow-new-zones

-

-                

+

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

-              

+                

 
auth-nxdomain

-

-                

+

                   If yes, then the AA bit
                   is always set on NXDOMAIN responses, even if the server is
                   not actually
@@ -3270,30 +3051,25 @@ 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

-

-                

+

                   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

-

-                

+

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

-              

+                

 
dialup

 

-                

+

                   If yes, then the
                   server treats all zones as if they are doing zone transfers
                   across
@@ -3308,14 +3084,14 @@ options {
                   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
                   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
@@ -3327,7 +3103,7 @@ options {
                   by
                   notify and also-notify.
                 

-                

+

                   If the
                   zone is a slave or stub zone, then the server will suppress
                   the regular
@@ -3337,7 +3113,7 @@ options {
                   addition to sending
                   NOTIFY requests.
                 

-                

+

                   Finer control can be achieved by using
                   notify which only sends NOTIFY
                   messages,
@@ -3352,9 +3128,7 @@ options {
                   refresh
                   processing.
                 

-
-                

-                  
+
@@ -3505,27 +3279,21 @@ options {
                         
-

 
 
 

 
 

-                

-
-                

+

+

                   Note that normal NOTIFY processing is not affected by
                   dialup.
                 

-
-              
+
 
fake-iquery

-

-                

+

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

-              

+                

 
fetch-glue

-

-                

+

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

-              

+                

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

-              

+                

 
has-old-clients

-

-                

+

                   This option was incorrectly implemented
                   in BIND 8, and is ignored by BIND 9.
                   To achieve the intended effect
@@ -3555,20 +3319,16 @@ options {
                   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

-

-                

+

                   This option is obsolete.
                   It was used in BIND 8 to
                   determine whether a transaction log was
@@ -3576,32 +3336,27 @@ options {
                   log whenever possible.  If you need to disable outgoing
                   incremental zone
                   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

-

-                

+

                   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

 

-                

+

                   If yes (the default),
                   DNS NOTIFY messages are sent when a zone the server is
                   authoritative for
@@ -3612,7 +3367,7 @@ options {
                   in the SOA MNAME field), and to any servers listed in the
                   also-notify option.
                 

-                

+

                   If master-only, notifies are only
                   sent
                   for master zones.
@@ -3621,7 +3376,7 @@ options {
                   servers explicitly listed using also-notify.
                   If no, no notifies are sent.
                 

-                

+

                   The notify option may also be
                   specified in the zone
                   statement,
@@ -3630,10 +3385,9 @@ options {
                   caused slaves
                   to crash.
                 

-              

+
 
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
@@ -3642,11 +3396,9 @@ 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

-

-                

+

                   If yes, and a
                   DNS query requests recursion, then the server will attempt
                   to do
@@ -3663,11 +3415,9 @@ options {
                   Caching may still occur as an effect the server's internal
                   operation, such as NOTIFY address lookups.
                   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
@@ -3676,35 +3426,31 @@ options {
                   the resolver category at level
                   info.
                   The default is no.
-                

-              

+                

 
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

-

-                

+

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

-              

+                

 
use-ixfr

-

-                

+

                   This option is obsolete.
                   If you need to disable IXFR to a particular server or
                   servers, see
@@ -3713,29 +3459,23 @@ options {
             Usage”.
                   See also
                   the section called “Incremental Zone Transfers (IXFR)”.
-                

-              

+                

 
provide-ixfr

-

-                

+

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

-              

+                

 
request-ixfr

-

-                

+

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

-              

+                

 
treat-cr-as-space

-

-                

+

                   This option was used in BIND
                   8 to make
                   the server treat carriage return ("\r") characters the same way
@@ -3746,22 +3486,19 @@ options {
                   and NT/DOS "\r\n" newlines
                   are always accepted,
                   and the option is ignored.
-                

-              

+                

 

 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
@@ -3781,8 +3518,7 @@ 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,
@@ -3792,8 +3528,7 @@ options {
                   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
@@ -3802,8 +3537,7 @@ options {
                   server to
                   ignore the options and log a warning message.
                 

-
-                

+

                   Specifying additional-from-cache no actually
                   disables the use of the cache not only for additional data
                   lookups
@@ -3813,8 +3547,7 @@ 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
@@ -3832,16 +3565,15 @@ options {
                   upwards referrals are not required for the resolution
                   process.
                 

-
-              

+
 
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
@@ -3850,10 +3582,10 @@ options {
                   named now solves this problem
                   internally.  The use of this option is discouraged.
                 

-              

+
 
filter-aaaa-on-v4

 

-                

+

                   This option is only available when
                   BIND 9 is compiled with the
                   --enable-filter-aaaa option on the
@@ -3867,7 +3599,7 @@ options {
                   to override the global filter-aaaa-on-v4
                   option.
                 

-                

+

                   If yes,
                   the DNS client is at an IPv4 address, in filter-aaaa,
                   and if the response does not include DNSSEC signatures,
@@ -3875,13 +3607,13 @@ options {
                   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
@@ -3889,22 +3621,22 @@ 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.
                 

-              

+
 
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
@@ -3914,7 +3646,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
@@ -3926,7 +3658,7 @@ options {
                   temporarily allocate memory to hold this complete
                   difference set.
                 

-                
ixfr-from-differences
+
ixfr-from-differences
                   also accepts master and
                   slave at the view and options
                   levels which causes
@@ -3935,10 +3667,9 @@ options {
                   slave zones respectively.
                   It is off by default.
                 

-              

+
 
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
@@ -3946,22 +3677,21 @@ options {
                   when the serial number on the master is less than what named
                   currently
                   has.  The default is no.
-                

-              

+                

 
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
                   keys to be updated and the zone fully re-signed
                   whenever the user issues the command rndc sign
                   zonename.
                 

-                

+

                   auto-dnssec maintain; includes the
                   above, but also automatically adjusts the zone's DNSSEC
                   keys on schedule, according to the keys' timing metadata
@@ -3984,24 +3714,22 @@ options {
                   interval is defined by
                   dnssec-loadkeys-interval.)
                 

-                

+

                   The default setting is auto-dnssec off.
                 

-              

+
 
dnssec-enable

-

-                

+

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

-              

+                

 
dnssec-validation

 

-                

+

                   Enable DNSSEC validation in named.
                   Note dnssec-enable also needs to be
                   set to yes to be effective.
@@ -4015,39 +3743,35 @@ options {
                   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-accept-expired

-

-                

+

                   Accept expired signatures when verifying DNSSEC signatures.
                   The default is no.
                   Setting this option to yes
                   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

 

-                

+

                   This option is used to restrict the character set and syntax
                   of
                   certain domain names in master files and/or DNS responses
@@ -4060,11 +3784,11 @@ options {
                   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.
@@ -4072,29 +3796,24 @@ 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 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

-

-                

+

                   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

-

-                

+

                   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
@@ -4102,11 +3821,10 @@ options {
                   This option
                   affects master zones.  The default (yes) is to check
                   for non-terminal wildcards and issue a warning.
-                

-              

+                

 
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
@@ -4119,7 +3837,7 @@ options {
                   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.
@@ -4129,65 +3847,53 @@ options {
                   TXT record does not exist and can be suppressed with
                   check-spf.
                 

-              

+
 
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
                   fail, warn or ignore SRV records that refer
                   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
                   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

-

-                

+

                   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

-

-                

+

                   When caching a negative response to a SOA query
                   set the TTL to zero.
                   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
@@ -4198,7 +3904,7 @@ options {
                   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
@@ -4206,10 +3912,10 @@ options {
                   this requirement is not met, this option will be ignored
                   for that algorithm.
                 

-              

+
 
dnssec-dnskey-kskonly

 

-                

+

                   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
@@ -4219,23 +3925,21 @@ options {
                   This is similar to the
                   dnssec-signzone -x command line option.
                 

-                

+

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

-              

+
 
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

 

-                

+

                   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.
@@ -4243,30 +3947,27 @@ options {
                   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
                   private keys remain accessible in the key repository,
                   then the zone will be automatically signed again the
                   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
@@ -4276,11 +3977,9 @@ options {
             the server is not authoritative and does not have the answer in
             its cache.
           

-
-          

+

 
forward

-

-                

+

                   This option is only meaningful if the
                   forwarders list is not empty. A value of first,
                   the default, causes the server to query the forwarders
@@ -4290,19 +3989,15 @@ options {
                   the answer itself. If only is
                   specified, the
                   server will only query the forwarders.
-                

-              

+                

 
forwarders

-

-                

+

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

-              

+                

 

-
-          

+

             Forwarding can also be configured on a per-domain basis, allowing
             for the global forwarding options to be overridden in a variety
             of ways. You can set particular domains to use different
@@ -4311,24 +4006,20 @@ options {
             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

-

-                

+

                   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
@@ -4337,26 +4028,20 @@ options {
                   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).
-                

-              

+                

 

-        

-
-        

+

+

 

 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
             details on how to specify IP address lists.
           

-
-          

+

 
allow-notify

-

-                

+

                   Specifies which hosts are allowed to
                   notify this server, a slave, of zone changes in addition
                   to the zone masters.
@@ -4369,11 +4054,10 @@ options {
                   for a slave zone.  If not specified, the default is to
                   process notify messages
                   only from a zone's master.
-                

-              

+                

 
allow-query

 

-                

+

                   Specifies which hosts are allowed to ask ordinary
                   DNS questions. allow-query may
                   also be specified in the zone
@@ -4382,50 +4066,49 @@ options {
                   If not specified, the default is to allow queries
                   from all hosts.
                 

-                

+

 
Note

-                  

+

                     allow-query-cache is now
                     used to specify access to the cache.
                   

-                

-              

+

+
 
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
                   checked for queries that are permitted by
                   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
                   statement, in which case it overrides the
                   options allow-query-on statement.
                 

-                

+

                   If not specified, the default is to allow queries
                   on all addresses.
                 

-                

+

 
Note

-                  

+

                     allow-query-cache is
                     used to specify access to the 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
@@ -4434,21 +4117,17 @@ options {
                   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

-

-                

+

                   Specifies which hosts are allowed to make recursive
                   queries through this server. If
                   allow-recursion is not set
@@ -4457,30 +4136,25 @@ options {
                   is used if set, otherwise the default
                   (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

-

-                

+

                   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

 

-                

+

                   Specifies which hosts are allowed to
                   submit Dynamic DNS updates to slave zones to be forwarded to
                   the
@@ -4497,7 +4171,7 @@ 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
@@ -4505,10 +4179,9 @@ options {
                   access control to attacks; see the section called “Dynamic Update Security”
                   for more details.
                 

-              

+
 
allow-v6-synthesis

-

-                

+

                   This option was introduced for the smooth transition from
                   AAAA
                   to A6 and from "nibble labels" to binary labels.
@@ -4516,11 +4189,9 @@ options {
                   deprecated,
                   this option was also deprecated.
                   It is now ignored with some warning messages.
-                

-              

+                

 
allow-transfer

-

-                

+

                   Specifies which hosts are allowed to
                   receive zone transfers from the server. allow-transfer may
                   also be specified in the zone
@@ -4528,29 +4199,24 @@ options {
                   case it overrides the options allow-transfer statement.
                   If not specified, the default is to allow transfers to all
                   hosts.
-                

-              

+                

 
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

-

-                

+

                   Specifies a list of addresses to which
                   filter-aaaa-on-v4
                   is applies.  The default is any.
-                

-              

+                

 
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
@@ -4558,7 +4224,7 @@ options {
                   1034 to use case-insensitive name comparisons when
                   checking for matching domain names.
                 

-                

+

                   If left undefined, the ACL defaults to
                   none: case-insensitive compression
                   will be used for all clients.  If the ACL is defined and
@@ -4566,7 +4232,7 @@ options {
                   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
@@ -4578,12 +4244,12 @@ 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
                   will not preserve the case of owner names of records:
                   if a zone file defines records of different types with
@@ -4598,26 +4264,21 @@ options {
                   have their case preserved unless the client matches this
                   ACL.
                 

-              

+
 
resolver-query-timeout

-

-                

+

                   The amount of time the resolver will spend attempting
                   to resolve a recursive query before failing.  The default
                   and minimum is 10 and the maximum is
                   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
             an optional port and an address_match_list
@@ -4626,35 +4287,30 @@ options {
             The server will listen on all interfaces allowed by the address
             match list. If a port is not specified, port 53 will be used.
           

-          

+

             Multiple listen-on statements are
             allowed.
             For example,
           

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

-
-          

+

             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
             server will listen on port 53 on all IPv4 interfaces.
           

-
-          

+

             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.
           

-
-          

+

             When 

 
{ any; }

 
 is
@@ -4669,8 +4325,7 @@ 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
@@ -4679,45 +4334,37 @@ listen-on port 1234 { !1.2.3.4; 1.2/16; };
             IPv4 addresses specified in listen-on-v6
             will be ignored, with a logged warning.
           

-
-          

+

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

-
-          

+

             If no listen-on-v6 option is
             specified, the server will not listen on any IPv6 address
             unless -6 is specified when named is
             invoked.  If -6 is specified then
             named will listen on port 53 on all IPv6 interfaces by default.
           

-        
-
-        

+

+

 

 Query Address

-          
-          

+

             If the server doesn't know the answer to a question, it will
             query other name servers. query-source specifies
             the address and port used for such queries. For queries sent over
@@ -4726,8 +4373,7 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; };
             a wildcard IP address (INADDR_ANY)
             will be used.
           

-
-          

+

             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.
@@ -4738,18 +4384,15 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; };
             the avoid-v4-udp-ports
             and avoid-v6-udp-ports options, respectively.
           

-
-          

+

             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
@@ -4759,12 +4402,10 @@ query-source-v6 address * port *;
             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
@@ -4780,8 +4421,7 @@ use-v6-udp-ports { range 1024 65535; };
             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
             of some ports.  For example, UNIX systems will not allow
@@ -4793,18 +4433,15 @@ 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
             are:
           

-
 
avoid-v4-udp-ports {};
 avoid-v6-udp-ports {};
 

-
-          

+

             Note: BIND 9.5.0 introduced
             the use-queryport-pool
             option to support a pool of such random ports, but this
@@ -4816,67 +4453,57 @@ avoid-v6-udp-ports {};
             query-source-v6 options;
             it implicitly disables the use of randomized port numbers.
           

-
-          

+

 
use-queryport-pool

-

-                

+

                   This option is obsolete.
-                

-              

+                

 
queryport-pool-ports

-

-                

+

                   This option is obsolete.
-                

-              

+                

 
queryport-pool-updateinterval

-

-                

+

                   This option is obsolete.
-                

-              

+                

 

-          

+

 
Note

-            

+

               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.
             

-          

-        

-
-        

+

+

+

 

 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

 

-                

+

                   Defines a global list of IP addresses of name servers
                   that are also sent NOTIFY messages whenever a fresh copy of
                   the
@@ -4894,7 +4521,7 @@ avoid-v6-udp-ports {};
                   In place of explicit addresses, one or more named
                   masters lists can be used.
                 

-                

+

                   If an also-notify list
                   is given in a zone statement,
                   it will override
@@ -4907,46 +4534,38 @@ avoid-v6-udp-ports {};
                   the empty
                   list (no global notification list).
                 

-              

+
 
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

-

-                

+

                   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

-

-                

+

                   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

-

-                

+

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

-              

+                

 
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
@@ -4959,17 +4578,16 @@ avoid-v6-udp-ports {};
                   The lowest possible rate is one per second; when set
                   to zero, it will be silently raised to one.
                 

-                

+

                   In addition to controlling the rate SOA refresh
                   queries are issued at,
                   serial-query-rate also controls
                   the rate at which NOTIFY messages are sent from
                   both master and slave zones.
                 

-              

+
 
serial-queries

-

-                

+

                   In BIND 8, the serial-queries
                   option
                   set the maximum number of concurrent serial number queries
@@ -4978,12 +4596,9 @@ avoid-v6-udp-ports {};
                   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

-

-
-                

+

                   Zone transfers can be sent using two different formats,
                   one-answer and
                   many-answers.
@@ -5003,32 +4618,25 @@ avoid-v6-udp-ports {};
                   transfer-format may be overridden on a
                   per-server basis by using the server
                   statement.
-                

-
-              

+                

 
transfers-in

-

-                

+

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

-              

+                

 
transfers-out

-

-                

+

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

-              

+                

 
transfers-per-ns

-

-                

+

                   The maximum number of inbound zone transfers
                   that can be concurrently transferring from a given remote
                   name server.
@@ -5040,11 +4648,10 @@ avoid-v6-udp-ports {};
                   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
@@ -5065,30 +4672,28 @@ avoid-v6-udp-ports {};
                   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

 

-                

+

                   An alternate transfer source if the one listed in
                   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
@@ -5097,29 +4702,25 @@ avoid-v6-udp-ports {};
                   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

 

-                
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
@@ -5133,30 +4734,25 @@ avoid-v6-udp-ports {};
                   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,
                   but applies to notify messages sent to IPv6 addresses.
-                

-              

+                

 

-
-        

-
-        

+

+

 

-UDP Port Lists

-          
-          

+UDP Port Lists

+

             use-v4-udp-ports,
             avoid-v4-udp-ports,
             use-v6-udp-ports, and
@@ -5167,20 +4763,17 @@ avoid-v6-udp-ports {};
             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
              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
@@ -5197,14 +4790,11 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
              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
@@ -5217,8 +4807,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             that was in force when the server was started. See the description
             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
@@ -5226,18 +4815,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             the
             unsupported limit is used.
           

-
-          

+

 
coresize

-

-                

+

                   The maximum size of a core dump. The default
                   is default.
-                

-              

+                

 
datasize

-

-                

+

                   The maximum amount of data memory the server
                   may use. The default is default.
                   This is a hard limit on server memory usage.
@@ -5252,50 +4837,37 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   max-cache-size and
                   recursive-clients
                   options instead.
-                

-              

+                

 
files

-

-                

+

                   The maximum number of files the server
                   may have open concurrently. The default is unlimited.
-                

-              

+                

 
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

-

-                

+

                   This option is obsolete; it is accepted
                   and ignored for BIND 8 compatibility.  The option
                   max-journal-size performs a
                   similar function in BIND 9.
-                

-              

+                

 
max-journal-size

-

-                

+

                   Sets a maximum size for each journal file
                   (see the section called “The journal file”).  When the journal file
                   approaches
@@ -5306,19 +4878,16 @@ 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

-

-                

+

                   In BIND 8, specifies the maximum number of host statistics
                   entries to be kept.
                   Not implemented in BIND 9.
-                

-              

+                

 
recursive-clients

 

-                

+

                   The maximum number ("hard quota") of simultaneous
                   recursive lookups the server will perform on behalf
                   of clients.  The default is
@@ -5329,14 +4898,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   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.
@@ -5346,20 +4915,18 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   otherwise it is set to 90% of
                   recursive-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
 

 

-                
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
@@ -5367,7 +4934,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   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
@@ -5377,22 +4944,22 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   estimate will then be lowered in 20 minutes if it has
                   remained unchanged.
                 

-                

+

                   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,
                   then there is no upper bound other than imposed by
                   recursive-clients.
                 

-              

+
 

 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
@@ -5402,7 +4969,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
@@ -5414,7 +4981,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
@@ -5422,12 +4989,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   or answered with SERVFAIL.  The default is
                   drop.
                 

-                

+

                   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
                   includes the number of active fetches for each
@@ -5440,16 +5007,16 @@ 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.)
                 

-                

+

                   (Note: This option is only available when BIND is
                   built with configure --enable-fetchlimit.)
                 

-              

+
 

 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
@@ -5459,7 +5026,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
@@ -5468,12 +5035,12 @@ 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,
                   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
                   dynamically adjusted in response to detected
                   congestion. As queries are sent to a server
@@ -5489,19 +5056,19 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   can be used to adjust the parameters for this
                   calculation.
                 

-                

+

                   (Note: This option is only available when BIND is
                   built with configure --enable-fetchlimit.)
                 

-              

+
 
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
@@ -5509,7 +5076,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
@@ -5524,14 +5091,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   precision of 1/100: at most two places after
                   the decimal point are significant.
                 

-                

+

                   (Note: This option is only available when BIND is
                   built with configure --enable-fetchlimit.)
                 

-              

+
 
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
@@ -5541,13 +5108,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   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

-

-                

+

                   The maximum amount of memory to use for the
                   server's cache, in bytes.
                   When the amount of data in the cache
@@ -5567,11 +5133,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   In a server with multiple views, the limit applies
                   separately to the cache of each view.
                   The default is 0.
-                

-              

+                

 
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
@@ -5581,21 +5145,15 @@ 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

-          
-
-          

+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.
@@ -5604,11 +5162,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   rely on the periodic cleaning any more.
                   Specifying this option therefore has no effect on
                   the server's behavior.
-                

-              

+                

 
heartbeat-interval

-

-                

+

                   The server will perform zone maintenance tasks
                   for all zones marked as dialup whenever this
                   interval expires. The default is 60 minutes. Reasonable
@@ -5616,11 +5172,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   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

-

-                

+

                   The server will scan the network interface list
                   every interface-interval
                   minutes. The default
@@ -5633,35 +5187,30 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   listen-on configuration), and
                   will
                   stop listening on interfaces that have gone away.
-                

-              

+                

 
statistics-interval

 

-                

+

                   Name server statistics will be logged
                   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
@@ -5678,42 +5227,34 @@ 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
               is not implemented in BIND 9.
             

-          

-        

-
-        

+

+

+

 

 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
@@ -5729,8 +5270,7 @@ 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)
             takes
             an address_match_list and
@@ -5746,7 +5286,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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
@@ -5761,7 +5301,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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
@@ -5779,7 +5319,6 @@ 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
@@ -5803,8 +5342,7 @@ 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
@@ -5816,19 +5354,16 @@ 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.
@@ -5838,27 +5373,25 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             See also the sortlist statement,
             the section called “The sortlist Statement”.
           

-
-          

+

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

-          

+

             The legal values for ordering are:
           

-          

-            
+
@@ -5902,53 +5435,46 @@ 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
             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
               "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

 

-                

+

                   Sets the number of seconds to cache a
                   lame server indication. 0 disables caching. (This is
                   NOT recommended.)
@@ -5956,18 +5482,15 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   maximum value is
                   1800 (30 minutes).
                 

-
-                

+

                   Lame-ttl also controls the amount of time DNSSEC
                   validation failures are cached.  There is a minimum
                   of 30 seconds applied to bad cache entries if the
                   lame-ttl is set to less than 30 seconds.
                 

-
-              

+
 
max-ncache-ttl

-

-                

+

                   To reduce network traffic and increase performance,
                   the server stores negative answers. max-ncache-ttl is
                   used to set a maximum retention time for these answers in
@@ -5977,11 +5500,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   max-ncache-ttl cannot exceed
                   7 days and will
                   be silently truncated to 7 days if set to a greater value.
-                

-              

+                

 
max-cache-ttl

-

-                

+

                   Sets the maximum time for which the server will
                   cache ordinary (positive) answers. The default is
                   one week (7 days).
@@ -5989,26 +5510,25 @@ 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

 

-                

+

                   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

 

-                

+

                   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
@@ -6022,48 +5542,44 @@ 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
                   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

-

-                

+

                   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

-

-                

+

                   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

 

-                

+

                   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
                   a zone-signing process, i.e., whether it is still active
@@ -6079,12 +5595,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   records for a zone, use
                   rndc signing -clear all zone.
                 

-              

+
 

 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.
@@ -6094,7 +5610,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 either per-zone, per-view, or
@@ -6103,7 +5619,7 @@ 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
@@ -6111,10 +5627,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   and max-retry-time 1209600 seconds
                   (2 weeks).
                 

-              

+
 
edns-udp-size

 

-                

+

                   Sets the advertised EDNS UDP buffer size in bytes
                   to control the size of packets received.
                   Valid values are 512 to 4096 (values outside this range
@@ -6125,17 +5641,17 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   firewalls that block fragmented packets and/or
                   block UDP packets that are greater than 512 bytes.
                 

-                

+

                   named will fallback to using 512 bytes
                   if it get a series of timeout at the initial value.  512
                   bytes is not being offered to encourage sites to fix their
                   firewalls.  Small EDNS UDP sizes will result in the
                   excessive use of TCP.
                 

-              

+
 
max-udp-size

 

-                

+

                   Sets the maximum EDNS UDP message size
                   named will send in bytes.
                   Valid values are 512 to 4096 (values outside this
@@ -6148,14 +5664,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   This is independent of the advertised receive
                   buffer (edns-udp-size).
                 

-                

+

                   Setting this to a low value will encourage additional
                   TCP traffic to the nameserver.
                 

-              

+
 
masterfile-format

 

-                
Specifies
+
Specifies
                   the file format of zone files (see
                   the section called “Additional File Formats”).
                   The default value is text, which is the
@@ -6166,7 +5682,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   named-compilezone tool, or dumped by
                   named.
                 

-                

+

                   Note that when a zone file in a different format than
                   text is loaded, named
                   may omit some of the checks which would be performed for a
@@ -6184,12 +5700,11 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   view block in the configuration
                   file.
                 

-              

+
 

 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
@@ -6198,13 +5713,11 @@ 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
 

-

-                

+

                   Sets the maximum number of iterative queries that
                   may be sent while servicing a recursive query.
                   If more queries are sent, the recursive query
@@ -6212,38 +5725,31 @@ 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

 

-                

+

                   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.
                 

-              

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

-              

+                

 

-
-        

-
-        

+

+

 

 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
@@ -6260,29 +5766,25 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             allow-new-zones are
             always set to no.
           

-          

+

             If you need to disable these zones, use the options
             below, or hide the built-in CHAOS
             view by
             defining an explicit view of class CHAOS
             that matches all clients.
           

-
-          

+

 
version

-

-                

+

                   The version the server should report
                   via a query of the name version.bind
                   with type TXT, class CHAOS.
                   The default is the real version number of this server.
                   Specifying version none
                   disables processing of the queries.
-                

-              

+                

 
hostname

-

-                

+

                   The hostname the server should report via a query of
                   the name hostname.bind
                   with type TXT, class CHAOS.
@@ -6293,11 +5795,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   identify which of a group of anycast servers is actually
                   answering your queries.  Specifying hostname none;
                   disables processing of the queries.
-                

-              

+                

 
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
@@ -6309,17 +5809,13 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
                   Specifying server-id hostname; will cause named to
                   use the hostname as found by the gethostname() function.
                   The default server-id is none.
-                

-              

+                

 

-
-        

-
-        

+

+

 

 Built-in Empty Zones

-          
-          

+

             Named 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
@@ -6331,15 +5827,15 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             IPv6 link local addresses, the IPv6 loopback address and the
             IPv6 unknown address.
           

-          

+

             Named 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
      • 
@@ -6440,7 +5936,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
 
    
 
    
           
    
-          
    
+
    
             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
@@ -6452,7 +5948,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
@@ -6461,53 +5957,42 @@ 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

-

-                

+

                   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

-

-                

+

                   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

-

-                

+

                   Enable or disable all empty zones.  By default, they
                   are enabled.
-                

-              

+                

 
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,
             is an internal cache to improve the response performance of BIND 9.
             When additional section caching is enabled, BIND 9 will
@@ -6517,8 +6002,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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
@@ -6526,8 +6010,7 @@ 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
@@ -6536,8 +6019,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             does not short-cut of additional section information from the
             DNS cache data.
           

-
-          

+

             One obvious disadvantage of acache is
             that it requires much more
             memory for the internal cached data.
@@ -6550,8 +6032,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             consumption
             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,
@@ -6567,33 +6048,26 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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-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.
                   The default is 60 minutes.
                   If set to 0, no periodic cleaning will occur.
-                

-              

+                

 
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
@@ -6603,17 +6077,13 @@ 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.
@@ -6639,12 +6109,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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
             ip_addr
@@ -6652,14 +6120,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
             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
@@ -6669,53 +6135,44 @@ 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,
             "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
@@ -6736,8 +6193,7 @@ 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
@@ -6746,13 +6202,11 @@ 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.
@@ -6760,8 +6214,7 @@ 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
             global options if there is no response-policy option for the view.
@@ -6770,8 +6223,7 @@ deny-answer-aliases { "example.net"; };
             It is usually best to restrict those queries with something like
             allow-query { localhost; };.
           

-
-          

+

             Four policy triggers are encoded in RPZ records, QNAME, IP, NSIP,
             and NSDNAME.
             QNAME RPZ records triggered by query names of requests and targets
@@ -6779,8 +6231,7 @@ deny-answer-aliases { "example.net"; };
             The owner name of a QNAME RPZ record is the query name relativized
             to the RPZ.
           

-
-          

+

             The second kind of RPZ trigger is an IP address in an A and AAAA
             record in the ANSWER section of a response.
             IP address triggers are encoded in records that have owner names
@@ -6803,8 +6254,7 @@ deny-answer-aliases { "example.net"; };
             analogous to double colons (::) in standard IPv6 text encodings.
             The prefix length must be between 1 and 128.
           

-
-          

+

             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.
@@ -6821,8 +6271,7 @@ deny-answer-aliases { "example.net"; };
             The default value of min-ns-dots is 1 to
             exclude top level domains.
           

-
-          

+

             The query response is checked against all RPZs, so
             two or more policy records can be triggered by a response.
             Because DNS responses can be rewritten according to at most one
@@ -6831,7 +6280,7 @@ deny-answer-aliases { "example.net"; };
             Triggers or the records that encode them are chosen in
             the following order:
             

-
    
+
      
 
    • Choose the triggered record in the zone that appears
                 first in the response-policy option.
               
      • 
@@ -6851,20 +6300,18 @@ deny-answer-aliases { "example.net"; };
 
    
 
    
           
    
-
-          
    
+
    
             When the processing of a response is restarted to resolve
             DNAME or CNAME records and a policy record set has
             not been triggered,
             all RPZs are again consulted for the DNAME or CNAME names
             and addresses.
           
    
-
-          
    
+
    
             RPZ record sets are sets of any types of DNS record except
             DNAME or DNSSEC that encode actions or responses to queries.
             
    
-
      
+
        
 
      • The NXDOMAIN response is encoded
                 by a CNAME whose target is the root domain (.)
               
        • 
@@ -6895,15 +6342,14 @@ deny-answer-aliases { "example.net"; };
 
      
 
      
           
      
-
-          
      
+
      
             The actions specified in an RPZ can be overridden with a
             policy clause in the
             response-policy option.
             An organization using an RPZ provided by another organization might
             use this mechanism to redirect domains to its own walled garden.
             
      
-
        
+
          
 
        • 
 GIVEN says "do not override but
                 perform the action specified in the zone."
@@ -6938,8 +6384,7 @@ deny-answer-aliases { "example.net"; };
 
        
 
        
           
        
-
-          
        
+
        
             By default, the actions encoded in an RPZ are applied
             only to queries that ask for recursion (RD=1).
             That default can be changed for a single RPZ or all RPZs in a view
@@ -6949,8 +6394,7 @@ deny-answer-aliases { "example.net"; };
             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
@@ -6961,24 +6405,22 @@ deny-answer-aliases { "example.net"; };
             The name of the clause option reflects the fact that results
             rewritten by RPZ actions cannot verify.
           
        
-
-          
        
+
        
             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 that
             maximum 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
@@ -7008,7 +6450,7 @@ bzone.domain.com        CNAME   garden.example.com.
 ns.domain.com.rpz-nsdname   CNAME   .
 48.zz.2.2001.rpz-nsip       CNAME   .
 
        
-          
        
+
        
             RPZ can affect server performance.
             Each configured response policy zone requires the server to
             perform one to four additional database lookups before a
@@ -7023,23 +6465,20 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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.
           
        
-        
      
-
-        
      
+
      
+
      
 
      
-Response Rate Limiting
      
-          
-          
      
+Response Rate Limiting

+

             This feature is only available when BIND 9
             is compiled with the --enable-rrl
             option on the "configure" command line.
           

-          

+

             Excessive almost identical UDP responses
             can be controlled by configuring a
             rate-limit clause in an
@@ -7052,8 +6491,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7061,8 +6499,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7081,8 +6518,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7091,8 +6527,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7116,14 +6551,12 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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).
@@ -7134,8 +6567,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             but it can be set separately with
             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
@@ -7159,8 +6591,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             cannot be replaced with truncated responses and are instead
             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
@@ -7173,8 +6604,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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,
@@ -7192,8 +6622,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             Responses sent via TCP are not limited
             but are counted to compute the query per second rate.
           

-
-          

+

             Communities of DNS clients can be given their own parameters or no
             rate limiting by putting
             rate-limit statements in view
@@ -7205,8 +6634,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             DNS clients within a view can be exempted from rate limits
             with the exempt-clients clause.
           

-
-          

+

             UDP responses of all kinds can be limited with the
             all-per-second phrase.
             This rate limiting is unlike the rate limiting provided by
@@ -7242,8 +6670,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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.
             Each entry in the table is between 40 and 80 bytes.
@@ -7257,27 +6684,22 @@ ns.domain.com.rpz-nsdname   CNAME   .
             expansions of the table and inform
             choices for the initial and maximum table size.
           

-
-          

+

             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
             statistics.
             Responses that truncated by rate limits are included in
             RateSlipped and RespTruncated.
           

-        
-      
-
-      

+

+
+

 

 server Statement Grammar

-        
-
 
server ip_addr[/prefixlen] {
     [ bogus yes_or_no ; ]
     [ provide-ixfr yes_or_no ; ]
@@ -7302,16 +6724,12 @@ ns.domain.com.rpz-nsdname   CNAME   .
     [ queryport-pool-updateinterval number; ]
 };
 

-
-        

-
-        

+

+

 

 server Statement Definition and
             Usage

-          
-
-          

+

             The server statement defines
             characteristics
             to be associated with a remote name server.  If a prefix length is
@@ -7320,8 +6738,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             server clause applies regardless of the order in
             named.conf.
           

-
-          

+

             The server statement can occur at
             the top level of the
             configuration file or inside a view
@@ -7336,14 +6753,13 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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.
           

-          

+

             The provide-ixfr clause determines
             whether
             the local server, acting as master, will respond with an
@@ -7359,8 +6775,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             view or
             global options block is used as a default.
           

-
-          

+

             The request-ixfr clause determines
             whether
             the local server, acting as a slave, will request incremental zone
@@ -7370,8 +6785,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7385,14 +6799,12 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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 edns clause determines whether
             the local server will attempt to use EDNS when communicating
             with the remote server.  The default is yes.
           

-
-          

+

             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
@@ -7401,8 +6813,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             advertise globally, for example, when there is a firewall at the
             remote site that is blocking large replies.
           

-
-          

+

             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
@@ -7410,8 +6821,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             know that there is a firewall that is blocking large
             replies from named.
           

-
-          

+

             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
@@ -7425,16 +6835,14 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
             limit is set according to the
             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”)
@@ -7445,12 +6853,10 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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 IPv4 and IPv6 source
@@ -7466,8 +6872,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             transfer-source-v6 in
             the section called “Zone Transfers”.
           

-
-          

+

             The notify-source and
             notify-source-v6 clauses specify the
             IPv4 and IPv6 source address to be used for notify
@@ -7476,8 +6881,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             can be specified.  Similarly, for an IPv6 remote server,
             only notify-source-v6 can be specified.
           

-
-          

+

             The query-source and
             query-source-v6 clauses specify the
             IPv4 and IPv6 source address to be used for queries
@@ -7486,43 +6890,35 @@ ns.domain.com.rpz-nsdname   CNAME   .
             be specified.  Similarly, for an IPv6 remote server,
             only query-source-v6 can be specified.
           

-
-          

+

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

-        

-
-      

+

+

 

 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
           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.
@@ -7531,8 +6927,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
           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
@@ -7542,14 +6937,12 @@ ns.domain.com.rpz-nsdname   CNAME   .
           To listen on the IPv6 wildcard address,
           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.
         

-
-        

+

           The attempt of opening a statistics channel is
           restricted by the optional allow clause.
           Connections to the statistics channel are permitted based on the
@@ -7561,17 +6954,15 @@ ns.domain.com.rpz-nsdname   CNAME   .
           recommended to restrict the source of connection requests
           appropriately.
         

-
-        

+

           If no statistics-channels statement is present,
           named will not open any communication channels.
         

-
-        

+

           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.  When
           BIND 9 is configured with --enable-newstats,
@@ -7581,37 +6972,31 @@ ns.domain.com.rpz-nsdname   CNAME   .
           to render data into into charts and graphs 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.
         

-      

-
-        

+

+

 

 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
             public key for a non-authoritative zone is known, but
@@ -7622,7 +7007,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
             of what parent zones say.  Similarly for all keys listed in
@@ -7630,7 +7015,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             used to validate the DNSKEY RRset.  The parent's DS RRset
             will not be used.
           

-          

+

             The trusted-keys statement can contain
             multiple key entries, each consisting of the key's
             domain name, flags, protocol, algorithm, and the Base-64
@@ -7639,33 +7024,28 @@ ns.domain.com.rpz-nsdname   CNAME   .
             in the key data, so the configuration may be split up into
             multiple lines.
           

-          

+

             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.
           

-        

-
-        

+

+

 

-managed-keys Statement Grammar

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

-          
-          

+

             The managed-keys statement, like
             trusted-keys, defines DNSSEC
             security roots.  The difference is that
@@ -7673,7 +7053,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
@@ -7683,7 +7063,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             continue until the resolver operator had updated the
             trusted-keys statement with the new key.
           

-          

+

             If, however, the zone were listed in a
             managed-keys statement instead, then the
             zone owner could add a "stand-by" key to the zone in advance.
@@ -7694,7 +7074,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             using that key to validate answers, minimizing the damage that
             the compromised key could do.
           

-          

+

             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
@@ -7705,7 +7085,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             allow keys to be initialized by other methods, eliminating this
             requirement.)
           

-          

+

             Consequently, a managed-keys statement
             appears similar to a trusted-keys, differing
             in the presence of the second field, containing the keyword
@@ -7718,7 +7098,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             managed key database and start the RFC 5011 key maintenance
             process.
           

-          

+

             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
@@ -7726,7 +7106,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
             make sure RFC 5011 key maintenance has already been initialized
@@ -7735,7 +7115,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
             has been removed from the
             managed-keys statement, the corresponding
@@ -7743,13 +7123,13 @@ ns.domain.com.rpz-nsdname   CNAME   .
             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
             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
@@ -7764,7 +7144,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             the working directory should be always be writable by
             named.)
           

-          

+

             If the dnssec-validation option is
             set to auto, named
             will automatically initialize a managed key for the
@@ -7776,13 +7156,10 @@ ns.domain.com.rpz-nsdname   CNAME   .
             maintenance process is built into named,
             and can be overridden from bindkeys-file.
           

-        

-
-        

+

+

 

 view Statement Grammar

-          
-
 
view view_name
       [class] {
       match-clients { address_match_list };
@@ -7792,14 +7169,11 @@ ns.domain.com.rpz-nsdname   CNAME   .
       [ zone_statement; ...]
 };
 

-
-        

-        

+

+

 

-view Statement Definition and Usage

-          
-
-          

+view Statement Definition and Usage

+

             The view statement is a powerful
             feature
             of BIND 9 that lets a name server
@@ -7808,8 +7182,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             implementing
             split DNS setups without having to run multiple servers.
           

-
-          

+

             Each view statement defines a view
             of the
             DNS namespace that will be seen by a subset of clients.  A client
@@ -7837,8 +7210,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             a client request will be resolved in the context of the first
             view that it matches.
           

-
-          

+

             Zones defined within a view
             statement will
             only be accessible to clients that match the view.
@@ -7847,8 +7219,7 @@ ns.domain.com.rpz-nsdname   CNAME   .
             "internal"
             and "external" clients in a split DNS setup.
           

-
-          

+

             Many of the options given in the options statement
             can also be used within a view
             statement, and then
@@ -7861,14 +7232,12 @@ ns.domain.com.rpz-nsdname   CNAME   .
             view-specific defaults
             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
             the config
             file, a default view that matches any client is automatically
@@ -7884,12 +7253,10 @@ ns.domain.com.rpz-nsdname   CNAME   .
             statements must
             occur inside view statements.
           

-
-          

+

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

-
 
view "internal" {
       // This should match our internal networks.
       match-clients { 10.0.0.0/8; };
@@ -7922,14 +7289,11 @@ view "external" {
       };
 };
 

-
-        
-        

+

+

 

 zone
             Statement Grammar

-          
-
 
zone zone_name [class] {
     type master;
     [ allow-query { address_match_list }; ]
@@ -8117,18 +7481,14 @@ zone zone_name [
-
-        

-        

+

+

 

-zone Statement Definition and Usage

-          
-          

+zone Statement Definition and Usage

+

 

-Zone Types

-            
-
-            

+Zone Types

+

               The type keyword is required
               for the zone configuration. Its
               acceptable values include: delegation-only,
@@ -8137,9 +7497,7 @@ zone zone_name [slave, static-stub,
               and stub.
             

-
-            

-              
+
@@ -8452,20 +7810,17 @@ zone zone_name [
 
 
-

 
 
 


-            

-          
-
-          

+

+
+

 

-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
@@ -8474,70 +7829,52 @@ 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

-
-            
-
-            

+Zone Options

+

 
allow-notify

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     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

-

-                  

+

                     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
                     is
                     active for this zone. The set of machines that will
@@ -8558,11 +7895,9 @@ zone zone_name [also-notify is not
                     meaningful for stub zones.
                     The default is the empty list.
-                  

-                

+                  

 
check-names

-

-                  

+

                     This option is used to restrict the character set and
                     syntax of
                     certain domain names in master files and/or DNS responses
@@ -8570,90 +7905,67 @@ zone zone_name [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
                     is interpreted as a list of whitespace-delimited words.
@@ -8664,60 +7976,53 @@ 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

 

-                  

+

                     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.
                   

-                

+
 
forward

-

-                  

+

                     Only meaningful if the zone has a forwarders
                     list. The only value causes
                     the lookup to fail
                     after trying the forwarders and getting no answer, while first would
                     allow a normal lookup to be tried.
-                  

-                

+                  

 
forwarders

-

-                  

+

                     Used to override the list of global forwarders.
                     If it is not specified in a zone of type forward,
                     no forwarding is done for the zone and the global options are
                     not used.
-                  

-                

+                  

 
ixfr-base

-

-                  

+

                     Was used in BIND 8 to
                     specify the name
                     of the transaction log (journal) file for dynamic update
@@ -8727,103 +8032,78 @@ zone zone_name [.jnl"
                     to the name of the
                     zone file.
-                  

-                

+                  

 
ixfr-tmp-file

-

-                  

+

                     Was an undocumented option in BIND 8.
                     Ignored in BIND 9.
-                  

-                

+                  

 
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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     max-transfer-idle-out in the section called “Zone Transfers”.
-                  

-                

+                  

 
notify

-

-                  

+

                     See the description of
                     notify in the section called “Boolean Options”.
-                  

-                

+                  

 
notify-delay

-

-                  

+

                     See the description of
                     notify-delay in the section called “Tuning”.
-                  

-                

+                  

 
notify-to-soa

-

-                  

+

                     See the description of
                     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

 

-                  

+

                     Only meaningful for static-stub zones.
                     This is a list of IP addresses to which queries
                     should be sent in recursive resolution for the
@@ -8832,7 +8112,7 @@ 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,
@@ -8841,7 +8121,7 @@ zone zone_name [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
@@ -8849,10 +8129,10 @@ 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

 

-                  

+

                     Only meaningful for static-stub zones.
                     This is a list of domain names of nameservers that
                     act as authoritative servers of the static-stub
@@ -8870,7 +8150,7 @@ example.com. AAAA 2001:db8::1234

                     "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
@@ -8882,7 +8162,7 @@ example.com. AAAA 2001:db8::1234

 
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
@@ -8892,181 +8172,139 @@ 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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     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

-

-                  

+

                     See the description of
                     notify-source-v6 in the section called “Zone Transfers”.
-                  

-                

+                  

 

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

-

-                  

+

                     See the description of
                     key-directory in the section called “options Statement Definition and
           Usage”.
-                  

-                

+                  

 
auto-dnssec

-

-                  

+

                     See the description of
                     auto-dnssec in
                     the section called “options Statement Definition and
           Usage”.
-                  

-                

+                  

 
serial-update-method

-

-                  

+

                     See the description of
                     serial-update-method in
                     the section called “options Statement Definition and
           Usage”.
-                  

-                

+                  

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

-                

+                  

 
dnssec-secure-to-insecure

-

-                  

+

                     See the description of
                     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.
             

-            

+

               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
               allows more fine-grained control over what updates are
               allowed.  A set of rules is specified, where each rule
@@ -9076,7 +8314,7 @@ 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
               zone option, and are only meaningful for master zones.
               When the update-policy statement
@@ -9086,7 +8324,7 @@ example.com. NS ns2.example.net.
               only examines the signer of a message; the source
               address is not relevant.
             

-            

+

               There is a pre-defined update-policy
               rule which can be switched on with the command
               update-policy local;.
@@ -9101,31 +8339,26 @@ example.com. NS ns2.example.net.
               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
               requests to localhost, and signs them using the session key.
             

-
-            

+

               Other rule definitions look like this:
             

-
 
 ( 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
@@ -9134,13 +8367,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
@@ -9157,14 +8390,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,
@@ -9176,8 +8409,7 @@ example.com. NS ns2.example.net.
               tcp-self, 6to4-self,
               zonesub, and external.
             

-            

-              
+
@@ -9384,7 +8616,7 @@ example.com. NS ns2.example.net.
                         IP address into the IN-ADDR.ARPA and IP6.ARPA
                         namespaces match the name to be updated.
                       

-                      

+                      

 
Note

                         It is theoretically possible to spoof these TCP
                         sessions.
@@ -9405,7 +8637,7 @@ example.com. NS ns2.example.net.
                         to allow NS or DNAME RRsets to be added to the
                         reverse tree.
                       

-                      

+                      

 
Note

                         It is theoretically possible to spoof these TCP
                         sessions.
@@ -9457,15 +8689,12 @@ 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
@@ -9474,30 +8703,26 @@ example.com. NS ns2.example.net.
               all records associated with a name, the rules are
               checked for each existing record type.
             

-          
-        
-      
-      

+

+
+
+

 

-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
@@ -9507,12 +8732,10 @@ example.com. NS ns2.example.net.
               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”.
             

-
-            

+

               The components of a Resource Record are:
             

-            

-              
+
@@ -9587,13 +8810,11 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 
 

-            

-            

+
+

               The following are types of valid RRs:
             

-            

-              
+
@@ -10574,14 +9795,12 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 
 

-            

-            

+
+

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

-            

-
+
@@ -10634,10 +9853,8 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 
 

-            

-
-            

+
+

               The owner name is often implicit, rather than forming an
               integral
               part of the RR.  For example, many name servers internally form
@@ -10648,7 +9865,7 @@ example.com. NS ns2.example.net.
               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
@@ -10668,18 +9885,17 @@ example.com. NS ns2.example.net.
               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
@@ -10692,13 +9908,13 @@ example.com. NS ns2.example.net.
               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
@@ -10709,15 +9925,14 @@ example.com. NS ns2.example.net.
               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:
             

-            

-
+
@@ -10821,23 +10036,21 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 
 

-            

-            

+
+

               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:
             

-            

-
+
@@ -10875,21 +10088,17 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 
 

-            

-            

+
+

               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,
@@ -10898,8 +10107,7 @@ example.com. NS ns2.example.net.
             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
@@ -10916,7 +10124,7 @@ example.com. NS ns2.example.net.
             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,
@@ -10925,8 +10133,7 @@ example.com. NS ns2.example.net.
             pointed to by the CNAME.
             For example:
           

-          

-            
+
@@ -11063,20 +10270,18 @@ example.com. NS ns2.example.net.
                   
-

 
 
 

 
 

-            

+
 

             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
@@ -11084,8 +10289,7 @@ example.com. NS ns2.example.net.
             currently
             used in a zone file.
           

-          

-            
+
@@ -11140,18 +10344,16 @@ example.com. NS ns2.example.net.
                   
-

 
 
 

 
 

-          

-          

+

+

             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
@@ -11166,8 +10368,7 @@ example.com. NS ns2.example.net.
             PTR records if the machine has more than one name. For example,
             in the [example.com] domain:
           

-          

-            
+
@@ -11198,24 +10399,22 @@ example.com. NS ns2.example.net.
                   
-

 
 
 

 
 

-          

-          

+

+

 
Note

-            

+

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

-          

-        
-        

+

+
+

 

-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
@@ -11223,32 +10422,30 @@ example.com. NS ns2.example.net.
             same
             class.
           

-          

+

             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

-            
-            

+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
@@ -11258,47 +10455,42 @@ example.com. NS ns2.example.net.
               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

-            
-            

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

-            

+

               The origin and the current domain name
               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
@@ -11308,33 +10500,31 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
                 This could be construed as a deviation from RFC 1035, a
                 feature, or both.
               

-            

-          

-          

+

+
+

 

-The $TTL Directive

-            
-            

+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

-          
-          

+BIND Master File Extension: the  $GENERATE Directive

+

             Syntax: $GENERATE
             range
             lhs
@@ -11344,7 +10534,7 @@ 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
@@ -11352,15 +10542,12 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
             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.
@@ -11368,22 +10555,18 @@ $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
@@ -11394,9 +10577,7 @@ HOST-3.EXAMPLE.   MX 0 .
 HOST-127.EXAMPLE. A  1.2.3.127
 HOST-127.EXAMPLE. MX 0 .
 

-
-          

-            
+
@@ -11524,22 +10705,19 @@ HOST-127.EXAMPLE. MX 0 .
                   
-

 
 
 

 
 

-          

-          

+
+

             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
@@ -11548,7 +10726,7 @@ HOST-127.EXAMPLE. MX 0 .
             structure directly, thereby remarkably improving the
             loading time.
           

-          

+

             For a primary server, a zone file in the
             raw format is expected to be
             generated from a textual zone file by the
@@ -11559,7 +10737,7 @@ HOST-127.EXAMPLE. MX 0 .
             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
@@ -11567,7 +10745,7 @@ HOST-127.EXAMPLE. MX 0 .
             should then be converted to the binary form by the
             named-compilezone command again.
           

-          

+

              Although the raw format uses the
              network byte order and avoids architecture-dependent
              data alignment so that it is as much portable as
@@ -11577,14 +10755,12 @@ HOST-127.EXAMPLE. MX 0 .
              portable backup of the file, it is recommended to
              convert the file to the standard textual representation.
           

-        

-      
-
-      

+

+
+

 

 BIND9 Statistics

-        
-        

+

           BIND 9 maintains lots of statistics
           information and provides several interfaces for users to
           get access to the statistics.
@@ -11593,14 +10769,11 @@ 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.
         

-
-        

-          
+
@@ -11698,10 +10871,8 @@ 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
@@ -11711,13 +10882,11 @@ HOST-127.EXAMPLE. MX 0 .
           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
@@ -11727,18 +10896,16 @@ HOST-127.EXAMPLE. MX 0 .
           is specified in the configuration file
           (see the section called “statistics-channels Statement Grammar”.)
         

-
-        

+

 

 The Statistics File

-          
-          

+

             The text format statistics dump begins with a line, like:
           

-          

+

             +++ Statistics Dump +++ (973798949)
           

-          

+

             The number in parentheses is a standard
             Unix-style timestamp, measured as seconds since January 1, 1970.
 
@@ -11747,33 +10914,28 @@ HOST-127.EXAMPLE. MX 0 .
             as described above.
             Each section begins with a line, like:
           

-
-          

+

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

-          
-          

+

             The following tables summarize statistics counters that
             BIND 9 provides.
             For each row of the tables, the leftmost column is the
@@ -11789,14 +10951,10 @@ 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
+
@@ -12387,17 +11545,12 @@ HOST-127.EXAMPLE. MX 0 .
                     
-

 
 
 

 
 

-            

-          

-
-          

+

+

+

 

-Zone Maintenance Statistics Counters

-            
-
-            

-              
+Zone Maintenance Statistics Counters
+
@@ -12546,17 +11699,12 @@ HOST-127.EXAMPLE. MX 0 .
                     
-

 
 
 

 
 

-            

-          

-
-          

+

+

+

 

-Resolver Statistics Counters

-            
-
-            

-              
+Resolver Statistics Counters
+
@@ -12934,17 +12082,12 @@ HOST-127.EXAMPLE. MX 0 .
                     
-

 
 
 

 
 

-            

-
-          

-
-          

+

+

+

 

-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),
@@ -12959,9 +12102,7 @@ HOST-127.EXAMPLE. MX 0 .
               Not all counters are available for all socket types;
               exceptions are noted in the description field.
             

-
-            

-              
+
@@ -13096,57 +12237,45 @@ 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.
               Here are notes about other counters that do not appear
               in these tables.
             

-
-            

+

 
RFwdR,SFwdR

-

-                  

+

                     These counters are not supported
                     because BIND 9 does not adopt
                     the notion of forwarding
                     as BIND 8 did.
-                  

-                

+                  

 
RAXFR

-

-                  

+

                     This counter is accessible in the Incoming Queries section.
-                  

-                

+                  

 
RIQ

-

-                  

+

                     This counter is accessible in the Incoming Requests section.
-                  

-                

+                  

 
ROpts

-

-                  

+

                     This counter is not supported
                     because BIND 9 does not care
                     about IP options in the first place.
-                  

-                

+                  

 

-          

-        
-      
-
-    
+
+
+
+
 

 

 
diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html
index 61640d52d0..9a0c7d572e 100644
--- a/doc/arm/Bv9ARM.ch07.html
+++ b/doc/arm/Bv9ARM.ch07.html
@@ -18,7 +18,7 @@
 Chapter 7. BIND 9 Security Considerations
-
+
@@ -38,27 +38,25 @@
 

 
 
 
 
 

 

 

-

-

-Chapter 7. BIND 9 Security Considerations

+

+

+Chapter 7. BIND 9 Security Considerations

 

 
Table of Contents

-

+

 
Access Control Lists

-
Chroot and Setuid

+
Chroot and Setuid

 

-
The chroot Environment

-
Using the setuid Function

+
The chroot Environment

+
Using the setuid Function

 

 
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,
@@ -66,21 +64,20 @@
           blackhole, allow-transfer,
           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.
         

-        

+

           Here is an example of how to properly apply ACLs:
         

-
 
 // Set up an ACL named "bogusnets" that will block
 // RFC1918 space and some reserved space, which is
@@ -109,18 +106,16 @@ zone "example.com" {
   allow-query { any; };
 };
 

-
-        

+

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

-      

-      

+

+

 

-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
@@ -129,26 +124,23 @@ zone "example.com" {
           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.
         

-        

+

           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

-          
-
-          

+The chroot Environment

+

             In order for a chroot environment
             to
             work properly in a particular directory
@@ -161,7 +153,7 @@ zone "example.com" {
             like directory and pid-file to account
             for this.
           

-          

+

             Unlike with earlier versions of BIND, you typically will
             not need to compile named
             statically nor install shared libraries under the new root.
@@ -172,14 +164,11 @@ zone "example.com" {
             /dev/log, and
             /etc/localtime.
           

-        

-
-        

+

+

 

-Using the setuid Function

-          
-
-          

+Using the setuid Function

+

             Prior to running the named daemon,
             use
             the touch utility (to change file
@@ -190,21 +179,18 @@ zone "example.com" {
             to which you want BIND
             to write.
           

-          

+

 
Note

             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
@@ -224,8 +210,7 @@ zone "example.com" {
           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
@@ -234,8 +219,7 @@ zone "example.com" {
           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
@@ -243,9 +227,8 @@ zone "example.com" {
           of public web and mail servers need not allow dynamic update at
           all.
         

-
-      

-    
+
+
 

 

 
diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html
index 04cdab0139..ce913eafb5 100644
--- a/doc/arm/Bv9ARM.ch08.html
+++ b/doc/arm/Bv9ARM.ch08.html
@@ -18,7 +18,7 @@
 Chapter 8. Troubleshooting
-
+
@@ -38,44 +38,37 @@
 

 
 
 
 
 

 

 

-

-

-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.
@@ -87,27 +80,22 @@
           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
@@ -120,16 +108,15 @@
           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.
         

-      
-    
+
+
 

 

 
diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index 4a20f1d23f..55a3b54211 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html
@@ -18,7 +18,7 @@
 Appendix A. Release Notes
-
+
@@ -38,13 +38,13 @@
 

 
 
 
 
 

 

 

-

-

-Appendix A. Release Notes

+

+

+Release Notes

 

 
Table of Contents

-

-
Release Notes for BIND Version 9.9.8

+

+

 

 
Introduction

 
Download

@@ -58,84 +58,75 @@
 

 

 

-      
-      

-

-Release Notes for BIND Version 9.9.8

-  
-  

+

+

+<title>Release Notes for BIND Version 9.9.8</title>

 

 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/.
+      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]
 	
      
-      
      • 
+
 
    
-  

-  

+

+

 

 New Features

-    
-    
    
+
      
 
    • 
-	
      
+
      
 	  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,
@@ -144,14 +135,13 @@
 	  experienced by recursives when they are being used as a
 	  vehicle for such an attack.
 	
      
-	
      
+
      
 	  NOTE: These options are not available by default; use
 	  configure --enable-fetchlimit to include
 	  them in the build.
 	
      
-	
        
-
      • 
-	    
        
+
          
+
        • 
 	      fetches-per-server limits the number of
 	      simultaneous queries that can be sent to any single
 	      authoritative server.  The configured value is a starting
@@ -159,101 +149,77 @@
 	      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.
 	
        
-      
        • 
-
      • 
-	
        
+
        • 
+
      • 
 	  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]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  The following types have been implemented: CSYNC, NINFO, RKEY,
 	  SINK, TA, TALINK.
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  EDNS COOKIE options content is now displayed as
 	  "COOKIE: <hexvalue>".
-	
        
-      
        • 
+	
        
 
      
-  
    
-  
    
+
    
+
    
 
    
 Feature Changes
    
-    
-    
      
-
    • 
-	
      
+
        
+
      • 
 	  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]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  Retrieving the local port range from net.ipv4.ip_local_port_range
 	  on Linux is now supported.
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  Active Directory names of the form gc._msdcs.<forest> are
 	  now accepted as valid hostnames when using the
 	  check-names option. <forest> is still
 	  restricted to letters, digits and hyphens.
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  Names containing rich text are now accepted as valid
 	  hostnames in PTR records in DNS-SD reverse lookup zones,
 	  as specified in RFC 6763. [RT #37889]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  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
@@ -262,83 +228,65 @@
 	  previously compiled in the binary. Read
 	  win32utils/build.txt for more details.
 	  [RT #38915]
-	
        
-      
      
-  
    
-  
    
+	

+

+

 

 Bug Fixes

-    
-    
    
-
  • 
-	
    
+
      
+
    • 
 	  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]
-	
      
-      
      • 
-
    • 
-	
      
+	
      • 
+
    • 
 	  Malformed records of some types, including NSAP and UNSPEC,
 	  could trigger assertion failures when loading text zone files.
 	  [RT #40274] [RT #40285]
-	
      
-      
      • 
-
    • 
-	
      
+	
      • 
+
    • 
 	  Fixed a possible crash in ratelimiter.c caused by NOTIFY
 	  messages being removed from the wrong rate limiter queue.
 	  [RT #40350]
-	
      
-      
      • 
-
    • 
-	
      
+	
      • 
+
    • 
 	  The default rrset-order of random
 	  was inconsistently applied. [RT #40456]
-	
      
-      
      • 
-
    • 
-	
      
+	
      • 
+
    • 
 	  BADVERS responses from broken authoritative name servers were
 	  not handled correctly. [RT #40427]
-	
      
-      
      • 
+	
      
 
    
-  

-  

+

+

 

 End of Life

-    
-    

+

       The BIND 9.9 (Extended Support Version) will be supported until June, 2017.
-      https://www.isc.org/downloads/software-support-policy/
+      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/.
+      http://www.isc.org/donate/.
     

-  

 

-    

+

+

 

 

 
diff --git a/doc/arm/Bv9ARM.ch10.html b/doc/arm/Bv9ARM.ch10.html
index 6de3ca60f7..3b8c3770cc 100644
--- a/doc/arm/Bv9ARM.ch10.html
+++ b/doc/arm/Bv9ARM.ch10.html
@@ -18,7 +18,7 @@
 Appendix B. A Brief History of the DNS and BIND
-
+
@@ -39,22 +39,21 @@
 

 
 
 
 
 

 

 

-

-

-Appendix B. A Brief History of the DNS and BIND
-

+

+

+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
@@ -69,8 +68,7 @@
             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
@@ -88,12 +86,11 @@
             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
@@ -108,7 +105,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
@@ -120,42 +117,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.
           

-      

-    

+

+

 

 

 
diff --git a/doc/arm/Bv9ARM.ch11.html b/doc/arm/Bv9ARM.ch11.html
index 0839fdea99..f990914f5d 100644
--- a/doc/arm/Bv9ARM.ch11.html
+++ b/doc/arm/Bv9ARM.ch11.html
@@ -18,7 +18,7 @@
 Appendix C. General DNS Reference Information
-
+
@@ -38,27 +38,25 @@
 

 
 
 
 
 

 

 

-

-

-Appendix C. General DNS Reference Information

+

+

+General DNS Reference Information

 

 
Table of Contents

-

+

 
IPv6 addresses (AAAA)

 
Bibliography (and Suggested Reading)

 

 
Request for Comments (RFCs)

 
Internet Drafts

-
Other Documents About BIND

+
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,
@@ -69,13 +67,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
@@ -89,14 +87,14 @@
             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
@@ -104,7 +102,7 @@
             address might look like:
             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
@@ -112,16 +110,14 @@
             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)
@@ -129,776 +125,336 @@
             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

+

+

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

 

-              

-
[RFC2308] 
-                
-                M. Andrews. 
-                Negative Caching of DNS
-                  Queries. 
-                March 1998. 
-              

+

+

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

 

-              

-
[RFC1995] 
-                
-                M. Ohta. 
-                Incremental Zone Transfer in DNS. 
-                August 1996. 
-              

+

+
[RFC2308] M. Andrews. Negative Caching of DNS
+                  Queries. March 1998. 

 

-              

-
[RFC1996] 
-                
-                P. Vixie. 
-                A Mechanism for Prompt Notification of Zone Changes. 
-                August 1996. 
-              

+

+
[RFC1995] M. Ohta. Incremental Zone Transfer in DNS. August 1996. 

 

-              

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

+

+
[RFC1996] P. Vixie. A Mechanism for Prompt Notification of Zone Changes. August 1996. 

 

-              

-
[RFC2671] 
-                
-                P. Vixie. 
-                Extension Mechanisms for DNS (EDNS0). 
-                August 1997. 
-              

+

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

 

-              

-
[RFC2672] 
-                
-                M. Crawford. 
-                Non-Terminal DNS Name Redirection. 
-                August 1999. 
-              

+

+
[RFC2671] P. Vixie. Extension Mechanisms for DNS (EDNS0). August 1997. 

 

-              

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

+

+
[RFC2672] M. Crawford. Non-Terminal DNS Name Redirection. August 1999. 

 

-              

-
[RFC2930] 
-                
-                D. Eastlake, 3rd. 
-                Secret Key Establishment for DNS (TKEY RR). 
-                September 2000. 
-              

+

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

 

-              

-
[RFC2931] 
-                
-                D. Eastlake, 3rd. 
-                DNS Request and Transaction Signatures (SIG(0)s). 
-                September 2000. 
-              

+

+
[RFC2930] D. Eastlake, 3rd. Secret Key Establishment for DNS (TKEY RR). September 2000. 

 

-              

-
[RFC3007] 
-                
-                B. Wellington. 
-                Secure Domain Name System (DNS) Dynamic Update. 
-                November 2000. 
-              

+

+
[RFC2931] D. Eastlake, 3rd. DNS Request and Transaction Signatures (SIG(0)s). September 2000. 

 

-              

-
[RFC3645] 
-                
-                S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. 
-                Generic Security Service Algorithm for Secret
+

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

 

-              

-
[RFC3833] 
-                
-                D. Atkins and R. Austein. 
-                Threat Analysis of the Domain Name System (DNS). 
-                August 2004. 
-              

+

+

+
[RFC3225] D. Conrad. Indicating Resolver Support of DNSSEC. December 2001. 

 

-              

-
[RFC4033] 
-                
-                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
-                DNS Security Introduction and Requirements. 
-                March 2005. 
-              

+

+
[RFC3833] D. Atkins and R. Austein. Threat Analysis of the Domain Name System (DNS). August 2004. 

 

-              

-
[RFC4034] 
-                
-                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
-                Resource Records for the DNS Security Extensions. 
-                March 2005. 
-              

+

+
[RFC4033] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. March 2005. 

 

-              

-
[RFC4035] 
-                
-                R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. 
-                Protocol Modifications 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. 

 

-            

-            

-

-Other Important RFCs About DNS
-                Implementation

-              
-              

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

+

+
[RFC4035] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Protocol Modifications for the DNS
+                       Security Extensions. March 2005. 

 

-              

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

+

+

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

 

-              

-
[RFC4074] 
-                
-                Y. Morishita and T. Jinmei. 
-                Common Misbehaviour Against DNS
-                Queries for IPv6 Addresses. 
-                May 2005. 
-              

+

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

 

-            

-            

-

-Resource Record Types

-              
-              

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

+

+
[RFC1982] R. Elz and R. Bush. Serial Number Arithmetic. August 1996. 

 

-              

-
[RFC1706] 
-                
-                B. Manning and R. Colella. 
-                DNS NSAP Resource Records. 
-                October 1994. 
-              

+

+
[RFC4074] Y. Morishita and T. Jinmei. Common Misbehaviour Against DNS
+                Queries for IPv6 Addresses. May 2005. 

 

-              

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

+

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

+

+

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

 

-              

-
[RFC1123] 
-                
-                Braden. 
-                Requirements for Internet Hosts - Application and
-                  Support. 
-                October 1989. 
-              

+

+

+
[RFC1101] P. V. Mockapetris. DNS Encoding of Network Names
+                  and Other Types. April 1989. 

 

-              

-
[RFC1591] 
-                
-                J. Postel. 
-                Domain Name System Structure and Delegation. 
-                March 1994. 
-              

+

+
[RFC1123] Braden. Requirements for Internet Hosts - Application and
+                  Support. October 1989. 

 

-              

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

+

+
[RFC1591] J. Postel. Domain Name System Structure and Delegation. March 1994. 

 

-              

-
[RFC2826] 
-                
-                Internet Architecture Board. 
-                IAB Technical Comment on the Unique DNS Root. 
-                May 2000. 
-              

+

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

 

-              

-
[RFC2929] 
-                
-                D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. 
-                Domain Name System (DNS) IANA Considerations. 
-                September 2000. 
-              

+

+
[RFC2826] Internet Architecture Board. IAB Technical Comment on the Unique DNS Root. May 2000. 

 

-            

-            

-

-DNS Operations

-              
-              

-
[RFC1033] 
-                
-                M. Lottor. 
-                Domain administrators operations guide.. 
-                November 1987. 
-              

+

+
[RFC2929] D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. September 2000. 

 

-              

-
[RFC1537] 
-                
-                P. Beertema. 
-                Common DNS Data File
-                  Configuration Errors. 
-                October 1993. 
-              

 

-              

-
[RFC1912] 
-                
-                D. Barr. 
-                Common DNS Operational and
-                  Configuration Errors. 
-                February 1996. 
-              

+

+

+
[RFC1033] M. Lottor. Domain administrators operations guide.. November 1987. 

 

-              

-
[RFC2010] 
-                
-                B. Manning and P. Vixie. 
-                Operational Criteria for Root Name Servers.. 
-                October 1996. 
-              

+

+
[RFC1537] P. Beertema. Common DNS Data File
+                  Configuration Errors. October 1993. 

 

-              

-
[RFC2219] 
-                
-                M. Hamilton and R. Wright. 
-                Use of DNS Aliases for
-                  Network Services.. 
-                October 1997. 
-              

+

+
[RFC1912] D. Barr. Common DNS Operational and
+                  Configuration Errors. February 1996. 

 

-            

-            

-

-Internationalized Domain Names

-              
-              

-
[RFC2825] 
-                
-                IAB and R. Daigle. 
-                A Tangled Web: Issues of I18N, Domain Names,
-                       and the Other Internet protocols. 
-                May 2000. 
-              

+

+
[RFC2010] B. Manning and P. Vixie. Operational Criteria for Root Name Servers.. October 1996. 

 

-              

-
[RFC3490] 
-                
-                P. Faltstrom, P. Hoffman, and A. Costello. 
-                Internationalizing Domain Names in Applications (IDNA). 
-                March 2003. 
-              

+

+
[RFC2219] M. Hamilton and R. Wright. Use of DNS Aliases for
+                  Network Services.. October 1997. 

 

-              

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

+

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

+

+

+
[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
                        for Internationalized Domain Names in
-                       Applications (IDNA). 
-                March 2003. 
-              

+                       Applications (IDNA). March 2003. 

 

-            

-            

-

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

 

-              

-
[RFC1713] 
-                
-                A. Romao. 
-                Tools for DNS Debugging. 
-                November 1994. 
-              

+

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

 

-              

-
[RFC1794] 
-                
-                T. Brisco. 
-                DNS Support for Load
-                  Balancing. 
-                April 1995. 
-              

+

+
[RFC1713] A. Romao. Tools for DNS Debugging. November 1994. 

 

-              

-
[RFC2240] 
-                
-                O. Vaughan. 
-                A Legal Basis for Domain Name Allocation. 
-                November 1997. 
-              

+

+
[RFC1794] T. Brisco. DNS Support for Load
+                  Balancing. April 1995. 

 

-              

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

+

+
[RFC2240] O. Vaughan. A Legal Basis for Domain Name Allocation. November 1997. 

 

-              

-
[RFC2352] 
-                
-                O. Vaughan. 
-                A Convention For Using Legal Names as Domain Names. 
-                May 1998. 
-              

+

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

 

-              

-
[RFC3071] 
-                
-                J. Klensin. 
-                Reflections on the DNS, RFC 1591, and Categories of Domains. 
-                February 2001. 
-              

+

+
[RFC2352] O. Vaughan. A Convention For Using Legal Names as Domain Names. May 1998. 

 

-              

-
[RFC3258] 
-                
-                T. Hardie. 
-                Distributing Authoritative Name Servers via
-                       Shared Unicast Addresses. 
-                April 2002. 
-              

+

+
[RFC3071] J. Klensin. Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001. 

 

-              

-
[RFC3901] 
-                
-                A. Durand and J. Ihren. 
-                DNS IPv6 Transport Operational Guidelines. 
-                September 2004. 
-              

+

+
[RFC3258] T. Hardie. Distributing Authoritative Name Servers via
+                       Shared Unicast Addresses. April 2002. 

 

-            

-            

-

-Obsolete and Unimplemented Experimental RFC

-              
-              

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

+

+
[RFC3901] A. Durand and J. Ihren. DNS IPv6 Transport Operational Guidelines. September 2004. 

 

-              

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

+

+

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

 

-            

-            

-

-Obsoleted DNS Security RFCs

-              
-              

+

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

+

+

+

+

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

 

-              

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

+

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

 

-              

-
[RFC2535] 
-                
-                D. Eastlake, 3rd. 
-                Domain Name System Security Extensions. 
-                March 1999. 
-              

+

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

 

-              

-
[RFC3008] 
-                
-                B. Wellington. 
-                Domain Name System Security (DNSSEC)
-                       Signing Authority. 
-                November 2000. 
-              

+

+
[RFC2535] D. Eastlake, 3rd. Domain Name System Security Extensions. March 1999. 

 

-              

-
[RFC3090] 
-                
-                E. Lewis. 
-                DNS Security Extension Clarification on Zone Status. 
-                March 2001. 
-              

+

+
[RFC3008] B. Wellington. Domain Name System Security (DNSSEC)
+                       Signing Authority. November 2000. 

 

-              

-
[RFC3445] 
-                
-                D. Massey and S. Rose. 
-                Limiting the Scope of the KEY Resource Record (RR). 
-                December 2002. 
-              

+

+
[RFC3090] E. Lewis. DNS Security Extension Clarification on Zone Status. March 2001. 

 

-              

-
[RFC3655] 
-                
-                B. Wellington and O. Gudmundsson. 
-                Redefinition of DNS Authenticated Data (AD) bit. 
-                November 2003. 
-              

+

+
[RFC3445] D. Massey and S. Rose. Limiting the Scope of the KEY Resource Record (RR). December 2002. 

 

-              

-
[RFC3658] 
-                
-                O. Gudmundsson. 
-                Delegation Signer (DS) Resource Record (RR). 
-                December 2003. 
-              

+

+
[RFC3655] B. Wellington and O. Gudmundsson. Redefinition of DNS Authenticated Data (AD) bit. November 2003. 

 

-              

-
[RFC3755] 
-                
-                S. Weiler. 
-                Legacy Resolver Compatibility for Delegation Signer (DS). 
-                May 2004. 
-              

+

+
[RFC3658] O. Gudmundsson. Delegation Signer (DS) Resource Record (RR). December 2003. 

 

-              

-
[RFC3757] 
-                
-                O. Kolkman, J. Schlyter, and E. Lewis. 
-                Domain Name System KEY (DNSKEY) Resource Record
-                      (RR) Secure Entry Point (SEP) Flag. 
-                April 2004. 
-              

+

+
[RFC3755] S. Weiler. Legacy Resolver Compatibility for Delegation Signer (DS). May 2004. 

 

-              

-
[RFC3845] 
-                
-                J. Schlyter. 
-                DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. 
-                August 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. 

+

+

+

+

+

 

 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
@@ -908,27 +464,22 @@
             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
-

-          
-          

-          

-

-Bibliography

-            

-

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

 

-          

-        

-      

-    

+

+

+Other Documents About BIND
+

+

+

+

+Bibliography

+

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

+

+

+

+

+

 

 

 
diff --git a/doc/arm/Bv9ARM.ch12.html b/doc/arm/Bv9ARM.ch12.html
index 1ed6179ab7..b74418d577 100644
--- a/doc/arm/Bv9ARM.ch12.html
+++ b/doc/arm/Bv9ARM.ch12.html
@@ -18,7 +18,7 @@
 Appendix D. BIND 9 DNS Library Support
-
+
@@ -38,99 +38,86 @@
 

 
 
 
 
 

 

 

-

-

-Appendix D. BIND 9 DNS Library Support

+

+

+BIND 9 DNS Library Support

 

 
Table of Contents

-

+

 
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
@@ -140,24 +127,20 @@ $ make install
   "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).
    
-    
    • 
+      before).
    
 
  • 
-      
    The "fixed" RRset order is not (currently) supported in
+
    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
       export library even without the fixed order support, build
@@ -172,34 +155,27 @@ $ 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.
@@ -213,31 +189,29 @@ $ make
   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.)
    
-  
-  
    
+
    
+
    
 
    
-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
   
    
@@ -286,21 +260,20 @@ $ make
 	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
    
    
@@ -326,14 +299,13 @@ $ 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
@@ -342,46 +314,39 @@ $ make
   ultimate answer. In other words, this utility acts as a very
   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
@@ -391,27 +356,26 @@ $ 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.
   
    
-  
    
+
    
    Usage: sample-update [options] (add|delete) "update data"
   
    
-  
    
+
    
   Options and Arguments:
   
    
-  
    
+
    
 
    
   -a auth_server
    
    
@@ -467,51 +431,47 @@ $ make
 	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
   
    
@@ -550,19 +510,18 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mm
 	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.
    
-  
 
-    
+
+
 
    
 
    
 
diff --git a/doc/arm/Bv9ARM.ch13.html b/doc/arm/Bv9ARM.ch13.html
index 0e9b826a1a..d7abbaba62 100644
--- a/doc/arm/Bv9ARM.ch13.html
+++ b/doc/arm/Bv9ARM.ch13.html
@@ -18,7 +18,7 @@
 Manual pages
-
+
@@ -38,7 +38,7 @@
 
    
 
 
 
 
 
    
 
    
 
    
-
    
+
    
 
    
 
    
 Manual pages
    
@@ -46,7 +46,7 @@
 
    
 
    
 
    Table of Contents
    
-
    
+
    
 
    
 dig — DNS lookup utility
 
    
@@ -130,35 +130,7 @@
 
 
    
 
    
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-      
-    
    
+
    
 
    
 
    
 
diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html
index 056c30562e..3c6821ff4e 100644
--- a/doc/arm/Bv9ARM.html
+++ b/doc/arm/Bv9ARM.html
@@ -18,7 +18,7 @@
 BIND 9 Administrator Reference Manual
-
+
@@ -35,12 +35,11 @@
 
    
 
 
 
 
 
    
 
    
 
    
-
    
+
    
 
    
 
    
 
    
-BIND 9 Administrator Reference Manual
    
-
    BIND Version 9.9.8
    
+BIND 9 Administrator Reference Manual
    
 
    Copyright © 2004-2015 Internet Systems Consortium, Inc. ("ISC")
    
 
    Copyright © 2000-2003 Internet Software Consortium.
    
 
    
@@ -48,42 +47,42 @@
 
    
 
    
 
    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
    
 
    
-
    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
    
@@ -92,64 +91,64 @@
 
    Dynamic Update
    
 
    The journal file
    
 
    Incremental Zone Transfers (IXFR)
    
-
    Split DNS
    
-
    Example split DNS setup
    
+
    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)
    
+
    TKEY
    
+
    SIG(0)
    
 
    DNSSEC
    
 
    
-
    Generating Keys
    
-
    Signing the Zone
    
-
    Configuring Servers
    
+
    Generating Keys
    
+
    Signing the Zone
    
+
    Configuring Servers
    
 
    
 
    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
    
 
    
-
    Validating Resolver
    
-
    Authoritative Server
    
+
    Validating Resolver
    
+
    Authoritative Server
    
 
    
 
    PKCS #11 (Cryptoki) support
    
 
    
-
    Prerequisites
    
-
    Building BIND 9 with PKCS#11
    
-
    PKCS #11 Tools
    
-
    Using the HSM
    
-
    Specifying the engine on the command line
    
-
    Running named with automatic zone re-signing
    
+
    Prerequisites
    
+
    Building BIND 9 with PKCS#11
    
+
    PKCS #11 Tools
    
+
    Using the HSM
    
+
    Specifying the engine on the command line
    
+
    Running named with automatic zone re-signing
    
 
    
-
    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
    
+
    The Lightweight Resolver Library
    
 
    Running a Resolver Daemon
    
 
    
 
    6. BIND 9 Configuration Reference
    
@@ -157,58 +156,58 @@
 
    Configuration File Elements
    
 
    
 
    Address Match Lists
    
-
    Comment Syntax
    
+
    Comment Syntax
    
 
    
 
    Configuration File Grammar
    
 
    
-
    acl Statement Grammar
    
+
    acl Statement Grammar
    
 
    acl Statement Definition and
           Usage
    
-
    controls Statement Grammar
    
+
    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 Grammar
    
 
    options Statement Definition and
           Usage
    
 
    server Statement Grammar
    
 
    server Statement Definition and
             Usage
    
 
    statistics-channels Statement Grammar
    
-
    statistics-channels Statement Definition and
+
    statistics-channels Statement Definition and
             Usage
    
 
    trusted-keys Statement Grammar
    
-
    trusted-keys Statement Definition
+
    trusted-keys Statement Definition
             and Usage
    
-
    managed-keys Statement Grammar
    
+
    managed-keys Statement Grammar
    
 
    managed-keys Statement Definition
             and Usage
    
 
    view Statement Grammar
    
-
    view Statement Definition and Usage
    
+
    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
    
+
    Discussion of MX Records
    
 
    Setting TTLs
    
-
    Inverse Mapping in IPv4
    
-
    Other Zone File Directives
    
-
    BIND Master File Extension: the  $GENERATE Directive
    
+
    Inverse Mapping in IPv4
    
+
    Other Zone File Directives
    
+
    BIND Master File Extension: the  $GENERATE Directive
    
 
    Additional File Formats
    
 
    
 
    BIND9 Statistics
    
@@ -220,23 +219,23 @@
 
    7. BIND 9 Security Considerations
    
 
    
 
    Access Control Lists
    
-
    Chroot and Setuid
    
+
    Chroot and Setuid
    
 
    
-
    The chroot Environment
    
-
    Using the setuid Function
    
+
    The chroot Environment
    
+
    Using the setuid Function
    
 
    
 
    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.9.8
    
+
    
 
    
 
    Introduction
    
 
    Download
    
@@ -261,20 +260,20 @@
 
    
 
    Request for Comments (RFCs)
    
 
    Internet Drafts
    
-
    Other Documents About BIND
    
+
    Other Documents About BIND
    
 
    
 
    
 
    D. 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
    
@@ -363,34 +362,7 @@
 
    
 
    
 
    
-  
-
-  
-
-  
-
-  
-
-  
-
-  
-
-  
-    
-
-    
-
-    
-
-    
-
-    
-
-    
-
-    
-
-  
    
+
 
    
 
    
 
diff --git a/doc/arm/man.arpaname.html b/doc/arm/man.arpaname.html
index 2edfeda946..ea0a994abe 100644
--- a/doc/arm/man.arpaname.html
+++ b/doc/arm/man.arpaname.html
@@ -18,7 +18,7 @@
 arpaname
-
+
@@ -38,47 +38,29 @@
 
    
 
 
 
 
 
    
 
    
 
    
-
    
+
    
 
    
-  
-  
-  
-
-  
    
+
    
 
    Name
    
-
    
-    arpaname
-     — translate IP addresses to the corresponding ARPA names
-  
    
+
    arpaname — translate IP addresses to the corresponding ARPA names
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      arpaname 
-       {ipaddress ...}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.ddns-confgen.html b/doc/arm/man.ddns-confgen.html
index 28e2b99962..57f35dbf1d 100644
--- a/doc/arm/man.ddns-confgen.html
+++ b/doc/arm/man.ddns-confgen.html
@@ -18,7 +18,7 @@
 
 
 ddns-confgen
-
+
 
 
 
@@ -38,44 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    ddns-confgen
-     — ddns key generation tool
-  
    
+
    ddns-confgen — ddns key generation tool
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      ddns-confgen 
-       [-a algorithm]
-       [-h]
-       [-k keyname]
-       [-r randomfile]
-       [
-         -s name 
-         |   -z zone 
-      ]
-       [-q]
-       [name]
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    ddns-confgen
+
    ddns-confgen  [-a algorithm] [-h] [-k keyname] [-r randomfile] [ -s name  |   -z zone ] [-q] [name]
    
+
    
+
    
+
    DESCRIPTION
    
+
    ddns-confgen
       generates a key for use by nsupdate
       and named.  It simplifies configuration
       of dynamic zones by generating a key and providing the
@@ -83,8 +58,7 @@
       syntax that will be needed to use it, including an example
       update-policy statement.
     
    
-
-    
    
+
    
       If a domain name is specified on the command line, it will
       be used in the name of the generated key and in the sample
       named.conf syntax.  For example,
@@ -93,39 +67,30 @@
       named.conf command that could be used
       in the zone definition for "example.com".
     
    
-
-    
    
+
    
       Note that named itself can configure a
       local DDNS key for use with nsupdate -l.
       ddns-confgen is only needed when a 
       more elaborate configuration is required: for instance, 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.
-	  
    
-	
    
+	  
    
 
    -h
    
-
    
-	  
    
+
    
 	    Prints a short summary of the options and arguments to
 	    ddns-confgen.
-	  
    
-	
    
+	  
    
 
    -k keyname
    
-
    
-	  
    
+
    
 	    Specifies the key name of the DDNS authentication key.
 	    The default is ddns-key when neither
 	    the -s nor -z option is
@@ -135,18 +100,14 @@
 	    ddns-key.example.com.
 	    The key name must have the format of a valid domain name,
 	    consisting of letters, digits, hyphens and periods.
-	  
    
-	
    
+	  
    
 
    -q
    
-
    
-	  
    
+
    
 	    Quiet mode:  Print only the key, with no explanatory text or
             usage examples.
-	  
    
-	
    
+	  
    
 
    -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
@@ -156,11 +117,9 @@
             instead of the default.  The special value
             keyboard indicates that keyboard input
             should be used.
-	  
    
-	
    
+	  
    
 
    -s name
    
-
    
-	  
    
+
    
 	    Single host mode: The example named.conf text
 	    shows how to set an update policy for the specified
 	    name
@@ -170,11 +129,9 @@
 	    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
    
-
    
-	  
    
+
    
 	    zone mode:  The example named.conf text
             shows how to set an update policy for the specified
 	    zone
@@ -182,27 +139,17 @@
 	    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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html
index 4ef8afe09a..3824776633 100644
--- a/doc/arm/man.dig.html
+++ b/doc/arm/man.dig.html
@@ -18,7 +18,7 @@
 
 
 dig
-
+
 
 
 
@@ -38,64 +38,21 @@
 
 
    
 
    
-
    
+
    
 
    
-
-  
-  
-
-  
-
-  
    
+
    
 
    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
@@ -104,8 +61,7 @@
       clarity of output.  Other lookup tools tend to have less functionality
       than dig.
     
    
-
-    
    
+
    
       Although dig is normally used with
       command-line
       arguments, it also has a batch mode of operation for reading lookup
@@ -116,42 +72,34 @@
       from the
       command line.
     
    
-
-    
    
+
    
       Unless it is told to query a specific name server,
       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
       host.
     
    
-
-    
    
+
    
       When no command line arguments or options are given,
       dig will perform an NS query for "." (the root).
     
    
-
-    
    
+
    
       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
    
-    
-
-    
    
+
    
+
    
+
    SIMPLE USAGE
    
+
    
       A typical invocation of dig looks like:
       
    
 
     dig @server name type 
    
@@ -159,10 +107,10 @@
       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
@@ -170,7 +118,7 @@
 	      dig resolves that name before querying
 	      that name server.
 	    
    
-	    
    
+
    
 	      If no server argument is
 	      provided, dig consults
 	      /etc/resolv.conf; if an
@@ -183,16 +131,13 @@
 	      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
@@ -200,109 +145,81 @@
 	      type argument is supplied,
 	      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
 	    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.
-	  
    
-        
    
+	  
    
 
    -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)
-	    .
+	    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
 	    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
@@ -314,17 +231,13 @@
 	    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
@@ -339,11 +252,10 @@
 	    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.
@@ -354,34 +266,28 @@
 	    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
@@ -395,29 +301,22 @@
       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
@@ -427,161 +326,123 @@
 	      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]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
 	      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]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
 	      /etc/resolv.conf, and enable
 	      search list processing as if the
 	      +search option were given.
-	    
    
-	  
    
+	    
    
 
    +[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]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]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
 	      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
@@ -593,123 +454,97 @@
 	      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
 	      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]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
 	      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
@@ -718,30 +553,24 @@
 	      +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]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.
-	    
    
-	  
    
+	    
    
 
    +time=T
    
-
    
-	    
    
+
    
 
 	      Sets the timeout for a query to
 	      T seconds.  The default
@@ -749,18 +578,15 @@
 	      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,
@@ -768,67 +594,62 @@
 	      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
 	      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
 	      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]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".
-	    
    
-	  
    
+	    
    
 
    
 
    
 
     
    
-  
    
-
-  
    
-
    MULTIPLE QUERIES
    
-    
-
-    
    
+
    
+
    
+
    MULTIPLE QUERIES
    
+
    
       The BIND 9 implementation of dig 
       supports
       specifying multiple queries on the command line (in addition to
@@ -836,8 +657,7 @@
       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
@@ -845,8 +665,7 @@
       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
@@ -873,13 +692,10 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
       will not print the initial query when it looks up the NS records for
       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.
       dig appropriately converts character encoding of
@@ -890,40 +706,28 @@ 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
    
-    
-    
    /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.
     
    
-  
    
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-checkds.html b/doc/arm/man.dnssec-checkds.html
index 818cbcb798..fac984f39e 100644
--- a/doc/arm/man.dnssec-checkds.html
+++ b/doc/arm/man.dnssec-checkds.html
@@ -18,7 +18,7 @@
 
 
 dnssec-checkds
-
+
 
 
 
@@ -38,108 +38,61 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
-          
    
-        
    
+          
    
 
    -d dig path
    
-
    
-          
    
+
    
             Specifies a path to a dig binary.  Used
             for testing.
-          
    
-        
    
+          
    
 
    -D dsfromkey path
    
-
    
-          
    
+
    
             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),
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-coverage.html b/doc/arm/man.dnssec-coverage.html
index da47ab6427..4215597dc4 100644
--- a/doc/arm/man.dnssec-coverage.html
+++ b/doc/arm/man.dnssec-coverage.html
@@ -18,7 +18,7 @@
 
 
 dnssec-coverage
-
+
 
 
 
@@ -38,46 +38,24 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    dnssec-coverage
-     — checks future DNSKEY coverage for a zone
-  
    
+
    dnssec-coverage — checks future DNSKEY coverage for a zone
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      dnssec-coverage 
-       [-K directory]
-       [-f file]
-       [-d DNSKEY TTL]
-       [-m max TTL]
-       [-r interval]
-       [-c compilezone path]
-       [zone]
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    dnssec-coverage
+
    dnssec-coverage  [-K directory] [-f file] [-d DNSKEY TTL] [-m max TTL] [-r interval] [-c compilezone path] [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.,
@@ -90,40 +68,33 @@
       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
    
+
    
 
    -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.
-          
    
-        
    
+          
    
 
    -K directory
    
-
    
-          
    
+
    
             Sets the directory in which keys can be found.  Defaults to the
             current working directory.
-          
    
-        
    
+          
    
 
    -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
@@ -132,21 +103,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
@@ -156,12 +127,12 @@
             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
@@ -169,10 +140,10 @@
             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
@@ -182,41 +153,28 @@
             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.
           
    
-        
    
+
 
    -c compilezone path
    
-
    
-          
    
+
    
             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)
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-dsfromkey.html b/doc/arm/man.dnssec-dsfromkey.html
index ee5a92da1f..991092660e 100644
--- a/doc/arm/man.dnssec-dsfromkey.html
+++ b/doc/arm/man.dnssec-dsfromkey.html
@@ -18,7 +18,7 @@
 
 
 dnssec-dsfromkey
-
+
 
 
 
@@ -38,245 +38,161 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
             command as input, as in:
           
    
-          
    
+
    
             dig dnskey example.com | dnssec-dsfromkey -f - example.com
           
    
-        
    
+
 
    -A
    
-
    
-          
    
+
    
             Include ZSK's 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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-importkey.html b/doc/arm/man.dnssec-importkey.html
index 585f43ff1a..94a222a150 100644
--- a/doc/arm/man.dnssec-importkey.html
+++ b/doc/arm/man.dnssec-importkey.html
@@ -18,7 +18,7 @@
 
 
 dnssec-importkey
-
+
 
 
 
@@ -38,54 +38,20 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
@@ -93,7 +59,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
@@ -102,68 +68,53 @@
       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
@@ -174,52 +125,38 @@
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-keyfromlabel.html b/doc/arm/man.dnssec-keyfromlabel.html
index c020fb0581..86c0f5312f 100644
--- a/doc/arm/man.dnssec-keyfromlabel.html
+++ b/doc/arm/man.dnssec-keyfromlabel.html
@@ -18,7 +18,7 @@
 
 
 dnssec-keyfromlabel
-
+
 
 
 
@@ -38,58 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
@@ -97,80 +58,68 @@
       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 name of the crypto hardware (OpenSSL engine).
             When compiled with PKCS#11 support it defaults to "pkcs11".
-          
    
-        
    
+          
    
 
    -l label
    
-
    
-          
    
+
    
             Specifies the label of the key pair in the crypto hardware.
             The label may be preceded by an optional OpenSSL engine name,
             separated by a colon, as in "pkcs11:keylabel".
-          
    
-        
    
+          
    
 
    -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
 	    will include the key's creation date in the metadata stored
@@ -178,71 +127,53 @@
 	    (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.
-          
    
-        
    
+          
    
 
    -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
@@ -250,47 +181,35 @@
 	    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
@@ -301,53 +220,42 @@
       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
@@ -356,83 +264,68 @@
             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
    
-    
-    
    
+
    
+
    
+
    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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-keygen.html b/doc/arm/man.dnssec-keygen.html
index 3dc4508cd6..de7dd26168 100644
--- a/doc/arm/man.dnssec-keygen.html
+++ b/doc/arm/man.dnssec-keygen.html
@@ -18,7 +18,7 @@
 
 
 dnssec-keygen
-
+
 
 
 
@@ -38,84 +38,36 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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,
@@ -125,26 +77,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
@@ -153,7 +105,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 (ZSK's) and 2048 bits for key signing keys (KSK's,
@@ -162,10 +114,9 @@
             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
@@ -173,22 +124,18 @@
             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
 	    will include the key's creation date in the metadata stored
@@ -196,69 +143,51 @@
 	    (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
    
-
    
-          
    
+
    
             Uses a crypto hardware (OpenSSL engine) for random number
             and, when supported, key generation. When compiled with PKCS#11
             support it defaults to pkcs11; the empty name resets it to
             no engine.
-          
    
-        
    
+          
    
 
    -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.
-          
    
-        
    
+          
    
 
    -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
@@ -267,20 +196,16 @@
             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
@@ -292,11 +217,9 @@
             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
@@ -306,11 +229,9 @@
             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
@@ -318,19 +239,16 @@
             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
@@ -342,36 +260,27 @@
             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
@@ -382,55 +291,44 @@
       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
@@ -439,51 +337,42 @@
             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
    
-    
-    
    
+
    
+
    
+
    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
@@ -491,61 +380,54 @@
       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
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-revoke.html b/doc/arm/man.dnssec-revoke.html
index e04e4e2c71..fd99811e35 100644
--- a/doc/arm/man.dnssec-revoke.html
+++ b/doc/arm/man.dnssec-revoke.html
@@ -18,7 +18,7 @@
 
 
 dnssec-revoke
-
+
 
 
 
@@ -38,119 +38,73 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-
-  
-
-  
    
+
    
 
    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
    
-
    
-          
    
+
    
             Use the given OpenSSL engine. When compiled with PKCS#11 support
             it defaults to pkcs11; the empty name resets it to no engine.
-          
    
-        
    
+          
    
 
    -f
    
-
    
-          
    
+
    
             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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-settime.html b/doc/arm/man.dnssec-settime.html
index b41413a063..098cef0546 100644
--- a/doc/arm/man.dnssec-settime.html
+++ b/doc/arm/man.dnssec-settime.html
@@ -18,7 +18,7 @@
 
 
 dnssec-settime
-
+
 
 
 
@@ -38,47 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
@@ -87,12 +59,12 @@
       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
       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.
@@ -101,16 +73,12 @@
       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
             fail when attempting to update a legacy key.  With this option,
@@ -119,17 +87,13 @@
             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
@@ -138,40 +102,29 @@
             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
    
-
    
-          
    
+
    
             Use the given OpenSSL engine. When compiled with PKCS#11 support
             it defaults to pkcs11; the empty name resets it to no engine.
-          
    
-        
    
+          
    
 
    
-  
    
-
-  
    
-
    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
@@ -181,51 +134,39 @@
       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
@@ -233,11 +174,10 @@
             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
@@ -246,40 +186,34 @@
             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
    
-    
-    
    
+
    
+
    
+
    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:
@@ -290,25 +224,17 @@
             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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.dnssec-signzone.html b/doc/arm/man.dnssec-signzone.html
index be7b491b9a..493c6dccdc 100644
--- a/doc/arm/man.dnssec-signzone.html
+++ b/doc/arm/man.dnssec-signzone.html
@@ -18,7 +18,7 @@
 
 
 dnssec-signzone
-
+
 
 
 
@@ -38,72 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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]
-       [-i interval]
-       [-I input-format]
-       [-j jitter]
-       [-N soa-serial-format]
-       [-o origin]
-       [-O output-format]
-       [-P]
-       [-p]
-       [-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] [-i interval] [-I input-format] [-j jitter] [-N soa-serial-format] [-o origin] [-O output-format] [-P] [-p] [-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
@@ -111,46 +58,34 @@
       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.
-          
    
-        
    
+          
    
 
    -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,
 	    NSEC3 and NSEC3PARAM records. If smart signing
@@ -159,49 +94,37 @@
 	    zone file with $INCLUDE. This option
 	    cannot be combined with -O raw or serial
 	    number updating.
-          
    
-        
    
+          
    
 
    -E engine
    
-
    
-          
    
+
    
             Uses a crypto hardware (OpenSSL engine) for the crypto operations
             it supports, for instance signing with private keys from
             a secure key store. When compiled with PKCS#11 support
             it defaults to pkcs11; the empty name resets it to no engine.
-          
    
-        
    
+          
    
 
    -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.
-          
    
-        
    
+          
    
 
    -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
@@ -210,11 +133,9 @@
             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
@@ -224,11 +145,10 @@
             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
@@ -236,7 +156,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
@@ -247,34 +167,28 @@
             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.
-          
    
-        
    
+          
    
 
    -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
@@ -282,7 +196,7 @@
             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
@@ -293,10 +207,9 @@
             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)
 	    and "raw".
@@ -305,11 +218,10 @@
             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.
@@ -320,66 +232,51 @@
             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' 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" and
 	    "unixtime".
           
    
-
-          
    
+
    
 
    "keep"
    
-
    
-                
    Do not modify the SOA serial number.
    
-	      
    
+
    Do not modify the SOA serial number.
    
 
    "increment"
    
-
    
-                
    Increment the SOA serial number using RFC 1982
-                      arithmetics.
    
-	      
    
+
    Increment the SOA serial number using RFC 1982
+                      arithmetics.
    
 
    "unixtime"
    
-
    
-                
    Set the SOA serial number to the number of seconds
-	        since epoch.
    
-	      
    
+
    Set the SOA serial number to the number of seconds
+	        since epoch.
    
 
    
-
-        
    
+
 
    -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)
 	    "full", which is text output in a
@@ -391,36 +288,33 @@
             is 0, the raw file can be read by 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 
@@ -432,23 +326,22 @@
             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
             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
@@ -458,65 +351,53 @@
             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
             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
@@ -528,102 +409,81 @@
             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
             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.)
-          
    
-        
    
+          
    
 
    -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.)
-          
    
-        
    
+          
    
 
    -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
@@ -636,13 +496,13 @@
 Kexample.com.+003+17247
 db.example.com.signed
 %
    
-    
    
+
    
       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.
     
    
@@ -650,19 +510,14 @@ 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.
     
    
-  
    
-
+
 
 
    
 
    
diff --git a/doc/arm/man.dnssec-verify.html b/doc/arm/man.dnssec-verify.html
index 309c3cf88f..046b5f5f75 100644
--- a/doc/arm/man.dnssec-verify.html
+++ b/doc/arm/man.dnssec-verify.html
@@ -18,7 +18,7 @@
 
 
 dnssec-verify
-
+
 
 
 
@@ -38,63 +38,33 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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.
-          
    
-        
    
+          
    
 
    -I input-format
    
-
    
-          
    
+
    
             The format of the input zone file.
 	    Possible formats are "text" (default)
 	    and "raw".
@@ -103,41 +73,32 @@
             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.
-          
    
-        
    
+          
    
 
    -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
@@ -145,7 +106,7 @@
 	    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
@@ -154,28 +115,21 @@
             for both purposes.  This corresponds to the -z
             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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.genrandom.html b/doc/arm/man.genrandom.html
index 34d6ce0997..52164fe318 100644
--- a/doc/arm/man.genrandom.html
+++ b/doc/arm/man.genrandom.html
@@ -18,7 +18,7 @@
 
 
 genrandom
-
+
 
 
 
@@ -38,83 +38,50 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    genrandom
-     — generate a file containing random data
-  
    
+
    genrandom — generate a file containing random data
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      genrandom 
-       [-n number]
-       {size}
-       {filename}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    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)
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.host.html b/doc/arm/man.host.html
index c1a94a984f..8f7027b3e8 100644
--- a/doc/arm/man.host.html
+++ b/doc/arm/man.host.html
@@ -18,7 +18,7 @@
 
 
 host
-
+
 
 
 
@@ -38,56 +38,26 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
       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
@@ -99,14 +69,12 @@
       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
       a query of type ANY.
     
    
-
-    
    
+
    
       When the -C option is used, host
       will attempt to display the SOA records for zone
       name from all the listed
@@ -114,15 +82,13 @@
       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
       the
       -d or -v option is used.  The two
@@ -131,8 +97,7 @@
       switched on debugging traces and -v enabled verbose
       output.
     
    
-
-    
    
+
    
       List mode is selected by the -l option.  This makes
       host perform a zone transfer for zone
       name.  Transfer the zone printing out
@@ -140,15 +105,13 @@
       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
@@ -160,8 +123,7 @@
       or domain directive in
       /etc/resolv.conf.
     
    
-
-    
    
+
    
       The number of UDP retries for a lookup can be changed with the
       -R option.  number
       indicates
@@ -172,8 +134,7 @@
       number of
       retries will default to 1.
     
    
-
-    
    
+
    
       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.
@@ -185,22 +146,19 @@
       expecting to receive answers to those queries that are usually
       referrals to other name servers.
     
    
-
-    
    
+
    
       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
       use IPv4 query transport.  The -6 option forces
       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,
@@ -216,8 +174,7 @@
       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
@@ -230,31 +187,26 @@
       will be set to the number of seconds given by the hardware's maximum
       value for an integer quantity.
     
    
-
-    
    
+
    
       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
       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. 
       host appropriately converts character encoding of
@@ -265,27 +217,18 @@
       The IDN support is disabled if the variable is set when
       host runs.
     
    
-  
    
-
-  
    
-
    FILES
    
-
-    
    /etc/resolv.conf
+
    
+
    
+
    FILES
    
+
    /etc/resolv.conf
     
    
-  
    
-
-  
    
-
    SEE ALSO
    
-
-    
    
-        dig(1)
-      ,
-      
-        named(8)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    dig(1),
+      named(8).
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.isc-hmac-fixup.html b/doc/arm/man.isc-hmac-fixup.html
index 029bb85100..b8a80a1839 100644
--- a/doc/arm/man.isc-hmac-fixup.html
+++ b/doc/arm/man.isc-hmac-fixup.html
@@ -18,7 +18,7 @@
 
 
 isc-hmac-fixup
-
+
 
 
 
@@ -38,36 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    isc-hmac-fixup
-     — fixes HMAC keys generated by older versions of BIND
-  
    
+
    isc-hmac-fixup — fixes HMAC keys generated by older versions of BIND
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      isc-hmac-fixup 
-       {algorithm}
-       {secret}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    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
@@ -75,13 +58,13 @@
       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
       modifies those keys to restore compatibility.
     
    
-    
    
+
    
       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
@@ -90,12 +73,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
       operation anyway, it does not affect security.  RFC 2104 notes,
@@ -103,17 +84,14 @@
       extra length would not significantly increase the function
       strength."
     
    
-  
    
-
-  
    
-
    SEE ALSO
    
-    
-    
    
+
    
+
    
+
    SEE ALSO
    
+
    
       BIND 9 Administrator Reference Manual,
       RFC 2104.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.lwresd.html b/doc/arm/man.lwresd.html
index cb8c3ed431..112724eb2e 100644
--- a/doc/arm/man.lwresd.html
+++ b/doc/arm/man.lwresd.html
@@ -18,7 +18,7 @@
 
 
 lwresd
-
+
 
 
 
@@ -38,59 +38,26 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
@@ -98,14 +65,14 @@
       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 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
       sends recursive DNS queries to those servers.  This is similar
@@ -115,80 +82,60 @@
       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
             		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,
@@ -197,61 +144,54 @@
             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
             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
@@ -259,62 +199,40 @@
               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).
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.named-checkconf.html b/doc/arm/man.named-checkconf.html
index 0aa77fc2a3..e3834645da 100644
--- a/doc/arm/man.named-checkconf.html
+++ b/doc/arm/man.named-checkconf.html
@@ -18,7 +18,7 @@
 
 
 named-checkconf
-
+
 
 
 
@@ -38,49 +38,26 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
 
    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
       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
       parser contexts, such as rndc.key and
       bind.keys, are not automatically read
@@ -90,44 +67,32 @@
       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.
-          
    
-        
    
+          
    
 
    -v
    
-
    
-          
    
+
    
             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
@@ -135,53 +100,37 @@
             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.
     
    
-  
    
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.named-checkzone.html b/doc/arm/man.named-checkzone.html
index 1b189b5f5a..cd479deae3 100644
--- a/doc/arm/man.named-checkzone.html
+++ b/doc/arm/man.named-checkzone.html
@@ -18,7 +18,7 @@
 
 
 named-checkzone
-
+
 
 
 
@@ -38,92 +38,26 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
 
    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]
-       [-i mode]
-       [-k mode]
-       [-m mode]
-       [-M mode]
-       [-n mode]
-       [-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]
-       [-i mode]
-       [-k mode]
-       [-m mode]
-       [-n mode]
-       [-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] [-i mode] [-k mode] [-m mode] [-M mode] [-n mode] [-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] [-i mode] [-k mode] [-m mode] [-n mode] [-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
       checking zone files before configuring them into a name server.
     
    
-    
    
+
    
         named-compilezone is similar to
 	named-checkzone, but it always dumps the
         zone contents to a specified file in a specified format.
@@ -134,53 +68,38 @@
         least be as strict as those specified in the
 	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
             program and exit.
-          
    
-        
    
+          
    
 
    -j
    
-
    
-          
    
+
    
             When loading the zone file read the journal if it exists.
-          
    
-        
    
+          
    
 
    -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",
@@ -188,19 +107,19 @@
 	      "local-sibling" and
 	      "none".
 	  
    
-	  
    
+
    
 	      Mode "full" checks that MX records
 	      refer to A or AAAA record (both in-zone and out-of-zone
 	      hostnames).  Mode "local" only
 	      checks MX records which refer to in-zone hostnames.
 	  
    
-	  
    
+
    
 	      Mode "full" checks that SRV records
 	      refer to A or AAAA record (both in-zone and out-of-zone
 	      hostnames).  Mode "local" only
 	      checks SRV records which refer to in-zone hostnames.
 	  
    
-	  
    
+
    
 	      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
@@ -209,33 +128,31 @@
 	      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 "none" disables the checks.
 	  
    
-	
    
+
 
    -f format
    
-
    
-	  
    
+
    
 	    Specify the format of the zone file.
 	    Possible formats are "text" (default)
 	    and "raw".
-	  
    
-	
    
+	  
    
 
    -F format
    
 
    
-	  
    
+
    
 	    Specify the format of the output file specified.
 	    For named-checkzone,
 	    this does not cause any effects unless it dumps the zone
 	    contents.
 	  
    
-	  
    
+
    
 	    Possible formats are "text" (default)
 	    and "raw" or "raw=N",
             which store the zone in a binary format for rapid loading
@@ -245,10 +162,9 @@
             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
 	    specified failure mode.
             Possible modes are "fail"
@@ -256,37 +172,29 @@
             "warn"
 	    (default for named-checkzone) and
             "ignore".
-          
    
-        
    
+          
    
 
    -L serial
    
-
    
-          
    
+
    
             When compiling a zone to 'raw' 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".
-          
    
-        
    
+          
    
 
    -M mode
    
-
    
-	  
    
+
    
 	    Check if a MX record refers to a CNAME.
             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"
@@ -294,30 +202,24 @@
             "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.
-          
    
-        
    
+          
    
 
    -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".
-	  
    
-        
    
+	  
    
 
    -s style
    
-
    
-	  
    
+
    
 	    Specify the style of the dumped zone file.
 	    Possible styles are "full" (default)
 	    and "relative".
@@ -330,102 +232,75 @@
 	    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".
-	  
    
-        
    
+	  
    
 
    -t directory
    
-
    
-          
    
+
    
             Chroot to directory so that
             include
             directives in the configuration file are processed as if
             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".
-	  
    
-	
    
+	  
    
 
    -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.
-          
    
-        
    
+          
    
 
    -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)
             and
             "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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.named-journalprint.html b/doc/arm/man.named-journalprint.html
index c585947985..4b17dbb28a 100644
--- a/doc/arm/man.named-journalprint.html
+++ b/doc/arm/man.named-journalprint.html
@@ -18,7 +18,7 @@
 
 
 named-journalprint
-
+
 
 
 
@@ -38,40 +38,24 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    named-journalprint
-     — print zone journal in human-readable form
-  
    
+
    named-journalprint — print zone journal in human-readable form
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      named-journalprint 
-       {journal}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    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 
       when changes are made to dynamic zones (e.g., by
       nsupdate).  They record each addition
@@ -82,29 +66,22 @@
       .jnl to the name of the corresponding
       zone file.
     
    
-    
    
+
    
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.named.conf.html b/doc/arm/man.named.conf.html
index 1d53ee48a8..f5a93b0206 100644
--- a/doc/arm/man.named.conf.html
+++ b/doc/arm/man.named.conf.html
@@ -18,7 +18,7 @@
 
 
 named.conf
-
+
 
 
 
@@ -38,86 +38,63 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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
       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;
    
@@ -136,32 +113,26 @@ 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 | * ) ]
    
@@ -170,12 +141,10 @@ controls
 	unix unsupported; // not implemented
    
 };
    
 
    
-  
    
-
-  
    
-
    LOGGING
    
-    
-    

    
+
    
+
    
+
    LOGGING
    
+

    
 logging {
    
 	channel string {
    
 		file log_file;
    
@@ -190,12 +159,10 @@ logging
 	category string { string; ... };
    
 };
    
 
    
-  
    
-
-  
    
-
    LWRES
    
-    
-    

    
+
    
+
    
+
    LWRES
    
+

    
 lwres {
    
 	listen-on [ port integer ] {
    
 		( ipv4_address | ipv6_address ) [ port integer ]; ...
    
@@ -205,12 +172,10 @@ lwres
 	ndots integer;
    
 };
    
 
    
-  
    
-
-  
    
-
    OPTIONS
    
-    
-    

    
+
    
+
    
+
    OPTIONS
    
+

    
 options {
    
 	avoid-v4-udp-ports { port; ... };
    
 	avoid-v6-udp-ports { port; ... };
    
@@ -412,12 +377,10 @@ options
 	use-id-pool boolean; // obsolete
    
 };
    
 
    
-  
    
-
-  
    
-
    VIEW
    
-    
-    

    
+
    
+
    
+
    VIEW
    
+

    
 view string optional_class {
    
 	match-clients { address_match_element; ... };
    
 	match-destinations { address_match_element; ... };
    
@@ -578,12 +541,10 @@ view
 	max-ixfr-log-size size; // obsolete
    
 };
    
 
    
-  
    
-
-  
    
-
    ZONE
    
-    
-    

    
+
    
+
    
+
    ZONE
    
+

    
 zone string optional_class {
    
 	type ( master | slave | stub | hint | redirect |
    
 		forward | delegation-only );
    
@@ -677,31 +638,20 @@ 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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.named.html b/doc/arm/man.named.html
index cea724553a..063a1a27c7 100644
--- a/doc/arm/man.named.html
+++ b/doc/arm/man.named.html
@@ -18,7 +18,7 @@
 
 
 named
-
+
 
 
 
@@ -38,90 +38,48 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    named
-     — Internet domain name server
-  
    
+
    named — Internet domain name server
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      named 
-       [-4]
-       [-6]
-       [-c config-file]
-       [-d debug-level]
-       [-E engine-name]
-       [-f]
-       [-g]
-       [-M option]
-       [-m flag]
-       [-n #cpus]
-       [-p port]
-       [-s]
-       [-S #max-socks]
-       [-t directory]
-       [-U #listeners]
-       [-u user]
-       [-v]
-       [-V]
-       [-x cache-file]
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    named
+
    named  [-4] [-6] [-c config-file] [-d debug-level] [-E engine-name] [-f] [-g] [-M option] [-m flag] [-n #cpus] [-p port] [-s] [-S #max-socks] [-t directory] [-U #listeners] [-u user] [-v] [-V] [-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
       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
@@ -131,52 +89,40 @@
             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
             more verbose as the debug level increases.
-          
    
-        
    
+          
    
 
    -E engine-name
    
-
    
-          
    
+
    
             Use a crypto hardware (OpenSSL engine) for the crypto operations
             it supports, for instance re-signing with private keys from
             a secure key store. When compiled with PKCS#11 support
             engine-name
             defaults to pkcs11, the empty name resets it to no engine.
-          
    
-        
    
+          
    
 
    -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.
-          
    
-        
    
+          
    
 
    -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.
-          
    
-        
    
+          
    
 
    -m flag
    
-
    
-          
    
+
    
 	    Turn on memory usage debugging flags.  Possible flags are
 	    usage,
 	    trace,
@@ -185,48 +131,43 @@
 	    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
             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.
 	  
    
-          
    
+
    
 
    Warning
    
-            
    
+
    
               This option should be unnecessary for the vast majority
               of users.
 	      The use of this option could even be harmful because the
@@ -241,18 +182,18 @@
 	      named reserves some file descriptors
 	      for its internal use.
             
    
-          
    
-	
    
+
    
+
 
    -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
@@ -260,11 +201,10 @@
               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
@@ -277,18 +217,17 @@
             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
+
    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
               except the ability to bind(2) to
@@ -301,80 +240,63 @@
               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 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
       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
    
-    
-    
    
+
    
+
    
+
    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
       (file creation mode mask) from the parent process. If files
       created by named, such as journal files,
@@ -382,60 +304,33 @@
       should be set explicitly in the script used to start the
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.nsec3hash.html b/doc/arm/man.nsec3hash.html
index 94efbb213e..cac5a66f98 100644
--- a/doc/arm/man.nsec3hash.html
+++ b/doc/arm/man.nsec3hash.html
@@ -18,7 +18,7 @@
 
 
 nsec3hash
-
+
 
 
 
@@ -36,87 +36,55 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    nsec3hash
-     — generate NSEC3 hash
-  
    
+
    nsec3hash — generate NSEC3 hash
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      nsec3hash 
-       {salt}
-       {algorithm}
-       {iterations}
-       {domain}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.nsupdate.html b/doc/arm/man.nsupdate.html
index d7ddf19a68..7fc8b3ed69 100644
--- a/doc/arm/man.nsupdate.html
+++ b/doc/arm/man.nsupdate.html
@@ -18,7 +18,7 @@
 
 
 nsupdate
-
+
 
 
 
@@ -38,49 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-  
-  
    
+
    
 
    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]
-       [-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] [-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
@@ -89,27 +59,27 @@
       one
       resource record.
     
    
-    
    
+
    
       Zones that are under dynamic control via
       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
       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.
@@ -124,41 +94,33 @@
       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
@@ -170,11 +132,9 @@
 	    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
 	    address cannot be overridden).  Connections to the local server will
@@ -183,31 +143,23 @@
 	    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.
-	  
    
-	
    
+	  
    
 
    -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
@@ -216,43 +168,34 @@
 	  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.
-	  
    
-	
    
+	  
    
 
    -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
 	    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.
@@ -263,23 +206,19 @@
 	    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.
@@ -293,7 +232,7 @@
       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
@@ -303,17 +242,16 @@
       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
 	       {servername}
 	       [port]
 	    
    
-
    
-	    
    
+
    
 	      Sends all dynamic update requests to the name server
 	      servername.
 	      When no server statement is provided,
@@ -329,15 +267,13 @@
 	      If no port number is specified, the default DNS port number of
 	      53 is
 	      used.
-	    
    
-	  
    
+	    
    
 
    
 	      local
 	       {address}
 	       [port]
 	    
    
-
    
-	    
    
+
    
 	      Sends all dynamic update requests using the local
 	      address.
 
@@ -349,14 +285,12 @@
 	      can additionally be used to make requests come from a specific
 	      port.
 	      If no port number is specified, the system will assign one.
-	    
    
-	  
    
+	    
    
 
    
 	      zone
 	       {zonename}
 	    
    
-
    
-	    
    
+
    
 	      Specifies that all updates are to be made to the zone
 	      zonename.
 	      If no
@@ -365,38 +299,32 @@
 	      nsupdate
 	      will attempt determine the correct zone to update based on the
 	      rest of the input.
-	    
    
-	  
    
+	    
    
 
    
 	      class
 	       {classname}
 	    
    
-
    
-	    
    
+
    
 	      Specify the default class.
 	      If no class is specified, the
 	      default class is
 	      IN.
-	    
    
-	  
    
+	    
    
 
    
 	      ttl
 	       {seconds}
 	    
    
-
    
-	    
    
+
    
 	      Specify the default time to live for records to be added.
 	      The value none will clear the default
 	      ttl.
-	    
    
-	  
    
+	    
    
 
    
 	      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
@@ -404,67 +332,55 @@
 	      hmac-md5.  The key
 	      command overrides any key specified on the command line via
 	      -y or -k.
-	    
    
-	  
    
+	    
    
 
    
 	    gsstsig
 	  
    
-
    
-	    
    
+
    
 	      Use GSS-TSIG to sign the updated.  This is equivalent to
 	      specifying -g on the commandline.
-	    
    
-	  
    
+	    
    
 
    
 	    oldgsstsig
 	  
    
-
    
-	    
    
+
    
 	      Use the Windows 2000 version of GSS-TSIG to sign the updated.
 	      This is equivalent to specifying -o on the
 	      commandline.
-	    
    
-	  
    
+	    
    
 
    
 	    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.
-	    
    
-	  
    
+	    
    
 
    
 	      [prereq] nxdomain
 	       {domain-name}
 	    
    
-
    
-	    
    
+
    
 	      Requires that no resource record of any type exists with name
 	      domain-name.
-	    
    
-	  
    
+	    
    
 
    
 	      [prereq] yxdomain
 	       {domain-name}
 	    
    
-
    
-	    
    
+
    
 	      Requires that
 	      domain-name
 	      exists (has as at least one resource record, of any type).
-	    
    
-	  
    
+	    
    
 
    
 	      [prereq] nxrrset
 	       {domain-name}
 	       [class]
 	       {type}
 	    
    
-
    
-	    
    
+
    
 	      Requires that no resource record exists of the specified
 	      type,
 	      class
@@ -473,16 +389,14 @@
 	      If
 	      class
 	      is omitted, IN (internet) is assumed.
-	    
    
-	  
    
+	    
    
 
    
 	      [prereq] yxrrset
 	       {domain-name}
 	       [class]
 	       {type}
 	    
    
-
    
-	    
    
+
    
 	      This requires that a resource record of the specified
 	      type,
 	      class
@@ -492,8 +406,7 @@
 	      If
 	      class
 	      is omitted, IN (internet) is assumed.
-	    
    
-	  
    
+	    
    
 
    
 	      [prereq] yxrrset
 	       {domain-name}
@@ -501,8 +414,7 @@
 	       {type}
 	       {data...}
 	    
    
-
    
-	    
    
+
    
 	      The
 	      data
 	      from each set of prerequisites of this form
@@ -523,8 +435,7 @@
 	      are written in the standard text representation of the resource
 	      record's
 	      RDATA.
-	    
    
-	  
    
+	    
    
 
    
 	      [update] del[ete]
 	       {domain-name}
@@ -532,8 +443,7 @@
 	       [class]
 	       [type [data...]]
 	    
    
-
    
-	    
    
+
    
 	      Deletes any resource records named
 	      domain-name.
 	      If
@@ -546,8 +456,7 @@
 	      is not supplied.  The
 	      ttl
 	      is ignored, and is only allowed for compatibility.
-	    
    
-	  
    
+	    
    
 
    
 	      [update] add
 	       {domain-name}
@@ -556,80 +465,62 @@
 	       {type}
 	       {data...}
 	    
    
-
    
-	    
    
+
    
 	      Adds a new resource record with the specified
 	      ttl,
 	      class
 	      and
 	      data.
-	    
    
-	  
    
+	    
    
 
    
 	      show
 	    
    
-
    
-	    
    
+
    
 	      Displays the current message, containing all of the
 	      prerequisites and
 	      updates specified since the last send.
-	    
    
-	  
    
+	    
    
 
    
 	      send
 	    
    
-
    
-	    
    
+
    
 	      Sends the current message.  This is equivalent to entering a
 	      blank line.
-	    
    
-	  
    
+	    
    
 
    
 	      answer
 	    
    
-
    
-	    
    
+
    
 	      Displays the answer.
-	    
    
-	  
    
+	    
    
 
    
 	      debug
 	    
    
-
    
-	    
    
+
    
 	      Turn on debugging.
-	    
    
-	  
    
+	    
    
 
    
 	      version
 	    
    
-
    
-	    
    
+
    
 	      Print version number.
-	    
    
-	  
    
+	    
    
 
    
 	      help
 	    
    
-
    
-	    
    
+
    
 	      Print a list of commands.
-	    
    
-	  
    
+	    
    
 
    
 
    
     
    
-
-    
    
+
    
       Lines beginning with a semicolon are comments and are ignored.
     
    
-
-  
    
-
-  
    
-
    EXAMPLES
    
-    
-    
    
+
    
+
    
+
    EXAMPLES
    
+
    
       The examples below show how
       nsupdate
       could be used to insert and delete resource records from the
@@ -650,7 +541,7 @@
 
    
 
    
     
    
-    
    
+
    
       Any A records for
       oldhost.example.com
       are deleted.
@@ -667,7 +558,7 @@
 
    
 
    
     
    
-    
    
+
    
       The prerequisite condition gets the name server to check that there
       are no resource records of any type for
       nickname.example.com.
@@ -680,50 +571,33 @@
       (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,
@@ -731,28 +605,20 @@
       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.
     
    
-  
    
+
    
 
 
    
 
    
diff --git a/doc/arm/man.rndc-confgen.html b/doc/arm/man.rndc-confgen.html
index 993793f9fe..0bd9a81521 100644
--- a/doc/arm/man.rndc-confgen.html
+++ b/doc/arm/man.rndc-confgen.html
@@ -18,7 +18,7 @@
 
 
 rndc-confgen
-
+
 
 
 
@@ -38,44 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    rndc-confgen
-     — rndc key generation tool
-  
    
+
    rndc-confgen — rndc key generation tool
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      rndc-confgen 
-       [-a]
-       [-b keysize]
-       [-c keyfile]
-       [-h]
-       [-k keyname]
-       [-p port]
-       [-r randomfile]
-       [-s address]
-       [-t chrootdir]
-       [-u user]
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    rndc-confgen
+
    rndc-confgen  [-a] [-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
       convenient alternative to writing the
@@ -88,17 +63,13 @@
       avoid the need for a rndc.conf file
       and a controls statement altogether.
     
    
-
-  
    
-
-  
    
-
    OPTIONS
    
-    
-
-    
    
+
    
+
    
+
    OPTIONS
    
+
    
 
    -a
    
 
    
-          
    
+
    
             Do automatic rndc configuration.
             This creates a file rndc.key
             in /etc (or whatever
@@ -113,7 +84,7 @@
             named on the local host
             with no further configuration.
           
    
-          
    
+
    
             Running rndc-confgen -a allows
             BIND 9 and rndc to be used as
             drop-in
@@ -121,7 +92,7 @@
             with no changes to the existing BIND 8
             named.conf file.
           
    
-          
    
+
    
             If a more elaborate configuration than that
             generated by rndc-confgen -a
             is required, for example if rndc is to be used remotely,
@@ -132,47 +103,36 @@
             named.conf
             as directed.
           
    
-        
    
+
 
    -b keysize
    
-
    
-          
    
+
    
             Specifies the size of the authentication key in bits.
             Must be between 1 and 512 bits; the default is 128.
-          
    
-        
    
+          
    
 
    -c keyfile
    
-
    
-          
    
+
    
             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.
-          
    
-        
    
+          
    
 
    -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.
             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
@@ -183,30 +143,24 @@
             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
             listens for command channel connections from
             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
             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.
-          
    
-        
    
+          
    
 
    -u user
    
-
    
-          
    
+
    
             Used with the -a option to set the
             owner
             of the rndc.key file generated.
@@ -214,46 +168,34 @@
             -t is also specified only the file
             in
             the chroot area has its owner changed.
-          
    
-        
    
+          
    
 
    
-  
    
-
-  
    
-
    EXAMPLES
    
-    
-    
    
+
    
+
    
+
    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
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.rndc.conf.html b/doc/arm/man.rndc.conf.html
index cc44735a7e..2652368182 100644
--- a/doc/arm/man.rndc.conf.html
+++ b/doc/arm/man.rndc.conf.html
@@ -18,7 +18,7 @@
 
 
 rndc.conf
-
+
 
 
 
@@ -38,34 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    rndc.conf
-     — rndc configuration file
-  
    
+
    rndc.conf — rndc configuration file
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      rndc.conf 
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    rndc.conf is the configuration file
+
    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
@@ -73,21 +58,21 @@
       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
@@ -110,7 +95,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:
@@ -124,7 +109,7 @@
       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 encryption algorithm
@@ -134,7 +119,7 @@
       the base-64 encoding of the algorithm's encryption 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
       can
@@ -147,13 +132,10 @@
       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;
@@ -161,14 +143,14 @@
 
    
 
    
     
    
-    
    +
           server localhost {
         key             samplekey;
       };
 
    
 
    
     
    
-    
    +
           server testserver {
         key		testkey;
         addresses	{ localhost port 5353; };
@@ -176,7 +158,7 @@
 
    
 
    
     
    
-    
    +
           key samplekey {
         algorithm       hmac-md5;
         secret          "6FMfj43Osz4lyb24OIe2iGEz9lf1llJO+lz";
@@ -184,7 +166,7 @@
 
    
 
    
     
    
-    
    +
           key testkey {
         algorithm	hmac-md5;
         secret		"R3HI8P6BKw9ZwXwN3VZKuQ==";
@@ -192,8 +174,7 @@
     
    
 
    
     
    
-
-    
    
+
    
       In the above example, rndc will by
       default use
       the server at localhost (127.0.0.1) and the key called samplekey.
@@ -203,16 +184,16 @@
       uses the HMAC-MD5 algorithm and its secret clause contains the
       base-64 encoding of the HMAC-MD5 secret enclosed in double quotes.
     
    
-    
    
+
    
       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:
     
    
-    
    rndc-confgen
+
    rndc-confgen
     
    
-    
    
+
    
       A complete rndc.conf file, including
       the
       randomly generated key, will be written to the standard
@@ -220,41 +201,30 @@
       controls statements for
       named.conf are also printed.
     
    
-    
    
+
    
       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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/man.rndc.html b/doc/arm/man.rndc.html
index 579b6c77b2..fe05ca764c 100644
--- a/doc/arm/man.rndc.html
+++ b/doc/arm/man.rndc.html
@@ -18,7 +18,7 @@
 
 
 rndc
-
+
 
 
 
@@ -38,42 +38,19 @@
 
 
    
 
    
-
    
+
    
 
    
-  
-  
-
-  
-
-  
    
+
    
 
    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]
-       [-V]
-       [-y key_id]
-       {command}
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    rndc
+
    rndc  [-b source-address] [-c config-file] [-k key-file] [-s server] [-p port] [-V] [-y key_id] {command}
    
+
    
+
    
+
    DESCRIPTION
    
+
    rndc
       controls the operation of a name
       server.  It supersedes the ndc utility
       that was provided in old BIND releases.  If
@@ -82,7 +59,7 @@
       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
@@ -94,38 +71,30 @@
       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
@@ -133,37 +102,29 @@
 	    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
 	    command line, the host named by the default-server clause
 	    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.
-	  
    
-	
    
+	  
    
 
    -V
    
-
    
-	  
    
+
    
 	    Enable verbose logging.
-	  
    
-	
    
+	  
    
 
    -y key_id
    
-
    
-	  
    
+
    
 	    Use the key key_id
 	    from the configuration file.
 	    key_id
@@ -179,26 +140,22 @@
 	    which are used to send authenticated control commands
 	    to name servers.  It should therefore not have general read
 	    or write access.
-	  
    
-	
    
+	  
    
 
    
-  
    
-
-  
    
-
    COMMANDS
    
-    
-    
    
+
    
+
    
+
    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
@@ -208,7 +165,7 @@
 	    configuration text that would ordinarily be
 	    placed in named.conf.
 	  
    
-	  
    
+
    
 	    The configuration is saved in a file called
 	   hash.nzf,
 	    where hash is a
@@ -218,37 +175,36 @@
 	    configuration, so that zones that were added
 	    can persist after a restart.
 	  
    
-	  
    
+
    
 	    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.
 	  
    
-	
    
+
 
    delzone zone [class [view]] 
    
 
    
-	  
    
+
    
 	    Delete a zone while the server is running.
 	    Only zones that were originally added via
 	    rndc addzone can be deleted
 	    in this manner. 
 	  
    
-	  
    
+
    
 	    See also rndc addzone
 	  
    
-	
    
+
 
    dumpdb [-all|-cache|-zone|-adb|-bad] [view ...]
    
-
    
-	  
    
+
    
 	    Dump the server's caches (default) and/or zones to
 	    the
 	    dump file for the specified views.  If no view is
@@ -256,34 +212,27 @@
 	    views are dumped.
 	    (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 or bad-server cache.
-	  
    
-	
    
+	  
    
 
    flushtree name [view] 
    
-
    
-	  
    
+
    
 	    Flushes the given name, and all of its subdomains,
 	    from the view's DNS cache.  Note that this does
 	    not affect he server's address
 	    database or bad-server 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
@@ -292,13 +241,13 @@
 	    All dynamic update attempts will be refused while
 	    the zone is frozen.
 	  
    
-	  
    
+
    
 	    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
@@ -307,13 +256,13 @@
 	    This allows an external process to determine when named
 	    had completed halting.
 	  
    
-	  
    
+
    
 	    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
@@ -322,7 +271,7 @@
 	    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
 	    be set to maintain,
@@ -331,30 +280,28 @@
 	    (See "Dynamic Update Policies" in the Administrator
 	    Reference Manual for more details.)
 	  
    
-	
    
+
 
    notify zone [class [view]]
    
-
    
-	  
    
+
    
 	    Resend NOTIFY messages for the zone.
-	  
    
-	
    
+	  
    
 
    notrace
    
 
    
-	  
    
+
    
 	    Sets the server's debugging level to 0.
 	  
    
-	  
    
+
    
 	    See also rndc trace.
 	  
    
-	
    
+
 
    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
@@ -365,10 +312,9 @@
 	    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.
@@ -376,43 +322,34 @@
 	    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
             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
 	    version of the zone is discarded; after the
@@ -420,19 +357,17 @@
 	    signed version will be regenerated with all new
 	    signatures.
 	  
    
-	
    
+
 
    secroots [view ...]
    
-
    
-	  
    
+
    
 	    Dump the server's security roots to the secroots
 	    file for the specified views.  If no view is
 	    specified, security roots for all
 	    views are dumped.
-	  
    
-	
    
+	  
    
 
    sign zone [class [view]]
    
 
    
-	  
    
+
    
 	    Fetch all DNSSEC keys for the given zone
 	    from the key directory (see the 
 	    key-directory option in
@@ -442,7 +377,7 @@
 	    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
 	    to allow or
@@ -452,13 +387,13 @@
 	    (See "Dynamic Update Policies" in the Administrator
 	    Reference Manual for more details.)
 	  
    
-	  
    
+
    
 	    See also rndc loadkeys.
 	  
    
-	
    
+
 
    signing [( -list | -clear keyid/algorithm | -clear all | -nsec3param ( parameters | none ) ) ] 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
@@ -471,7 +406,7 @@
 	    or have finished signing the zone, and which NSEC3
 	    chains are being created or removed.
 	  
    
-	  
    
+
    
 	    rndc signing -clear can remove
 	    a single key (specified in the same format that
 	    rndc signing -list uses to
@@ -480,7 +415,7 @@
 	    that a key has not yet finished signing the zone
 	    will be retained.
 	  
    
-	  
    
+
    
 	    rndc signing -nsec3param sets
 	    the NSEC3 parameters for a zone.  This is the
 	    only supported mechanism for using NSEC3 with
@@ -489,7 +424,7 @@
 	    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
@@ -502,7 +437,7 @@
 	    in hexadecimal, or a hyphen (`-') if no salt is
 	    to be used.
 	  
    
-	  
    
+
    
 	    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:
@@ -511,33 +446,29 @@
 	    salt, use:
 	    rndc signing -nsec3param 1 1 15 - zone.
 	  
    
-	  
    
+
    
 	    rndc signing -nsec3param none
 	    removes an existing NSEC3 chain and replaces it
 	    with NSEC.
 	  
    
-	
    
+
 
    stats
    
-
    
-	  
    
+
    
 	    Write server statistics to the statistics file.
 	    (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
 	    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.
@@ -545,20 +476,18 @@
 	    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
@@ -572,89 +501,66 @@
 	    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.
 	  
    
-	
    
+
 
    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
 	    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
 	    set to yes or
 	    auto to be effective.
 	    It defaults to enabled.
-	  
    
-	
    
+	  
    
 
    
-  
    
-
-  
    
-
    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.
     
    
-  
    
-
+
    
 
    
 
    
 
    
diff --git a/doc/arm/notes.html b/doc/arm/notes.html
index 0a63fac958..8bf8d1d385 100644
--- a/doc/arm/notes.html
+++ b/doc/arm/notes.html
@@ -17,87 +17,77 @@
 
 
 
-
+
 
-
    
-  
-  
    
-
    
-Release Notes for BIND Version 9.9.8
    
-  
-  
    
+
    
+
    
+<title>Release Notes for BIND Version 9.9.8</title>
    
 
    
 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/.
+      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]
 	
        
-      
        • 
+
 
      
-  
    
-  
    
+
    
+
    
 
    
 New Features
    
-    
-    
      
+
        
 
      • 
-	
        
+
        
 	  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,
@@ -106,14 +96,13 @@
 	  experienced by recursives when they are being used as a
 	  vehicle for such an attack.
 	
        
-	
        
+
        
 	  NOTE: These options are not available by default; use
 	  configure --enable-fetchlimit to include
 	  them in the build.
 	
        
-	
          
-
        • 
-	    
          
+
            
+
          • 
 	      fetches-per-server limits the number of
 	      simultaneous queries that can be sent to any single
 	      authoritative server.  The configured value is a starting
@@ -121,101 +110,77 @@
 	      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.
 	
          
-      
          • 
-
        • 
-	
          
+
          • 
+
        • 
 	  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]
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  The following types have been implemented: CSYNC, NINFO, RKEY,
 	  SINK, TA, TALINK.
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  EDNS COOKIE options content is now displayed as
 	  "COOKIE: <hexvalue>".
-	
          
-      
          • 
+	
          
 
        
-  
      
-  
      
+
      
+
      
 
      
 Feature Changes
      
-    
-    
        
-
      • 
-	
        
+
          
+
        • 
 	  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]
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  Retrieving the local port range from net.ipv4.ip_local_port_range
 	  on Linux is now supported.
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  Active Directory names of the form gc._msdcs.<forest> are
 	  now accepted as valid hostnames when using the
 	  check-names option. <forest> is still
 	  restricted to letters, digits and hyphens.
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  Names containing rich text are now accepted as valid
 	  hostnames in PTR records in DNS-SD reverse lookup zones,
 	  as specified in RFC 6763. [RT #37889]
-	
          
-      
          • 
-
        • 
-	
          
+	
          • 
+
        • 
 	  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
@@ -224,81 +189,62 @@
 	  previously compiled in the binary. Read
 	  win32utils/build.txt for more details.
 	  [RT #38915]
-	
          
-      
        
-  
      
-  
      
+	
    
+
    
+
    
 
    
 Bug Fixes
    
-    
-    
      
-
    • 
-	
      
+
        
+
      • 
 	  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]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  Malformed records of some types, including NSAP and UNSPEC,
 	  could trigger assertion failures when loading text zone files.
 	  [RT #40274] [RT #40285]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  Fixed a possible crash in ratelimiter.c caused by NOTIFY
 	  messages being removed from the wrong rate limiter queue.
 	  [RT #40350]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  The default rrset-order of random
 	  was inconsistently applied. [RT #40456]
-	
        
-      
        • 
-
      • 
-	
        
+	
        • 
+
      • 
 	  BADVERS responses from broken authoritative name servers were
 	  not handled correctly. [RT #40427]
-	
        
-      
        • 
+	
        
 
      
-  
    
-  
    
+
    
+
    
 
    
 End of Life
    
-    
-    
    
+
    
       The BIND 9.9 (Extended Support Version) will be supported until June, 2017.
-      https://www.isc.org/downloads/software-support-policy/
+      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/.
+      http://www.isc.org/donate/.
     
    
-  
    
 
    
-
    
+
    
 
diff --git a/isc-config.sh.1 b/isc-config.sh.1
index b8f23dcd7a..1d3e4be7c0 100644
--- a/isc-config.sh.1
+++ b/isc-config.sh.1
@@ -17,7 +17,7 @@
 '\" t
 .\"     Title: isc-config.sh
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2009-02-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -46,7 +46,7 @@
 .SH "NAME"
 isc-config.sh \- Get information about the installed version of ISC BIND
 .SH "SYNOPSIS"
-.HP 14
+.HP \w'\fBisc\-config\&.sh\fR\ 'u
 \fBisc\-config\&.sh\fR [\fB\-\-cflags\fR] [\fB\-\-exec\-prefix\fR] [\fB\-\-libs\fR] [\fB\-\-prefix\fR] [\fB\-\-version\fR] [libraries...]
 .SH "DESCRIPTION"
 .PP
diff --git a/isc-config.sh.html b/isc-config.sh.html
index 0b27b72f02..18eb130c93 100644
--- a/isc-config.sh.html
+++ b/isc-config.sh.html
@@ -18,47 +18,26 @@
 
 
 isc-config.sh
-
+
 
-
    
+
    
 
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
 
    Name
    
-
    
-    isc-config.sh
-     — Get information about the installed version of ISC BIND
-  
    
+
    isc-config.sh — Get information about the installed version of ISC BIND
    
 
    
-
-  
    
+
    
 
    Synopsis
    
-    
    
-      isc-config.sh 
-       [--cflags]
-       [--exec-prefix]
-       [--libs]
-       [--prefix]
-       [--version]
-       [libraries...]
-    
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    isc-config.sh
+
    isc-config.sh  [--cflags] [--exec-prefix] [--libs] [--prefix] [--version] [libraries...]
    
+
    
+
    
+
    DESCRIPTION
    
+
    isc-config.sh
 	prints information related to the installed version of ISC BIND,
 	such as the compiler and linker flags required to compile
 	and link programs that use ISC BIND libraries.
     
    
-    
    
+
    
 	The optional libraries are used to report specific details
 	for compiling and linking for the listed libraries.
 	The allowed choices are:
@@ -71,65 +50,47 @@
 	Multiple libraries may be listed on the command line.
 	(Some libraries require other libraries, so are implied.)
     
    
-
-  
    
-
-  
    
-
    OPTIONS
    
-    
-
-    
    
+
    
+
    
+
    OPTIONS
    
+
    
 
    --cflags
    
-
    
-          
    
+
    
             Prints the compiler command line options required to
             compile files that use ISC BIND.
             Use the libraries command line argument(s)
             to print additional specific flags to pass to the C compiler.
-          
    
-        
    
+          
    
 
    --exec-prefix
    
-
    
-          
    
+
    
             Prints the directory prefix used in the ISC BIND installation
             for architecture dependent files to standard output.
-          
    
-        
    
+          
    
 
    --libs
    
-
    
-          
    
+
    
             Prints the linker command line options used to
             link with the ISC BIND libraries.
             Use the libraries command line argument(s)
             to print additional specific flags.
-          
    
-        
    
+          
    
 
    --prefix
    
-
    
-          
    
+
    
             Prints the directory prefix used in the ISC BIND installation
             for architecture independent files to standard output.
-          
    
-        
    
+          
    
 
    --version
    
-
    
-          
    
+
    
             Prints the version of the installed ISC BIND suite.
-          
    
-        
    
+          
    
 
    
-
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    isc-config.sh
+
    
+
    
+
    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.
     
    
-  
    
-
+
    
 
    
 
diff --git a/lib/lwres/man/lwres.3 b/lib/lwres/man/lwres.3
index fa26be1df7..4d1eec7e67 100644
--- a/lib/lwres/man/lwres.3
+++ b/lib/lwres/man/lwres.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres \- introduction to the lightweight resolver library
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .SH "DESCRIPTION"
 .PP
 The BIND 9 lightweight resolver library is a simple, name service independent stub resolver library\&. It provides hostname\-to\-address and address\-to\-hostname lookup services to applications by transmitting lookup requests to a resolver daemon
diff --git a/lib/lwres/man/lwres.html b/lib/lwres/man/lwres.html
index da2db77f95..aa405a4f5e 100644
--- a/lib/lwres/man/lwres.html
+++ b/lib/lwres/man/lwres.html
@@ -18,35 +18,21 @@
 
 
 lwres
-
+
 
-
    
-
    
-  
-  
-
-  
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres
-     — introduction to the lightweight resolver library
-  
    
+
    lwres — introduction to the lightweight resolver library
    
 
    
-
-  
-
-  
    
+
    
 
    Synopsis
    
-    
    
-
    #include <lwres/lwres.h>
    
+
    #include <lwres/lwres.h>
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    DESCRIPTION
    
+
    
       The BIND 9 lightweight resolver library is a simple, name service
       independent stub resolver library.  It provides hostname-to-address
       and address-to-hostname lookup services to applications by
@@ -58,12 +44,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
       gethostbyname(),
@@ -88,7 +72,7 @@
       library into their base distributions should rename the functions
       in the library proper so that the renaming macros are not needed.
     
    
-    
    
+
    
       The library also provides a native API consisting of the functions
       lwres_getaddrsbyname()
       and
@@ -97,14 +81,14 @@
       control over the lookup process than the standard functions
       provide.
     
    
-    
    
+
    
       In addition to these name service independent address lookup
       functions, the library implements a new, experimental API
       for looking up arbitrary DNS resource records, using the
       lwres_getaddrsbyname()
       function.
     
    
-    
    
+
    
       Finally, there is a low-level API for converting lookup
       requests and responses to and from raw lwres protocol packets.
       This API can be used by clients requiring nonblocking operation,
@@ -114,65 +98,63 @@
       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
       sequence of actions.
     
    
-    
    
+
    
       (1) Allocate or use an existing lwres_packet_t,
       called pkt below.
     
    
-    
    
+
    
       (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
       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
       0.
     
    
-    
    
+
    
       (5) Set pkt.result to 0.
     
    
-    
    
+
    
       (6) Call lwres_*request_render(),
       or marshall in the data using the primitives
       such as lwres_packet_render()
       and storing the packet data.
     
    
-    
    
+
    
       (7) Transmit the resulting buffer.
     
    
-    
    
+
    
       (8) Call lwres_*response_parse()
       to parse any packets received.
     
    
-    
    
+
    
       (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
       following is typically involved in processing each request packet.
     
    
-    
    
+
    
       Note that the same lwres_packet_t is used
       in both the _parse() and _render() calls,
       with only a few modifications made
@@ -180,15 +162,15 @@
       recommended
       as it keeps the serial, opcode, and other fields correct.
     
    
-    
    
+
    
       (1) When a packet is received, call lwres_*request_parse() to
       unmarshall it.  This returns a lwres_packet_t (also called pkt, below)
       as well as a data specific type, such as lwres_gabnrequest_t.
     
    
-    
    
+
    
       (2) Process the request in the data specific type.
     
    
-    
    
+
    
       (3) Set the pkt.result,
       pkt.recvlength as above.  All other fields
       can
@@ -198,59 +180,38 @@
       properly.  Otherwise, the LWRES_LWPACKETFLAG_RESPONSE bit should be
       set.
     
    
-    
    
+
    
       (4) Call the data specific rendering function, such as
       lwres_gabnresponse_render().
     
    
-    
    
+
    
       (5) Send the resulting packet to the client.
     
    
-    
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_gethostent(3)
-      ,
+
    
+
    
+
    
+
    SEE ALSO
    
+
    lwres_gethostent(3),
 
-      
-        lwres_getipnode(3)
-      ,
+      lwres_getipnode(3),
 
-      
-        lwres_getnameinfo(3)
-      ,
+      lwres_getnameinfo(3),
 
-      
-        lwres_noop(3)
-      ,
+      lwres_noop(3),
 
-      
-        lwres_gabn(3)
-      ,
+      lwres_gabn(3),
 
-      
-        lwres_gnba(3)
-      ,
+      lwres_gnba(3),
 
-      
-        lwres_context(3)
-      ,
+      lwres_context(3),
 
-      
-        lwres_config(3)
-      ,
+      lwres_config(3),
 
-      
-        resolver(5)
-      ,
+      resolver(5),
 
-      
-        lwresd(8)
-      .
+      lwresd(8).
 
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_buffer.3 b/lib/lwres/man/lwres_buffer.3
index d634aaf708..363c0da6d0 100644
--- a/lib/lwres/man/lwres_buffer.3
+++ b/lib/lwres/man/lwres_buffer.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_buffer
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_buffer_init, lwres_buffer_invalidate, lwres_buffer_add, lwres_buffer_subtract, lwres_buffer_clear, lwres_buffer_first, lwres_buffer_forward, lwres_buffer_back, lwres_buffer_getuint8, lwres_buffer_putuint8, lwres_buffer_getuint16, lwres_buffer_putuint16, lwres_buffer_getuint32, lwres_buffer_putuint32, lwres_buffer_putmem, lwres_buffer_getmem \- lightweight resolver buffer management
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'void\ lwres_buffer_init('u
 .BI "void lwres_buffer_init(lwres_buffer_t\ *" "b" ", void\ *" "base" ", unsigned\ int\ " "length" ");"
 .HP \w'void\ lwres_buffer_invalidate('u
@@ -152,8 +155,7 @@ is an (optional) subregion of the remaining region\&. It extends from the curren
 .PP
 \fBlwres_buffer_init()\fR
 initializes the
-\fBlwres_buffer_t\fR
-\fI*b\fR
+\fBlwres_buffer_t\fR\fI*b\fR
 and assocates it with the memory region of size
 \fIlength\fR
 bytes starting at location
diff --git a/lib/lwres/man/lwres_buffer.html b/lib/lwres/man/lwres_buffer.html
index f3bdab26aa..05c3eead73 100644
--- a/lib/lwres/man/lwres_buffer.html
+++ b/lib/lwres/man/lwres_buffer.html
@@ -18,49 +18,21 @@
 
 
 lwres_buffer
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_buffer_init, 
-    lwres_buffer_invalidate, 
-    lwres_buffer_add, 
-    lwres_buffer_subtract, 
-    lwres_buffer_clear, 
-    lwres_buffer_first, 
-    lwres_buffer_forward, 
-    lwres_buffer_back, 
-    lwres_buffer_getuint8, 
-    lwres_buffer_putuint8, 
-    lwres_buffer_getuint16, 
-    lwres_buffer_putuint16, 
-    lwres_buffer_getuint32, 
-    lwres_buffer_putuint32, 
-    lwres_buffer_putmem, 
-    lwres_buffer_getmem
-     — lightweight resolver buffer management
-  
    
+
    lwres_buffer_init, lwres_buffer_invalidate, lwres_buffer_add, lwres_buffer_subtract, lwres_buffer_clear, lwres_buffer_first, lwres_buffer_forward, lwres_buffer_back, lwres_buffer_getuint8, lwres_buffer_putuint8, lwres_buffer_getuint16, lwres_buffer_putuint16, lwres_buffer_getuint32, lwres_buffer_putuint32, lwres_buffer_putmem, lwres_buffer_getmem — lightweight resolver buffer management
    
 
    
-
-  
    
+
    
 
    Synopsis
    
-
-    
    
+
    
 
     #include <lwres/lwbuffer.h>
 
    
-
-
+
    
 
    
 
 void
@@ -77,15 +49,14 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
 void
 lwres_buffer_invalidate(
 lwres_buffer_t *b);
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -98,8 +69,7 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -112,24 +82,21 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
 void
 lwres_buffer_clear(
 lwres_buffer_t *b);
 
    
 
     
    
-
-
+
    
 
 void
 lwres_buffer_first(
 lwres_buffer_t *b);
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -142,7 +109,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -155,16 +122,14 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
 lwres_uint8_t
 lwres_buffer_getuint8(
 lwres_buffer_t *b);
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -177,16 +142,14 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
 lwres_uint16_t
 lwres_buffer_getuint16(
 lwres_buffer_t *b);
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -199,16 +162,14 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
 lwres_uint32_t
 lwres_buffer_getuint32(
 lwres_buffer_t *b);
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -221,8 +182,7 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -239,8 +199,7 @@ void
 
    
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -257,22 +216,18 @@ void
 
    
 
    
 
     
    
-
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These functions provide bounds checked access to a region of memory
       where data is being read or written.
       They are based on, and similar to, the
       isc_buffer_
       functions in the ISC library.
     
    
-    
    
+
    
       A buffer is a region of memory, together with a set of related
       subregions.
       The used region and the
@@ -286,7 +241,7 @@ void
       buffer commands.
       Initially, the used region is empty.
     
    
-    
    
+
    
       The used region is further subdivided into two disjoint regions: the
       consumed region and the remaining region.
       The union of these two regions is the used region.
@@ -299,7 +254,7 @@ void
       buffer commands.
       Initially, the consumed region is empty.
     
    
-    
    
+
    
       The active region is an (optional) subregion of the
       remaining
       region.
@@ -309,7 +264,7 @@ void
       If the current offset advances beyond the chosen offset,
       the active region will also be empty.
     
    
-    
    +
        /------------entire length---------------\\
    /----- used region -----\\/-- available --\\
    +----------------------------------------+
@@ -319,7 +274,7 @@ void
       
    
 
    
     
    
-    
    +
       a == base of buffer.
   b == current pointer.  Can be anywhere between a and d.
   c == active pointer.  Meaningful between b and d.
@@ -328,7 +283,7 @@ void
       
    
 
    
     
    
-    
    +
       a-e == entire length of buffer.
   a-d == used region.
   a-b == consumed region.
@@ -337,7 +292,7 @@ void
 
    
 
    
     
    
-    
    lwres_buffer_init()
+
    lwres_buffer_init()
       initializes the
       lwres_buffer_t
       *b
@@ -346,12 +301,12 @@ void
       bytes starting at location
       base.
     
    
-    
    lwres_buffer_invalidate()
+
    lwres_buffer_invalidate()
       marks the buffer *b
       as invalid.  Invalidating a buffer after use is not required,
       but makes it possible to catch its possible accidental use.
     
    
-    
    
+
    
       The functions
       lwres_buffer_add()
       and
@@ -370,7 +325,7 @@ void
       They just change the value of
       used.
     
    
-    
    
+
    
       A buffer is re-initialised by
       lwres_buffer_clear().
       The function sets
@@ -380,14 +335,14 @@ void
       active
       to zero.
     
    
-    
    lwres_buffer_first
+
    lwres_buffer_first
       makes the consumed region of buffer
       *p
       empty by setting
       current
       to zero (the start of the buffer).
     
    
-    
    lwres_buffer_forward()
+
    lwres_buffer_forward()
       increases the consumed region of buffer
       *b
       by
@@ -401,7 +356,7 @@ void
       n
       bytes and checks for underflow.
     
    
-    
    lwres_buffer_getuint8()
+
    lwres_buffer_getuint8()
       reads an unsigned 8-bit integer from
       *b
       and returns it.
@@ -411,7 +366,7 @@ void
       to buffer
       *b.
     
    
-    
    lwres_buffer_getuint16()
+
    lwres_buffer_getuint16()
       and
       lwres_buffer_getuint32()
       are identical to
@@ -429,7 +384,7 @@ void
       b,
       in network byte order.
     
    
-    
    
+
    
       Arbitrary amounts of data are read or written from a lightweight
       resolver buffer with
       lwres_buffer_getmem()
@@ -452,6 +407,6 @@ void
       to
       base.
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_config.3 b/lib/lwres/man/lwres_config.3
index cb157e5d85..aff3233b8e 100644
--- a/lib/lwres/man/lwres_config.3
+++ b/lib/lwres/man/lwres_config.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_config
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_conf_init, lwres_conf_clear, lwres_conf_parse, lwres_conf_print, lwres_conf_get \- lightweight resolver configuration
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'void\ lwres_conf_init('u
 .BI "void lwres_conf_init(lwres_context_t\ *" "ctx" ");"
 .HP \w'void\ lwres_conf_clear('u
@@ -88,8 +91,7 @@ prints the
 structure for resolver context
 \fIctx\fR
 to the
-\fBFILE\fR
-\fIfp\fR\&.
+\fBFILE\fR\fIfp\fR\&.
 .SH "RETURN VALUES"
 .PP
 \fBlwres_conf_parse()\fR
diff --git a/lib/lwres/man/lwres_config.html b/lib/lwres/man/lwres_config.html
index 9f75a8e8a3..f6337bb9e6 100644
--- a/lib/lwres/man/lwres_config.html
+++ b/lib/lwres/man/lwres_config.html
@@ -18,48 +18,33 @@
 
 
 lwres_config
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_conf_init, 
-    lwres_conf_clear, 
-    lwres_conf_parse, 
-    lwres_conf_print, 
-    lwres_conf_get
-     — lightweight resolver configuration
-  
    
+
    lwres_conf_init, lwres_conf_clear, lwres_conf_parse, lwres_conf_print, lwres_conf_get — lightweight resolver configuration
    
 
    
-
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/lwres.h>
    
-
+
    
 
 void
 lwres_conf_init(
 lwres_context_t *ctx);
 
    
 
     
    
-
+
    
 
 void
 lwres_conf_clear(
 lwres_context_t *ctx);
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -72,7 +57,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -85,7 +70,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
@@ -93,28 +78,23 @@ lwres_conf_t *
 
    
 
 lwres_conf_t *
 lwres_conf_get(
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_conf_init()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_conf_init()
       creates an empty
       lwres_conf_t
       structure for lightweight resolver context
       ctx.
     
    
-
-    
    lwres_conf_clear()
+
    lwres_conf_clear()
       frees up all the internal memory used by
       that
       lwres_conf_t
       structure in resolver context
       ctx.
     
    
-
-    
    lwres_conf_parse()
+
    lwres_conf_parse()
       opens the file
       filename
       and parses it to initialise the resolver context
@@ -122,8 +102,7 @@ lwres_conf_t *
       lwres_conf_t
       structure.
     
    
-
-    
    lwres_conf_print()
+
    lwres_conf_print()
       prints the
       lwres_conf_t
       structure for resolver context
@@ -132,13 +111,10 @@ lwres_conf_t *
       FILE
       fp.
     
    
-  
    
-  
    
-
    RETURN VALUES
    
-
-    
-
-    
    lwres_conf_parse()
+
    
+
    
+
    RETURN VALUES
    
+
    lwres_conf_parse()
       returns LWRES_R_SUCCESS
       if it successfully read and parsed
       filename.
@@ -147,31 +123,24 @@ lwres_conf_t *
       could not be opened or contained incorrect
       resolver statements.
     
    
-
-    
    lwres_conf_print()
+
    lwres_conf_print()
       returns LWRES_R_SUCCESS
       unless an error occurred when converting the network addresses to a
       numeric host address string.
       If this happens, the function returns
       LWRES_R_FAILURE.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        stdio(3)
-      ,
-      
-        resolver(5)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    stdio(3),
+      resolver(5).
     
    
-  
    
-  
    
-
    FILES
    
-    
-    
    /etc/resolv.conf
+
    
+
    
+
    FILES
    
+
    /etc/resolv.conf
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_context.3 b/lib/lwres/man/lwres_context.3
index 70f0f3fb11..77c1342b8c 100644
--- a/lib/lwres/man/lwres_context.3
+++ b/lib/lwres/man/lwres_context.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_context
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_context_create, lwres_context_destroy, lwres_context_nextserial, lwres_context_initserial, lwres_context_freemem, lwres_context_allocmem, lwres_context_sendrecv \- lightweight resolver context management
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_context_create('u
 .BI "lwres_result_t lwres_context_create(lwres_context_t\ **" "contextp" ", void\ *" "arg" ", lwres_malloc_t\ " "malloc_function" ", lwres_free_t\ " "free_function" ");"
 .HP \w'lwres_result_t\ lwres_context_destroy('u
diff --git a/lib/lwres/man/lwres_context.html b/lib/lwres/man/lwres_context.html
index 095ec72ecc..919dff77f2 100644
--- a/lib/lwres/man/lwres_context.html
+++ b/lib/lwres/man/lwres_context.html
@@ -18,35 +18,19 @@
 
 
 lwres_context
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_context_create, 
-    lwres_context_destroy, 
-    lwres_context_nextserial, 
-    lwres_context_initserial, 
-    lwres_context_freemem, 
-    lwres_context_allocmem, 
-    lwres_context_sendrecv
-     — lightweight resolver context management
-  
    
+
    lwres_context_create, lwres_context_destroy, lwres_context_nextserial, lwres_context_initserial, lwres_context_freemem, lwres_context_allocmem, lwres_context_sendrecv — lightweight resolver context management
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/lwres.h>
    
-
+
    
 
    
 
 lwres_result_t
@@ -67,14 +51,14 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
 lwres_result_t
 lwres_context_destroy(
 lwres_context_t **contextp);
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -87,14 +71,14 @@ void
 
    
 
    
 
     
    
-
+
    
 
 lwres_uint32_t
 lwres_context_nextserial(
 lwres_context_t *ctx);
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -111,7 +95,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -124,7 +108,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void *
@@ -154,12 +138,10 @@ void *
 
    
 
     
    
 
    
-  
    
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_context_create()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_context_create()
       creates a lwres_context_t structure for use in
       lightweight resolver operations.  It holds a socket and other
       data needed for communicating with a resolver daemon.  The new
@@ -170,7 +152,7 @@ void *
       is modified to point to the newly created
       lwres_context_t.
     
    
-    
    
+
    
       When the lightweight resolver needs to perform dynamic memory
       allocation, it will call
       malloc_function
@@ -181,13 +163,9 @@ void *
       and
       free_function
       are NULL, memory is allocated using
-      
-        malloc(3)
-      .
+      malloc(3).
       and
-      
-        free(3)
-      .
+      free(3).
 
       It is not permitted to have a NULL
       malloc_function and a non-NULL
@@ -199,24 +177,19 @@ void *
       arg is unused and should be passed as
       NULL.
     
    
-
-    
    
+
    
       Once memory for the structure has been allocated,
       it is initialized using
-      
-        lwres_conf_init(3)
-      
+      lwres_conf_init(3)
       and returned via *contextp.
     
    
-
-    
    lwres_context_destroy()
+
    lwres_context_destroy()
       destroys a lwres_context_t, closing its socket.
       contextp is a pointer to a pointer to the
       context that is to be destroyed.  The pointer will be set to
       NULL when the context has been destroyed.
     
    
-
-    
    
+
    
       The context holds a serial number that is used to identify
       resolver request packets and associate responses with the
       corresponding requests.  This serial number is controlled using
@@ -228,8 +201,7 @@ void *
       lwres_context_nextserial() increments the
       serial number and returns the previous value.
     
    
-
-    
    
+
    
       Memory for a lightweight resolver context is allocated and freed
       using lwres_context_allocmem() and
       lwres_context_freemem().  These use
@@ -242,8 +214,7 @@ void *
       len bytes of space starting at location
       mem.
     
    
-
-    
    lwres_context_sendrecv()
+
    lwres_context_sendrecv()
       performs I/O for the context ctx.  Data
       are read and written from the context's socket.  It writes data
       from sendbase — typically a
@@ -253,24 +224,21 @@ void *
       written to this receive buffer is returned in
       *recvd_len.
     
    
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-
-    
    lwres_context_create()
+
    
+
    
+
    RETURN VALUES
    
+
    lwres_context_create()
       returns LWRES_R_NOMEMORY if memory for
       the struct lwres_context could not be allocated,
       LWRES_R_SUCCESS otherwise.
     
    
-    
    
+
    
       Successful calls to the memory allocator
       lwres_context_allocmem()
       return a pointer to the start of the allocated space.
       It returns NULL if memory could not be allocated.
     
    
-    
    LWRES_R_SUCCESS
+
    LWRES_R_SUCCESS
       is returned when
       lwres_context_sendrecv()
       completes successfully.
@@ -281,22 +249,15 @@ void *
       lwres_context_sendrecv()
       times out waiting for a response.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_conf_init(3)
-      ,
+
    
+
    
+
    SEE ALSO
    
+
    lwres_conf_init(3),
 
-      
-        malloc(3)
-      ,
+      malloc(3),
 
-      
-        free(3)
-      .
+      free(3).
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_gabn.3 b/lib/lwres/man/lwres_gabn.3
index cb1a76db5a..2e5b8f7b43 100644
--- a/lib/lwres/man/lwres_gabn.3
+++ b/lib/lwres/man/lwres_gabn.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_gabn
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_gabnrequest_render, lwres_gabnresponse_render, lwres_gabnrequest_parse, lwres_gabnresponse_parse, lwres_gabnresponse_free, lwres_gabnrequest_free \- lightweight resolver getaddrbyname message handling
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_gabnrequest_render('u
 .BI "lwres_result_t lwres_gabnrequest_render(lwres_context_t\ *" "ctx" ", lwres_gabnrequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
 .HP \w'lwres_result_t\ lwres_gabnresponse_render('u
@@ -183,8 +186,7 @@ structures referenced via
 .PP
 The getaddrbyname opcode functions
 \fBlwres_gabnrequest_render()\fR,
-\fBlwres_gabnresponse_render()\fR
-\fBlwres_gabnrequest_parse()\fR
+\fBlwres_gabnresponse_render()\fR\fBlwres_gabnrequest_parse()\fR
 and
 \fBlwres_gabnresponse_parse()\fR
 all return
diff --git a/lib/lwres/man/lwres_gabn.html b/lib/lwres/man/lwres_gabn.html
index 504c86279f..949d6d28a7 100644
--- a/lib/lwres/man/lwres_gabn.html
+++ b/lib/lwres/man/lwres_gabn.html
@@ -18,34 +18,19 @@
 
 
 lwres_gabn
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_gabnrequest_render, 
-    lwres_gabnresponse_render, 
-    lwres_gabnrequest_parse, 
-    lwres_gabnresponse_parse, 
-    lwres_gabnresponse_free, 
-    lwres_gabnrequest_free
-     — lightweight resolver getaddrbyname message handling
-  
    
+
    lwres_gabnrequest_render, lwres_gabnresponse_render, lwres_gabnrequest_parse, lwres_gabnresponse_parse, lwres_gabnresponse_free, lwres_gabnrequest_free — lightweight resolver getaddrbyname message handling
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/lwres.h>
    
-
+
    
 
    
 
 lwres_result_t
@@ -66,7 +51,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -87,7 +72,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -108,7 +93,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -129,7 +114,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -142,7 +127,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -156,16 +141,15 @@ void
 
    
 
     
    
 
    
-  
    
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These are low-level routines for creating and parsing
       lightweight resolver name-to-address lookup request and
       response messages.
     
    
-    
    
+
    
       There are four main functions for the getaddrbyname opcode.
       One render function converts a getaddrbyname request structure —
       lwres_gabnrequest_t —
@@ -178,23 +162,23 @@ void
       This is complemented by a parse function which converts a packet in
       canonical format to a getaddrbyname response structure.
     
    
-    
    
+
    
       These structures are defined in
       <lwres/lwres.h>.
       They are shown below.
     
    
-    
    +
     #define LWRES_OPCODE_GETADDRSBYNAME     0x00010001U
 
    
 
    
     
    
-    
    +
     typedef struct lwres_addr lwres_addr_t;
 typedef LWRES_LIST(lwres_addr_t) lwres_addrlist_t;
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint32_t  flags;
         lwres_uint32_t  addrtypes;
@@ -204,7 +188,7 @@ typedef struct {
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint32_t          flags;
         lwres_uint16_t          naliases;
@@ -220,8 +204,7 @@ typedef struct {
 
    
 
    
     
    
-
-    
    lwres_gabnrequest_render()
+
    lwres_gabnrequest_render()
       uses resolver context ctx to convert
       getaddrbyname request structure req to
       canonical format.  The packet header structure
@@ -235,8 +218,7 @@ typedef struct {
       lwres_gabnresponse_t to the lightweight resolver's
       canonical format.
     
    
-
-    
    lwres_gabnrequest_parse()
+
    lwres_gabnrequest_parse()
       uses context ctx to convert the contents
       of packet pkt to a
       lwres_gabnrequest_t structure.  Buffer
@@ -249,8 +231,7 @@ typedef struct {
       semantics as lwres_gabnrequest_parse()
       except it yields a lwres_gabnresponse_t structure.
     
    
-
-    
    lwres_gabnresponse_free()
+
    lwres_gabnresponse_free()
       and lwres_gabnrequest_free() release the
       memory in resolver context ctx that was
       allocated to the lwres_gabnresponse_t or
@@ -260,11 +241,10 @@ 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(),
       lwres_gabnresponse_render()
@@ -299,14 +279,11 @@ typedef struct {
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_packet(3)
-      
+
    
+
    
+
    SEE ALSO
    
+
    lwres_packet(3)
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_gai_strerror.3 b/lib/lwres/man/lwres_gai_strerror.3
index 6b0e8f94a3..feb7c38a90 100644
--- a/lib/lwres/man/lwres_gai_strerror.3
+++ b/lib/lwres/man/lwres_gai_strerror.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_gai_strerror
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_gai_strerror \- print suitable error string
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'char\ *\ gai_strerror('u
 .BI "char * gai_strerror(int\ " "ecode" ");"
 .SH "DESCRIPTION"
diff --git a/lib/lwres/man/lwres_gai_strerror.html b/lib/lwres/man/lwres_gai_strerror.html
index 83aa6b7933..ce452128a7 100644
--- a/lib/lwres/man/lwres_gai_strerror.html
+++ b/lib/lwres/man/lwres_gai_strerror.html
@@ -18,30 +18,19 @@
 
 
 lwres_gai_strerror
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_gai_strerror
-     — print suitable error string
-  
    
+
    lwres_gai_strerror — print suitable error string
    
 
    
-
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
@@ -49,91 +38,66 @@ char *
 
    
 
 char *
 gai_strerror(
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_gai_strerror()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_gai_strerror()
       returns an error message corresponding to an error code returned by
       getaddrinfo().
       The following error codes and their meaning are defined in
       include/lwres/netdb.h.
       
    
-
    
+
    
 
    EAI_ADDRFAMILY
    
-
    
-            
    
+
    
               address family for hostname not supported
-            
    
-          
    
+            
    
 
    EAI_AGAIN
    
-
    
-            
    
+
    
               temporary failure in name resolution
-            
    
-          
    
+            
    
 
    EAI_BADFLAGS
    
-
    
-            
    
+
    
               invalid value for
               ai_flags
-            
    
-          
    
+            
    
 
    EAI_FAIL
    
-
    
-            
    
+
    
               non-recoverable failure in name resolution
-            
    
-          
    
+            
    
 
    EAI_FAMILY
    
-
    
-            
    ai_family not supported
-            
    
-          
    
+
    ai_family not supported
+            
    
 
    EAI_MEMORY
    
-
    
-            
    
+
    
               memory allocation failure
-            
    
-          
    
+            
    
 
    EAI_NODATA
    
-
    
-            
    
+
    
               no address associated with hostname
-            
    
-          
    
+            
    
 
    EAI_NONAME
    
-
    
-            
    
+
    
               hostname or servname not provided, or not known
-            
    
-          
    
+            
    
 
    EAI_SERVICE
    
-
    
-            
    
+
    
               servname not supported for ai_socktype
-            
    
-          
    
+            
    
 
    EAI_SOCKTYPE
    
-
    
-            
    ai_socktype not supported
-            
    
-          
    
+
    ai_socktype not supported
+            
    
 
    EAI_SYSTEM
    
-
    
-            
    
+
    
               system error returned in errno
-            
    
-          
    
+            
    
 
    
 
    
       The message invalid error code is returned if
       ecode
       is out of range.
     
    
-    
    ai_flags,
+
    ai_flags,
       ai_family
       and
       ai_socktype
@@ -142,27 +106,17 @@ char *
       used by
       lwres_getaddrinfo().
     
    
-  
    
+
    
+
    
+
    SEE ALSO
    
+
    strerror(3),
 
-  
    
-
    SEE ALSO
    
-    
-    
    
-        strerror(3)
-      ,
+      lwres_getaddrinfo(3),
 
-      
-        lwres_getaddrinfo(3)
-      ,
+      getaddrinfo(3),
 
-      
-        getaddrinfo(3)
-      ,
-
-      
-        RFC2133
-      .
+      RFC2133.
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_getaddrinfo.3 b/lib/lwres/man/lwres_getaddrinfo.3
index 5160d3c05f..af54543652 100644
--- a/lib/lwres/man/lwres_getaddrinfo.3
+++ b/lib/lwres/man/lwres_getaddrinfo.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_getaddrinfo
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_getaddrinfo, lwres_freeaddrinfo \- socket address structure to host and service name
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'int\ lwres_getaddrinfo('u
 .BI "int lwres_getaddrinfo(const\ char\ *" "hostname" ", const\ char\ *" "servname" ", const\ struct\ addrinfo\ *" "hints" ", struct\ addrinfo\ **" "res" ");"
 .HP \w'void\ lwres_freeaddrinfo('u
@@ -235,8 +238,7 @@ if an error occurs\&. If both
 and
 \fIservname\fR
 are
-\fBNULL\fR
-\fBlwres_getaddrinfo()\fR
+\fBNULL\fR\fBlwres_getaddrinfo()\fR
 returns
 \fBEAI_NONAME\fR\&.
 .SH "SEE ALSO"
diff --git a/lib/lwres/man/lwres_getaddrinfo.html b/lib/lwres/man/lwres_getaddrinfo.html
index 9f56d358f7..b65488464d 100644
--- a/lib/lwres/man/lwres_getaddrinfo.html
+++ b/lib/lwres/man/lwres_getaddrinfo.html
@@ -18,30 +18,19 @@
 
 
 lwres_getaddrinfo
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_getaddrinfo, 
-    lwres_freeaddrinfo
-     — socket address structure to host and service name
-  
    
+
    lwres_getaddrinfo, lwres_freeaddrinfo — socket address structure to host and service name
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
    
 
 int
@@ -62,7 +51,7 @@ int
 
    
 
    
 
     
    
-
+
    
@@ -70,13 +59,12 @@ void
 
    
 
 void
 lwres_freeaddrinfo(
    
 
     
    
 
    
-
-    
    
+
    
       If the operating system does not provide a
       struct addrinfo,
       the following structure is used:
     
    
-    
    +
     struct  addrinfo {
         int             ai_flags;       /* AI_PASSIVE, AI_CANONNAME */
         int             ai_family;      /* PF_xxx */
@@ -90,14 +78,10 @@ struct  addrinfo {
 
    
 
    
     
    
-
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_getaddrinfo()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_getaddrinfo()
       is used to get a list of IP addresses and port numbers for host
       hostname and service
       servname.
@@ -114,8 +98,7 @@ struct  addrinfo {
       decimal port number or a service name as listed in
       /etc/services.
     
    
-
-    
    hints
+
    hints
       is an optional pointer to a
       struct addrinfo.
       This structure can be used to provide hints concerning the type of
@@ -125,10 +108,9 @@ struct  addrinfo {
       *hints:
 
       
    
-
    
+
    
 
    ai_family
    
-
    
-            
    
+
    
               The protocol family that should be used.
               When
               ai_family
@@ -137,11 +119,9 @@ struct  addrinfo {
               it means the caller will accept any protocol family supported by
               the
               operating system.
-            
    
-          
    
+            
    
 
    ai_socktype
    
-
    
-            
    
+
    
               denotes the type of socket —
               SOCK_STREAM,
               SOCK_DGRAM
@@ -151,21 +131,18 @@ struct  addrinfo {
               When
               ai_socktype
               is zero the caller will accept any socket type.
-            
    
-          
    
+            
    
 
    ai_protocol
    
-
    
-            
    
+
    
               indicates which transport protocol is wanted: IPPROTO_UDP or
               IPPROTO_TCP.
               If
               ai_protocol
               is zero the caller will accept any protocol.
-            
    
-          
    
+            
    
 
    ai_flags
    
 
    
-            
    
+
    
               Flag bits.
               If the
               AI_CANONNAME
@@ -183,9 +160,7 @@ struct  addrinfo {
               bit indicates that the returned socket address structure is
               intended
               for used in a call to
-              
-                bind(2)
-              .
+              bind(2).
 
               In this case, if the hostname argument is a
               NULL
@@ -196,29 +171,21 @@ struct  addrinfo {
               IN6ADDR_ANY_INIT
               for an IPv6 address.
             
    
-            
    
+
    
               When
               ai_flags
               does not set the
               AI_PASSIVE
               bit, the returned socket address structure will be ready
               for use in a call to
-              
-                connect(2)
-              
+              connect(2)
               for a connection-oriented protocol or
-              
-                connect(2)
-              ,
+              connect(2),
 
-              
-                sendto(2)
-              ,
+              sendto(2),
 
               or
-              
-                sendmsg(2)
-              
+              sendmsg(2)
               if a connectionless protocol was chosen.
               The IP address portion of the socket address structure will be
               set to the loopback address if
@@ -230,7 +197,7 @@ struct  addrinfo {
               is not set in
               ai_flags.
             
    
-            
    
+
    
               If
               ai_flags
               is set to
@@ -241,25 +208,22 @@ struct  addrinfo {
               address
               and no name resolution should be attempted.
             
    
-          
    
+
 
    
 
    
     
    
-
-    
    
+
    
       All other elements of the struct addrinfo passed
       via hints must be zero.
     
    
-
-    
    
+
    
       A hints of NULL is
       treated as if
       the caller provided a struct addrinfo initialized to zero
       with ai_familyset to
       PF_UNSPEC.
     
    
-
-    
    
+
    
       After a successful call to
       lwres_getaddrinfo(),
       *res
@@ -283,9 +247,7 @@ struct  addrinfo {
       returned
       addrinfo
       structure contain the corresponding arguments for a call to
-      
-        socket(2)
-      .
+      socket(2).
       For each
       addrinfo
       structure in the list, the
@@ -293,8 +255,7 @@ struct  addrinfo {
       member points to a filled-in socket address structure of length
       ai_addrlen.
     
    
-
-    
    
+
    
       All of the information returned by
       lwres_getaddrinfo()
       is dynamically allocated: the addrinfo structures, and the socket
@@ -311,72 +272,42 @@ struct  addrinfo {
       created by a call to
       lwres_getaddrinfo().
     
    
-
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-
-    
    lwres_getaddrinfo()
+
    
+
    
+
    RETURN VALUES
    
+
    lwres_getaddrinfo()
       returns zero on success or one of the error codes listed in
-      
-        gai_strerror(3)
-      
+      gai_strerror(3)
       if an error occurs.  If both hostname and
       servname are NULL
       lwres_getaddrinfo() returns
       EAI_NONAME.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres(3)
-      ,
+
    
+
    
+
    SEE ALSO
    
+
    lwres(3),
 
-      
-        lwres_getaddrinfo(3)
-      ,
+      lwres_getaddrinfo(3),
 
-      
-        lwres_freeaddrinfo(3)
-      ,
+      lwres_freeaddrinfo(3),
 
-      
-        lwres_gai_strerror(3)
-      ,
+      lwres_gai_strerror(3),
 
-      
-        RFC2133
-      ,
+      RFC2133,
 
-      
-        getservbyname(3)
-      ,
+      getservbyname(3),
 
-      
-        bind(2)
-      ,
+      bind(2),
 
-      
-        connect(2)
-      ,
+      connect(2),
 
-      
-        sendto(2)
-      ,
+      sendto(2),
 
-      
-        sendmsg(2)
-      ,
+      sendmsg(2),
 
-      
-        socket(2)
-      .
+      socket(2).
     
    
-
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_gethostent.3 b/lib/lwres/man/lwres_gethostent.3
index 7a14bdfb7d..36e249431f 100644
--- a/lib/lwres/man/lwres_gethostent.3
+++ b/lib/lwres/man/lwres_gethostent.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_gethostent
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_gethostbyname, lwres_gethostbyname2, lwres_gethostbyaddr, lwres_gethostent, lwres_sethostent, lwres_endhostent, lwres_gethostbyname_r, lwres_gethostbyaddr_r, lwres_gethostent_r, lwres_sethostent_r, lwres_endhostent_r \- lightweight resolver get network host entry
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'struct\ hostent\ *\ lwres_gethostbyname('u
 .BI "struct hostent * lwres_gethostbyname(const\ char\ *" "name" ");"
 .HP \w'struct\ hostent\ *\ lwres_gethostbyname2('u
diff --git a/lib/lwres/man/lwres_gethostent.html b/lib/lwres/man/lwres_gethostent.html
index 8cfe8a5050..ef0a5f3820 100644
--- a/lib/lwres/man/lwres_gethostent.html
+++ b/lib/lwres/man/lwres_gethostent.html
@@ -18,46 +18,26 @@
 
 
 lwres_gethostent
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_gethostbyname, 
-    lwres_gethostbyname2, 
-    lwres_gethostbyaddr, 
-    lwres_gethostent, 
-    lwres_sethostent, 
-    lwres_endhostent, 
-    lwres_gethostbyname_r, 
-    lwres_gethostbyaddr_r, 
-    lwres_gethostent_r, 
-    lwres_sethostent_r, 
-    lwres_endhostent_r
-     — lightweight resolver get network host entry
-  
    
+
    lwres_gethostbyname, lwres_gethostbyname2, lwres_gethostbyaddr, lwres_gethostent, lwres_sethostent, lwres_endhostent, lwres_gethostbyname_r, lwres_gethostbyaddr_r, lwres_gethostent_r, lwres_sethostent_r, lwres_endhostent_r — lightweight resolver get network host entry
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
 struct hostent *
 lwres_gethostbyname(
 const char *name);
 
    
 
     
    
-
+
    
 
    
 
 struct hostent *
@@ -70,7 +50,7 @@ struct hostent *
 
    
 
    
 
     
    
-
+
    
 
    
 
 struct hostent *
@@ -87,28 +67,28 @@ struct hostent *
 
    
 
    
 
     
    
-
+
    
 
 struct hostent *
 lwres_gethostent(
 void);
 
    
 
     
    
-
+
    
 
 void
 lwres_sethostent(
 int stayopen);
 
    
 
     
    
-
+
    
 
 void
 lwres_endhostent(
 void);
 
    
 
     
    
-
+
    
 
    
 
 struct hostent *
@@ -133,7 +113,7 @@ struct hostent *
 
    
 
    
 
     
    
-
+
    
 
    
 
 struct hostent  *
@@ -166,7 +146,7 @@ struct hostent  *
 
    
 
    
 
     
    
-
+
    
 
    
 
 struct hostent  *
@@ -187,14 +167,14 @@ struct hostent  *
 
    
 
    
 
     
    
-
+
    
 
 void
 lwres_sethostent_r(
 int stayopen);
 
    
 
     
    
-
+
    
@@ -202,25 +182,21 @@ void
 
    
 
 void
 lwres_endhostent_r(
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These functions provide hostname-to-address and
       address-to-hostname lookups by means of the lightweight resolver.
       They are similar to the standard
-      
-        gethostent(3)
-      
+      gethostent(3)
       functions provided by most operating systems.
       They use a
       struct hostent
       which is usually defined in
       <namedb.h>.
     
    
-    
    +
     struct  hostent {
         char    *h_name;        /* official name of host */
         char    **h_aliases;    /* alias list */
@@ -232,56 +208,46 @@ struct  hostent {
 
    
 
    
     
    
-    
    
+
    
       The members of this structure are:
       
    
-
    
+
    
 
    h_name
    
-
    
-            
    
+
    
               The official (canonical) name of the host.
-            
    
-          
    
+            
    
 
    h_aliases
    
-
    
-            
    
+
    
               A NULL-terminated array of alternate names (nicknames) for the
               host.
-            
    
-          
    
+            
    
 
    h_addrtype
    
-
    
-            
    
+
    
               The type of address being returned —
               PF_INET
               or
               PF_INET6.
-            
    
-          
    
+            
    
 
    h_length
    
-
    
-            
    
+
    
               The length of the address in bytes.
-            
    
-          
    
+            
    
 
    h_addr_list
    
-
    
-            
    
+
    
               A NULL
               terminated array of network addresses for the host.
               Host addresses are returned in network byte order.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-    
    
+
    
       For backward compatibility with very old software,
       h_addr
       is the first address in
       h_addr_list.
     
    
-    
    lwres_gethostent(),
+
    lwres_gethostent(),
       lwres_sethostent(),
       lwres_endhostent(),
       lwres_gethostent_r(),
@@ -295,8 +261,7 @@ struct  hostent {
       these functions; it only provides them as stub functions that always
       return failure.
     
    
-
-    
    lwres_gethostbyname()
+
    lwres_gethostbyname()
       and lwres_gethostbyname2() look up the
       hostname name.
       lwres_gethostbyname() always looks for an
@@ -310,8 +275,7 @@ struct  hostent {
       lwres_gethostbyname() or
       lwres_gethostbyname2() fail.
     
    
-
-    
    
+
    
       Reverse lookups of addresses are performed by
       lwres_gethostbyaddr().
       addr is an address of length
@@ -334,8 +298,7 @@ struct  hostent {
       return resbuf,
       which is a pointer to the struct hostent it created.
     
    
-
-    
    lwres_gethostbyaddr_r()
+
    lwres_gethostbyaddr_r()
       is a thread-safe function
       that performs a reverse lookup of address addr
       which is len bytes long and is of
@@ -357,13 +320,10 @@ struct  hostent {
       resbuf, which is a pointer to the
       struct hostent() it created.
     
    
-
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       The functions
       lwres_gethostbyname(),
       lwres_gethostbyname2(),
@@ -376,52 +336,39 @@ struct  hostent {
       <lwres/netdb.h>:
 
       
    
-
    
+
    
 
    HOST_NOT_FOUND
    
-
    
-            
    
+
    
               The host or address was not found.
-            
    
-          
    
+            
    
 
    TRY_AGAIN
    
-
    
-            
    
+
    
               A recoverable error occurred, e.g., a timeout.
               Retrying the lookup may succeed.
-            
    
-          
    
+            
    
 
    NO_RECOVERY
    
-
    
-            
    
+
    
               A non-recoverable error occurred.
-            
    
-          
    
+            
    
 
    NO_DATA
    
-
    
-            
    
+
    
               The name exists, but has no address information
               associated with it (or vice versa in the case
               of a reverse lookup).  The code NO_ADDRESS
               is accepted as a synonym for NO_DATA for backwards
               compatibility.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-
-    
    
-        lwres_hstrerror(3)
-      
+
    lwres_hstrerror(3)
       translates these error codes to suitable error messages.
     
    
-
-    
    lwres_gethostent()
+
    lwres_gethostent()
       and lwres_gethostent_r()
       always return NULL.
     
    
-
-    
    
+
    
       Successful calls to lwres_gethostbyname_r() and
       lwres_gethostbyaddr_r() return
       resbuf, a pointer to the
@@ -437,29 +384,19 @@ struct  hostent {
       variable
       errno to ERANGE.
     
    
+
    
+
    
+
    SEE ALSO
    
+
    gethostent(3),
 
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        gethostent(3)
-      ,
+      lwres_getipnode(3),
 
-      
-        lwres_getipnode(3)
-      ,
-
-      
-        lwres_hstrerror(3)
-      
+      lwres_hstrerror(3)
     
    
-  
    
-
-  
    
-
    BUGS
    
-    
-    
    lwres_gethostbyname(),
+
    
+
    
+
    BUGS
    
+
    lwres_gethostbyname(),
       lwres_gethostbyname2(),
       lwres_gethostbyaddr()
       and
@@ -472,7 +409,7 @@ struct  hostent {
       lwres_gethostbyaddr_r()
       respectively.
     
    
-    
    
+
    
       The resolver daemon does not currently support any non-DNS
       name services such as
       /etc/hosts
@@ -480,6 +417,6 @@ struct  hostent {
       NIS,
       consequently the above functions don't, either.
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_getipnode.3 b/lib/lwres/man/lwres_getipnode.3
index 8a18a51f61..ab8f0b5a6e 100644
--- a/lib/lwres/man/lwres_getipnode.3
+++ b/lib/lwres/man/lwres_getipnode.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_getipnode
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_getipnodebyname, lwres_getipnodebyaddr, lwres_freehostent \- lightweight resolver nodename / address translation API
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'struct\ hostent\ *\ lwres_getipnodebyname('u
 .BI "struct hostent * lwres_getipnodebyname(const\ char\ *" "name" ", int\ " "af" ", int\ " "flags" ", int\ *" "error_num" ");"
 .HP \w'struct\ hostent\ *\ lwres_getipnodebyaddr('u
diff --git a/lib/lwres/man/lwres_getipnode.html b/lib/lwres/man/lwres_getipnode.html
index 627ae89690..a27b3994cb 100644
--- a/lib/lwres/man/lwres_getipnode.html
+++ b/lib/lwres/man/lwres_getipnode.html
@@ -18,31 +18,19 @@
 
 
 lwres_getipnode
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_getipnodebyname, 
-    lwres_getipnodebyaddr, 
-    lwres_freehostent
-     — lightweight resolver nodename / address translation API
-  
    
+
    lwres_getipnodebyname, lwres_getipnodebyaddr, lwres_freehostent — lightweight resolver nodename / address translation API
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
    
 
 struct hostent *
@@ -63,7 +51,7 @@ struct hostent *
 
    
 
    
 
     
    
-
+
    
 
    
 
 struct hostent *
@@ -84,7 +72,7 @@ struct hostent *
 
    
 
    
 
     
    
-
+
    
@@ -92,25 +80,21 @@ void
 
    
 
 void
 lwres_freehostent(
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These functions perform thread safe, protocol independent
       nodename-to-address and address-to-nodename
       translation as defined in RFC2553.
     
    
-
-    
    
+
    
       They use a
       struct hostent
       which is defined in
       namedb.h:
     
    
-    
    +
     struct  hostent {
         char    *h_name;        /* official name of host */
         char    **h_aliases;    /* alias list */
@@ -122,54 +106,42 @@ struct  hostent {
 
    
 
    
     
    
-
-    
    
+
    
       The members of this structure are:
       
    
-
    
+
    
 
    h_name
    
-
    
-            
    
+
    
               The official (canonical) name of the host.
-            
    
-          
    
+            
    
 
    h_aliases
    
-
    
-            
    
+
    
               A NULL-terminated array of alternate names (nicknames) for the
               host.
-            
    
-          
    
+            
    
 
    h_addrtype
    
-
    
-            
    
+
    
               The type of address being returned - usually
               PF_INET
               or
               PF_INET6.
 
-            
    
-          
    
+            
    
 
    h_length
    
-
    
-            
    
+
    
               The length of the address in bytes.
-            
    
-          
    
+            
    
 
    h_addr_list
    
-
    
-            
    
+
    
               A
               NULL
               terminated array of network addresses for the host.
               Host addresses are returned in network byte order.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-
-    
    lwres_getipnodebyname()
+
    lwres_getipnodebyname()
       looks up addresses of protocol family af
       for the hostname name.  The
       flags parameter contains ORed flag bits
@@ -177,20 +149,17 @@ struct  hostent {
       types of addresses that are returned.  The flag bits are:
 
       
    
-
    
+
    
 
    AI_V4MAPPED
    
-
    
-            
    
+
    
               This is used with an
               af
               of AF_INET6, and causes IPv4 addresses to be returned as
               IPv4-mapped
               IPv6 addresses.
-            
    
-          
    
+            
    
 
    AI_ALL
    
-
    
-            
    
+
    
               This is used with an
               af
               of AF_INET6, and causes all known addresses (IPv6 and IPv4) to
@@ -198,37 +167,31 @@ struct  hostent {
               If AI_V4MAPPED is also set, the IPv4 addresses are return as
               mapped
               IPv6 addresses.
-            
    
-          
    
+            
    
 
    AI_ADDRCONFIG
    
-
    
-            
    
+
    
               Only return an IPv6 or IPv4 address if here is an active network
               interface of that type.  This is not currently implemented
               in the BIND 9 lightweight resolver, and the flag is ignored.
-            
    
-          
    
+            
    
 
    AI_DEFAULT
    
-
    
-            
    
+
    
               This default sets the
               AI_V4MAPPED
               and
               AI_ADDRCONFIG
               flag bits.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-
-    
    lwres_getipnodebyaddr()
+
    lwres_getipnodebyaddr()
       performs a reverse lookup of address src
       which is len bytes long.
       af denotes the protocol family, typically
       PF_INET or PF_INET6.
     
    
-    
    lwres_freehostent()
+
    lwres_freehostent()
       releases all the memory associated with the struct
       hostent pointer he.  Any memory
       allocated for the h_name,
@@ -236,11 +199,10 @@ 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()
       and
@@ -253,72 +215,49 @@ struct  hostent {
       The error codes and their meanings are defined in
       <lwres/netdb.h>:
       
    
-
    
+
    
 
    HOST_NOT_FOUND
    
-
    
-            
    
+
    
               No such host is known.
-            
    
-          
    
+            
    
 
    NO_ADDRESS
    
-
    
-            
    
+
    
               The server recognised the request and the name but no address is
               available.  Another type of request to the name server for the
               domain might return an answer.
-            
    
-          
    
+            
    
 
    TRY_AGAIN
    
-
    
-            
    
+
    
               A temporary and possibly transient error occurred, such as a
               failure of a server to respond.  The request may succeed if
               retried.
-            
    
-          
    
+            
    
 
    NO_RECOVERY
    
-
    
-            
    
+
    
               An unexpected failure occurred, and retrying the request
               is pointless.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-    
    
-        lwres_hstrerror(3)
-      
+
    lwres_hstrerror(3)
       translates these error codes to suitable error messages.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        RFC2553
-      ,
+
    
+
    
+
    SEE ALSO
    
+
    RFC2553,
 
-      
-        lwres(3)
-      ,
+      lwres(3),
 
-      
-        lwres_gethostent(3)
-      ,
+      lwres_gethostent(3),
 
-      
-        lwres_getaddrinfo(3)
-      ,
+      lwres_getaddrinfo(3),
 
-      
-        lwres_getnameinfo(3)
-      ,
+      lwres_getnameinfo(3),
 
-      
-        lwres_hstrerror(3)
-      .
+      lwres_hstrerror(3).
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_getnameinfo.3 b/lib/lwres/man/lwres_getnameinfo.3
index 7e345f7690..c0c4ff4cf9 100644
--- a/lib/lwres/man/lwres_getnameinfo.3
+++ b/lib/lwres/man/lwres_getnameinfo.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_getnameinfo
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_getnameinfo \- lightweight resolver socket address structure to hostname and service name
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'int\ lwres_getnameinfo('u
 .BI "int lwres_getnameinfo(const\ struct\ sockaddr\ *" "sa" ", size_t\ " "salen" ", char\ *" "host" ", size_t\ " "hostlen" ", char\ *" "serv" ", size_t\ " "servlen" ", int\ " "flags" ");"
 .SH "DESCRIPTION"
@@ -59,8 +62,7 @@ This function is equivalent to the
 function defined in RFC2133\&.
 \fBlwres_getnameinfo()\fR
 returns the hostname for the
-\fBstruct sockaddr\fR
-\fIsa\fR
+\fBstruct sockaddr\fR\fIsa\fR
 which is
 \fIsalen\fR
 bytes long\&. The hostname is of length
diff --git a/lib/lwres/man/lwres_getnameinfo.html b/lib/lwres/man/lwres_getnameinfo.html
index 43518ec006..3b3d10f3ad 100644
--- a/lib/lwres/man/lwres_getnameinfo.html
+++ b/lib/lwres/man/lwres_getnameinfo.html
@@ -18,31 +18,21 @@
 
 
 lwres_getnameinfo
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_getnameinfo
-     — lightweight resolver socket address structure to hostname and
+
    lwres_getnameinfo — lightweight resolver socket address structure to hostname and
       service name
-    
-  
    
+    
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
    
 
 int
@@ -76,17 +66,12 @@ int
 
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
        This function is equivalent to the
-      
-        getnameinfo(3)
-       function defined in RFC2133.
+      getnameinfo(3) function defined in RFC2133.
       lwres_getnameinfo() returns the
       hostname for the
       struct sockaddr sa which
@@ -98,56 +83,45 @@ int
       hostname is
       1025 bytes: NI_MAXHOST.
     
    
-
-    
     The name of the service associated with the port number in
+
     The name of the service associated with the port number in
       sa is returned in *serv.
       It is servlen bytes long.  The
       maximum length
       of the service name is NI_MAXSERV - 32
       bytes.
     
    
-
-    
    
+
    
        The flags argument sets the
       following
       bits:
       
    
-
    
+
    
 
    NI_NOFQDN
    
-
    
-            
    
+
    
               A fully qualified domain name is not required for local hosts.
               The local part of the fully qualified domain name is returned
               instead.
-            
    
-          
    
+            
    
 
    NI_NUMERICHOST
    
-
    
-            
    
+
    
               Return the address in numeric form, as if calling inet_ntop(),
               instead of a host name.
-            
    
-          
    
+            
    
 
    NI_NAMEREQD
    
-
    
-            
    
+
    
               A name is required. If the hostname cannot be found in the DNS
               and
               this flag is set, a non-zero error code is returned.
               If the hostname is not found and the flag is not set, the
               address is returned in numeric form.
-            
    
-          
    
+            
    
 
    NI_NUMERICSERV
    
-
    
-            
    
+
    
               The service name is returned as a digit string representing the
               port number.
-            
    
-          
    
+            
    
 
    NI_DGRAM
    
-
    
-            
    
+
    
               Specifies that the service being looked up is a datagram
               service,  and causes getservbyport() to be called with a second
               argument of "udp" instead of its default of "tcp".  This is
@@ -155,53 +129,34 @@ int
               for the few ports (512-514) that have different services for UDP
               and
               TCP.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    lwres_getnameinfo()
+
    
+
    
+
    RETURN VALUES
    
+
    lwres_getnameinfo()
       returns 0 on success or a non-zero error code if an error occurs.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        RFC2133
-      ,
-      
-        getservbyport(3)
-      ,
-      
-        lwres(3)
-      ,
-      
-        lwres_getnameinfo(3)
-      ,
-      
-        lwres_getnamebyaddr(3)
-      .
-      
-        lwres_net_ntop(3)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    RFC2133,
+      getservbyport(3),
+      lwres(3),
+      lwres_getnameinfo(3),
+      lwres_getnamebyaddr(3).
+      lwres_net_ntop(3).
     
    
-  
    
-  
    
-
    BUGS
    
-    
-    
    
+
    
+
    
+
    BUGS
    
+
    
       RFC2133 fails to define what the nonzero return values of
-      
-        getnameinfo(3)
-      
+      getnameinfo(3)
       are.
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_getrrsetbyname.3 b/lib/lwres/man/lwres_getrrsetbyname.3
index cdbeee8088..ac724c0249 100644
--- a/lib/lwres/man/lwres_getrrsetbyname.3
+++ b/lib/lwres/man/lwres_getrrsetbyname.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_getrrsetbyname
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_getrrsetbyname, lwres_freerrset \- retrieve DNS records
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'int\ lwres_getrrsetbyname('u
 .BI "int lwres_getrrsetbyname(const\ char\ *" "hostname" ", unsigned\ int\ " "rdclass" ", unsigned\ int\ " "rdtype" ", unsigned\ int\ " "flags" ", struct\ rrsetinfo\ **" "res" ");"
 .HP \w'void\ lwres_freerrset('u
diff --git a/lib/lwres/man/lwres_getrrsetbyname.html b/lib/lwres/man/lwres_getrrsetbyname.html
index 126e7ea2f0..33c718547a 100644
--- a/lib/lwres/man/lwres_getrrsetbyname.html
+++ b/lib/lwres/man/lwres_getrrsetbyname.html
@@ -18,30 +18,19 @@
 
 
 lwres_getrrsetbyname
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_getrrsetbyname, 
-    lwres_freerrset
-     — retrieve DNS records
-  
    
+
    lwres_getrrsetbyname, lwres_freerrset — retrieve DNS records
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
    
 
 int
@@ -66,7 +55,7 @@ int
 
    
 
    
 
     
    
-
+
    
@@ -74,11 +63,10 @@ void
 
    
 
 void
 lwres_freerrset(
    
 
     
    
 
    
-
-    
    
+
    
       The following structures are used:
     
    
-    
    +
     struct  rdatainfo {
         unsigned int            rdi_length;     /* length of data */
         unsigned char           *rdi_data;      /* record data */
@@ -86,7 +74,7 @@ struct  rdatainfo {
 
    
 
    
     
    
-    
    +
     struct  rrsetinfo {
         unsigned int            rri_flags;      /* RRSET_VALIDATED... */
         unsigned int            rri_rdclass;    /* class number */
@@ -101,12 +89,10 @@ struct  rrsetinfo {
 
    
 
    
     
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    lwres_getrrsetbyname()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_getrrsetbyname()
       gets a set of resource records associated with a
       hostname, class,
       and type.
@@ -114,7 +100,7 @@ struct  rrsetinfo {
       null-terminated string.  The flags field
       is currently unused and must be zero.
     
    
-    
    
+
    
       After a successful call to
       lwres_getrrsetbyname(),
       *res is a pointer to an
@@ -133,7 +119,7 @@ struct  rrsetinfo {
       bit is set, the data has been DNSSEC validated and the
       signatures verified.
     
    
-    
    
+
    
       All of the information returned by
       lwres_getrrsetbyname() is dynamically
       allocated: the rrsetinfo and
@@ -150,63 +136,46 @@ struct  rrsetinfo {
       rrset created by a call to
       lwres_getrrsetbyname().
     
    
-    
    
-  
    
-  
    
-
    RETURN VALUES
    
-    
-    
    lwres_getrrsetbyname()
+
    
+
    
+
    
+
    RETURN VALUES
    
+
    lwres_getrrsetbyname()
       returns zero on success, and one of the following error codes if
       an error occurred:
       
    
-
    
+
    
 
    ERRSET_NONAME
    
-
    
-            
    
+
    
               the name does not exist
-            
    
-          
    
+            
    
 
    ERRSET_NODATA
    
-
    
-            
    
+
    
               the name exists, but does not have data of the desired type
-            
    
-          
    
+            
    
 
    ERRSET_NOMEMORY
    
-
    
-            
    
+
    
               memory could not be allocated
-            
    
-          
    
+            
    
 
    ERRSET_INVAL
    
-
    
-            
    
+
    
               a parameter is invalid
-            
    
-          
    
+            
    
 
    ERRSET_FAIL
    
-
    
-            
    
+
    
               other failure
-            
    
-          
    
+            
    
 
    
-
    
-            
    
-          
    
+
    
 
    
 
    
 
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres(3)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    lwres(3).
     
    
-
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_gnba.3 b/lib/lwres/man/lwres_gnba.3
index 3f2b41c71a..4f65268555 100644
--- a/lib/lwres/man/lwres_gnba.3
+++ b/lib/lwres/man/lwres_gnba.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_gnba
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_gnbarequest_render, lwres_gnbaresponse_render, lwres_gnbarequest_parse, lwres_gnbaresponse_parse, lwres_gnbaresponse_free, lwres_gnbarequest_free \- lightweight resolver getnamebyaddress message handling
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_gnbarequest_render('u
 .BI "lwres_result_t lwres_gnbarequest_render(lwres_context_t\ *" "ctx" ", lwres_gnbarequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
 .HP \w'lwres_result_t\ lwres_gnbaresponse_render('u
@@ -168,8 +171,7 @@ structures referenced via
 .PP
 The getnamebyaddr opcode functions
 \fBlwres_gnbarequest_render()\fR,
-\fBlwres_gnbaresponse_render()\fR
-\fBlwres_gnbarequest_parse()\fR
+\fBlwres_gnbaresponse_render()\fR\fBlwres_gnbarequest_parse()\fR
 and
 \fBlwres_gnbaresponse_parse()\fR
 all return
diff --git a/lib/lwres/man/lwres_gnba.html b/lib/lwres/man/lwres_gnba.html
index 7e65a0ad52..4b8e7d910f 100644
--- a/lib/lwres/man/lwres_gnba.html
+++ b/lib/lwres/man/lwres_gnba.html
@@ -18,39 +18,21 @@
 
 
 lwres_gnba
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_gnbarequest_render, 
-    lwres_gnbaresponse_render, 
-    lwres_gnbarequest_parse, 
-    lwres_gnbaresponse_parse, 
-    lwres_gnbaresponse_free, 
-    lwres_gnbarequest_free
-     — lightweight resolver getnamebyaddress message handling
-  
    
+
    lwres_gnbarequest_render, lwres_gnbaresponse_render, lwres_gnbarequest_parse, lwres_gnbaresponse_parse, lwres_gnbaresponse_free, lwres_gnbarequest_free — lightweight resolver getnamebyaddress message handling
    
 
    
-
-  
    
+
    
 
    Synopsis
    
-
-    
    
+
    
 
     #include <lwres/lwres.h>
 
    
-
-
+
    
 
    
 
 lwres_result_t
@@ -72,8 +54,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
-
+
    
 
    
 
 lwres_result_t
@@ -95,7 +76,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -116,7 +97,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -137,8 +118,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
-
+
    
 
    
 
 void
@@ -152,7 +132,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -166,18 +146,15 @@ void
 
    
 
     
    
 
    
-
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These are low-level routines for creating and parsing
       lightweight resolver address-to-name lookup request and
       response messages.
     
    
-    
    
+
    
       There are four main functions for the getnamebyaddr opcode.
       One render function converts a getnamebyaddr request structure —
       lwres_gnbarequest_t —
@@ -191,17 +168,17 @@ void
       This is complemented by a parse function which converts a packet in
       canonical format to a getnamebyaddr response structure.
     
    
-    
    
+
    
       These structures are defined in
       lwres/lwres.h.
       They are shown below.
     
    
-    
    +
     #define LWRES_OPCODE_GETNAMEBYADDR      0x00010002U
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint32_t  flags;
         lwres_addr_t    addr;
@@ -209,7 +186,7 @@ typedef struct {
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint32_t  flags;
         lwres_uint16_t  naliases;
@@ -223,8 +200,7 @@ typedef struct {
 
    
 
    
     
    
-
-    
    lwres_gnbarequest_render()
+
    lwres_gnbarequest_render()
       uses resolver context ctx to convert
       getnamebyaddr request structure req to
       canonical format.  The packet header structure
@@ -236,8 +212,7 @@ typedef struct {
       lwres_gnbaresponse_t to the lightweight resolver's
       canonical format.
     
    
-
-    
    lwres_gnbarequest_parse()
+
    lwres_gnbarequest_parse()
       uses context ctx to convert the contents of
       packet pkt to a
       lwres_gnbarequest_t structure.  Buffer
@@ -249,8 +224,7 @@ typedef struct {
       semantics as lwres_gnbarequest_parse()
       except it yields a lwres_gnbaresponse_t structure.
     
    
-
-    
    lwres_gnbaresponse_free()
+
    lwres_gnbaresponse_free()
       and lwres_gnbarequest_free() release the
       memory in resolver context ctx that was
       allocated to the lwres_gnbaresponse_t or
@@ -259,12 +233,10 @@ typedef struct {
       ancillary buffers and strings for those structures is also
       discarded.
     
    
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       The getnamebyaddr opcode functions
       lwres_gnbarequest_render(),
       lwres_gnbaresponse_render()
@@ -299,14 +271,11 @@ typedef struct {
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_packet(3)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    lwres_packet(3).
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_hstrerror.3 b/lib/lwres/man/lwres_hstrerror.3
index 1681ced187..ec71b3e0c5 100644
--- a/lib/lwres/man/lwres_hstrerror.3
+++ b/lib/lwres/man/lwres_hstrerror.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_hstrerror
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_herror, lwres_hstrerror \- lightweight resolver error message generation
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'void\ lwres_herror('u
 .BI "void lwres_herror(const\ char\ *" "s" ");"
 .HP \w'const\ char\ *\ lwres_hstrerror('u
diff --git a/lib/lwres/man/lwres_hstrerror.html b/lib/lwres/man/lwres_hstrerror.html
index 99f7992dc5..0f4dbe831c 100644
--- a/lib/lwres/man/lwres_hstrerror.html
+++ b/lib/lwres/man/lwres_hstrerror.html
@@ -18,37 +18,26 @@
 
 
 lwres_hstrerror
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_herror, 
-    lwres_hstrerror
-     — lightweight resolver error message generation
-  
    
+
    lwres_herror, lwres_hstrerror — lightweight resolver error message generation
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/netdb.h>
    
-
+
    
 
 void
 lwres_herror(
 const char *s);
 
    
 
     
    
-
+
    
@@ -56,79 +45,57 @@ const char *
 
    
 
 const char *
 lwres_hstrerror(
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_herror()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_herror()
       prints the string s on
       stderr followed by the string generated by
       lwres_hstrerror() for the error code stored
       in the global variable lwres_h_errno.
     
    
-
-    
    lwres_hstrerror()
+
    lwres_hstrerror()
       returns an appropriate string for the error code gievn by
       err.  The values of the error codes and
       messages are as follows:
 
       
    
-
    
+
    
 
    NETDB_SUCCESS
    
-
    
-            
    Resolver Error 0 (no error)
-            
    
-          
    
+
    Resolver Error 0 (no error)
+            
    
 
    HOST_NOT_FOUND
    
-
    
-            
    Unknown host
-            
    
-          
    
+
    Unknown host
+            
    
 
    TRY_AGAIN
    
-
    
-            
    Host name lookup failure
-            
    
-          
    
+
    Host name lookup failure
+            
    
 
    NO_RECOVERY
    
-
    
-            
    Unknown server error
-            
    
-          
    
+
    Unknown server error
+            
    
 
    NO_DATA
    
-
    
-            
    No address associated with name
-            
    
-          
    
+
    No address associated with name
+            
    
 
    
 
    
     
    
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       The string Unknown resolver error is returned by
       lwres_hstrerror()
       when the value of
       lwres_h_errno
       is not a valid error code.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        herror(3)
-      ,
+
    
+
    
+
    SEE ALSO
    
+
    herror(3),
 
-      
-        lwres_hstrerror(3)
-      .
+      lwres_hstrerror(3).
     
    
-
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_inetntop.3 b/lib/lwres/man/lwres_inetntop.3
index 3ddd05c966..077bbf609b 100644
--- a/lib/lwres/man/lwres_inetntop.3
+++ b/lib/lwres/man/lwres_inetntop.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_inetntop
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_net_ntop \- lightweight resolver IP address presentation
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'const\ char\ *\ lwres_net_ntop('u
 .BI "const char * lwres_net_ntop(int\ " "af" ", const\ void\ *" "src" ", char\ *" "dst" ", size_t\ " "size" ");"
 .SH "DESCRIPTION"
diff --git a/lib/lwres/man/lwres_inetntop.html b/lib/lwres/man/lwres_inetntop.html
index bbedd780d2..1e08e7a768 100644
--- a/lib/lwres/man/lwres_inetntop.html
+++ b/lib/lwres/man/lwres_inetntop.html
@@ -18,29 +18,19 @@
 
 
 lwres_inetntop
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_net_ntop
-     — lightweight resolver IP address presentation
-  
    
+
    lwres_net_ntop — lightweight resolver IP address presentation
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/net.h>
    
-
+
    
 
    
 
 const char *
@@ -62,13 +52,10 @@ const char *
 
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_net_ntop()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_net_ntop()
       converts an IP address of protocol family
       af — IPv4 or IPv6 — at
       location src from network format to its
@@ -76,21 +63,17 @@ const char *
       that string would be a dotted-decimal.  An IPv6 address would be
       represented in colon notation as described in RFC1884.
     
    
-
-    
    
+
    
       The generated string is copied to dst
       provided
       size indicates it is long enough to
       store the
       ASCII representation of the address.
     
    
-
-  
    
-  
    
-
    RETURN VALUES
    
-    
-
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       If successful, the function returns dst:
       a pointer to a string containing the presentation format of the
       address.  lwres_net_ntop() returns
@@ -100,21 +83,13 @@ const char *
       not
       supported.
     
    
-
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        RFC1884
-      ,
-      
-        inet_ntop(3)
-      ,
-      
-        errno(3)
-      .
+
    
+
    
+
    SEE ALSO
    
+
    RFC1884,
+      inet_ntop(3),
+      errno(3).
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_noop.3 b/lib/lwres/man/lwres_noop.3
index d5846193c2..423cdd301d 100644
--- a/lib/lwres/man/lwres_noop.3
+++ b/lib/lwres/man/lwres_noop.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_noop
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_nooprequest_render, lwres_noopresponse_render, lwres_nooprequest_parse, lwres_noopresponse_parse, lwres_noopresponse_free, lwres_nooprequest_free \- lightweight resolver no\-op message handling
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_nooprequest_render('u
 .BI "lwres_result_t lwres_nooprequest_render(lwres_context_t\ *" "ctx" ", lwres_nooprequest_t\ *" "req" ", lwres_lwpacket_t\ *" "pkt" ", lwres_buffer_t\ *" "b" ");"
 .HP \w'lwres_result_t\ lwres_noopresponse_render('u
@@ -168,8 +171,7 @@ structures referenced via
 .PP
 The no\-op opcode functions
 \fBlwres_nooprequest_render()\fR,
-\fBlwres_noopresponse_render()\fR
-\fBlwres_nooprequest_parse()\fR
+\fBlwres_noopresponse_render()\fR\fBlwres_nooprequest_parse()\fR
 and
 \fBlwres_noopresponse_parse()\fR
 all return
diff --git a/lib/lwres/man/lwres_noop.html b/lib/lwres/man/lwres_noop.html
index d95f3a52c4..6f67cab984 100644
--- a/lib/lwres/man/lwres_noop.html
+++ b/lib/lwres/man/lwres_noop.html
@@ -18,35 +18,20 @@
 
 
 lwres_noop
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_nooprequest_render, 
-    lwres_noopresponse_render, 
-    lwres_nooprequest_parse, 
-    lwres_noopresponse_parse, 
-    lwres_noopresponse_free, 
-    lwres_nooprequest_free
-     — lightweight resolver no-op message handling
-  
    
+
    lwres_nooprequest_render, lwres_noopresponse_render, lwres_nooprequest_parse, lwres_noopresponse_parse, lwres_noopresponse_free, lwres_nooprequest_free — lightweight resolver no-op message handling
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
     #include <lwres/lwres.h>
    
-
+
    
 
    
 
 lwres_result_t
@@ -67,7 +52,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -88,7 +73,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -109,7 +94,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -130,7 +115,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -143,7 +128,7 @@ void
 
    
 
    
 
     
    
-
+
    
 
    
 
 void
@@ -157,22 +142,21 @@ void
 
    
 
     
    
 
    
-  
    
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These are low-level routines for creating and parsing
       lightweight resolver no-op request and response messages.
     
    
-    
    
+
    
       The no-op message is analogous to a ping
       packet:
       a packet is sent to the resolver daemon and is simply echoed back.
       The opcode is intended to allow a client to determine if the server is
       operational or not.
     
    
-    
    
+
    
       There are four main functions for the no-op opcode.
       One render function converts a no-op request structure —
       lwres_nooprequest_t —
@@ -185,18 +169,18 @@ void
       This is complemented by a parse function which converts a packet in
       canonical format to a no-op response structure.
     
    
-    
    
+
    
       These structures are defined in
       lwres/lwres.h.
 
       They are shown below.
     
    
-    
    +
     #define LWRES_OPCODE_NOOP       0x00000000U
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint16_t  datalength;
         unsigned char   *data;
@@ -204,7 +188,7 @@ typedef struct {
 
    
 
    
     
    
-    
    +
     typedef struct {
         lwres_uint16_t  datalength;
         unsigned char   *data;
@@ -212,13 +196,12 @@ typedef struct {
 
    
 
    
     
    
-    
    
+
    
       Although the structures have different types, they are identical.
       This is because the no-op opcode simply echos whatever data was sent:
       the response is therefore identical to the request.
     
    
-
-    
    lwres_nooprequest_render()
+
    lwres_nooprequest_render()
       uses resolver context ctx to convert
       no-op request structure req to canonical
       format.  The packet header structure pkt
@@ -231,8 +214,7 @@ typedef struct {
       lwres_noopresponse_t to the lightweight resolver's
       canonical format.
     
    
-
-    
    lwres_nooprequest_parse()
+
    lwres_nooprequest_parse()
       uses context ctx to convert the contents
       of packet pkt to a
       lwres_nooprequest_t structure.  Buffer
@@ -244,20 +226,17 @@ typedef struct {
       semantics as lwres_nooprequest_parse()
       except it yields a lwres_noopresponse_t structure.
     
    
-
-    
    lwres_noopresponse_free()
+
    lwres_noopresponse_free()
       and lwres_nooprequest_free() release the
       memory in resolver context ctx that was
       allocated to the lwres_noopresponse_t or
       lwres_nooprequest_t structures referenced via
       structp.
     
    
-
-  
    
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       The no-op opcode functions
       lwres_nooprequest_render(),
 
@@ -293,14 +272,11 @@ typedef struct {
       lwres_lwpacket_t
       indicate that the packet is not a response to an earlier query.
     
    
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_packet(3)
-      
+
    
+
    
+
    SEE ALSO
    
+
    lwres_packet(3)
     
    
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_packet.3 b/lib/lwres/man/lwres_packet.3
index 4ddf635d71..8f5c020534 100644
--- a/lib/lwres/man/lwres_packet.3
+++ b/lib/lwres/man/lwres_packet.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_packet
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_lwpacket_renderheader, lwres_lwpacket_parseheader \- lightweight resolver packet handling functions
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_lwpacket_renderheader('u
 .BI "lwres_result_t lwres_lwpacket_renderheader(lwres_buffer_t\ *" "b" ", lwres_lwpacket_t\ *" "pkt" ");"
 .HP \w'lwres_result_t\ lwres_lwpacket_parseheader('u
@@ -158,8 +161,7 @@ return the hostname for the given address\&. The lwres_gnba_*() functions should
 .PP
 \fBlwres_lwpacket_renderheader()\fR
 transfers the contents of lightweight resolver packet structure
-\fBlwres_lwpacket_t\fR
-\fI*pkt\fR
+\fBlwres_lwpacket_t\fR\fI*pkt\fR
 in network byte order to the lightweight resolver buffer,
 \fI*b\fR\&.
 .PP
diff --git a/lib/lwres/man/lwres_packet.html b/lib/lwres/man/lwres_packet.html
index 2d9fb91dfc..4116443108 100644
--- a/lib/lwres/man/lwres_packet.html
+++ b/lib/lwres/man/lwres_packet.html
@@ -18,30 +18,19 @@
 
 
 lwres_packet
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_lwpacket_renderheader, 
-    lwres_lwpacket_parseheader
-     — lightweight resolver packet handling functions
-  
    
+
    lwres_lwpacket_renderheader, lwres_lwpacket_parseheader — lightweight resolver packet handling functions
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/lwpacket.h>
    
-
+
    
 
    
 
 lwres_result_t
@@ -54,7 +43,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -68,23 +57,21 @@ lwres_result_t
 
    
 
     
    
 
    
-  
    
-  
    
-
    DESCRIPTION
    
-    
-    
    
+
    
+
    
+
    DESCRIPTION
    
+
    
       These functions rely on a
       struct lwres_lwpacket
       which is defined in
       lwres/lwpacket.h.
     
    
-
-    
    +
     typedef struct lwres_lwpacket lwres_lwpacket_t;
       
    
 
    
     
    
-    
    +
     struct lwres_lwpacket {
         lwres_uint32_t          length;
         lwres_uint16_t          version;
@@ -99,32 +86,26 @@ struct lwres_lwpacket {
 
    
 
    
     
    
-
-    
    
+
    
       The elements of this structure are:
       
    
-
    
+
    
 
    length
    
-
    
-            
    
+
    
               the overall packet length, including the entire packet header.
               This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
               calls.
-            
    
-          
    
+            
    
 
    version
    
-
    
-            
    
+
    
               the header format. There is currently only one format,
               LWRES_LWPACKETVERSION_0.
 
               This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
               calls.
-            
    
-          
    
+            
    
 
    pktflags
    
-
    
-            
    
+
    
               library-defined flags for this packet: for instance whether the
               packet
               is a request or a reply. Flag values can be set, but not defined
@@ -135,11 +116,9 @@ struct lwres_lwpacket {
               LWRES_LWPACKETFLAG_RESPONSE bit, which is set by the library in
               the
               lwres_gabn_*() and lwres_gnba_*() calls.
-            
    
-          
    
+            
    
 
    serial
    
-
    
-            
    
+
    
               is set by the requestor and is returned in all replies. If two
               or more
               packets from the same source have the same serial number and are
@@ -148,11 +127,9 @@ struct lwres_lwpacket {
               latter ones
               may be dropped.
               This field must be set by the application.
-            
    
-          
    
+            
    
 
    opcode
    
-
    
-            
    
+
    
               indicates the operation.
               Opcodes between 0x00000000 and 0x03ffffff are
               reserved for use by the lightweight resolver library. Opcodes
@@ -160,11 +137,9 @@ struct lwres_lwpacket {
               0x04000000 and 0xffffffff are application defined.
               This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
               calls.
-            
    
-          
    
+            
    
 
    result
    
-
    
-            
    
+
    
               is only valid for replies.
               Results between 0x04000000 and 0xffffffff are application
               defined.
@@ -172,91 +147,73 @@ struct lwres_lwpacket {
               library use.
               This field is filled in by the lwres_gabn_*() and lwres_gnba_*()
               calls.
-            
    
-          
    
+            
    
 
    recvlength
    
-
    
-            
    
+
    
               is the maximum buffer size that the receiver can handle on
               requests
               and the size of the buffer needed to satisfy a request when the
               buffer
               is too large for replies.
               This field is supplied by the application.
-            
    
-          
    
+            
    
 
    authtype
    
-
    
-            
    
+
    
               defines the packet level authentication that is used.
               Authorisation types between 0x1000 and 0xffff are application
               defined
               and types between 0x0000 and 0x0fff are reserved for library
               use.
               Currently these are not used and must be zero.
-            
    
-          
    
+            
    
 
    authlen
    
-
    
-            
    
+
    
               gives the length of the authentication data.
               Since packet authentication is currently not used, this must be
               zero.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-    
    
+
    
       The following opcodes are currently defined:
       
    
-
    
+
    
 
    NOOP
    
-
    
-            
    
+
    
               Success is always returned and the packet contents are echoed.
               The lwres_noop_*() functions should be used for this type.
-            
    
-          
    
+            
    
 
    GETADDRSBYNAME
    
-
    
-            
    
+
    
               returns all known addresses for a given name.
               The lwres_gabn_*() functions should be used for this type.
-            
    
-          
    
+            
    
 
    GETNAMEBYADDR
    
-
    
-            
    
+
    
               return the hostname for the given address.
               The lwres_gnba_*() functions should be used for this type.
-            
    
-          
    
+            
    
 
    
 
    
     
    
-
-    
    lwres_lwpacket_renderheader()
+
    lwres_lwpacket_renderheader()
       transfers the contents of lightweight resolver packet structure
       lwres_lwpacket_t *pkt in
       network byte order to the lightweight resolver buffer,
       *b.
     
    
-
-    
    lwres_lwpacket_parseheader()
+
    lwres_lwpacket_parseheader()
       performs the converse operation.  It transfers data in network
       byte order from buffer *b to resolver
       packet *pkt.  The contents of the buffer
       b should correspond to a
       lwres_lwpacket_t.
     
    
-
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       Successful calls to
       lwres_lwpacket_renderheader() and
       lwres_lwpacket_parseheader() return
@@ -266,7 +223,6 @@ struct lwres_lwpacket {
       functions
       return LWRES_R_UNEXPECTEDEND.
     
    
-
-  
    
+
    
 
    
 
diff --git a/lib/lwres/man/lwres_resutil.3 b/lib/lwres/man/lwres_resutil.3
index 0cb78efbe6..991fb05ca4 100644
--- a/lib/lwres/man/lwres_resutil.3
+++ b/lib/lwres/man/lwres_resutil.3
@@ -18,7 +18,7 @@
 '\" t
 .\"     Title: lwres_resutil
 .\"    Author: 
-.\" Generator: DocBook XSL Stylesheets v1.76.1 
+.\" Generator: DocBook XSL Stylesheets v1.78.1 
 .\"      Date: 2007-06-18
 .\"    Manual: BIND9
 .\"    Source: ISC
@@ -47,9 +47,12 @@
 .SH "NAME"
 lwres_string_parse, lwres_addr_parse, lwres_getaddrsbyname, lwres_getnamebyaddr \- lightweight resolver utility functions
 .SH "SYNOPSIS"
+.sp
+.ft B
 .nf
 #include 
 .fi
+.ft
 .HP \w'lwres_result_t\ lwres_string_parse('u
 .BI "lwres_result_t lwres_string_parse(lwres_buffer_t\ *" "b" ", char\ **" "c" ", lwres_uint16_t\ *" "len" ");"
 .HP \w'lwres_result_t\ lwres_addr_parse('u
diff --git a/lib/lwres/man/lwres_resutil.html b/lib/lwres/man/lwres_resutil.html
index 16afd860b3..5855978c2f 100644
--- a/lib/lwres/man/lwres_resutil.html
+++ b/lib/lwres/man/lwres_resutil.html
@@ -18,32 +18,19 @@
 
 
 lwres_resutil
-
+
 
-
    
-
    
-  
-  
-
-  
-
-  
-
-  
    
+
    
+
    
+
    
 
    Name
    
-
    
-    lwres_string_parse, 
-    lwres_addr_parse, 
-    lwres_getaddrsbyname, 
-    lwres_getnamebyaddr
-     — lightweight resolver utility functions
-  
    
+
    lwres_string_parse, lwres_addr_parse, lwres_getaddrsbyname, lwres_getnamebyaddr — lightweight resolver utility functions
    
 
    
-  
    
+
    
 
    Synopsis
    
-    
    
+
    
 
    #include <lwres/lwres.h>
    
-
+
    
 
    
 
 lwres_result_t
@@ -60,7 +47,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -73,7 +60,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -94,7 +81,7 @@ lwres_result_t
 
    
 
    
 
     
    
-
+
    
 
    
 
 lwres_result_t
@@ -120,13 +107,10 @@ lwres_result_t
 
    
 
     
    
 
    
-  
    
-
-  
    
-
    DESCRIPTION
    
-    
-
-    
    lwres_string_parse()
+
    
+
    
+
    DESCRIPTION
    
+
    lwres_string_parse()
       retrieves a DNS-encoded string starting the current pointer of
       lightweight resolver buffer b: i.e.
       b->current.  When the function returns,
@@ -137,8 +121,7 @@ lwres_result_t
       string length, the encoded string, and the trailing
       NULL character.
     
    
-
-    
    lwres_addr_parse()
+
    lwres_addr_parse()
       extracts an address from the buffer b.
       The buffer's current pointer b->current
       is presumed to point at an encoded address: the address preceded
@@ -151,12 +134,10 @@ lwres_result_t
       next byte of available data in the buffer following the encoded
       address.
     
    
-
-    
    lwres_getaddrsbyname()
+
    lwres_getaddrsbyname()
       and lwres_getnamebyaddr() use the
       lwres_gnbaresponse_t structure defined below:
     
    
-
 
     typedef struct {
         lwres_uint32_t          flags;
@@ -171,17 +152,13 @@ typedef struct {
         size_t                  baselen;
 } lwres_gabnresponse_t;
 
    
-
-    
    
+
    
       The contents of this structure are not manipulated directly but
       they are controlled through the
-      
-        lwres_gabn(3)
-      
+      lwres_gabn(3)
       functions.
     
    
-
-    
    
+
    
       The lightweight resolver uses
       lwres_getaddrsbyname() to perform
       forward lookups.
@@ -195,8 +172,7 @@ typedef struct {
       LWRES_ADDRTYPE_V6 for IPv6 addresses.  Results of the
       lookup are returned in *structp.
     
    
-
-    
    lwres_getnamebyaddr()
+
    lwres_getnamebyaddr()
       performs reverse lookups.  Resolver context
       ctx is used for memory allocation.  The
       address type is indicated by addrtype:
@@ -207,12 +183,10 @@ typedef struct {
       function call is made available through
       *structp.
     
    
-  
    
-
-  
    
-
    RETURN VALUES
    
-    
-    
    
+
    
+
    
+
    RETURN VALUES
    
+
    
       Successful calls to
       lwres_string_parse()
       and
@@ -226,18 +200,16 @@ typedef struct {
       if the buffer has less space than expected for the components of the
       encoded string or address.
     
    
-
-    
    lwres_getaddrsbyname()
+
    lwres_getaddrsbyname()
       returns LWRES_R_SUCCESS on success and it
       returns LWRES_R_NOTFOUND if the hostname
       name could not be found.
     
    
-    
    LWRES_R_SUCCESS
+
    LWRES_R_SUCCESS
       is returned by a successful call to
       lwres_getnamebyaddr().
     
    
-
-    
    
+
    
       Both
       lwres_getaddrsbyname()
       and
@@ -249,20 +221,13 @@ typedef struct {
       if the buffers used for sending queries and receiving replies are too
       small.
     
    
+
    
+
    
+
    SEE ALSO
    
+
    lwres_buffer(3),
 
-  
    
-  
    
-
    SEE ALSO
    
-    
-    
    
-        lwres_buffer(3)
-      ,
-
-      
-        lwres_gabn(3)
-      .
+      lwres_gabn(3).
     
    
-
-  
    
+