From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MAWZk-00084Q-JZ for garchives@archives.gentoo.org; Sat, 30 May 2009 21:58:48 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1BFB2E03B7; Sat, 30 May 2009 21:58:47 +0000 (UTC) Received: from bonsai.taydin.org (mail.taydin.org [78.189.26.160]) by pigeon.gentoo.org (Postfix) with ESMTP id ACF8EE03B7 for ; Sat, 30 May 2009 21:58:46 +0000 (UTC) Received: from [127.0.0.1] (bonsai.taydin.org [127.0.0.1]) by bonsai.taydin.org (Postfix) with ESMTPA id 3915E2C4A6C for ; Sun, 31 May 2009 00:59:51 +0300 (EEST) Message-ID: <4A21AC52.1020807@taydin.org> Date: Sun, 31 May 2009 00:59:46 +0300 From: Timur Aydin User-Agent: Thunderbird 2.0.0.21 (X11/20090430) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Sync'ed my ~x86 system yesterday and now resolver stopped working References: <4A1EE1C6.7030807@taydin.org> <87fxenw60t.fsf@newton.gmurray.org.uk> In-Reply-To: <87fxenw60t.fsf@newton.gmurray.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 94f26898-a22b-419a-8872-c02f12d35cd7 X-Archives-Hash: 520087b9d8bf8f94a4f6d81480032569 Graham Murray wrote: > Timur Aydin 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 >> says "unknown host name". It doesn't even contact the dns >> server, which is running on the same host. But dig 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