From 3b9b6d0b8e7f798023c9d109c490449d528fde80 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sun, 7 Apr 2024 17:59:48 +0200 Subject: Adding upstream version 1:9.18.19. Signed-off-by: Daniel Baumann --- doc/notes/notes-9.18.15.rst | 57 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 doc/notes/notes-9.18.15.rst (limited to 'doc/notes/notes-9.18.15.rst') diff --git a/doc/notes/notes-9.18.15.rst b/doc/notes/notes-9.18.15.rst new file mode 100644 index 0000000..7642ab2 --- /dev/null +++ b/doc/notes/notes-9.18.15.rst @@ -0,0 +1,57 @@ +.. Copyright (C) Internet Systems Consortium, Inc. ("ISC") +.. +.. SPDX-License-Identifier: MPL-2.0 +.. +.. 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 https://mozilla.org/MPL/2.0/. +.. +.. See the COPYRIGHT file distributed with this work for additional +.. information regarding copyright ownership. + +Notes for BIND 9.18.15 +---------------------- + +Bug Fixes +~~~~~~~~~ + +- The :any:`max-transfer-time-in` and :any:`max-transfer-idle-in` + statements have not had any effect since the BIND 9 networking stack + was refactored in version 9.16. The missing functionality has been + re-implemented and incoming zone transfers now time out properly when + not progressing. :gl:`#4004` + +- The read timeout in :iscman:`rndc` is now 60 seconds, matching the + behavior in BIND 9.16 and earlier. It had previously been lowered to + 30 seconds by mistake. :gl:`#4046` + +- When the ``ISC_R_INVALIDPROTO`` (``ENOPROTOOPT``, ``EPROTONOSUPPORT``) + error code is returned by libuv, it is now treated as a network + failure: the server for which that error code is returned gets marked + as broken and is not contacted again during a given resolution + process. :gl:`#4005` + +- When removing delegations from an opt-out range, empty-non-terminal + NSEC3 records generated by those delegations were not cleaned up. This + has been fixed. :gl:`#4027` + +- Log file rotation code did not clean up older versions of log files + when the logging :any:`channel` had an absolute path configured as a + ``file`` destination. This has been fixed. :gl:`#3991` + +Known Issues +~~~~~~~~~~~~ + +- Sending NOTIFY messages silently fails when the source port specified + in the :any:`notify-source` statement is already in use. This can + happen e.g. when multiple servers are configured as NOTIFY targets for + a zone and some of them are unresponsive. This issue can be worked + around by not specifying the source port for NOTIFY messages in the + :any:`notify-source` statement; note that source port configuration is + already `deprecated`_ and will be removed altogether in a future + release. :gl:`#4002` + +- See :ref:`above ` for a list of all known + issues affecting this BIND 9 branch. + +.. _deprecated: https://gitlab.isc.org/isc-projects/bind9/-/issues/3781 -- cgit v1.2.3