bind: Update to 9.16.33

bind: Update to 9.16.33

For details see:
https://downloads.isc.org/isc/bind9/9.16.33/doc/arm/html/notes.html#notes-for-bind-9-16-33

"Security Fixes

    Previously, there was no limit to the number of database lookups
    performed while processing large delegations, which could be abused to
    severely impact the performance of named running as a recursive
    resolver. This has been fixed. (CVE-2022-2795)

    ISC would like to thank Yehuda Afek from Tel-Aviv University and Anat
    Bremler-Barr & Shani Stajnrod from Reichman University for bringing
    this vulnerability to our attention. [GL #3394]

    named running as a resolver with the stale-answer-client-timeout option
    set to 0 could crash with an assertion failure, when there was a stale
    CNAME in the cache for the incoming query. This has been fixed.
    (CVE-2022-3080) [GL #3517]

    A memory leak was fixed that could be externally triggered in the
    DNSSEC verification code for the ECDSA algorithm. (CVE-2022-38177) [GL
    #3487]

    Memory leaks were fixed that could be externally triggered in the
    DNSSEC verification code for the EdDSA algorithm. (CVE-2022-38178) [GL
    #3487]

Feature Changes

    Response Rate Limiting (RRL) code now treats all QNAMEs that are
    subject to wildcard processing within a given zone as the same name, to
    prevent circumventing the limits enforced by RRL. [GL #3459]

    Zones using dnssec-policy now require dynamic DNS or inline-signing to
    be configured explicitly. [GL #3381]

    A backward-compatible approach was implemented for encoding
    internationalized domain names (IDN) in dig and converting the domain
    to IDNA2008 form; if that fails, BIND tries an IDNA2003 conversion. [GL
    #3485]

Bug Fixes

    A serve-stale bug was fixed, where BIND would try to return stale data
    from cache for lookups that received duplicate queries or queries that
    would be dropped. This bug resulted in premature SERVFAIL responses,
    and has now been resolved. [GL #2982]"

Signed-off-by: Matthias Fischer <matthias.fischer@ipfire.org>
Reviewed-by: Peter Müller <peter.mueller@ipfire.org>