[gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[Timur Aydin]

Hi,

I have synced my ~x86 system yesterday and after it completed, the 
resolver doesn't work for some programs anymore. For example, ping 
<hostname> says "unknown host name". It doesn't even contact the dns 
server, which is running on the same host. But dig <hostname> works 
fine. Also, using the IP address directly, I can access the internet.

I am suspecting that the new glibc 2.10 is causing this. Anybody else 
having this issue?

-- 
Timur

Re: [gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[Mike Kazantsev]

[-- Attachment #1: Type: text/plain, Size: 804 bytes --]

On Thu, 28 May 2009 22:11:02 +0300
Timur Aydin <ta@taydin.org> wrote:

> I have synced my ~x86 system yesterday and after it completed, the 
> resolver doesn't work for some programs anymore. For example, ping 
> <hostname> says "unknown host name". It doesn't even contact the dns 
> server, which is running on the same host. But dig <hostname> works 
> fine. Also, using the IP address directly, I can access the internet.
> 
> I am suspecting that the new glibc 2.10 is causing this. Anybody else 
> having this issue?

Synced two ~x86 today and one more two days ago, but can't confirm the
issue - everything seem to be working fine.
All three are using nscd (part of glibc) to cache glibc requests,
but shutting it down doesn't seem to matter.

-- 
Mike Kazantsev // fraggod.net

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[Graham Murray]

Timur Aydin <ta@taydin.org> writes:

> Hi,
>
> I have synced my ~x86 system yesterday and after it completed, the
> resolver doesn't work for some programs anymore. For example, ping
> <hostname> says "unknown host name". It doesn't even contact the dns
> server, which is running on the same host. But dig <hostname> works
> fine. Also, using the IP address directly, I can access the internet.
>
> I am suspecting that the new glibc 2.10 is causing this. Anybody else
> having this issue?

I had this issue a couple of weeks ago. I think it was the upgrade to
net-dns/openresolv-3.3.2 which was responsible. The solution was to
edit etc/resolvconf.conf and uncomment the line
name_servers=127.0.0.1

[gentoo-user] Re: Sync'ed my ~x86 system yesterday and now resolver stopped working

[Christer Ekholm]

Timur Aydin <ta@taydin.org> writes:

> Hi,
>
> I have synced my ~x86 system yesterday and after it completed, the
> resolver doesn't work for some programs anymore. For example, ping
> <hostname> says "unknown host name". It doesn't even contact the dns
> server, which is running on the same host. But dig <hostname> works
> fine. Also, using the IP address directly, I can access the internet.
>
> I am suspecting that the new glibc 2.10 is causing this. Anybody else
> having this issue?

I experienced similar problem when I upgraded to glibc-2.10, but the
only thing I had to do was change from 'server' to 'nameserver' in
/etc/resolv.conf (as told by my 'man resolv.conf'). I don't know why I
had only 'server' before, perhaps that was allowed with earlier glibc.

-- 
 Christer

Re: [gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[Timur Aydin]

Graham Murray wrote:
> Timur Aydin <ta@taydin.org> writes:
>
>   
>> Hi,
>>
>> I have synced my ~x86 system yesterday and after it completed, the
>> resolver doesn't work for some programs anymore. For example, ping
>> <hostname> says "unknown host name". It doesn't even contact the dns
>> server, which is running on the same host. But dig <hostname> works
>> fine. Also, using the IP address directly, I can access the internet.
>>
>> I am suspecting that the new glibc 2.10 is causing this. Anybody else
>> having this issue?
>>     
>
> I had this issue a couple of weeks ago. I think it was the upgrade to
> net-dns/openresolv-3.3.2 which was responsible. The solution was to
> edit etc/resolvconf.conf and uncomment the line
> name_servers=127.0.0.1
>
>   
That's what I tried yesterday and it resolved the problem. So it seems 
the new resolver does not default to checking localhost as a dns server 
and needs to be explicitely told to do so...

-- 
Timur

Re: [gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working

[Alan McKinnon]

On Saturday 30 May 2009 23:59:46 Timur Aydin wrote:
> Graham Murray wrote:
> > Timur Aydin <ta@taydin.org> writes:
> >> Hi,
> >>
> >> I have synced my ~x86 system yesterday and after it completed, the
> >> resolver doesn't work for some programs anymore. For example, ping
> >> <hostname> says "unknown host name". It doesn't even contact the dns
> >> server, which is running on the same host. But dig <hostname> works
> >> fine. Also, using the IP address directly, I can access the internet.
> >>
> >> I am suspecting that the new glibc 2.10 is causing this. Anybody else
> >> having this issue?
> >
> > I had this issue a couple of weeks ago. I think it was the upgrade to
> > net-dns/openresolv-3.3.2 which was responsible. The solution was to
> > edit etc/resolvconf.conf and uncomment the line
> > name_servers=127.0.0.1
>
> That's what I tried yesterday and it resolved the problem. So it seems
> the new resolver does not default to checking localhost as a dns server
> and needs to be explicitely told to do so...

Which is a sensible default choice - few machines these days run a local 
resolver. A better default is whatever the DHCP server says the resolvers are. 

-- 
alan dot mckinnon at gmail dot com