bind: Update ot 9.20.12

bind: Update ot 9.20.12

For details see:

https://downloads.isc.org/isc/bind9/9.20.12/doc/arm/html/notes.html#notes-for-bind-9-20-12

"Notes for BIND 9.20.12
New Features

    Support for parsing DSYNC records has been added.

    These records are used for discovering the receiver endpoint for DNS
    notification messages. For more information, see
    draft-ietf-dnsop-generalized-notify-09. [GL #5440]

Feature Changes

    Add deprecation warnings for RSASHA1, RSASHA1-NSEC3SHA1, and DS digest
    type 1.

    RSASHA1 and RSASHA1-NSEC-SHA1 DNSKEY algorithms have been deprecated by
    the IETF and should no longer be used for DNSSEC. DS digest type 1
    (SHA1) has also been deprecated in BIND 9. Validators are now expected
    to treat these algorithms and digest as unknown, resulting in some
    zones being treated as insecure when they were previously treated as
    secure. Warnings have been added to named and tools when these
    algorithms and this digest are being used for signing.

    Zones signed with RSASHA1 or RSASHA1-NSEC-SHA1 should be migrated to a
    different DNSKEY algorithm.

    Zones with DS or CDS records with digest type 1 (SHA1) should be
    updated to use a different digest type (e.g. SHA256) and the digest
    type 1 records should be removed. [GL #5358]

Bug Fixes

    Stale RRsets in a CNAME chain were not always refreshed.

    Previously, with serve-stale enabled and a CNAME chain that contained a
    stale RRset, the refresh query didn’t always properly refresh the stale
    RRsets. This has been fixed. [GL #5243]

    Add RPZ extended DNS error for zones with a CNAME override policy
    configured.

    Previously, when the zone was configured with a CNAME override policy,
    or the response policy zone contained a wildcard CNAME, the extended
    DNS error code was not added. This has been fixed. [GL #5342]

    Fix dig issues.

    When used with the +keepopen option, dig could terminate unexpectedly
    in rare situations. Additionally, dig could hang and fail to shutdown
    properly when interrupted during a query. These have been fixed. [GL
    #5381]

    Log dropped or slipped responses in the query-errors category.

    Responses which were dropped or slipped because of Response Rate
    Limiting (RRL) were logged in the rate-limit category instead of the
    query-errors category, as documented in the ARM. This has been fixed.
    [GL #5388]

    synth-from-dnssec was not working in some scenarios.

    Aggressive use of DNSSEC-Validated cache with NSEC was not working in
    scenarios when no parent NSEC was in cache. This has been fixed. [GL
    #5422]

    Clean enough memory when adding new ADB names/entries under memory
    pressure.

    The ADB memory cleaning is opportunistic even when BIND is under memory
    pressure (in the overmem condition). named now ensures that the
    assigned memory limit is not exceeded by releasing twice the amount of
    memory allocated for each new ADB name/entry when under memory
    pressure. [GL !10637]

    Prevent spurious validation failures.

    Under rare circumstances, validation could fail if multiple clients
    simultaneously iterated the same set of DNSSEC signatures. This has
    been fixed. [GL #3014]"

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>