From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 918D21391DB for ; Sat, 26 Jul 2014 21:00:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3C694E0E44; Sat, 26 Jul 2014 21:00:12 +0000 (UTC) Received: from mail-wg0-f66.google.com (mail-wg0-f66.google.com [74.125.82.66]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0E727E0CEC for ; Sat, 26 Jul 2014 21:00:10 +0000 (UTC) Received: by mail-wg0-f66.google.com with SMTP id a1so1910687wgh.9 for ; Sat, 26 Jul 2014 14:00:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=q8CaUfCJc+gKKP2u2m7HlPg6+OwVBpE7h5IAfUeqIvs=; b=aYO41J0zKklqDXHMTzB5pBe8Q5uLu/UXdXaf9Ks0Cf5v+Elwl48AHGrQgkTCMqs4PV fYxvrFndsNTODSrWP8cUGokkTL0L331Z+AC1YO0DmkYk+GmVojkITP6AKB/h68XEcckn Mrb2cOKjB/6JA11pupP7q5WUH5mf33Fryfht8RndCOzKfhRApF1TBJrI3rFGXHb40X0G t8hzRnQ+M3nDOTaEPW7LvFKJbuxXUGVa1qf5PN8gkf4vYsDfRbwlR6oGGRKt/V4Xmw8F n1PvOqjxaAo2q4g6wWX2syq+g4igzhrPk7ZJucCqACqsFPxp0CZ7FN/swlDCaYwGkDKO EzAw== 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 X-Received: by 10.180.187.113 with SMTP id fr17mr15840139wic.51.1406408409491; Sat, 26 Jul 2014 14:00:09 -0700 (PDT) Received: by 10.180.75.235 with HTTP; Sat, 26 Jul 2014 14:00:09 -0700 (PDT) In-Reply-To: <2085095.1SX8G0RYVZ@wstn> References: <53D3F137.3040308@gmail.com> <2085095.1SX8G0RYVZ@wstn> Date: Sun, 27 Jul 2014 00:00:09 +0300 Message-ID: Subject: Re: [gentoo-user] Something went wrong with DNS, plz help! From: Grand Duet To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 33c00b1a-0ebb-4073-a20f-1f63498ec0c9 X-Archives-Hash: 0559f098126740b6b42e7eec3d14d908 2014-07-26 22:43 GMT+03:00 Peter Humphrey : > On Saturday 26 July 2014 22:16:53 Grand Duet wrote: >> 2014-07-26 21:19 GMT+03:00 Alan McKinnon : >> > On 26/07/2014 18:16, Grand Duet wrote: >> >> 2014-07-26 19:02 GMT+03:00 Alan McKinnon : >> >>> On 26/07/2014 17:23, Grand Duet wrote: >> >>>> The first reboot after recent update of the system have >> >>>> shown that I cannot open any webpage in Firefox. >> >>>> >> >>>> More exactly, Firefox or my system cannot any more resolve >> >>>> URL to IP address (sorry if I use wrong terms). >> >>>> >> >>>> Thus, >> >>>> >> >>>> host gmail.com >> >>>> >> >>>> gives: >> >>>> ;; connection timed out no servers could be reached >> >>>> >> >>>> Nevertheless >> >>>> >> >>>> dig @8.8.8.8 gmail.com >> >>>> >> >>>> reports the corresponding IP adresses. >> >>>> >> >>>> I have not changed any my network settings and my >> >>>> /etc/conf.d/net file still contains list of my DNS servers >> >>>> that contains server 8.8.8.8 as well but somehow it is >> >>>> not enough any more. :( >> >>>> >> >>>> During my last system update, I suddenly found that >> >>>> I had to update about 150 packages, what was a little >> >>>> bit strange as I update my system at least once a week. >> >>>> >> >>>> I have attributed that to the remnants of gnome2 (now I am using >> >>>> fxce4) that I have not cleaned completely and that is now going >> >>>> to update. So, I deviated a bit from my usual system update routine >> >>>> trying to fix that. Nevertheless, as to my view, during my system >> >>>> update >> >>>> I did nothing to distroy the DNS lookup. >> >>>> >> >>>> Luckily, I save my system update logs and now can attach >> >>>> the last one to this e-mail. >> >>>> >> >>>> Please, help me to recover my internet access, >> >>>> as I still have to do a lot of real work till Monday >> >>>> and have not enough time to investigate this problem >> >>>> alone and without a proper internet access. :( >> >>> >> >>> what is the contents of /etc/resolve.conf? >> >>> >> >> # Generated by net-scripts for interface lo >> >> domain mynetwork > > That isn't right. It should say it's for interface eth0. At first I thought > eth0 wasn't being brought up, but then you quoted replies from dig, > so it must be. After the last reboot I magically have got the right /etc/resolv.conf with DNS servers IPs. Even more strange is that it happened *without* my intervention: just a few reboots (one was no enough!). This, by the way, reminds me MS Windows very much. I am afraid that you will not believe me, but I really did not changed any configuration and have not (re)emerged anything after the previous reboot. Why it did not worked then and does work now? It is really very strange! >> >> That is all. >> >> >> >> I tried to add here lines like: >> >> nameserver 8.8.8.8 >> >> >> >> but found out that this file is rewritten on every reboot. >> >> >> >> My net try was to create /etc/resolv.conf.tail file >> >> and put that line there but that did not help either. >> > >> > Then the problem is obvious - you have no nameserver entries as you >> > don't create any. The computer can't make them up by magic... >> >> But it did it just before the last update: it created DNS entries in >> /etc/resolv.conf >> from my /etc/conf.d/net file on every reboot. And now it "cannot do this >> magic"? >> > You need to create static nameserver entries because you use a static >> > (i.e. no dhcp) configuration. Add them to /etc/resolvconf.conf >> >> It does not help as /etc/resolv.conf is overwritten on every reboot. >> >> > If it still gets removed across restarts >> >> Yes, it does. > > Do you still have netifrc installed? Maybe it got lost in all that updating > work. Try emerging it again anyway. As I have already written, DNS resolution now magically works again and without any intervention from my side: just a few reboots (one was no enough!). So, no need to re-emerge netifrc now. > Do your 90-network-rules look like mine? > > $ cat /lib/udev/rules.d/90-network.rules > # do not edit this file, it will be overwritten on update > > # /etc/udev/rules/90-network.rules: triggering network init-scripts > > # Activate our network if we can > SUBSYSTEM=="net", ACTION=="add", RUN+="net.sh %k start" > SUBSYSTEM=="net", ACTION=="remove", RUN+="net.sh %k stop" My file is exactly the same, and it was changed on May 10, 2014 last time. So, it could not be the cause. > I'm clutching at straws here, and I hear others doing the same ;-( Everything is very, very strange.