DNS resolution issue.

[Ken D'Ambrosio]

On Mon, October 18, 2010 12:32 pm, Benjamin Scott wrote:

> That's historically a sign that you haven't configured your DNS
> suffix search list properly.  E.g., if all hosts in your org have names of
> the form <bar.foo.local.>, then your resolv.conf should have a line like
> this in it:
>
> search foo.local

Nope; my resolv.conf line is thus:
search foo.local foo.com jots.org

(I like resolving my own domain, too).  I hadn't entered that to my
original e-mail, yet, as I suddenly found stuff that was working.  Don't
forget, also, that "host gildor.foo.local" and "host gildor" both came
back, ASAP, with valid responses.  (Sidenote: I wonder if "host" bypasses
nsswitch.conf entirely, and just checks DNS-specific files, such as
resolv.conf.  Updated: I guess so.  I modified /etc/hosts to resolve
gildor to 127.0.0.1.  That's where ping, then, looks, as per
nsswitch.conf, but "host" still goes to the DNS-resolvable IP.  Which
would explain the delay bit in the Ubuntu tech note, below.)


> I suspect your name-resolution configuration is still broken, and
> you just happened to find a combination of options which masks the
> trouble.

I don't have an answer, but googling on mdns4_minimal showed me I'm not
alone, either:

https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/94940

Apparently, things *are* resolving... just very, very slowly.  And, as per
my strace, ping seems to time out after five seconds.  Ubuntu-only issue?

-Ken


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.