Files
bind9/doc/arm/notes-9.17.0.xml
T

96 lines
4.0 KiB
XML

<!--
- Copyright (C) Internet Systems Consortium, Inc. ("ISC")
-
- This Source Code Form is subject to the terms of the Mozilla Public
- License, v. 2.0. If a copy of the MPL was not distributed with this
- file, You can obtain one at http://mozilla.org/MPL/2.0/.
-
- See the COPYRIGHT file distributed with this work for additional
- information regarding copyright ownership.
-->
<section xml:id="relnotes-9.17.0"><info><title>Notes for BIND 9.17.0</title></info>
<section xml:id="relnotes-9.17.0-known"><info><title>Known Issues</title></info>
<itemizedlist>
<listitem>
<para>
UDP network ports used for listening can no longer simultaneously be
used for sending traffic. An example configuration which triggers
this issue would be one which uses the same
<replaceable>address:port</replaceable> pair for
<command>listen-on(-v6)</command> statements as for
<command>notify-source(-v6)</command> or
<command>transfer-source(-v6)</command>. While this issue affects all
operating systems, it only triggers log messages (e.g. "unable to
create dispatch for reserved port") on some of them. There are
currently no plans to make such a combination of settings work again.
</para>
</listitem>
</itemizedlist>
</section>
<section xml:id="relnotes-9.17.0-new"><info><title>New Features</title></info>
<itemizedlist>
<listitem>
<para>
When a secondary server receives a large incremental zone
transfer (IXFR), it can have a negative impact on query
performance while the incremental changes are applied to
the zone. To address this, <command>named</command> can now
limit the size of IXFR responses it sends in response to zone
transfer requests. If an IXFR response would be larger than an
AXFR of the entire zone, it will send an AXFR response instead.
</para>
<para>
This behavior is controlled by the <command>max-ixfr-ratio</command>
option - a percentage value representing the ratio of IXFR size
to the size of a full zone transfer. The default is
<literal>100%</literal>. [GL #1515]
</para>
</listitem>
</itemizedlist>
</section>
<section xml:id="relnotes-9.17.0-changes"><info><title>Feature Changes</title></info>
<itemizedlist>
<listitem>
<para>
The system-provided POSIX Threads read-write lock implementation is
now used by default instead of the native BIND 9 implementation.
Please be aware that glibc versions 2.26 through 2.29 had a
<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://sourceware.org/bugzilla/show_bug.cgi?id=23844">bug</link>
that could cause BIND 9 to deadlock. A fix was released in glibc 2.30,
and most current Linux distributions have patched or updated glibc,
with the notable exception of Ubuntu 18.04 (Bionic) which is a work in
progress. If you are running on an affected operating system, compile
BIND 9 with <command>--disable-pthread-rwlock</command> until a fixed
version of glibc is available. [GL !3125]
</para>
</listitem>
<listitem>
<para>
The <command>rndc nta -dump</command> and
<command>rndc secroots</command> commands now both include
<command>validate-except</command> entries when listing negative
trust anchors. These are indicated by the keyword
<literal>permanent</literal> in place of the expiry
date. [GL #1532]
</para>
</listitem>
</itemizedlist>
</section>
<section xml:id="relnotes-9.17.0-bugs"><info><title>Bug Fixes</title></info>
<itemizedlist>
<listitem>
<para>
Fixed re-signing issues with inline zones which resulted in
records being re-signed late or not at all.
</para>
</listitem>
</itemizedlist>
</section>
</section>