321N/A - Copyright (C) 2000-2016 Internet Systems Consortium, Inc. ("ISC") 321N/A - This Source Code Form is subject to the terms of the Mozilla Public 321N/A - License, v. 2.0. If a copy of the MPL was not distributed with this 321N/A<
meta http-
equiv="Content-Type" content="text/html; charset=ISO-8859-1">
321N/A<
title>Appendix�A.�Release Notes</
title>
321N/A<
meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
321N/A<
link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
321N/A<
link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
321N/A<
body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
321N/A<
table width="100%" summary="Navigation header">
321N/A<
tr><
th colspan="3" align="center">Appendix�A.�Release Notes</
th></
tr>
321N/A<
td width="20%" align="left">
321N/A<
th width="60%" align="center">�</
th>
321N/A<
div class="titlepage"><
div><
div><
h1 class="title">
650N/A<
p><
b>Table of Contents</
b></
p>
650N/A<
dt><
span class="section"><
a href="Bv9ARM.ch09.html#id-1.10.2">Release Notes for BIND Version 9.11.0</
a></
span></
dt>
650N/A<
div class="titlepage"><
div><
div><
h2 class="title" style="clear: both">
650N/A<
a name="id-1.10.2"></
a>Release Notes for BIND Version 9.11.0</
h2></
div></
div></
div>
650N/A<
div class="titlepage"><
div><
div><
h3 class="title">
650N/A<
a name="relnotes_intro"></
a>Introduction</
h3></
div></
div></
div>
650N/A BIND 9.11.0 is a new feature release of BIND, still under development.
321N/A This document summarizes new features and functional changes that
333N/A have been introduced on this branch. With each development
333N/A release leading up to the final BIND 9.11.0 release, this document
333N/A will be updated with additional features added and bugs fixed.
333N/A<
div class="titlepage"><
div><
div><
h3 class="title">
333N/A<
a name="relnotes_download"></
a>Download</
h3></
div></
div></
div>
650N/A The latest versions of BIND 9 software can always be found at
650N/A There you will find additional information about each release,
650N/A source code, and pre-compiled versions for Microsoft Windows
650N/A<
div class="titlepage"><
div><
div><
h3 class="title">
650N/A<
a name="relnotes_license"></
a>License Change</
h3></
div></
div></
div>
650N/A With the release of BIND 9.11.0, ISC is changing the open
650N/A source license for BIND from the ISC license to the Mozilla
650N/A Public License (MPL 2.0). This change is effective from BIND
650N/A The MPL-2.0 license requires that if you make changes to
650N/A licensed software (
e.g. BIND) and distribute them outside
333N/A your organization, that you publish those changes under that
333N/A same license. It does not require that you publish or disclose
333N/A anything other than the changes you made to our software.
321N/A This new requirement will not affect anyone who is using BIND
321N/A without redistributing it, nor anyone redistributing it without
321N/A changes, therefore this change will be without consequence
321N/A for most individuals and organizations who are using BIND.
321N/A Those unsure whether or not the license change affects their
321N/A use of BIND, or who wish to discuss how to comply with the
321N/A<
div class="titlepage"><
div><
div><
h3 class="title">
321N/A<
a name="relnotes_security"></
a>Security Fixes</
h3></
div></
div></
div>
321N/A<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
321N/A<
li class="listitem"><
p>
321N/A Added the ability to specify the maximum number of records
321N/A permitted in a zone (max-records #;). This provides a mechanism
321N/A to block overly large zone transfers, which is a potential risk
321N/A with slave zones from other parties, as described in CVE-2016-6170.
321N/A<
li class="listitem"><
p>
321N/A It was possible to trigger a assertion when rendering a
321N/A message using a specially crafted request. This flaw is
321N/A disclosed in CVE-2016-2776. [RT #43139]
321N/A<
li class="listitem"><
p>
321N/A getrrsetbyname with a non absolute name could trigger an
321N/A infinite recursion bug in lwresd and named with lwres
321N/A configured if when combined with a search list entry the
321N/A resulting name is too long. This flaw is disclosed in
321N/A CVE-2016-2775. [RT #42694]
321N/A<
div class="titlepage"><
div><
div><
h3 class="title">
321N/A<
a name="relnotes_features"></
a>New Features</
h3></
div></
div></
div>
321N/A<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: disc; ">
321N/A A new method of provisioning secondary servers called
321N/A "Catalog Zones" has been added. This is an implementation of
321N/A draft-muks-dnsop-dns-catalog-zones/
321N/A A catalog zone is a regular DNS zone which contains a list
321N/A of "member zones", along with the configuration options for
321N/A each of those zones. When a server is configured to use a
321N/A catalog zone, all the zones listed in the catalog zone are
321N/A added to the local server as slave zones. When the catalog
321N/A zone is updated (
e.g., by adding or removing zones, or
321N/A changing configuration options for existing zones) those
321N/A changes will be put into effect. Since the catalog zone is
321N/A itself a DNS zone, this means configuration changes can be
321N/A This feature should be considered experimental. It currently
321N/A supports only basic features; more advanced features such as
321N/A ACLs and TSIG keys are not yet supported. Example catalog
321N/A zone configurations can be found in the Chapter 9 of the
321N/A BIND Administrator Reference Manual.
321N/A Support for master entries with TSIG keys has been added to catalog
321N/A zones, as well as support for allow-query and allow-transfer.
321N/A<
li class="listitem"><
p>
321N/A Added an <
span class="command"><
strong>
isc.rndc</
strong></
span> Python module, which allows
321N/A <
span class="command"><
strong>rndc</
strong></
span> commands to be sent from Python programs.
321N/A Added support for DynDB, a new interface for loading zone data
321N/A from an external database, developed by Red Hat for the FreeIPA
321N/A project. (Thanks in particular to Adam Tkac and Petr
321N/A Spacek of Red Hat for the contribution.)
321N/A Unlike the existing DLZ and SDB interfaces, which provide a
321N/A limited subset of database functionality within BIND —
321N/A translating DNS queries into real-time database lookups with
321N/A relatively poor performance and with no ability to handle
321N/A DNSSEC-signed data — DynDB is able to fully implement
321N/A and extend the database API used natively by BIND.
321N/A A DynDB module could pre-load data from an external data
321N/A source, then serve it with the same performance and
321N/A functionality as conventional BIND zones, and with the
321N/A ability to take advantage of database features not
321N/A available in BIND, such as multi-master replication.
321N/A Fetch quotas are now compiled in by default: they
321N/A no longer require BIND to be configured with
321N/A <
span class="command"><
strong>--enable-fetchlimit</
strong></
span>, as was the case
321N/A when the feature was introduced in BIND 9.10.3.
321N/A These quotas limit the queries that are sent by recursive
321N/A resolvers to authoritative servers experiencing denial-of-service
321N/A attacks. They can both reduce the harm done to authoritative
321N/A servers and also avoid the resource exhaustion that can be
321N/A experienced by recursive servers when they are being used as a
321N/A vehicle for such an attack.
321N/A<
div class="itemizedlist"><
ul class="itemizedlist" style="list-style-type: circle; ">
321N/A<
li class="listitem"><
p>
321N/A <
code class="option">fetches-per-server</
code> limits the number of
321N/A simultaneous queries that can be sent to any single
321N/A authoritative server. The configured value is a starting
321N/A point; it is automatically adjusted downward if the server is
321N/A partially or completely non-responsive. The algorithm used to
321N/A adjust the quota can be configured via the
321N/A <
code class="option">fetch-quota-params</
code> option.
321N/A<
li class="listitem"><
p>
321N/A <
code class="option">fetches-per-zone</
code> limits the number of
321N/A simultaneous queries that can be sent for names within a
321N/A single domain. (Note: Unlike "fetches-per-server", this
321N/A value is not self-tuning.)
321N/A Statistics counters have also been added to track the number
321N/A of queries affected by these quotas.
321N/A Added support for <
span class="command"><
strong>dnstap</
strong></
span>, a fast,
321N/A flexible method for capturing and logging DNS traffic,
321N/A developed by Robert Edmonds at Farsight Security, Inc.,
321N/A whose assistance is gratefully acknowledged.
321N/A To enable <
span class="command"><
strong>dnstap</
strong></
span> at compile time,
321N/A the <
span class="command"><
strong>fstrm</
strong></
span> and <
span class="command"><
strong>protobuf-c</
strong></
span>
321N/A libraries must be available, and BIND must be configured with
321N/A <
code class="option">--enable-dnstap</
code>.
321N/A A new utility <
span class="command"><
strong>dnstap-read</
strong></
span> has been added
321N/A to allow <
span class="command"><
strong>dnstap</
strong></
span> data to be presented in
321N/A a human-readable format.
321N/A <
span class="command"><
strong>rndc dnstap -roll</
strong></
span> causes <
span class="command"><
strong>dnstap</
strong></
span>
321N/A output files to be rolled like log files -- the most recent output
321N/A file is renamed with a <
code class="filename">.0</
code> suffix, the next
321N/A most recent with <
code class="filename">.1</
code>, etc. (Note that this
321N/A only works when <
span class="command"><
strong>dnstap</
strong></
span> output is being written
321N/A to a file, not to a UNIX domain socket.) An optional numerical
321N/A argument specifies how many backup log files to retain; if not
321N/A specified or set to 0, there is no limit.
321N/A <
span class="command"><
strong>rndc dnstap -reopen</
strong></
span> simply closes and reopens
321N/A the <
span class="command"><
strong>dnstap</
strong></
span> output channel without renaming
321N/A For more information on <
span class="command"><
strong>dnstap</
strong></
span>, see
321N/A New statistics counters have been added to track traffic
321N/A sizes, as specified in RSSAC002. Query and response
321N/A message sizes are broken up into ranges of histogram buckets:
321N/A TCP and UDP queries of size 0-15, 16-31, ..., 272-288, and 288+,
321N/A and TCP and UDP responses of size 0-15, 16-31, ..., 4080-4095,
321N/A and 4096+. These values can be accessed via the XML and JSON
321N/A statistics channels at, for example,
321N/A Statistics for RSSAC02v3 traffic-volume, traffic-sizes and
321N/A rcode-volume reporting are now collected.
321N/A A new DNSSEC key management utility,
321N/A <
span class="command"><
strong>dnssec-keymgr</
strong></
span>, has been added. This tool
321N/A is meant to run unattended (
e.g., under <
span class="command"><
strong>cron</
strong></
span>).
321N/A It reads a policy definition file
321N/A and creates or updates DNSSEC keys as necessary to ensure that a
321N/A zone's keys match the defined policy for that zone. New keys are
321N/A created whenever necessary to ensure rollovers occur correctly.
321N/A Existing keys' timing metadata is adjusted as needed to set the
321N/A correct rollover period, prepublication interval, etc. If
321N/A the configured policy changes, keys are corrected automatically.
321N/A See the <
span class="command"><
strong>dnssec-keymgr</
strong></
span> man page for full details.
321N/A Note: <
span class="command"><
strong>dnssec-keymgr</
strong></
span> depends on Python and on
321N/A the Python
lex/
yacc module, PLY. The other Python-based tools,
321N/A <
span class="command"><
strong>dnssec-coverage</
strong></
span> and
321N/A <
span class="command"><
strong>dnssec-checkds</
strong></
span>, have been
321N/A refactored and updated as part of this work.
321N/A <
span class="command"><
strong>dnssec-keymgr</
strong></
span> now takes a -r
321N/A <
em class="replaceable"><
code>randomfile</
code></
em> option.
321N/A (Many thanks to Sebasti�n
321N/A Castro for his assistance in developing this tool at the IETF
321N/A 95 Hackathon in Buenos Aires, April 2016.)
321N/A<
li class="listitem"><
p>
321N/A The serial number of a dynamically updatable zone can
321N/A <
span class="command"><
strong>rndc signing -serial <
em class="replaceable"><
code>number</
code></
em> <
em class="replaceable"><
code>zonename</
code></
em></
strong></
span>.
321N/A This is particularly useful with <
code class="option">inline-signing</
code>
321N/A zones that have been reset. Setting the serial number to a value
321N/A larger than that on the slaves will trigger an AXFR-style
321N/A<
li class="listitem"><
p>
321N/A When answering recursive queries, SERVFAIL responses can now be
321N/A cached by the server for a limited time; subsequent queries for
321N/A the same query name and type will return another SERVFAIL until
321N/A the cache times out. This reduces the frequency of retries
321N/A when a query is persistently failing, which can be a burden
321N/A on recursive servers. The SERVFAIL cache timeout is controlled
321N/A by <
code class="option">servfail-ttl</
code>, which defaults to 1 second
321N/A and has an upper limit of 30.
321N/A<
li class="listitem"><
p>
321N/A The new <
span class="command"><
strong>rndc nta</
strong></
span> command can now be used to
321N/A set a "negative trust anchor" (NTA), disabling DNSSEC validation for
321N/A a specific domain; this can be used when responses from a domain
321N/A are known to be failing validation due to administrative error
321N/A rather than because of a spoofing attack. NTAs are strictly
321N/A temporary; by default they expire after one hour, but can be
321N/A configured to last up to one week. The default NTA lifetime
321N/A can be changed by setting the <
code class="option">nta-lifetime</
code> in
321N/A <
code class="filename">
named.conf</
code>. When added, NTAs are stored in a
321N/A file (<
code class="filename"><
em class="replaceable"><
code>viewname</
code></
em>.nta</
code>)
321N/A in order to persist across restarts of the <
span class="command"><
strong>named</
strong></
span> server.
321N/A<
li class="listitem"><
p>
321N/A The EDNS Client Subnet (ECS) option is now supported for
321N/A authoritative servers; if a query contains an ECS option then
321N/A ACLs containing <
code class="option">geoip</
code> or <
code class="option">ecs</
code>
321N/A elements can match against the address encoded in the option.
321N/A This can be used to select a view for a query, so that different
321N/A answers can be provided depending on the client network.
321N/A<
li class="listitem"><
p>
321N/A The EDNS EXPIRE option has been implemented on the client
321N/A side, allowing a slave server to set the expiration timer
321N/A correctly when transferring zone data from another slave
321N/A<
li class="listitem"><
p>
321N/A A new <
code class="option">masterfile-style</
code> zone option controls
321N/A the formatting of text zone files: When set to
321N/A <
code class="literal">full</
code>, the zone file will dumped in
321N/A single-line-per-record format.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +ednsopt</
strong></
span> can now be used to set
321N/A arbitrary EDNS options in DNS requests.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +ednsflags</
strong></
span> can now be used to set
321N/A yet-to-be-defined EDNS flags in DNS requests.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +[no]ednsnegotiation</
strong></
span> can now be used enable /
321N/A disable EDNS version negotiation.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +header-only</
strong></
span> can now be used to send
321N/A queries without a question section.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +ttlunits</
strong></
span> causes <
span class="command"><
strong>dig</
strong></
span>
321N/A to print TTL values with time-unit suffixes: w, d, h, m, s for
321N/A weeks, days, hours, minutes, and seconds.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +zflag</
strong></
span> can be used to set the last
321N/A unassigned DNS header flag bit. This bit is normally zero.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +dscp=<
em class="replaceable"><
code>value</
code></
em></
strong></
span>
321N/A can now be used to set the DSCP code point in outgoing query
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>dig +mapped</
strong></
span> can now be used to determine
321N/A if mapped IPv4 addresses can be used.
321N/A<
li class="listitem"><
p>
321N/A <
span class="command"><
strong>nslookup</
strong></
span> will now look up IPv6 as well
321N/A as IPv4 addresses by default. [RT #40420]
321N/A<
li class="listitem"><
p>
321N/A <
code class="option">serial-update-method</
code> can now be set to
321N/A <
code class="literal">date</
code>. On update, the serial number will
321N/A be set to the current date in YYYYMMDDNN format.
354N/A<
li class="listitem"><
p>
354N/A <
span class="command"><
strong>dnssec-signzone -N date</
strong></
span> also sets the serial
354N/A<
li class="listitem"><
p>
354N/A <
span class="command"><
strong>named -L <
em class="replaceable"><
code>filename</
code></
em></
strong></
span>
354N/A causes <
span class="command"><
strong>named</
strong></
span> to send log messages to the
354N/A specified file by default instead of to the system log.
354N/A<
li class="listitem"><
p>
354N/A The rate limiter configured by the
354N/A <
code class="option">serial-query-rate</
code> option no longer covers
354N/A NOTIFY messages; those are now separately controlled by
354N/A <
code class="option">notify-rate</
code> and
354N/A <
code class="option">startup-notify-rate</
code> (the latter of which
354N/A controls the rate of NOTIFY messages sent when the server
354N/A is first started up or reconfigured).
354N/A<
li class="listitem"><
p>
354N/A The default number of tasks and client objects available
354N/A for serving lightweight resolver queries have been increased,
700N/A and are now configurable via the new <
code class="option">lwres-tasks</
code>
700N/A and <
code class="option">lwres-clients</
code> options in
700N/A<
li class="listitem"><
p>
700N/A Log output to files can now be buffered by specifying
700N/A <
span class="command"><
strong>buffered yes;</
strong></
span> when creating a channel.
700N/A<
li class="listitem"><
p>
700N/A <
span class="command"><
strong>delv +tcp</
strong></
span> will exclusively use TCP when
700N/A<
li class="listitem"><
p>
700N/A <
span class="command"><
strong>named</
strong></
span> will now check to see whether
700N/A other name server processes are running before starting up.
700N/A This is implemented in two ways: 1) by refusing to start
700N/A if the configured network interfaces all return "address
700N/A in use", and 2) by attempting to acquire a lock on a file
700N/A specified by the <
code class="option">lock-file</
code> option or
700N/A the <
span class="command"><
strong>-X</
strong></
span> command line option. The
700N/A Specifying <
code class="literal">none</
code> will disable the lock
700N/A<
li class="listitem"><
p>
700N/A <
span class="command"><
strong>rndc delzone</
strong></
span> can now be applied to zones
700N/A it is no longer restricted to zones which were added by
700N/A <
span class="command"><
strong>rndc addzone</
strong></
span>. (Note, however, that
700N/A must be removed from the configuration or it will return
321N/A when <
span class="command"><
strong>named</
strong></
span> is restarted or reloaded.)
<
span class="command"><
strong>rndc modzone</
strong></
span> can be used to reconfigure
a zone, using similar syntax to <
span class="command"><
strong>rndc addzone</
strong></
span>.
<
span class="command"><
strong>rndc showzone</
strong></
span> displays the current
configuration for a specified zone.
When BIND is built with the <
span class="command"><
strong>lmdb</
strong></
span> library
(Lightning Memory-Mapped Database), <
span class="command"><
strong>named</
strong></
span>
will store the configuration information for zones
that are added via <
span class="command"><
strong>rndc addzone</
strong></
span>
in a database, rather than in a flat "NZF" file. This
dramatically improves performance for
<
span class="command"><
strong>rndc delzone</
strong></
span> and
<
span class="command"><
strong>rndc modzone</
strong></
span>: deleting or changing
the contents of a database is much faster than rewriting
On startup, if <
span class="command"><
strong>named</
strong></
span> finds an existing
NZF file, it will automatically convert it to the new NZD
To view the contents of an NZD, or to convert an
NZD back to an NZF file (for example, to revert back
to an earlier version of BIND which did not support the
NZD format), use the new command <
span class="command"><
strong>named-nzd2nzf</
strong></
span>
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
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; };".
The new <
span class="command"><
strong>mdig</
strong></
span> command is a version of
<
span class="command"><
strong>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]
To enable better monitoring and troubleshooting of RFC 5011
trust anchor management, the new <
span class="command"><
strong>rndc managed-keys</
strong></
span>
can be used to check status of trust anchors or to force keys
to be refreshed. Also, the managed-keys data file now has
easier-to-read comments. [RT #38458]
An <
span class="command"><
strong>--enable-querytrace</
strong></
span> configure switch is
now available to enable very verbose query trace logging. This
option can only be set at compile time. This option has a
negative performance impact and should be used only for
A new <
span class="command"><
strong>tcp-only</
strong></
span> option can be specified
in <
span class="command"><
strong>server</
strong></
span> statements to force
<
span class="command"><
strong>named</
strong></
span> to connect to the specified
server via TCP. [RT #37800]
The <
span class="command"><
strong>nxdomain-redirect</
strong></
span> option specifies
a DNS namespace to use for NXDOMAIN redirection. When a
recursive lookup returns NXDOMAIN, a second lookup is
initiated with the specified name appended to the query
name. This allows NXDOMAIN redirection data to be supplied
by multiple zones configured on the server, or by recursive
queries to other servers. (The older method, using
a single <
span class="command"><
strong>type redirect</
strong></
span> zone, has
better average performance but is less flexible.) [RT #37989]
The following types have been implemented: CSYNC, NINFO, RKEY,
A new <
span class="command"><
strong>message-compression</
strong></
span> option can be
used to specify whether or not to use name compression when
answering queries. Setting this to <
strong class="userinput"><
code>no</
code></
strong>
results in larger responses, but reduces CPU consumption and
may improve throughput. The default is <
strong class="userinput"><
code>yes</
code></
strong>.
A <
span class="command"><
strong>read-only</
strong></
span> option is now available in the
<
span class="command"><
strong>controls</
strong></
span> statement to grant non-destructive
control channel access. In such cases, a restricted set of
<
span class="command"><
strong>rndc</
strong></
span> commands are allowed, which can
report information from <
span class="command"><
strong>named</
strong></
span>, but cannot
reconfigure or stop the server. By default, the control channel
access is <
span class="emphasis"><
em>not</
em></
span> restricted to these
read-only operations. [RT #40498]
When loading a signed zone, <
span class="command"><
strong>named</
strong></
span> will
now check whether an RRSIG's inception time is in the future,
and if so, it will regenerate the RRSIG immediately. This helps
when a system's clock needs to be reset backwards.
The new <
span class="command"><
strong>minimal-any</
strong></
span> option reduces the size
of answers to UDP queries for type ANY by implementing one of
the strategies in "draft-ietf-dnsop-refuse-any": returning
a single arbitrarily-selected RRset that matches the query
name rather than returning all of the matching RRsets.
Thanks to Tony Finch for the contribution. [RT #41615]
<
span class="command"><
strong>named</
strong></
span> now provides feedback to the
owners of zones which have trust anchors configured
(<
span class="command"><
strong>trusted-keys</
strong></
span>,
<
span class="command"><
strong>managed-keys</
strong></
span>, <
span class="command"><
strong>dnssec-validation
auto;</
strong></
span> and <
span class="command"><
strong>dnssec-lookaside auto;</
strong></
span>)
by sending a daily query which encodes the keyids of the
configured trust anchors for the zone. This is controlled
by <
span class="command"><
strong>trust-anchor-telemetry</
strong></
span> and defaults
<
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; ">
The logging format used for <
span class="command"><
strong>querylog</
strong></
span> has been
altered. It now includes an additional field indicating the
address in memory of the client object processing the query.
The ISC DNSSEC Lookaside Validation (DLV) service is scheduled
to be disabled in 2017. A warning is now logged when
<
span class="command"><
strong>named</
strong></
span> is configured to use this service,
either explicitly or via <
code class="option">dnssec-lookaside auto;</
code>.
The timers returned by the statistics channel (indicating current
time, server boot time, and most recent reconfiguration time) are
now reported with millisecond accuracy. [RT #40082]
ACLs containing <
span class="command"><
strong>geoip asnum</
strong></
span> elements were
not correctly matched unless the full organization name was
specified in the ACL (as in
<
span class="command"><
strong>geoip asnum "AS1234 Example, Inc.";</
strong></
span>).
They can now match against the AS number alone (as in
<
span class="command"><
strong>geoip asnum "AS1234";</
strong></
span>).
When using native PKCS#11 cryptography (
i.e.,
<
span class="command"><
strong>configure --enable-native-pkcs11</
strong></
span>) HSM PINs
of up to 256 characters can now be used.
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.)
Update forwarding performance has been improved by allowing
a single TCP connection to be shared between multiple updates.
By default, <
span class="command"><
strong>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 class="command"><
strong>check-names no</
strong></
span>.
Added support for OPENPGPKEY type.
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.
"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
Errors reported when running <
span class="command"><
strong>rndc addzone</
strong></
span>
(
e.g., when a zone file cannot be loaded) have been clarified
to make it easier to diagnose problems.
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.
If <
span class="command"><
strong>named</
strong></
span> is not configured to validate
answers, 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
Large inline-signing changes should be less disruptive.
Signature generation is now done incrementally; the number
of signatures to be generated in each quantum is controlled
by "sig-signing-signatures <
em class="replaceable"><
code>number</
code></
em>;".
The experimental SIT option (code point 65001) of BIND
9.10.0 through BIND 9.10.2 has been replaced with the COOKIE
option (code point 10). It is no longer experimental, and
is sent by default, by both <
span class="command"><
strong>named</
strong></
span> and
<
span class="command"><
strong>dig</
strong></
span>.
The SIT-related
named.conf options have been marked as
obsolete, and are otherwise ignored.
When <
span class="command"><
strong>dig</
strong></
span> receives a truncated (TC=1)
response or a BADCOOKIE response code from a server, it
will automatically retry the query using the server COOKIE
that was returned by the server in its initial response.
on Linux is now supported.
A new <
code class="option">nsip-wait-recurse</
code> directive has been
added to RPZ, specifying whether to look up unknown name server
IP addresses and wait for a response before applying RPZ-NSIP rules.
The default is <
strong class="userinput"><
code>yes</
code></
strong>. If set to
<
strong class="userinput"><
code>no</
code></
strong>, <
span class="command"><
strong>named</
strong></
span> will only
apply RPZ-NSIP rules to servers whose addresses are already cached.
The addresses will be looked up in the background so the rule can
be applied on subsequent queries. This improves performance when
the cache is cold, at the cost of temporary imprecision in applying
policy directives. [RT #35009]
Within the <
code class="option">response-policy</
code> option, it is now
possible to configure RPZ rewrite logging on a per-zone basis
using the <
code class="option">log</
code> clause.
The default preferred glue is now the address type of the
transport the query was received over.
On machines with 2 or more processors (CPU), the default value
for the number of UDP listeners has been changed to the number
of detected processors minus one.
Zone transfers now use smaller message sizes to improve
message compression. This results in reduced network usage.
Added support for the AVC resource record type (Application
Changed <
span class="command"><
strong>rndc reconfig</
strong></
span> behavior so that newly
added zones are loaded asynchronously and the loading does not
<
span class="command"><
strong>minimal-responses</
strong></
span> now takes two new
arguments: <
code class="option">no-auth</
code> suppresses
populating the authority section but not the additional
section; <
code class="option">no-auth-recursive</
code>
does the same but only when answering recursive queries.
At server startup time, the queues for processing
notify and zone refresh queries are now processed in
LIFO rather than FIFO order, to speed up
loading of newly added zones. [RT #42825]
When answering queries of type MX or SRV, TLSA records for
the target name are now included in the additional section
to speed up DANE processing. [RT #42894]
<
span class="command"><
strong>named</
strong></
span> can now use the TCP Fast Open
mechanism on the server side, if supported by the
local operating system. [RT #42866]
<
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; ">
Fixed a crash when calling <
span class="command"><
strong>rndc stats</
strong></
span> on some
Windows builds: some Visual Studio compilers generate code that
crashes when the "%z" printf() format specifier is used. [RT #42380]
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]
<
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>