253N/A - Copyright (C) 2000-2016 Internet Systems Consortium, Inc. ("ISC") 253N/A - This Source Code Form is subject to the terms of the Mozilla Public 253N/A - License, v. 2.0. If a copy of the MPL was not distributed with this 253N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
253N/A<
title>Appendix�A.�Release Notes</
title>
253N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
253N/A<
link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
253N/A<
link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
253N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
3996N/A<
table width="100%" summary="Navigation header">
253N/A<
tr><
th colspan="3" align="center">Appendix�A.�Release Notes</
th></
tr>
253N/A<
td width="20%" align="left">
253N/A<
th width="60%" align="center">�</
th>
253N/A<
div class="titlepage"><
div><
div><
h1 class="title">
253N/A<
p><
b>Table of Contents</
b></
p>
844N/A<
dt><
span class="section"><
a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.1b1</
a></
span></
dt>
253N/A<
div class="titlepage"><
div><
div><
h2 class="title" style="clear: both">
253N/A<
a name="id-1.10.2"></
a>Release Notes for BIND Version 9.11.1b1</
h2></
div></
div></
div>
253N/A<
div class="titlepage"><
div><
div><
h3 class="title">
253N/A<
a name="relnotes_intro"></
a>Introduction</
h3></
div></
div></
div>
253N/A This document summarizes changes since the last production
253N/A release on the BIND 9.11 branch.
253N/A Please see the <
code class="filename">CHANGES</
code> file for a further
253N/A list of bug fixes and other changes.
253N/A<
div class="titlepage"><
div><
div><
h3 class="title">
253N/A<
a name="relnotes_download"></
a>Download</
h3></
div></
div></
div>
253N/A The latest versions of BIND 9 software can always be found at
253N/A There you will find additional information about each release,
253N/A source code, and pre-compiled versions for Microsoft Windows
253N/A<
div class="titlepage"><
div><
div><
h3 class="title">
253N/A<
a name="relnotes_license"></
a>License Change</
h3></
div></
div></
div>
253N/A With the release of BIND 9.11.0, ISC changed to the open
253N/A source license for BIND from the ISC license to the Mozilla
253N/A Public License (MPL 2.0).
253N/A The MPL-2.0 license requires that if you make changes to
253N/A licensed software (
e.g. BIND) and distribute them outside
253N/A your organization, that you publish those changes under that
253N/A same license. It does not require that you publish or disclose
253N/A anything other than the changes you made to our software.
253N/A This new requirement will not affect anyone who is using BIND
253N/A without redistributing it, nor anyone redistributing it without
253N/A changes, therefore this change will be without consequence
253N/A for most individuals and organizations who are using BIND.
253N/A Those unsure whether or not the license change affects their
253N/A use of BIND, or who wish to discuss how to comply with the
253N/A<
div class="titlepage"><
div><
div><
h3 class="title">
253N/A<
a name="relnotes_security"></
a>Security Fixes</
h3></
div></
div></
div>
253N/A <
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
253N/A If a server is configured with a response policy zone (RPZ)
253N/A that rewrites an answer with local data, and is also configured
2490N/A for DNS64 address mapping, a NULL pointer can be read
2490N/A triggering a server crash. This flaw is disclosed in
253N/A CVE-2017-3135. [RT #44434]
253N/A A coding error in the <
code class="option">nxdomain-redirect</
code>
253N/A feature could lead to an assertion failure if the redirection
253N/A namespace was served from a local authoritative data source
253N/A such as a local zone or a DLZ instead of via recursive
253N/A lookup. This flaw is disclosed in CVE-2016-9778. [RT #43837]
253N/A <
span class="command"><
strong>named</
strong></
span> could mishandle authority sections
253N/A with missing RRSIGs, triggering an assertion failure. This
253N/A flaw is disclosed in CVE-2016-9444. [RT #43632]
3996N/A <
span class="command"><
strong>named</
strong></
span> mishandled some responses where
253N/A covering RRSIG records were returned without the requested
3996N/A data, resulting in an assertion failure. This flaw is
disclosed in CVE-2016-9147. [RT #43548]
<
span class="command"><
strong>named</
strong></
span> 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 (<
code class="option">max-records #;</
code>).
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.
<
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; ">
Expanded and improved the YAML output from
<
span class="command"><
strong>dnstap-read -y</
strong></
span>: it now includes packet
size and a detailed breakdown of message contents.
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), <
span class="command"><
strong>named</
strong></
span> will now log a warning.
In future releases this will be a fatal configuration error.
<
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; ">
Named could deadlock there were multiple changes to
NSEC/
NSEC3 parameters for a zone being processed at the
Named could trigger a assertion when sending notify
Referencing a nonexistent zone in a <
span class="command"><
strong>response-policy</
strong></
span>
statement could cause an assertion failure during configuration.
<
span class="command"><
strong>rndc addzone</
strong></
span> could cause a crash
when attempting to add a zone with a type other than
<
span class="command"><
strong>master</
strong></
span> or <
span class="command"><
strong>slave</
strong></
span>.
Such zones are now rejected. [RT #43665]
<
span class="command"><
strong>named</
strong></
span> 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 <
span class="command"><
strong>named</
strong></
span> was
processing a query for nonexistent data, it could return
out-of-sync NSEC3 records causing potential DNSSEC validation
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_maint"></
a>Maintenance</
h3></
div></
div></
div>
<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; "><
li class="listitem">
The built-in root hints have been updated to include an
<
div class="titlepage"><
div><
div><
h3 class="title">
<
a name="relnotes_misc"></
a>Miscellaneous Notes</
h3></
div></
div></
div>
<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; "><
li class="listitem">
Authoritative server support for the EDNS Client Subnet option
(ECS), introduced in BIND 9.11.0, was based on an early version
of the specification, and is now known to have incompatibilities
with other ECS implementations. It is also inefficient, requiring
a separate view for each answer, and is unable to correct for
overlapping subnets in the configuration. It is intended for
testing purposes but is not recommended for for production use.
This was not made sufficiently clear in the documentation at
<
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
<
table width="100%" summary="Navigation footer">
<
td width="40%" align="left">
<
td width="20%" align="center">�</
td>
<
td width="40%" align="right">�<
a accesskey="n" href="Bv9ARM.ch10.html">Next</
a>
<
td width="40%" align="left" valign="top">Chapter�8.�Troubleshooting�</
td>
<
td width="20%" align="center"><
a accesskey="h" href="Bv9ARM.html">Home</
a></
td>
<
td width="40%" align="right" valign="top">�Appendix�B.�A Brief History of the <
acronym class="acronym">DNS</
acronym> and <
acronym class="acronym">BIND</
acronym>