Bug 693611

Summary: log spam when gethostby*.getanswer gets DNAME
Product: Red Hat Enterprise Linux 6 Reporter: Andrew C Aitchison <aca21>
Component: glibcAssignee: Jeff Law <law>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-tools-bugs
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.2CC: drepper, ebachalo, fweimer, jthomas, jzhenyon, law, mfranc
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 594192 Environment:
Last Closed: 2012-01-26 17:53:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Andrew C Aitchison 2011-04-05 05:11:06 UTC 
+++ This bug was initially created as a clone of Bug #594192 +++

The problem is a DNAME is sometimes returned to gethostby*.getanswer. In some cases this leads to a large amount of log messages such as:

 ping: gethostby*.getanswer: asked for "img.muresinfo.ro.nyud.net IN A", got type "DNAME"

The code in question seems to be 

resolv/nss_dns/dns-host.c

if (type != qtype) {
syslog(LOG_NOTICE|LOG_AUTH,
      "gethostby*.getanswer: asked for \"%s %s %s\", got type \"%s\"",
      qname, p_class(C_IN), p_type(qtype),
      p_type(type));
cp += n;
continue; /* XXX - had_error++ ? */
}

Possible ways to eliminate this:
-message should only occur if the answer doesn't also contain a CNAME. If a CNAME is returned, the message is informational and could be considered LOG_INFO. However, I'm not sure that would reduce the amount of output for some users.

-don't produce the message on DNAME

--- Additional comment from ebachalo on 2011-01-26 12:27:59 EST ---

This change did not go upstream. I am closing this request for RHEL 4.9.  If/When a change is made in upstream glibc a request to backport to previous RHELs may be requested.
Comment 2 RHEL Program Management 2011-04-05 05:23:24 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 5 Jeff Law 2012-01-26 17:53:21 UTC 

*** This bug has been marked as a duplicate of bug 660265 ***