Re: Dns resolution failure.. [message #3767 is a reply to message #3764] |
Wed, 14 June 2006 22:20 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to previous message](/theme/ovz3/images/down.png) |
Jonathan
Messages: 10 Registered: September 2005
|
Junior Member |
|
|
We'd still like to know what's causing this, if anyone has a clue!
We're moving the account over to XEN 3.0 in the meantime, as we just can't
find the problem and the customer account has been down several days. ;(
I'm totally bummed. This is weirdness!
Jonathan
On 6/14/06 2:25 AM, "Aaron Stewart" <aaron@firebright.com> wrote:
> Right. nsswitch is unmodified, and its set up for files dns as you have
> below.
>
> Still no resolution. I figured it's probably some issue with the system
> gethostbyname() call, but I can't figure for the life of me what could
> cause it.
>
> Thanks,
> -=Aaron
>
> Roman Kagan wrote:
>> On Tue, Jun 13, 2006 at 11:14:05AM -0700, Aaron Stewart wrote:
>>
>>> What's bugging me (and I can't wrap my brain around it) is that we can ping
>>> the outside world, wget to IP addresses, and ssh into external hosts. The
>>> only thing that seems to be
>>> failing is DNS at the application level.. Again, nslookup and host both work
>>> without issue.
>>>
>>
>> Check that you have 'dns' among the services for 'hosts' map in
>> /etc/nsswitch.conf, e.g.
>>
>> # grep hosts /etc/nsswitch.conf
>> hosts: files dns
>>
>> The point is that 'nslookup' and 'host' do DNS lookups (only) while the
>> applications use (through standard libc functions) whatever is
>> configured for NSS (Name Service Switch).
>>
>> Roman.
>>
>
--
|
|
|