From: Ondřej Surý Date: Mon, 3 Jan 2022 12:30:40 +0000 (+0100) Subject: Add CHANGES and release note for [GL #3071] X-Git-Tag: v9.17.22~14^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=4d71a3b3097383cc1dbc7a02f0a524cada0e36e7;p=thirdparty%2Fbind9.git Add CHANGES and release note for [GL #3071] --- diff --git a/CHANGES b/CHANGES index a6da0b1315d..3e59eb84b38 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,9 @@ +5786. [bug] Defer detaching from zone->raw in zone_shutdown() if + the zone is in the process of being dumped to disk to + ensure that the unsigned serial number information is + always written in the raw-format header of the signed + version on an inline-signed zone. [GL #3071] + 5785. [bug] named could leak memory when two dnssec-policy clauses had the same name. named failed to log this error. [GL #3085] diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index dbf3266abd2..5241f5558f6 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -43,3 +43,9 @@ Bug Fixes - On FreeBSD, a TCP connection would leak a small amount of heap memory leading to out-of-memory problem in a long run. This has been fixed. :gl:`#3051` + +- Under certain circumstances, the signed version of an inline-signed zone could + be dumped to disk without the serial number of the unsigned version of the + zone being saved. This could prevent resynchronization of zone contents after + ``named`` restarted, if the unsigned zone file had been modified while + ``named`` was not running. This has been fixed. :gl:`#3071`