Bug#160596: libc6: It's not nscd
Package: libc6
Version: 2.2.5-14.2
Followup-For: Bug #160596
I'm not running nscd or uscd.
Since this bug has been merged, I'll omit my config files until
requested (/etc/host.conf /etc/nsswitch.conf /etc/resolv.conf). My
config is not significantly different than as reported in 157693
(actually, only my /etc/resolv.conf is different).
/etc/hosts :
127.0.0.1 localhost
127.0.0.1 blah
127.0.0.1 blah.somedomain.com
(FWIW, merging the 127.0.0.1 lines doesn't make a difference)
~% ping -c 1 blah
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.4 ms
--- localhost ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.4/0.4/0.4 ms
~% ping -c 1 blah.somedomain.org
PING localhost (127.0.0.1): 56 data bytes
64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.1 ms
--- localhost ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 0.1/0.1/0.1 ms
~% w3m -dump_head http://blah/ |head -1
HTTP/1.1 200 OK
~% w3m -dump_head http://blah.somedomain.org/
Unknown URI: http://blah.somedomain.org/
~% sudo zsh
admin ~# echo 127.0.0.1 blah.somedomain.org. >> /etc/hosts
admin ~#
~% w3m -dump_head http://blah.somedomain.org/ |head -1
HTTP/1.1 200 OK
The HTTP/1.1 lines are successful connections to 127.0.0.1:80 . The
Unknown URI line is w3m telling me that it can't resolve the name
blah.somedomain.org . After I add the "127.0.0.1 blah.somedomain.org."
(and note the trailing dot if you haven't already) to /etc/hosts I can
resolve the domain properly, but I see a lag before I hit the site.
I fired up tcpdump from another machine and I see my machine sending a
DNS AAAA query for blah.somedomain.org . My DNS server says WTF?
My machine correctly resolves the domain through /etc/hosts after
giving up on DNS, but only if I have the domain name with trailing dot
in my /etc/hosts file.
Again, I can send more config info in but my config is
identical to bug#157693 aside from differences in /etc/resolv.conf .
I'm not running any services on my machine that are in any way related
to name resolution. I can duplicate these problems on any one of five
different Debian installs on my network. I can shut down every running
service, get my process table as small as it can (realistically) be and
I still see the problems.
I'm totally happy supplying more information or testing different things
out; let me know what I can do to help :)
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux commserv 2.4.18-686 #1 Sun Apr 14 11:32:47 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-4 The Berkeley database routines [gl
-- no debconf information
Reply to: