mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-09-03 16:15:27 +00:00
Code Issues Releases Wiki Activity

Add CHANGES and release note for [GL #2600]

Browse Source
This commit is contained in:
Mark Andrews
2021-03-31 15:15:19 +11:00
committed by Ondřej Surý
parent bb6f0faeed
commit 0174098aca
2 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CHANGES
View File

@@ -1,3 +1,9 @@
5613. [bug] It was possible to write an invalid transaction header
in the journal file for a managed-keys database after
upgrading. This has been fixed. Invalid headers in
existing journal files are detected and named is able
to recover from them. [GL #2600]
5612. [bug] Continued refactoring of the network manager: 5612. [bug] Continued refactoring of the network manager:
- allow recovery from read and connect timeout events - allow recovery from read and connect timeout events
- ensure that calls to isc_nm_*connect() always - ensure that calls to isc_nm_*connect() always

6
doc/notes/notes-current.rst
View File

@@ -74,3 +74,9 @@ Bug Fixes
recursion for a client query completed when ``named`` was about to look for recursion for a client query completed when ``named`` was about to look for
a stale answer, an assertion could fail in ``query_respond()``, resulting in a stale answer, an assertion could fail in ``query_respond()``, resulting in
a crash. This has been fixed. [GL #2594] a crash. This has been fixed. [GL #2594]
- After upgrading to the previous release, journal files for trust anchor
databases (e.g., ``managed-keys.bind.jnl``) could be left in a corrupt
state. (Other zone journal files were not affected.) This has been
fixed. If a corrupt journal file is detected, ``named`` can now recover
from it. [GL #2600]