BIND users-

Our August 2024 maintenance release of BIND 9.18, as well as the first 
maintenance release on the new 9.20 stable branch, and the brand new 9.21 
development branch, are available and can be downloaded from the ISC software 
download page, https://www.isc.org/download.

A summary of significant changes in the new releases can be found in their 
release notes:

- Current supported stable branches:

    9.18.29 - 
https://downloads.isc.org/isc/bind9/9.18.29/doc/arm/html/notes.html 
<https://downloads.isc.org/isc/bind9/9.18.2/doc/arm/html/notes.html>
    9.20.1  - https://downloads.isc.org/isc/bind9/9.20.1/doc/arm/html/notes.html
- New development branch:
    9.20.1 - https://downloads.isc.org/isc/bind9/9.21.0/doc/arm/html/notes.html 
<https://downloads.isc.org/isc/bind9/9.2.1/doc/arm/html/notes.html>


If you haven’t seen it, check out the blog post from Ondřej Surý on the 9.20 
branch, including performance testing results 
(https://www.isc.org/blogs/2024-bind920/).
9.20 remains in the bind-dev package repositories for this release. We will 
roll the package repositories over, moving 9.20 to bind, and adding 9.21 to 
bind-dev, sometime in the coming month. 

---
Please Note:

To create an effective mitigation for CVE-2024-1737 we introduced two new 
configurable limits that prevent the loading (into zones or into cache) of DNS 
resource records (RRs) that exceed them. We therefore recommend reading this KB 
article,
https://kb.isc.org/docs/rrset-limits-in-zones, in case you need to change the 
defaults to suit your specific operational environment. (This change was 
introduced in 9.18.28 and has not changed with this release but it has 
surprised some users who didn’t notice this message previously.)

We recommend that users planning to upgrade from the EOL 9.16 branch read the 
following document first:

    
https://kb.isc.org/docs/changes-to-be-aware-of-when-moving-from-bind-916-to-918


-- 
bind-announce mailing list
bind-announce@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-announce

Reply via email to