MRE updates of bind9 for focal, jammy and lunar

Bug #2028413 reported by Bryce Harrington
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bind-dyndb-ldap (Ubuntu)
Fix Released
Undecided
Unassigned
Focal
Triaged
Undecided
Unassigned
Jammy
Fix Committed
Undecided
Unassigned
Lunar
Fix Committed
Undecided
Unassigned
bind9 (Ubuntu)
Fix Released
Undecided
Lena Voytek
Focal
Triaged
Undecided
Lena Voytek
Jammy
Fix Committed
Undecided
Lena Voytek
Lunar
Fix Committed
Undecided
Lena Voytek

Bug Description

This bug tracks an update for the bind9 package, moving to versions:

 * lunar (23.04): bind9 9.18.18
 * jammy (22.04): bind9 9.18.18
 * focal (20.04): bind9 9.16.43

These updates include bug fixes following the SRU policy exception defined at https://wiki.ubuntu.com/Bind9Updates.

[Upstream changes]

9.18.13-9.18.18 for lunar and jammy:

Updates:

Mark a primary server as temporarily unreachable when a TCP connection response to an SOA query times out, matching behavior of a refused TCP connection.
Mark dialup and heartbeat-interval options as deprecated.
Retry DNS queries without an EDNS COOKIE when the first response is FORMERR with the EDNS COOKIE that was sent originally.
Use NS records for the relaxed QNAME minimization mode to reduce the number of queries from named.
Mark TKEY mode 2 as deprecated.
Mark delegation-only and root-delegation-only as deprecated.
Run RPZ and catalog zone updates on specialized offload threads to reduce blocked query processing time.

Bug Fixes:

Fix assertion failure from processing already-queued queries while server is being reconfigured or cache is being flushed.
Fix failure to load zones containing resource records with a TTL value larger than 86400 seconds when dnssec-policy is set to insecure.
Fix the ability to read HMAC-MD5 key files (LP: #2015176).
Fix stability issues with the catalog zone implementation.
Fix bind9 getting stuck when listen-on statement for HTTP is removed from configuration.
Do not return delegation from cache after stale-answer-client-timeout.
Fix failure to auto-tune clients-per-query limit in some situations.
Fix proper timeouts when using max-transfer-time-in and max-transfer-idle-in statements.
Bring rndc read timeout back to 60 seconds from 30.
Treat libuv returning ISC_R_INVALIDPROTO as a network error.
Clean up empty-non-terminal NSEC3 records.
Fix log file rotation cleanup for absolute file path destinations.
Fix various catalog zone processing crashes.
Fix transfer hang when downloading large zones over TLS.
Fix named crash when adding a new zone into the configuration file for a name which was already configured as a member zone for a catalog zone.
Delay DNSSEC key queries until all zones have finished loading.

CVE Fixes - already available as patches:

CVE-2023-2828
CVE-2023-2911

For full release notes, see: https://bind9.readthedocs.io/en/v9.18.18/notes.html#notes-for-bind-9-18-18

While there are behavioral changes in this release, I was unable to find any backwards-incompatible changes. Some features were marked as deprecated, but are still usable as they were before. Other changes are related to performance and timeout management, neither of which should change how bind9 works, but are worth keeping an eye on in case any regressions arise.

[Test Plan]

DEP-8 test results:

simpletest PASS
validation FLAKY non-zero exit status 1
zonetest PASS
dyndb-ldap PASS

validation is known to be broken in its current state, both due to a need for internet access and incorrect output checking, so the failure is expected.

[Other Information]

Note to SRU team: this update must happen together with src:bind-dyndb-ldap, and in a particular order:
- first src:bind9 must be accepted
- once src:bind9 is fully built in all architectures, *then* src:bind-dyndb-ldap can be accepted. In other words, src:bind-dyndb-ldap must build with the new src:bind9 version.
- it is expected that until both packages are in proposed and built in the correct order, DEP8 tests will fail. That's our safeguard against mistakenly releasing them out of sync

[Regression Potential]

Upstream has an extensive build and integration test suite. So regressions would likely arise from a change in interaction with Ubuntu-specific integrations.

Related branches

Bryce Harrington (bryce)
Changed in bind9 (Ubuntu):
milestone: none → ubuntu-23.08
Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu Focal):
assignee: nobody → Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu Jammy):
assignee: nobody → Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu Lunar):
assignee: nobody → Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu):
assignee: nobody → Lena Voytek (lvoytek)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bind9 (Ubuntu Focal):
status: New → Confirmed
Changed in bind9 (Ubuntu Jammy):
status: New → Confirmed
Changed in bind9 (Ubuntu Lunar):
status: New → Confirmed
Changed in bind9 (Ubuntu):
status: New → Confirmed
Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu):
milestone: ubuntu-23.08 → ubuntu-23.09
Changed in bind9 (Ubuntu Lunar):
status: Confirmed → In Progress
Lena Voytek (lvoytek)
description: updated
Changed in bind9 (Ubuntu):
status: Confirmed → In Progress
Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu):
status: In Progress → Fix Released
Lena Voytek (lvoytek)
Changed in bind9 (Ubuntu Jammy):
status: Confirmed → In Progress
Lena Voytek (lvoytek)
description: updated
Lena Voytek (lvoytek)
Changed in bind-dyndb-ldap (Ubuntu Jammy):
status: New → In Progress
Changed in bind-dyndb-ldap (Ubuntu Lunar):
status: New → In Progress
Changed in bind-dyndb-ldap (Ubuntu):
status: New → Fix Released
Changed in bind-dyndb-ldap (Ubuntu Focal):
status: New → Triaged
Changed in bind9 (Ubuntu Focal):
status: Confirmed → Triaged
Lena Voytek (lvoytek)
description: updated
Lena Voytek (lvoytek)
description: updated
description: updated
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Bryce, or anyone else affected,

Accepted bind9 into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.18.18-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in bind9 (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Changed in bind9 (Ubuntu Lunar):
status: In Progress → Fix Committed
tags: added: verification-needed-lunar
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Bryce, or anyone else affected,

Accepted bind9 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind9/1:9.18.18-0ubuntu0.23.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Bryce, or anyone else affected,

Accepted bind-dyndb-ldap into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.10-4ubuntu0.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-lunar. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in bind-dyndb-ldap (Ubuntu Lunar):
status: In Progress → Fix Committed
Changed in bind-dyndb-ldap (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Bryce, or anyone else affected,

Accepted bind-dyndb-ldap into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/bind-dyndb-ldap/11.9-5ubuntu0.22.04.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Lena Voytek (lvoytek) wrote :
tags: added: verification-done verification-done-jammy verification-done-lunar
removed: verification-needed verification-needed-jammy verification-needed-lunar
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.