RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1670041 - glibc: libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts
Summary: glibc: libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Arjun Shankar
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On: 1670028 1670043
Blocks: 1710258
TreeView+ depends on / blocked
 
Reported: 2019-01-28 13:31 UTC by Florian Weimer
Modified: 2020-03-31 19:08 UTC (History)
8 users (show)

Fixed In Version: glibc-2.17-295.el7
Doc Type: Bug Fix
Doc Text:
Cause: glibc did not enable the reporting of all ICMP errors when performing a DNS lookup. Consequence: When the network reported that a configured DNS server was unreachable during a DNS lookup, the resolver would not immediately recognize the failure and query the next configured DNS server. Instead it would wait for a timeout, leading to a lookup time that was longer than necessary. Fix: The resolver now enables reporting of all ICMP errors when performing a DNS lookup. Result: The resolver now recognizes an unreachable DNS server and tries the next one immediately upon receiving an ICMP error message, leading to a faster DNS lookup in such cases.
Clone Of: 1670028
Environment:
Last Closed: 2020-03-31 19:08:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 715578 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Bugzilla 1328915 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHBA-2020:0989 0 None None None 2020-03-31 19:08:56 UTC
Sourceware 24047 0 P2 RESOLVED libresolv should use IP_RECVERR/IPV6_RECVERR to avoid long timeouts 2020-02-11 16:22:43 UTC

Internal Links: 715578

Description Florian Weimer 2019-01-28 13:31:41 UTC 
+++ This bug was initially created as a clone of Bug #1670028 +++

The Linux kernel does not forward certain ICMP errors to userspace unless IP_RECVERR/IPV6_RECVERR is specified.  We should use this socket option in the DNS stub resolver, as suggested in the upstream bug.
Comment 6 Sergey Kolosov 2019-10-24 07:48:05 UTC 
Verified with strace
Comment 8 errata-xmlrpc 2020-03-31 19:08:29 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0989
Note You need to log in before you can comment on or make changes to this bug.