regen v9_9
This commit is contained in:
Tinderbox User
@@ -26,14 +26,14 @@
|
||||
<dl>
|
||||
<dt><span class="preface"><a href="#id2542024"> </a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect1"><a href="#id2542012">Release Notes for BIND Version 9.9.6</a></span></dt>
|
||||
<dt><span class="sect1"><a href="#id2542008">Release Notes for BIND Version 9.9.6</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="#relnotes_intro">Introduction</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_download">Download</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_security">Security Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_features">New Features</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_changes">Feature Changes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_features">Bug Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_bugs">Bug Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_thanks">Thank You</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
@@ -45,21 +45,21 @@
|
||||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl>
|
||||
<dt><span class="sect1"><a href="#id2542012">Release Notes for BIND Version 9.9.6</a></span></dt>
|
||||
<dt><span class="sect1"><a href="#id2542008">Release Notes for BIND Version 9.9.6</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="#relnotes_intro">Introduction</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_download">Download</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_security">Security Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_features">New Features</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_changes">Feature Changes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_features">Bug Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_bugs">Bug Fixes</a></span></dt>
|
||||
<dt><span class="sect2"><a href="#relnotes_thanks">Thank You</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2542012"></a>Release Notes for BIND Version 9.9.6</h2></div></div></div>
|
||||
<a name="id2542008"></a>Release Notes for BIND Version 9.9.6</h2></div></div></div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="relnotes_intro"></a>Introduction</h3></div></div></div>
|
||||
@@ -92,12 +92,86 @@
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="relnotes_changes"></a>Feature Changes</h3></div></div></div>
|
||||
<div class="itemizedlist"><ul type="disc"><li><p>None</p></li></ul></div>
|
||||
<div class="itemizedlist"><ul type="disc">
|
||||
<li><p>
|
||||
NXDOMAIN responses to queries of type DS are now cached separately
|
||||
from those for other types. This helps when using "grafted" zones
|
||||
of type forward, for which the parent zone does not contain a
|
||||
delegation, such as local top-level domains. Previously a query
|
||||
of type DS for such a zone could cause the zone apex to be cached
|
||||
as NXDOMAIN, blocking all subsequent queries. (Note: This
|
||||
change is only helpful when DNSSEC validation is not enabled.
|
||||
"Grafted" zones without a delegation in the parent are not a
|
||||
recommended configuration.)
|
||||
</p></li>
|
||||
<li><p>
|
||||
NOTIFY messages that are sent because a zone has been updated
|
||||
are now given priority above NOTIFY messages that were scheduled
|
||||
when the server started up. This should mitigate delays in zone
|
||||
propagation when servers are restarted frequently.
|
||||
</p></li>
|
||||
<li><p>
|
||||
Errors reported when running <span><strong class="command">rndc addzone</strong></span>
|
||||
(e.g., when a zone file cannot be loaded) have been clarified
|
||||
to make it easier to diagnose problems.
|
||||
</p></li>
|
||||
</ul></div>
|
||||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="relnotes_features"></a>Bug Fixes</h3></div></div></div>
|
||||
<div class="itemizedlist"><ul type="disc"><li><p>None</p></li></ul></div>
|
||||
<a name="relnotes_bugs"></a>Bug Fixes</h3></div></div></div>
|
||||
<div class="itemizedlist"><ul type="disc">
|
||||
<li><p>
|
||||
<span><strong class="command">dig</strong></span>, <span><strong class="command">host</strong></span> and
|
||||
<span><strong class="command">nslookup</strong></span> aborted when encountering
|
||||
a name which, after appending search list elements,
|
||||
exceeded 255 bytes. Such names are now skipped, but
|
||||
processing of other names will continue. [RT #36892]
|
||||
</p></li>
|
||||
<li><p>
|
||||
The error message generated when
|
||||
<span><strong class="command">named-checkzone</strong></span> or
|
||||
<span><strong class="command">named-checkconf -z</strong></span> encounters a
|
||||
<code class="option">$TTL</code> directive without a value has
|
||||
been clarified. [RT #37138]
|
||||
</p></li>
|
||||
<li><p>
|
||||
Semicolon characters (;) included in TXT records were
|
||||
incorrectly escaped with a backslash when the record was
|
||||
displayed as text. This is actually only necessary when there
|
||||
are no quotation marks. [RT #37159]
|
||||
</p></li>
|
||||
<li><p>
|
||||
When files opened for writing by <span><strong class="command">named</strong></span>,
|
||||
such as zone journal files, were referenced more than once
|
||||
in <code class="filename">named.conf</code>, it could lead to file
|
||||
corruption as multiple threads wrote to the same file. This
|
||||
is now detected when loading <code class="filename">named.conf</code>
|
||||
and reported as an error. [RT #37172]
|
||||
</p></li>
|
||||
<li><p>
|
||||
<span><strong class="command">dnssec-keygen -S</strong></span> failed to generate successor
|
||||
keys for some algorithm types (including ECDSA and GOST) due to
|
||||
a difference in the content of private key files. This has been
|
||||
corrected. [RT #37183]
|
||||
</p></li>
|
||||
<li><p>
|
||||
UPDATE messages that arrived too soon after
|
||||
an <span><strong class="command">rndc thaw</strong></span> could be lost. [RT #37233]
|
||||
</p></li>
|
||||
<li><p>
|
||||
Forwarding of UPDATE messages did not work when they were
|
||||
signed with SIG(0); they resulted in a BADSIG response code.
|
||||
[RT #37216]
|
||||
</p></li>
|
||||
<li><p>
|
||||
When checking for updates to trust anchors listed in
|
||||
<code class="option">managed-keys</code>, <span><strong class="command">named</strong></span>
|
||||
now revalidates keys based on the current set of
|
||||
active trust anchors, without relying on any cached
|
||||
record of previous validation. [RT #37506]
|
||||
</p></li>
|
||||
</ul></div>
|
||||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
|
||||
Reference in New Issue
Block a user