<
div class="titlepage"><
div><
div><
h2 class="title" style="clear: both">
<
a name="id-1.2"></
a>Release Notes for BIND Version 9.11.2b1</
h2></
div></
div></
div>
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_intro"></
a>Introduction</
h3></
div></
div></
div>
This document summarizes changes since the last production
release on the BIND 9.11 branch.
Please see the <
code class="filename">CHANGES</
code> file for a further
list of bug fixes and other changes.
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_download"></
a>Download</
h3></
div></
div></
div>
The latest versions of BIND 9 software can always be found at
There you will find additional information about each release,
source code, and pre-compiled versions for Microsoft Windows
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="root_key"></
a>New DNSSEC Root Key</
h3></
div></
div></
div>
ICANN is in the process of introducing a new Key Signing Key (KSK) for
the global root zone. BIND has multiple methods for managing DNSSEC
trust anchors, with somewhat different behaviors. If the root
key is configured using the <
span class="command"><
strong>managed-keys</
strong></
span>
statement, or if the pre-configured root key is enabled by using
<
span class="command"><
strong>dnssec-validation auto</
strong></
span>, then BIND can keep
keys up to date automatically. Servers configured in this way
will roll seamlessly to the new key when it is published in
the root zone. However, keys configured using the
<
span class="command"><
strong>trusted-keys</
strong></
span> statement are not automatically
maintained. If your server is performing DNSSEC validation
and is configured using <
span class="command"><
strong>trusted-keys</
strong></
span>, you are
advised to change your configuration before the root zone begins
signing with the new KSK. This is currently scheduled for
This release includes an updated version of the
<
code class="filename">
bind.keys</
code> file containing the new root
key. This file can also be downloaded from
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_license"></
a>License Change</
h3></
div></
div></
div>
With the release of BIND 9.11.0, ISC changed to the open
source license for BIND from the ISC license to the Mozilla
Public License (MPL 2.0).
The MPL-2.0 license requires that if you make changes to
licensed software (
e.g. BIND) and distribute them outside
your organization, that you publish those changes under that
same license. It does not require that you publish or disclose
anything other than the changes you made to our software.
This new requirement will not affect anyone who is using BIND
without redistributing it, nor anyone redistributing it without
changes, therefore this change will be without consequence
for most individuals and organizations who are using BIND.
Those unsure whether or not the license change affects their
use of BIND, or who wish to discuss how to comply with the
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_security"></
a>Security Fixes</
h3></
div></
div></
div>
<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
The BIND installer on Windows used an unquoted service path,
which can enable privilege escalation. This flaw is disclosed
in CVE-2017-3141. [RT #45229]
With certain RPZ configurations, a response with TTL 0
could cause <
span class="command"><
strong>named</
strong></
span> to go into an infinite
query loop. This flaw is disclosed in CVE-2017-3140.
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_changes"></
a>Feature Changes</
h3></
div></
div></
div>
<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
<
span class="command"><
strong>dig +ednsopt</
strong></
span> now accepts the names
for EDNS options in addition to numeric values. For example,
an EDNS Client-Subnet option could be sent using
<
span class="command"><
strong>dig +ednsopt=ecs:...</
strong></
span>. Thanks to
John Worley of Secure64 for the contribution. [RT #44461]
Threads in <
span class="command"><
strong>named</
strong></
span> are now set to human-readable
names to assist debugging on operating systems that support that.
Threads will have names such as "isc-timer", "isc-sockmgr",
"isc-worker0001", and so on. This will affect the reporting of
subsidiary thread names in <
span class="command"><
strong>ps</
strong></
span> and
<
span class="command"><
strong>top</
strong></
span>, but not the main thread. [RT #43234]
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_bugs"></
a>Bug Fixes</
h3></
div></
div></
div>
<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
Due to some incorrectly deleted code, when BIND was
built with LMDB, zones that were deleted via
<
span class="command"><
strong>rndc delzone</
strong></
span> were removed from the
running server but were not removed from the new zone
database, so that deletion did not persist after a
server restart. This has been corrected. [RT #45185]
Semicolons are no longer escaped when printing CAA and
URI records. This may break applications that depend on the
presence of the backslash before the semicolon. [RT #45216]
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="end_of_life"></
a>End of Life</
h3></
div></
div></
div>
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.
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_thanks"></
a>Thank You</
h3></
div></
div></
div>
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