Bug 552555

Summary: resolv.conf without nameserver does not ask local named
Product: [openSUSE] openSUSE 11.2 Reporter: Harald Koenig <koenig>
Component: BasesystemAssignee: Petr Baudis <pbaudis>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: ug
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Harald Koenig 2009-11-04 16:34:38 UTC 
I'm running a local named (finally again, with default kernel;) but name resolving still is broken:

with no "nameserver" line in resolv.conf the man page claims that "the default is to use the name server  on  the local machine" which exactly is how it worked up to 11.1.  now in 11.2 I need an explicit "nameserver 127.0.0.1" line -- why ????


harald # ping www.x.org
ping: unknown host www.x.org

harald # host www.x.org
www.x.org is an alias for annarchy.freedesktop.org.
annarchy.freedesktop.org has address 131.252.210.176
annarchy.freedesktop.org mail is handled by 10 gabe.freedesktop.org.

harald # getent hosts www.x.org

harald # ping www.x.org 
ping: unknown host www.x.org

harald # echo nameserver 127.0.0.1 >> /etc/resolv.conf

harald # getent hosts www.x.org
131.252.210.176 annarchy.freedesktop.org www.x.org

harald # ping www.x.org 
PING annarchy.freedesktop.org (131.252.210.176) 56(84) bytes of data.
64 bytes from annarchy.freedesktop.org (131.252.210.176): icmp_seq=1 ttl=43 time=185 ms
64 bytes from annarchy.freedesktop.org (131.252.210.176): icmp_seq=2 ttl=43 time=186 ms
^C
--- annarchy.freedesktop.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1212ms
rtt min/avg/max/mdev = 185.093/185.967/186.842/0.975 ms
Comment 2 Marius Tomaschewski 2009-11-06 21:35:49 UTC 
A glibc feature => reassign.
Comment 3 Petr Baudis 2009-11-19 12:09:09 UTC 
Thank you for the report, it turns out we are already tracking this bug.

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