From: Evan Hunt Date: Tue, 23 Feb 2021 03:13:04 +0000 (-0800) Subject: CHANGES, release note X-Git-Tag: v9.17.11~20^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=82b82bb8210ac11b9ae44966e04f51535ecf6dbd;p=thirdparty%2Fbind9.git CHANGES, release note --- diff --git a/CHANGES b/CHANGES index b131b13d65e..26b7f355e46 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,9 @@ +5593. [bug] Journal files written by older versions of named + can now be read when loading zones so that journal + incompatibility will not cause problems on upgrade. + Outdated journals will be updated to the new format + after loading. [GL #2505] + 5592. [bug] Add globally available thread_id (isc_tid_v) that's incremented for each new thread, but the old thread ids are reused, so the maximum thread_id always diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index 1ee8b090254..3d615f149f5 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -64,3 +64,20 @@ Bug Fixes (crash) if the return of stale cached answers was enabled and ``stale-answer-client-timeout`` was applied to a client query in process. This has been fixed. [GL #2503] + +- Zone journal (``.jnl``) files created by versions of ``named`` prior + to 9.16.12 were no longer compatible; this could cause problems when + upgrading if journal files were not synchronized first. This has been + corrected: older journal files can now be read when starting up. When + an old-style journal file is detected, it is updated to the new + format immediately after loading. + + Note that journals created by the current version of ``named`` are not + usable by versions prior to 9.16.12. Before downgrading to a prior + release, users are advised to ensure that all dynamic zones have been + synchronized using ``rndc sync -clean``. + + A journal file's format can be changed manually by running + ``named-journalprint -d`` (downgrade) or ``named-journalprint -u`` + (upgrade). Note that this *must not* be done while ``named`` is + running. [GL #2505]