(This message is more of a general commentary than a specific reply.)
On Tue, 3 Jun 2003, at 4:28pm, [EMAIL PROTECTED] wrote:
> Ayup, it's only trying eng.lab, not the other domains listed in my
> /etc/resolv.conf file, which also seems to indicate that my DNS server
> isn
rectly to the DNS resolver library.
Ben> That can occasionally introduce subtle problems.
And it appears to be doing so :) I can ping the system just fine,
but can't 'host' it.
Ben> Try "host -v foo" as well. That might offer clues.
Ayup, it's only trying
sox.eng.lab", punted it up to
>a root nameserver, and that root nameserver stated authoritatively that
>there is no ".lab" top-level domain.
Though, ironically, on a different system with an identical /etc/resolv.conf
file, everything works just fine!
I'm wondering if
On Tue, 3 Jun 2003, at 3:15pm, [EMAIL PROTECTED] wrote:
> Am I doing something wrong, or am I misunderstanding the /etc/ resolv.conf
> file? *Should* this work?
One thing to be aware of is that "host" (and "nslookup" and "dig" too)
deliberately bypasses t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] writes:
> Which is pretty much what I stated above. However, this does not
> seem to be the way my resov.conf file is working:
>
> $ cat /etc/resolv.conf
>
> search eng.lab eng.foo.com corp.foo.co
of the domains listed in the 'search' line with the
caveat being that the search will stop on the first match. Thus, if
'penguin' exists in all three domains listed above, I will only get a
return for 'penguin.foo.com' and not the others.
According to the resolv.conf
