"ping www.google.com" does not work from linux commandline.
My old resolv.conf was as follows:
nameserver 207.218.192.38
It became clear that 207.218.192.38 came down from H1.
So, I read about the new resolvers available and tried editing resolv.conf.
I changed resolv.conf to read:
nameserver 129.250.35.250
nameserver 129.250.35.251
nameserver 67.15.31.131
The file gets saved. I tried all kinds of combinations and still cannot "ping www.google.com"
What am I doing wrong?
Thanks,
David
Full Version: H1 Resolver Down: Changing resolv.conf doesn't work!
So strange, it seems like there is a delay between setting resolv.conf and it taking effect. (still cannot get ping to work, but am measuring effects with webserver trying to communicate out)
QUOTE (DavidPesta @ Jun 4 2008, 05:50 PM) 
So strange, it seems like there is a delay between setting resolv.conf and it taking effect. (still cannot get ping to work, but am measuring effects with webserver trying to communicate out)
It worked with me. Ping started working after 1 or 2 minutes. Very slow to resolve though.
QUOTE (Torgut @ Jun 4 2008, 01:29 PM)
It worked with me. Ping started working after 1 or 2 minutes. Very slow to resolve though.
A reboot will help. Some processes only load resolv.conf once at runtime and cache the contents. Rebooting will force all apps to grab the new config.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.