BIND 9.9.10rc1 Release Notes
| Author: Michael McNally Reference Number: AA-01461 Views: 4475 Created: 2017-02-08 21:02 Last Updated: 2017-02-08 22:46
0 Rating/ Voters
This document summarizes significant changes since the last
production release of BIND on the corresponding major release
Please see the CHANGES file for a further list of bug fixes and
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
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 managed-keys
statement, or if the pre-configured root key is enabled by using
dnssec-validation auto, 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
trusted-keys statement are not automatically
maintained. If your server is performing DNSSEC validation
and is configured using trusted-keys, you are
advised to change your configuration before the root zone begins
signing with the new KSK. This is currently scheduled for
October 11, 2017.
This release includes an updated version of the
bind.keys file containing the new root
key. This file can also be downloaded from
If a server is configured with a response policy zone (RPZ)
that rewrites an answer with local data, and is also configured
for DNS64 address mapping, a NULL pointer can be read
triggering a server crash. This flaw is disclosed in
CVE-2017-3135. [RT #44434]
named could mishandle authority sections
with missing RRSIGs, triggering an assertion failure. This
flaw is disclosed in CVE-2016-9444. [RT #43632]
named mishandled some responses where
covering RRSIG records were returned without the requested
data, resulting in an assertion failure. This flaw is
disclosed in CVE-2016-9147. [RT #43548]
named incorrectly tried to cache TKEY
records which could trigger an assertion failure when there was
a class mismatch. This flaw is disclosed in CVE-2016-9131.
It was possible to trigger assertions when processing
responses containing answers of type DNAME. This flaw is
disclosed in CVE-2016-8864. [RT #43465]
Added the ability to specify the maximum number of records
permitted in a zone (
This provides a mechanism to block overly large zone
transfers, which is a potential risk with slave zones from
other parties, as described in CVE-2016-6170.
It was possible to trigger an assertion when rendering a
message using a specially crafted request. This flaw is
disclosed in CVE-2016-2776. [RT #43139]
Calling getrrsetbyname() with a non-
absolute name could trigger an infinite recursion bug in
lwresd or named with
lwres configured if, when combined with
a search list entry from
the resulting name is too long. This flaw is disclosed in
CVE-2016-2775. [RT #42694]
The built in mangaged keys for the global root zone have been
updated to include the upcoming key signing key (keyid 20326).
The ISC DNSSEC Lookaside Validation (DLV) service is scheduled
to be disabled in 2017. A warning is now logged when
named is configured to use this service,
either explicitly or via
If an ACL is specified with an address prefix in which the
prefix length is longer than the address portion (for example,
192.0.2.1/8), named will now log a warning.
In future releases this will be a fatal configuration error.
A synthesized CNAME record appearing in a response before the
associated DNAME could be cached, when it should not have been.
This was a regression introduced while addressing CVE-2016-8864.
Named could deadlock there were multiple changes to
NSEC/NSEC3 parameters for a zone being processed at the
same time. [RT #42770]
Named could trigger a assertion when sending notify
messages. [RT #44019]
Windows installs were failing due to triggering UAC without
the installation binary being signed.
A change in the internal binary representation of the RBT database
node structure enabled a race condition to occur (especially when
BIND was built with certain compilers or optimizer settings),
leading to inconsistent database state which caused random
assertion failures. [RT #42380]
Referencing a nonexistent zone in a response-policy
statement could cause an assertion failure during configuration.
rndc addzone could cause a crash
when attempting to add a zone with a type other than
master or slave.
Such zones are now rejected. [RT #43665]
named could hang when encountering log
file names with large apparent gaps in version number (for
example, when files exist called "logfile.0", "logfile.1",
and "logfile.1482954169"). This is now handled correctly.
If a zone was updated while named was
processing a query for nonexistent data, it could return
out-of-sync NSEC3 records causing potential DNSSEC validation
failure. [RT #43247]
named could crash when loading a zone
which had RRISG records whose expiry fields were far enough
apart to cause an integer overflow when comparing them.
The arpaname command was not installed into
the correct prefix
directory. [RT #42910]
When receiving a response from an authoritative server with
a TTL value of zero, named> will now only use
that response once, to answer the currently active clients that
were waiting for it. Previously, such response could be cached
and reused for up to one second. [RT #42142]
Corrected a bug in the rndc control channel
that could allow a read past the end of a buffer, crashing
named. Thanks to Lian Yihan for reporting
Reverted a change to the query logging format that was
inadvertently backported from the 9.11 branch. [RT #43238]
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
© 2001-2017 Internet Systems ConsortiumFor assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership.ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.