1 |
On Saturday 30 May 2009 23:59:46 Timur Aydin wrote: |
2 |
> Graham Murray wrote: |
3 |
> > Timur Aydin <ta@××××××.org> writes: |
4 |
> >> Hi, |
5 |
> >> |
6 |
> >> I have synced my ~x86 system yesterday and after it completed, the |
7 |
> >> resolver doesn't work for some programs anymore. For example, ping |
8 |
> >> <hostname> says "unknown host name". It doesn't even contact the dns |
9 |
> >> server, which is running on the same host. But dig <hostname> works |
10 |
> >> fine. Also, using the IP address directly, I can access the internet. |
11 |
> >> |
12 |
> >> I am suspecting that the new glibc 2.10 is causing this. Anybody else |
13 |
> >> having this issue? |
14 |
> > |
15 |
> > I had this issue a couple of weeks ago. I think it was the upgrade to |
16 |
> > net-dns/openresolv-3.3.2 which was responsible. The solution was to |
17 |
> > edit etc/resolvconf.conf and uncomment the line |
18 |
> > name_servers=127.0.0.1 |
19 |
> |
20 |
> That's what I tried yesterday and it resolved the problem. So it seems |
21 |
> the new resolver does not default to checking localhost as a dns server |
22 |
> and needs to be explicitely told to do so... |
23 |
|
24 |
Which is a sensible default choice - few machines these days run a local |
25 |
resolver. A better default is whatever the DHCP server says the resolvers are. |
26 |
|
27 |
-- |
28 |
alan dot mckinnon at gmail dot com |