Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
---------------------------------------------------------------------
When nscd is enabled and a lookup is performed for a DNS record with a TTL of 0, nscd proceeds to cache the result when it should not. This behavior is seen via lookups initiated by getaddrinfo when it should not.
Version-Release number of selected component (if applicable):
---------------------------------------------------------------------
Tested against RHEL5 and RHEL6, up to versions:
glibc-2.12-1.7.el6.x86_64
nscd-2.12-1.7.el6.x86_64
How reproducible:
---------------------------------------------------------------------
100%
Steps to Reproduce (hostnames and IPs masked):
---------------------------------------------------------------------
# DNS RECORD IS:
;; ANSWER SECTION:
nfs.appliance.company.com. 0 IN A 1.1.1.55
(where the returned IP may vary based on specific conditions determined by the NFS appliance)
# WITH NSCD ENABLED:
/etc/init.d/nscd start
/etc/init.d/nscd reload
ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf
getaddrinfo("nfs.appliance.company.com", NULL, 0x7fff65794a90, 0x7fff65794b08) = 0
1.1.1.56 STREAM nfs.appliance.company.com
# [ run this as many times as you want, same result ]
# WITH NSCD DISABLED:
/etc/init.d/nscd stop
ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf
getaddrinfo("nfs.appliance.company.com", NULL, 0x7ffff521eb80, 0x7ffff521ebf8) = 0
1.1.1.56 STREAM nfs.appliance.company.com
ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf
getaddrinfo("nfs.appliance.company.com", NULL, 0x7fffb80836b0, 0x7fffb8083728) = 0
1.1.1.53 STREAM nfs.appliance.company.com
ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf
getaddrinfo("nfs.appliance.company.com", NULL, 0x7fff9d6aa5e0, 0x7fff9d6aa658) = 0
1.1.1.57 STREAM nfs.appliance.company.com
# [ run this as many times as you want, different results ]
Expected results:
---------------------------------------------------------------------
For DNS records with a TTL of 0, the results with NSCD enabled should be identical to the results seen with NSCD disabled.
Additional info:
---------------------------------------------------------------------
References regarding expected nscd and getaddrinfo behavior here:
http://udrepper.livejournal.com/16362.htmlhttp://sourceware.org/bugzilla/show_bug.cgi?id=4428
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0584.html
Description of problem: --------------------------------------------------------------------- When nscd is enabled and a lookup is performed for a DNS record with a TTL of 0, nscd proceeds to cache the result when it should not. This behavior is seen via lookups initiated by getaddrinfo when it should not. Version-Release number of selected component (if applicable): --------------------------------------------------------------------- Tested against RHEL5 and RHEL6, up to versions: glibc-2.12-1.7.el6.x86_64 nscd-2.12-1.7.el6.x86_64 How reproducible: --------------------------------------------------------------------- 100% Steps to Reproduce (hostnames and IPs masked): --------------------------------------------------------------------- # DNS RECORD IS: ;; ANSWER SECTION: nfs.appliance.company.com. 0 IN A 1.1.1.55 (where the returned IP may vary based on specific conditions determined by the NFS appliance) # WITH NSCD ENABLED: /etc/init.d/nscd start /etc/init.d/nscd reload ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf getaddrinfo("nfs.appliance.company.com", NULL, 0x7fff65794a90, 0x7fff65794b08) = 0 1.1.1.56 STREAM nfs.appliance.company.com # [ run this as many times as you want, same result ] # WITH NSCD DISABLED: /etc/init.d/nscd stop ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf getaddrinfo("nfs.appliance.company.com", NULL, 0x7ffff521eb80, 0x7ffff521ebf8) = 0 1.1.1.56 STREAM nfs.appliance.company.com ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf getaddrinfo("nfs.appliance.company.com", NULL, 0x7fffb80836b0, 0x7fffb8083728) = 0 1.1.1.53 STREAM nfs.appliance.company.com ltrace -f getent ahosts nfs.appliance.company.com 2>&1 | egrep "getaddrinfo|STREAM" | grep -v printf getaddrinfo("nfs.appliance.company.com", NULL, 0x7fff9d6aa5e0, 0x7fff9d6aa658) = 0 1.1.1.57 STREAM nfs.appliance.company.com # [ run this as many times as you want, different results ] Expected results: --------------------------------------------------------------------- For DNS records with a TTL of 0, the results with NSCD enabled should be identical to the results seen with NSCD disabled. Additional info: --------------------------------------------------------------------- References regarding expected nscd and getaddrinfo behavior here: http://udrepper.livejournal.com/16362.html http://sourceware.org/bugzilla/show_bug.cgi?id=4428