Bug 2218436 - Re-patch bind-utils to support attempts in /etc/resolv.conf
Summary: Re-patch bind-utils to support attempts in /etc/resolv.conf
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: bind
Version: CentOS Stream
Hardware: Unspecified
OS: Linux
low
unspecified
Target Milestone: rc
: ---
Assignee: Petr Menšík
QA Contact: Petr Sklenar
URL:
Whiteboard:
Depends On: 2187436 1984876
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-29 06:38 UTC by Jacek Tomasiak
Modified: 2023-08-09 09:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Internet Systems Consortium (ISC) isc-projects bind9 merge_requests 5273 0 None merged Parse timeout and attempts from resolv.conf 2023-08-09 09:29:44 UTC
Red Hat Issue Tracker RHELPLAN-161149 0 None None None 2023-06-29 06:39:07 UTC

Description Jacek Tomasiak 2023-06-29 06:38:36 UTC
Description of problem:
Support for "options attempts:X" was "lost" when upstream switched from liblwres to libirs (in version 9.12). It was re-added in upstream version 9.17 and downstream patch was added in Fedora in version 32:9.16.28-2 of the package in May 2022.

However the el9 version of bind packages (at version 32:9.16.23-11 currently) still didn't get the patch added.

Please re-add the patch to get back support for resolv.conf options in RHEL9.

Comment 1 Jacek Tomasiak 2023-06-29 06:48:08 UTC
I see that this is a duplicate of #1984876 which was closed as WONTFIX.
Is there a chance for re-opening that?

Comment 2 Petr Menšík 2023-08-09 09:29:45 UTC
Yes, while I would say this is not high priority work, I think it would be useful backporting this also to 9.16 bind. Upstream has not backported the change to that version, but there should not be anything important blocking this feature.

I would propose doing that with rebase bug #2187436, which I doubt would be sooner than release 9.4. Especially if we had that already on Fedora and no issues were reported related to that. It is self-contained change with very low chance of breaking something else.


Note You need to log in before you can comment on or make changes to this bug.