[Bug libc/395] New: resolver updates causes resolver to stop resolving some hosts

["vapier at gentoo dot org" <sourceware-bugzilla at sources dot redhat dot com>]

original report here:
http://sources.redhat.com/ml/libc-alpha/2004-09/msg00146.html

basically somewhere between Aug 08 2004 and Sep 18 2004, the resolver library's
behavior broke when dealing with 'domain' entries in resolv.conf

when looking up a hostname, the old behavior was to try to search for the
hostname in each of the domains found in resolv.conf ... if those lookups
failed, the hostname itself would be tried
the new behavior is to only search in the domains found in resolv.conf

for example, i have the host 'aurora' setup to resolve to '192.168.0.7' on my
dns server ... on a client machine, i would look up 'aurora' via gethostbyname()
... in the resolv.conf on the client machine, i have one domain entry, 'domain
wh0rd.org' ...

the old glibc would query 'aurora.wh0rd.org' and fail, and then fall back and
try to look up 'aurora' which would work
the new glibc only tries 'aurora.wh0rd.org' and then fails

sniffing dns traffic via ethereal backed up this analysis

-- 
           Summary: resolver updates causes resolver to stop resolving some
                    hosts
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: vapier at gentoo dot org
                CC: glibc-bugs at sources dot redhat dot com,lv at gentoo
                    dot org
  GCC host triplet: i686-pc-linux-gnu


http://sources.redhat.com/bugzilla/show_bug.cgi?id=395

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.