Bug 2170097

Summary: bind9-next-9.19.10 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: bind9-nextAssignee: Petr Menšík <pemensik>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dns-sig, pemensik, pspacek
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://downloads.isc.org/isc/bind9/9.19.10/doc/arm/html/notes.html#notes-for-bind-9-19-10
Whiteboard:
Fixed In Version: bind9-next-9.19.10-1.fc38 bind9-next-9.19.10-1.fc37 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-11 03:15:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2023-02-15 16:03:09 UTC
Releases retrieved: 9.19.10
Upstream release that is considered latest: 9.19.10
Current version/release in rawhide: 9.19.9-3.fc38
URL: https://www.isc.org/bind/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/323379/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/bind9-next

Comment 1 Petr Menšík 2023-03-06 21:42:53 UTC
Upstream release notes:
https://downloads.isc.org/isc/bind9/9.19.10/doc/arm/html/notes.html#notes-for-bind-9-19-10

It is worth mentioning this is first version adding TLS channel forwarding of queries.
Copy & paste from release notes:

New Features

    The forwarders statement now supports the tls argument, to be used to forward queries to DoT-enabled servers. [GL #3726]

Removed Features

    Specifying a port when configuring source addresses (i.e., as an argument to query-source, query-source-v6, transfer-source, transfer-source-v6, notify-source, notify-source-v6, parental-source, or parental-source-v6, or in the source or source-v6 arguments to primaries, parental-agents, also-notify, or catalog-zones) has been deprecated. In addition, the use-v4-udp-ports, use-v6-udp-ports, avoid-v4-udp-ports, and avoid-v6-udp-ports options have also been deprecated.

    Warnings are now logged when any of these options are encountered in named.conf. In a future release, they will be made nonfunctional. [GL #3781]

    The Differentiated Services Code Point (DSCP) feature has been removed: configuring DSCP values in named.conf is now a configuration error. [GL #3789]

Feature Changes

    The memory statistics have been reduced to a single counter, InUse; Malloced is an alias that holds the same value. The other counters were usable with the old BIND 9 internal memory allocator, but they are unnecessary now that the latter has been removed. [GL #3718]

Bug Fixes

    A constant stream of zone additions and deletions via rndc reconfig could cause increased memory consumption due to delayed cleaning of view memory. This has been fixed. [GL #3801]

    The speed of the message digest algorithms (MD5, SHA-1, SHA-2), and of NSEC3 hashing, has been improved. [GL #3795]

    Pointing parental-agents to a resolver did not work because the RD bit was not set on DS requests. This has been fixed. [GL #3783]

    Building BIND 9 failed when the --enable-dnsrps switch for ./configure was used. This has been fixed. [GL #3827]

Comment 2 Fedora Update System 2023-03-06 21:45:59 UTC
FEDORA-2023-b3b28091a6 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b3b28091a6

Comment 3 Fedora Update System 2023-03-06 21:46:51 UTC
FEDORA-2023-9047ee4af3 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-9047ee4af3

Comment 4 Fedora Update System 2023-03-07 02:03:43 UTC
FEDORA-2023-b3b28091a6 has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b3b28091a6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-03-07 02:43:16 UTC
FEDORA-2023-9047ee4af3 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-9047ee4af3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-9047ee4af3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-03-11 03:15:19 UTC
FEDORA-2023-b3b28091a6 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2023-03-15 01:05:50 UTC
FEDORA-2023-9047ee4af3 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.