Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Chrome gives this error, yet I can ping the server!

The server at www.odesk.com can't be found, because the DNS lookup failed. DNS is the network service that translates a website's name to its Internet address. This error is most often caused by having no connection to the Internet or a misconfigured network. It can also be caused by an unresponsive DNS server or a firewall preventing Google Chrome from accessing the network. Check your Internet connection. Check any cables and reboot any routers, modems, or other network devices you may be using. Check your DNS settings. Contact your network administrator if you're not sure what this means. Try disabling network prediction. Go to the Chrome menu > Settings > Show advanced settings... and deselect "Predict network actions to improve page load performance." If this does not resolve the issue, we recommend selecting this option again for improved performance. Allow Chrome to access the network in your firewall or antivirus settings. If it is already listed as a program allowed to access the network, try removing it from the list and adding it again. If you use a proxy server... Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect "Use a proxy server for your LAN". Error code: ERR_NAME_NOT_RESOLVED

$ ping odesk.com

Pinging odesk.com [64.41.140.207] with 32 bytes of data:
Reply from 64.41.140.207: bytes=32 time=103ms TTL=47
Reply from 64.41.140.207: bytes=32 time=103ms TTL=47
Reply from 64.41.140.207: bytes=32 time=103ms TTL=47
Reply from 64.41.140.207: bytes=32 time=103ms TTL=47

Ping statistics for 64.41.140.207:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 103ms, Maximum = 103ms, Average = 103ms

$ ping www.odesk.com

Pinging e5489.g.akamaiedge.net [23.199.64.63] with 32 bytes of data:
Reply from 23.199.64.63: bytes=32 time=665ms TTL=52
Reply from 23.199.64.63: bytes=32 time=389ms TTL=52
Reply from 23.199.64.63: bytes=32 time=541ms TTL=52
Reply from 23.199.64.63: bytes=32 time=578ms TTL=52

Ping statistics for 23.199.64.63:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 389ms, Maximum = 665ms, Average = 543ms

I restarted Chrome, and I also disabled my network adapter and re-enabled it. I also ran ipconfig /flushdns. 'Predict network actions to improve page load performance' is already off.

share|improve this question

1 Answer 1

up vote 3 down vote accepted

You can try to disable Google Chrome's DNS Prefetching: Settings > Show Advanced Settings > Privacy and disable the option Predict network actions to improve page load performance.

Alternatively, flush Chrome's DNS cache.

enter image description here

More details here.

share|improve this answer
2  
I already had Predict Network Actions turned off, but I think chrome://net-internals/#dns is the ticket! –  Chloe Apr 4 at 19:18
    
I have the same problem, but this solution for me it is not working. (I am using a new tld category) do u have any tips? –  Nk SP yesterday

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.