Re: Resolvable unknown host

Great! While the fix wasn't exactly what I was shooting at, I was
imagining that the two applications were using different files/ways to
resolve the IP.

Sometimes the best help is to find a good lab dog. Glad to be one.

-Ben

James Zuelow wrote:
> Ben wrote:
>
>> James,
>> =20
>> Do you happen to have this host defined in /etc/hosts?
>> =20
>> -Ben
>> =20
>>
>
> No, it was resolved with DNS only. But you fixed my problem. (Yay!)
>
> I actually resolved it composing this message, because I wanted to show
> you what /etc/resolv.conf looks like. I looked at my desktop machine
> first and noticed a discrepancy between my desktop and the machine with
> the name issue.
>
> The machine in question needs to resolve hostnames in two domains. So
> /etc/resolv.conf had two search entries:
>
> search office.local
> search ci.juneau.ak.us
>
> The host utility understood this syntax, and would happily try one, then
> the other and resolve hostnames to the correct domain.
>
> However ping seems to work differently. I'm guessing that ping was
> using the last search entry, instead of both. (Which begs the question
> -- does ping have it's own resolver code, different than the dnsutils
> package?) That meant that ping tried to find cw3-wxp.ci.juneau.ak.us,
> which doesn't exist.
>
> Changing the search line to read:
>
> search office.local ci.juneau.ak.us
>
> resolves the issue. Now ping can resolve hostnames in either the
> office.local OR ci.juneau.ak.us domains.
>
> Thanks Ben!
>
> James Zuelow....................CBJ MIS (907)586-0236
> Network Specialist...Registered Linux User No. 186591
> ---------
> To unsubscribe, send email to <aklug-request@aklug.org>
> with 'unsubscribe' in the message body.
>
>
>

---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
Received on Thu Dec 28 11:21:30 2006