Commit b310dc7f authored by Tinderbox User's avatar Tinderbox User

Merge branch 'prep-release' into v9_16_2-release

parents e69c9b7f 9ac41ef8
Pipeline #39278 canceled with stages
in 4 seconds
--- 9.16.2 released ---
5383. [func] Add a quota attach function with a callback and clean up
the isc_quota API. [GL !3280]
......
......@@ -9,7 +9,7 @@
'\" t
.\" Title: host
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 2009-01-20
.\" Manual: BIND9
.\" Source: ISC
......@@ -38,8 +38,8 @@
.SH "NAME"
host \- DNS lookup utility
.SH "SYNOPSIS"
.HP 5
\fBhost\fR [\fB\-aACdlnrsTUwv\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]
.HP \w'\fBhost\fR\ 'u
\fBhost\fR [\fB\-aACdlnrsTUwv\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-N\ \fR\fB\fIndots\fR\fR] [\fB\-p\ \fR\fB\fIport\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
\fBhost\fR
......@@ -138,6 +138,11 @@ directive in
/etc/resolv\&.conf\&.
.RE
.PP
\-p \fIport\fR
.RS 4
Specify the port on the server to query\&. The default is 53\&.
.RE
.PP
\-r
.RS 4
Non\-recursive query: Setting this option clears the RD (recursion desired) bit in the query\&. This should mean that the name server receiving the query will not attempt to resolve
......
......@@ -36,6 +36,7 @@
[<code class="option">-aACdlnrsTUwv</code>]
[<code class="option">-c <em class="replaceable"><code>class</code></em></code>]
[<code class="option">-N <em class="replaceable"><code>ndots</code></em></code>]
[<code class="option">-p <em class="replaceable"><code>port</code></em></code>]
[<code class="option">-R <em class="replaceable"><code>number</code></em></code>]
[<code class="option">-t <em class="replaceable"><code>type</code></em></code>]
[<code class="option">-W <em class="replaceable"><code>wait</code></em></code>]
......@@ -165,6 +166,12 @@
in <code class="filename">/etc/resolv.conf</code>.
</p>
</dd>
<dt><span class="term">-p <em class="replaceable"><code>port</code></em></span></dt>
<dd>
<p>
Specify the port on the server to query. The default is 53.
</p>
</dd>
<dt><span class="term">-r</span></dt>
<dd>
<p>
......
......@@ -10,12 +10,12 @@
.\" Title: named.conf
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 2020-02-12
.\" Date: 2020-03-12
.\" Manual: BIND9
.\" Source: ISC
.\" Language: English
.\"
.TH "NAMED\&.CONF" "5" "2020\-02\-12" "ISC" "BIND9"
.TH "NAMED\&.CONF" "5" "2020\-03\-12" "ISC" "BIND9"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
......@@ -13,7 +13,7 @@
<refentry xmlns:db="http://docbook.org/ns/docbook" version="5.0" xml:id="man.named.conf">
<info>
<date>2020-02-12</date>
<date>2020-03-12</date>
</info>
<refentryinfo>
<corpname>ISC</corpname>
......
......@@ -719,7 +719,10 @@ ret=0
$RNDCCMD 10.53.0.3 addzone "test4.baz" '{ type master; file "e.db"; };' > /dev/null 2>&1 || ret=1
$RNDCCMD 10.53.0.3 addzone "test5.baz" '{ type master; file "e.db"; };' > /dev/null 2>&1 || ret=1
$RNDCCMD 10.53.0.3 addzone '"test/.baz"' '{ type master; check-names ignore; file "e.db"; };' > /dev/null 2>&1 || ret=1
$RNDCCMD 10.53.0.3 addzone '"test\".baz"' '{ type master; check-names ignore; file "e.db"; };' > /dev/null 2>&1 || ret=1
# FIXME: This check triggers a known issue in non-LMDB BIND builds
if [ -n "${NZD}" ]; then
$RNDCCMD 10.53.0.3 addzone '"test\".baz"' '{ type master; check-names ignore; file "e.db"; };' > /dev/null 2>&1 || ret=1
fi
$PERL $SYSTEMTESTTOP/stop.pl addzone ns3
$PERL $SYSTEMTESTTOP/start.pl --noclean --restart --port ${PORT} addzone ns3 || ret=1
retry_quiet 10 _check_version_bind || ret=1
......
......@@ -614,6 +614,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -146,6 +146,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -856,6 +856,6 @@ controls {
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -2915,6 +2915,6 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -9865,79 +9865,72 @@ view "external" {
<table border="1">
<colgroup>
<col class="1">
<col width="4.017in" class="2">
<col class="2">
</colgroup>
<tbody>
<tbody valign="top">
<tr>
<td>
<td valign="top">
<p>
<code class="varname">master</code>
<code class="varname">primary</code>
</p>
</td>
<td>
<td valign="top">
<p>
The server has a master copy of the data
for the zone and will be able to provide authoritative
answers for it. Type <code class="varname">primary</code> is
a synonym for <code class="varname">master</code>.
answers for it. Type <code class="varname">master</code> is
a synonym for <code class="varname">primary</code>.
</p>
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">slave</code>
<code class="varname">secondary</code>
</p>
</td>
<td>
<td valign="top">
<p>
A slave zone is a replica of a master
zone. Type <code class="varname">secondary</code> is a
synonym for <code class="varname">slave</code>.
A secondary zone is a replica of a master
zone. Type <code class="varname">slave</code> is a
synonym for <code class="varname">secondary</code>.
The <span class="command"><strong>masters</strong></span> list
specifies one or more IP addresses
of master servers that the slave contacts to update
its copy of the zone.
Masters list elements can also be names of other
masters lists.
By default, transfers are made from port 53 on the
servers; this can
be changed for all servers by specifying a port number
before the
list of IP addresses, or on a per-server basis after
the IP address.
its copy of the zone. Masters list elements can
also be names of other masters lists. By default,
transfers are made from port 53 on the servers;
this can be changed for all servers by specifying
a port number before the list of IP addresses,
or on a per-server basis after the IP address.
Authentication to the master can also be done with
per-server TSIG keys.
If a file is specified, then the
per-server TSIG keys. If a file is specified, then the
replica will be written to this file whenever the zone
is changed,
and reloaded from this file on a server restart. Use
of a file is
recommended, since it often speeds server startup and
eliminates
a needless waste of bandwidth. Note that for large
numbers (in the
tens or hundreds of thousands) of zones per server, it
is best to
use a two-level naming scheme for zone filenames. For
example,
a slave server for the zone <code class="literal">example.com</code> might place
is changed, and reloaded from this file on a server
restart. Use of a file is recommended, since it
often speeds server startup and eliminates a
needless waste of bandwidth. Note that for large
numbers (in the tens or hundreds of thousands) of
zones per server, it is best to use a two-level
naming scheme for zone filenames. For example,
a slave server for the zone
<code class="literal">example.com</code> might place
the zone contents into a file called
<code class="filename">ex/example.com</code> where <code class="filename">ex/</code> is
just the first two letters of the zone name. (Most
operating systems
<code class="filename">ex/example.com</code> where
<code class="filename">ex/</code> is just the first two
letters of the zone name. (Most operating systems
behave very slowly if you put 100000 files into
a single directory.)
</p>
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">stub</code>
</p>
</td>
<td>
<td valign="top">
<p>
A stub zone is similar to a slave zone,
except that it replicates only the NS records of a
......@@ -9990,66 +9983,63 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">mirror</code>
</p>
</td>
<td>
<p>
<span class="bold"><strong>Note:</strong></span> using
this zone type with any zone other than the root
zone should be considered
<span class="emphasis"><em>experimental</em></span> and may cause
performance issues, especially for zones which
are large and/or frequently updated.
</p>
<td valign="top">
<p>
A mirror zone acts like a zone of type
<strong class="userinput"><code>secondary</code></strong> whose data is
subject to DNSSEC validation before being used
in answers. Validation is performed during the
zone transfer process (for both AXFR and IXFR),
and again when the zone file is loaded from disk
when <span class="command"><strong>named</strong></span> is restarted. If
A mirror zone is similar to a zone of type
<strong class="userinput"><code>secondary</code></strong>, except its data
is subject to DNSSEC validation before being used
in answers. Validation is applied to the entire
zone during the zone transfer process, and again
when the zone file is loaded from disk when
<span class="command"><strong>named</strong></span> is restarted. If
validation of a new version of a mirror zone
fails, a retransfer is scheduled and the most
recent correctly validated version of that zone
is used until it expires; if a newer version of
that zone is later correctly validated, it
replaces the previously used version. If no
usable zone data is available for a mirror zone
(either because it was never loaded from disk
and has not yet been transferred from a primary
server or because its most recent correctly
validated version expired), traditional DNS
recursion will be used to look up the answers
instead.
</p>
<p>
While any zone may be configured with this type,
it is intended to be used to set up a fast local
copy of the root zone, similar to the one
described in RFC 7706. Note, however, that
mirror zones are not supposed to augment the
example configuration provided by RFC 7706 but
rather to replace it altogether.
</p>
<p>
A default list of primary servers for the IANA
root zone is built into <span class="command"><strong>named</strong></span>
and thus its mirroring can be enabled using the
following configuration:
is used until it either expires or a newer version
validates correctly. If no usable zone data is
available for a mirror zone at all, either due to
transfer failure or expiration, traditional DNS
recursion is used to look up the answers instead.
Mirror zones cannot be used in a view that does
not have recursion enabled.
</p>
<p>
Answers coming from a mirror zone look almost
exactly like answers from a zone of type
<strong class="userinput"><code>secondary</code></strong>, with the
notable exceptions that the AA bit
("authoritative answer") is not set, and the AD
bit ("authenticated data") is.
</p>
<p>
Mirror zones are intended to be used to set up a
fast local copy of the root zone, similar to the
one described in RFC 7706. A default list of primary
servers for the IANA root zone is built into
<span class="command"><strong>named</strong></span> and thus its mirroring
can be enabled using the following configuration:
</p>
<pre class="programlisting">zone "." {
type mirror;
};</pre>
<p>
In order to set up mirroring of any other zone,
an explicit list of primary servers needs to be
provided using the <span class="command"><strong>masters</strong></span>
option (see <a class="xref" href="Bv9ARM.ch05.html#masters_grammar" title="masters Statement Grammar">the section called &#8220;<span class="command"><strong>masters</strong></span> Statement Grammar&#8221;</a>
for details).
Other zones can be configured as mirror zones,
but this should be considered
<span class="emphasis"><em>experimental</em></span> and may cause
performance issues, especially with zones that
are large and/or frequently updated.
Mirroring a zone other than root requires an
explicit list of primary servers to be provided
using the <span class="command"><strong>masters</strong></span> option
(see <a class="xref" href="Bv9ARM.ch05.html#masters_grammar" title="masters Statement Grammar">the section called &#8220;<span class="command"><strong>masters</strong></span> Statement Grammar&#8221;</a>
for details), and a key-signing key (KSK)
for the specified zone to be explicitly
configured as a trust anchor.
</p>
<p>
To make mirror zone contents persist between
......@@ -10057,57 +10047,20 @@ view "external" {
<a class="xref" href="Bv9ARM.ch05.html#file_option"><span class="command"><strong>file</strong></span></a>
option.
</p>
<p>
Mirror zone validation always happens for the
entire zone contents, i.e. no "incremental
validation" takes place, even for IXFRs. This
is required to ensure that each version of the
zone used by the resolver is fully
self-consistent with respect to DNSSEC. Other,
more efficient zone verification methods may be
added in the future.
</p>
<p>
For validation to succeed, a key-signing key
(KSK) for the zone must be configured as a trust
anchor in <code class="filename">named.conf</code>: that
is, a key for the zone must be specified in
<span class="command"><strong>trust-anchors</strong></span>. In the case
of the root zone, you may also rely on the
built-in root trust anchor, which is enabled
when <a class="xref" href="Bv9ARM.ch05.html#dnssec_validation"><span class="command"><strong>dnssec-validation</strong></span></a> is set to the
default value <strong class="userinput"><code>auto</code></strong>.
</p>
<p>
Answers coming from a mirror zone look almost
exactly like answers from a zone of type
<strong class="userinput"><code>secondary</code></strong>, with the
notable exceptions that the AA bit
("authoritative answer") is not set, and the AD
bit ("authenticated data") is.
</p>
<p>
Since mirror zones are intended to be used by
recursive resolvers, adding one to a view with
recursion disabled is considered to be a
configuration error.
</p>
<p>
When configuring NOTIFY for a mirror zone, only
<strong class="userinput"><code>notify no;</code></strong> and
<strong class="userinput"><code>notify explicit;</code></strong> can be
used. Using any other <span class="command"><strong>notify</strong></span>
setting at the zone level is a configuration
error. Using any other
used at the zone level. Using any other
<span class="command"><strong>notify</strong></span> setting at the
<span class="command"><strong>options</strong></span> or
<span class="command"><strong>view</strong></span> level will cause
that setting to be overridden with
<strong class="userinput"><code>notify explicit;</code></strong> for the
mirror zone in question. Since the global
default for the <span class="command"><strong>notify</strong></span> option
is <strong class="userinput"><code>yes</code></strong>, mirror zones are
by default configured with
mirror zone. The global default for the
<span class="command"><strong>notify</strong></span> option is
<strong class="userinput"><code>yes</code></strong>, so mirror
zones are by default configured with
<strong class="userinput"><code>notify explicit;</code></strong>.
</p>
<p>
......@@ -10118,12 +10071,12 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">static-stub</code>
</p>
</td>
<td>
<td valign="top">
<p>
A static-stub zone is similar to a stub zone
with the following exceptions:
......@@ -10167,12 +10120,12 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">forward</code>
</p>
</td>
<td>
<td valign="top">
<p>
A "forward zone" is a way to configure
forwarding on a per-domain basis. A <span class="command"><strong>zone</strong></span> statement
......@@ -10200,12 +10153,12 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">hint</code>
</p>
</td>
<td>
<td valign="top">
<p>
The initial set of root name servers is
specified using a "hint zone". When the server starts
......@@ -10221,12 +10174,12 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">redirect</code>
</p>
</td>
<td>
<td valign="top">
<p>
Redirect zones are used to provide answers to
queries when normal resolution would result in
......@@ -10286,12 +10239,12 @@ view "external" {
</td>
</tr>
<tr>
<td>
<td valign="top">
<p>
<code class="varname">delegation-only</code>
</p>
</td>
<td>
<td valign="top">
<p>
This is used to enforce the delegation-only
status of infrastructure zones (e.g. COM,
......@@ -15348,6 +15301,6 @@ HOST-127.EXAMPLE. MX 0 .
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -360,6 +360,6 @@ allow-query { !{ !10/8; any; }; key example; };
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -191,6 +191,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -36,12 +36,13 @@
<div class="toc">
<p><b>Table of Contents</b></p>
<dl class="toc">
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2">Release Notes for BIND Version 9.16.1</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#id-1.9.2">Release Notes for BIND Version 9.16.2</a></span></dt>
<dd><dl>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes_intro">Introduction</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes_versions">Note on Version Numbering</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes_platforms">Supported Platforms</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes_download">Download</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes-9.16.2">Notes for BIND 9.16.2</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes-9.16.1">Notes for BIND 9.16.1</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes-9.16.0">Notes for BIND 9.16.0</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch08.html#relnotes_license">License</a></span></dt>
......@@ -52,7 +53,7 @@
</div>
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id-1.9.2"></a>Release Notes for BIND Version 9.16.1</h2></div></div></div>
<a name="id-1.9.2"></a>Release Notes for BIND Version 9.16.2</h2></div></div></div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
......@@ -118,6 +119,81 @@
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes-9.16.2"></a>Notes for BIND 9.16.2</h3></div></div></div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="relnotes-9.16.2-security"></a>Security Fixes</h4></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
DNS rebinding protection was ineffective when BIND 9 is configured as
a forwarding DNS server. Found and responsibly reported by Tobias
Klein. [GL #1574]
</p>
</li></ul></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="relnotes-9.16.2-known"></a>Known Issues</h4></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
We have received reports that in some circumstances, receipt of an
IXFR can cause the processing of queries to slow significantly. Some
of these were related to RPZ processing, which has been fixed in this
release (see below). Others appear to occur where there are
NSEC3-related changes (such as an operator changing the NSEC3 salt
used in the hash calculation). These are being investigated.
[GL #1685]
</p>
</li></ul></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="relnotes-9.16.2-changes"></a>Feature Changes</h4></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem">
<p>
The previous DNSSEC sign statistics used lots of memory. The number of
keys to track is reduced to four per zone, which should be enough for
99% of all signed zones. [GL #1179]
</p>
</li></ul></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="relnotes-9.16.2-bugs"></a>Bug Fixes</h4></div></div></div>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">
<p>
When an RPZ policy zone was updated via zone transfer and a large
number of records was deleted, <span class="command"><strong>named</strong></span> could become
nonresponsive for a short period while deleted names were removed from
the RPZ summary database. This database cleanup is now done
incrementally over a longer period of time, reducing such delays.
[GL #1447]
</p>
</li>
<li class="listitem">
<p>
When trying to migrate an already-signed zone from
<span class="command"><strong>auto-dnssec maintain</strong></span> to one based on
<span class="command"><strong>dnssec-policy</strong></span>, the existing keys were immediately
deleted and replaced with new ones. As the key rollover timing
constraints were not being followed, it was possible that some clients
would not have been able to validate responses until all old DNSSEC
information had timed out from caches. BIND now looks at the time
metadata of the existing keys and incorporates it into its DNSSEC
policy operation. [GL #1706]
</p>
</li>
</ul></div>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes-9.16.1"></a>Notes for BIND 9.16.1</h3></div></div></div>
<div class="section">
......@@ -482,6 +558,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -148,6 +148,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
This diff is collapsed.
......@@ -538,6 +538,6 @@ $ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mm
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -210,6 +210,6 @@
</tr>
</table>
</div>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.1 (Stable Release)</p>
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.16.2 (Stable Release)</p>
</body>
</html>
......@@ -10,7 +10,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>BIND 9 Administrator Reference Manual</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="next" href="Bv9ARM.ch01.html" title="Chapter1.Introduction">