notes.html revision de283bda6a902c2102a795192eeab3a769001c7d
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<!--
d7201de09b85929a86b157f4b2d91667c68c6b52Automatic Updater -
499b34cea04a46823d003d4c0520c8b03e8513cbBrian Wellington - Permission to use, copy, modify, and/or distribute this software for any
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington - purpose with or without fee is hereby granted, provided that the above
ec5347e2c775f027573ce5648b910361aa926c01Automatic Updater - copyright notice and this permission notice appear in all copies.
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington -
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews - PERFORMANCE OF THIS SOFTWARE.
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews-->
dafcb997e390efa4423883dafd100c975c4095d6Mark Andrews<!-- $Id$ -->
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<html>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<head>
d7201de09b85929a86b157f4b2d91667c68c6b52Automatic Updater<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<title></title>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington</head>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="article" lang="en"><div class="sect1" lang="en">
29747dfe5e073a299b3681e01f5c55540f8bfed7Mark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<a name="id2542126"></a>Release Notes for BIND Version 9.11.0pre-alpha</h2></div></div></div>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<div class="sect2" lang="en">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<div class="titlepage"><div><div><h3 class="title">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<a name="relnotes_intro"></a>Introduction</h3></div></div></div>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington This document summarizes changes since the last production release
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington of BIND on the corresponding major release branch.
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington </p>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt</div>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<div class="sect2" lang="en">
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<div class="titlepage"><div><div><h3 class="title">
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<a name="relnotes_download"></a>Download</h3></div></div></div>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<p>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt The latest versions of BIND 9 software can always be found at
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt <a href="http://www.isc.org/downloads/" target="_top">http://www.isc.org/downloads/</a>.
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt There you will find additional information about each release,
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington source code, and pre-compiled versions for Microsoft Windows
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt operating systems.
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington </p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington</div>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<div class="sect2" lang="en">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<div class="titlepage"><div><div><h3 class="title">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<a name="relnotes_security"></a>Security Fixes</h3></div></div></div>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<div class="itemizedlist"><ul type="disc">
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<li>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington On servers configured to perform DNSSEC validation using
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein managed trust anchors (i.e., keys configured explicitly
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein via <span><strong class="command">managed-keys</strong></span>, or implicitly
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington via <span><strong class="command">dnssec-validation auto;</strong></span> or
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington <span><strong class="command">dnssec-lookaside auto;</strong></span>), revoking
fb827ed6df9a473770fb69a75a455b4ad0d14f52Mark Andrews a trust anchor and sending a new untrusted replacement
fb827ed6df9a473770fb69a75a455b4ad0d14f52Mark Andrews could cause <span><strong class="command">named</strong></span> to crash with an
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington assertion failure. This could occur in the event of a
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington botched key rollover, or potentially as a result of a
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington deliberate attack if the attacker was in position to
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt monitor the victim's DNS traffic.
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt </p>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington This flaw was discovered by Jan-Piet Mens, and is
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington disclosed in CVE-2015-1349. [RT #38344]
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein </p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington</li>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<li>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt<p>
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt A flaw in delegation handling could be exploited to put
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington <span><strong class="command">named</strong></span> into an infinite loop, in which
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington each lookup of a name server triggered additional lookups
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein of more name servers. This has been addressed by placing
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein limits on the number of levels of recursion
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt <span><strong class="command">named</strong></span> will allow (default 7), and
67adc03ef81fb610f8df093b17f55275ee816754Evan Hunt on the number of queries that it will send before
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington terminating a recursive query (default 50).
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington </p>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<p>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein The recursion depth limit is configured via the
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington <code class="option">max-recursion-depth</code> option, and the query limit
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington via the <code class="option">max-recursion-queries</code> option.
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 </p>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉<p>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 The flaw was discovered by Florian Maury of ANSSI, and is
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 disclosed in CVE-2014-8500. [RT #37580]
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 </p>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉</li>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉<li>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉<p>
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 Two separate problems were identified in BIND's GeoIP code that
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 could lead to an assertion failure. One was triggered by use of
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 both IPv4 and IPv6 address families, the other by referencing
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 a GeoIP database in <code class="filename">named.conf</code> which was
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 not installed. Both are covered by CVE-2014-8680. [RT #37672]
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 [RT #37679]
307d2084502eddc7ce921e5ce439aec3531d90e0Tatuya JINMEI 神明達哉 </p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington A less serious security flaw was also found in GeoIP: changes
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington to the <span><strong class="command">geoip-directory</strong></span> option in
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein <code class="filename">named.conf</code> were ignored when running
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein <span><strong class="command">rndc reconfig</strong></span>. In theory, this could allow
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein <span><strong class="command">named</strong></span> to allow access to unintended clients.
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein </p>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein</li>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein</ul></div>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein</div>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<div class="sect2" lang="en">
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<div class="titlepage"><div><div><h3 class="title">
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<a name="relnotes_features"></a>New Features</h3></div></div></div>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<div class="itemizedlist"><ul type="disc">
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein<li><p>
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein The serial number of a dynamically updatable zone can
8a713ca49ddddb36e432d4717800f9258a5c2ea9Mark Andrews now be set using
8a713ca49ddddb36e432d4717800f9258a5c2ea9Mark Andrews <span><strong class="command">rndc signing -serial <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>zonename</code></em></strong></span>.
8a713ca49ddddb36e432d4717800f9258a5c2ea9Mark Andrews This is particularly useful with <code class="option">inline-signing</code>
8a713ca49ddddb36e432d4717800f9258a5c2ea9Mark Andrews zones that have been reset. Setting the serial number to a value
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein larger than that on the slaves will trigger an AXFR-style
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington transfer.
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington </p></li>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<li><p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington When answering recursive queries, SERVFAIL responses can now be
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein cached by the server for a limited time; subsequent queries for
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein the same query name and type will return another SERVFAIL until
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein the cache times out. This reduces the frequency of retries
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein when a query is persistently failing, which can be a burden
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington on recursive serviers. The SERVFAIL cache timeout is controlled
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington by <code class="option">servfail-ttl</code>, which defaults to 10 seconds
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein and has an upper limit of 30.
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein </p></li>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<li><p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington The new <span><strong class="command">rndc nta</strong></span> command can now be used to
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington set a "negative trust anchor" (NTA), disabling DNSSEC validation for
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington a specific domain; this can be used when responses from a domain
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein are known to be failing validation due to administrative error
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington rather than because of a spoofing attack. NTAs are strictly
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington temporary; by default they expire after one hour, but can be
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington configured to last up to one week. The default NTA lifetime
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein can be changed by setting the <code class="option">nta-lifetime</code> in
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington <code class="filename">named.conf</code>. When added, NTAs are stored in a
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington file (<code class="filename"><em class="replaceable"><code>viewname</code></em>.nta</code>)
ab023a65562e62b85a824509d829b6fad87e00b1Rob Austein in order to persist across restarts of the named server.
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington </p></li>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington<li><p>
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington The EDNS Client Subnet (ECS) option is now supported for
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington authoritative servers; if a query contains an ECS option then
30e6ea9dedbe0738f9729833b1b59042dbebc4dfBrian Wellington ACLs containing <code class="option">geoip</code> or <code class="option">ecs</code>
elements can match against the the address encoded in the option.
This can be used to select a view for a query, so that different
answers can be provided depending on the client network.
</p></li>
<li><p>
The EDNS EXPIRE option has been implemented on the client
side, allowing a slave server to set the expiration timer
correctly when transferring zone data from another slave
server.
</p></li>
<li><p>
A new <code class="option">masterfile-style</code> zone option controls
the formatting of text zone files: When set to
<code class="literal">full</code>, the zone file will dumped in
single-line-per-record format.
</p></li>
<li><p>
<span><strong class="command">dig +ednsopt</strong></span> can now be used to set
arbitrary EDNS options in DNS requests.
</p></li>
<li><p>
<span><strong class="command">dig +ednsflags</strong></span> can now be used to set
yet-to-be-defined EDNS flags in DNS requests.
</p></li>
<li><p>
<span><strong class="command">dig +[no]ednsnegotiation</strong></span> can now be used enable /
disable EDNS version negotiation.
</p></li>
<li><p>
<span><strong class="command">dig +header-only</strong></span> can now be used to send
queries without a question section.
</p></li>
<li><p>
<span><strong class="command">dig +ttlunits</strong></span> causes <span><strong class="command">dig</strong></span>
to print TTL values with time-unit suffixes: w, d, h, m, s for
weeks, days, hours, minutes, and seconds.
</p></li>
<li><p>
<span><strong class="command">dig +zflag</strong></span> can be used to set the last
unassigned DNS header flag bit. This bit in normally zero.
</p></li>
<li><p>
<span><strong class="command">dig +dscp=<em class="replaceable"><code>value</code></em></strong></span>
can now be used to set the DSCP code point in outgoing query
packets.
</p></li>
<li><p>
<code class="option">serial-update-method</code> can now be set to
<code class="literal">date</code>. On update, the serial number will
be set to the current date in YYYYMMDDNN format.
</p></li>
<li><p>
<span><strong class="command">dnssec-signzone -N date</strong></span> also sets the serial
number to YYYYMMDDNN.
</p></li>
<li><p>
<span><strong class="command">named -L <em class="replaceable"><code>filename</code></em></strong></span>
causes named to send log messages to the specified file by
default instead of to the system log.
</p></li>
<li><p>
The rate limiter configured by the
<code class="option">serial-query-rate</code> option no longer covers
NOTIFY messages; those are now separately controlled by
<code class="option">notify-rate</code> and
<code class="option">startup-notify-rate</code> (the latter of which
controls the rate of NOTIFY messages sent when the server
is first started up or reconfigured).
</p></li>
<li><p>
The default number of tasks and client objects available
for serving lightweight resolver queries have been increased,
and are now configurable via the new <code class="option">lwres-tasks</code>
and <code class="option">lwres-clients</code> options in
<code class="filename">named.conf</code>. [RT #35857]
</p></li>
<li><p>
Log output to files can now be buffered by specifying
<span><strong class="command">buffered yes;</strong></span> when creating a channel.
</p></li>
<li><p>
<span><strong class="command">delv +tcp</strong></span> will exclusively use TCP when
sending queries.
</p></li>
<li><p>
<span><strong class="command">named</strong></span> will now check to see whether
other name server processes are running before starting up.
This is implemented in two ways: 1) by refusing to start
if the configured network interfaces all return "address
in use", and 2) by acquiring a file lock on
<code class="filename">/var/run/named/named.lock</code>, or on a different
file specified via the <span><strong class="command">named -X</strong></span> command
line option.
</p></li>
<li><p>
<span><strong class="command">rndc delzone</strong></span> can now be applied to zones
which were configured in <code class="filename">named.conf</code>;
it is no longer restricted to zones which were added by
<span><strong class="command">rndc addzone</strong></span>. (Note, however, that
this does not edit <code class="filename">named.conf</code>; the zone
must be removed from the configuration or it will return
when <span><strong class="command">named</strong></span> is restarted or reloaded.)
</p></li>
<li><p>
<span><strong class="command">rndc modzone</strong></span> can be used to reconfigure
a zone, using similar syntax to <span><strong class="command">rndc addzone</strong></span>.
</p></li>
<li><p>
<span><strong class="command">rndc showzone</strong></span> displays the current
configuration for a specified zone.
</p></li>
<li>
<p>
Added server-side support for pipelined TCP queries. Clients
may continue sending queries via TCP while previous queries are
processed in parallel. Responses are sent when they are
ready, not necessarily in the order in which the queries were
received.
</p>
<p>
To revert to the former behavior for a particular
client address or range of addresses, specify the address prefix
in the "keep-response-order" option. To revert to the former
behavior for all clients, use "keep-response-order { any; };".
</p>
</li>
<li><p>
The new <span><strong class="command">mdig</strong></span> command is a version of
<span><strong class="command">dig</strong></span> that sends multiple pipelined
queries and then waits for responses, instead of sending one
query and waiting the response before sending the next. [RT #38261]
</p></li>
</ul></div>
</div>
<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>
ACLs containing <span><strong class="command">geoip asnum</strong></span> elements were
not correctly matched unless the full organization name was
specified in the ACL (as in
<span><strong class="command">geoip asnum "AS1234 Example, Inc.";</strong></span>).
They can now match against the AS number alone (as in
<span><strong class="command">geoip asnum "AS1234";</strong></span>).
</p></li>
<li><p>
When using native PKCS#11 cryptography (i.e.,
<span><strong class="command">configure --enable-native-pkcs11</strong></span>) HSM PINs
of up to 256 characters can now be used.
</p></li>
<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>
Update forwarding performance has been improved by allowing
a single TCP connection to be shared between multiple updates.
</p></li>
<li><p>
By default, <span><strong class="command">nsupdate</strong></span> will now check
the correctness of hostnames when adding records of type
A, AAAA, MX, SOA, NS, SRV or PTR. This behavior can be
disabled with <span><strong class="command">check-names no</strong></span>.
</p></li>
<li><p>
Added support for OPENPGPKEY type.
</p></li>
<li><p>
The names of the files used to store managed keys and added
zones for each view are no longer based on the SHA256 hash
of the view name, except when this is necessary because the
view name contains characters that would be incompatible with use
as a file name. For views whose names do not contain forward
slashes ('/'), backslashes ('\'), or capital letters - which
could potentially cause namespace collision problems on
case-insensitive filesystems - files will now be named
after the view (for example, <code class="filename">internal.mkeys</code>
or <code class="filename">external.nzf</code>). However, to ensure
consistent behavior when upgrading, if a file using the old
name format is found to exist, it will continue to be used.
</p></li>
<li><p>
"rndc" can now return text output of arbitrary size to
the caller. (Prior to this, certain commands such as
"rndc tsig-list" and "rndc zonestatus" could return
truncated output.)
</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>
<li><p>
When encountering an authoritative name server whose name is
an alias pointing to another name, the resolver treats
this as an error and skips to the next server. Previously
this happened silently; now the error will be logged to
the newly-created "cname" log category.
</p></li>
<li><p>
If named is not configured to validate the answer then
allow fallback to plain DNS on timeout even when we know
the server supports EDNS. This will allow the server to
potentially resolve signed queries when TCP is being
blocked.
</p></li>
</ul></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<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>
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>
<li><p>
Large-system tuning
(<span><strong class="command">configure --with-tuning=large</strong></span>) caused
problems on some platforms by setting a socket receive
buffer size that was too large. This is now detected and
corrected at run time. [RT #37187]
</p></li>
<li><p>
When NXDOMAIN redirection is in use, queries for a name
that is present in the redirection zone but a type that
is not present will now return NOERROR instead of NXDOMAIN.
</p></li>
<li><p>
Due to an inadvertent removal of code in the previous
release, when <span><strong class="command">named</strong></span> encountered an
authoritative name server which dropped all EDNS queries,
it did not always try plain DNS. This has been corrected.
[RT #37965]
</p></li>
<li><p>
A regression caused nsupdate to use the default recursive servers
rather than the SOA MNAME server when sending the UPDATE.
</p></li>
<li><p>
Adjusted max-recursion-queries to accommodate the smaller
initial packet sizes used in BIND 9.10 and higher when
contacting authoritative servers for the first time.
</p></li>
<li><p>
Built-in "empty" zones did not correctly inherit the
"allow-transfer" ACL from the options or view. [RT #38310]
</p></li>
<li><p>
Two leaks were fixed that could cause <span><strong class="command">named</strong></span>
processes to grow to very large sizes. [RT #38454]
</p></li>
</ul></div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="end_of_life"></a>End of Life</h3></div></div></div>
<p>
The end of life for BIND 9.11 is yet to be determined but
will not be before BIND 9.13.0 has been released for 6 months.
<a href="https://www.isc.org/downloads/software-support-policy/" target="_top">https://www.isc.org/downloads/software-support-policy/</a>
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="relnotes_thanks"></a>Thank You</h3></div></div></div>
<p>
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
<a href="http://www.isc.org/donate/" target="_top">http://www.isc.org/donate/</a>.
</p>
</div>
</div></div></body>
</html>