DNS resolution issue.
Ken D'Ambrosio
ken at jots.org
Mon Oct 18 10:54:58 EDT 2010
Boy, I love it when typing an e-mail helps you figure something out. I
actually even figured it out before clicking "send", for a change. So,
first, I'll give the solution; the original problem is below.
Changing resolv.conf's "hosts" line from
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
to
hosts: files dns mdns4
totally did the trick. Anyone wanna take a stab at telling me what went
wrong -- and why "NOTFOUND=return" is a default setting?
Thanks,
-Ken
------------------------- original message -------------------------
Hey, all. I've got an issue that's bugged me through several releases of
Ubuntu, but I've just never been compelled enough to figure it out. Here
goes:
1) Our DNS servers are 'doze boxen, running W2K3.
2) Our domain is foo.local -- which I don't love, but it (usually) works.
3) If I do a "host gildor.foo.local", it comes right back with:
gildor.foo.local has address 172.17.0.11
4) If I try to surf to the FQN, no dice. Just the hostname, though, and
all's peachy.
5) Same for pinging: "gildor" works fine, "gildor.foo.local", not so much.
Here's the strace snippet: [and this is where nsswitch.conf was listed,
which made me start tweaking]
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the gnhlug-discuss
mailing list