Mick <michaelkintz...@gmail.com> [17-03-06 03:39]: > On Sunday 05 Mar 2017 15:51:37 tu...@posteo.de wrote: > > Hi, > > > > The standard phrase: > > Still building...bla bla...new root...bla... :) > > > > The copy of the udev rules of the old root into the > > new one...give me...hmmmm....network access...somehow... > > (In any case: THX A LOT FOR THAT HINT! 8) > > I am sure there was an older news item explaining the persistent NIC naming. > You could also add an option on the kernel line which has the same effect, > but > I can't recall (without googling) what the correct stanza is. > > > > Several early services, which depend on network access fail > > while booting, but a ping right after login worked. > > > > I am able to firefox the internet now... > > > > Which an exception: www.startpage.com > > > > :Server could not be found. > > > > Same, if I try to ping that beauty. > > Other pages like www.heise.de worked > > fine ... so it is not a missing DNS > > configuration. > > http://downforeveryoneorjustme.com/ > > traceroute startpage.com > > ping -c 3 startpage.com > > nslookup startpage.com > > dig ANY startpage.com > > should show if it is an IP address problem, or a DNS resolution problem. > > -- > Regards, > Mick
Hi Mick, Thanks for your help ! :) since ping startpage.com results in "unknown host" all the commands will not be able to resolve startpage.com. By the way: dig ANY startpage.com results in nothing even on my working old root. Cheers Meino