Can't load google.com

June 07, 2013 03:30

Please read this thread on the old forum:

http://forums.opendns.com/comments.php?DiscussionID=74794

Here is the requested output from nslookup google.com:

Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: google.com
Address: 74.125.239.46
Name: google.com
Address: 74.125.239.36
Name: google.com
Address: 74.125.239.32
Name: google.com
Address: 74.125.239.34
Name: google.com
Address: 74.125.239.33
Name: google.com
Address: 74.125.239.39
Name: google.com
Address: 74.125.239.38
Name: google.com
Address: 74.125.239.41
Name: google.com
Address: 74.125.239.35
Name: google.com
Address: 74.125.239.37
Name: google.com
Address: 74.125.239.40

And the output from nslookup www.google.com.:

Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: www.google.com
Address: 74.125.239.50
Name: www.google.com
Address: 74.125.239.48
Name: www.google.com
Address: 74.125.239.51
Name: www.google.com
Address: 74.125.239.49
Name: www.google.com
Address: 74.125.239.52

I hope this helps someone help me! ;-)

Thanks,

Thad

Comments

13 comments

rotblitz June 07, 2013 06:33

Nothing is wrong with DNS according to this output. This must be an HTTP problem, not a DNS problem. E.g. a latency problem or simply a brower or computer resource problem. Btw, you forgot the trailing dots when executing the nslookup commands, but this didn't matter in this case.

To further investigate the issue, you may post the output of the following commands:

nslookup -type=txt debug.opendns.com.

tracert www.google.com

0

Comment actions Permalink
hawaiithad June 07, 2013 07:03

Here's the terminal transcript:

Thads-iMac:~ Thad$ nslookup -type=txt debug.opendns.com.
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
debug.opendns.com text = "server 9.lax"
debug.opendns.com text = "flags 20 0 2f4 800000000000000"
debug.opendns.com text = "id 0"
debug.opendns.com text = "source 98.155.149.89:47243"

Authoritative answers can be found from:

Thads-iMac:~ Thad$ tracert www.google.com
-bash: tracert: command not found
Thads-iMac:~ Thad$

BTW, I tried the last set of commands both with and without the trailing "." and, as you confirmed, it didn't seem to matter.

Thanks,

Thad

0

Comment actions Permalink
rotblitz June 07, 2013 09:30

You're using the Los Angeles OpenDNS location, and your IP address 98.155.149.89 is not currently registered with any OpenDNS network ("id 0"). This means in case you have any dashboard settings, these do not take effect yet. Not sure if this is your intention.

"Thads-iMac:~ Thad$ tracert www.google.com
-bash: tracert: command not found"

Yes, on a Mac or Linux the command would be:

traceroute www.google.com

Please repeat.

0

Comment actions Permalink
maintenance June 08, 2013 01:04

P.S., the trailing dot is only for nslookup. That's just how nslookup is.

0

Comment actions Permalink
hawaiithad June 08, 2013 01:36

I'm in Hawaii, so I'd guess that using the Los Angeles OpenDHS location makes sense, but please let me know if it does not. Right now, google searches are working. Here's the output from traceroute www.google.com:

Thads-iMac:~ Thad$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using 74.125.239.50
traceroute to www.google.com (74.125.239.50), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 2.333 ms 2.127 ms 2.292 ms
2 cpe-98-155-148-1.hawaii.res.rr.com (98.155.148.1) 59.604 ms 31.885 ms 29.685 ms
3 24.25.232.13 (24.25.232.13) 12.378 ms 12.759 ms 30.567 ms
4 agg11.milnhixd-ccr01.hawaii.rr.com (72.129.45.64) 66.950 ms 61.504 ms 60.817 ms
5 agg31.lsancarc-ccr01.socal.rr.com (72.129.45.0) 68.695 ms 66.470 ms 71.148 ms
6 bu-ether16.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.102) 70.454 ms 78.967 ms 63.725 ms
7 ae-0-0.pr0.lax10.tbone.rr.com (66.109.6.133) 61.183 ms 61.045 ms 60.592 ms
8 * 72.14.198.73 (72.14.198.73) 73.386 ms
72.14.197.157 (72.14.197.157) 174.078 ms
9 64.233.174.238 (64.233.174.238) 101.105 ms
216.239.46.40 (216.239.46.40) 68.996 ms
64.233.174.238 (64.233.174.238) 74.034 ms
10 64.233.174.192 (64.233.174.192) 75.189 ms
64.233.174.190 (64.233.174.190) 71.846 ms
64.233.174.192 (64.233.174.192) 70.304 ms
11 64.233.174.205 (64.233.174.205) 70.417 ms 70.901 ms 72.929 ms
12 209.85.250.61 (209.85.250.61) 112.832 ms 81.286 ms 74.747 ms
13 72.14.232.35 (72.14.232.35) 101.923 ms 75.182 ms 71.125 ms
14 nuq04s19-in-f18.1e100.net (74.125.239.50) 74.929 ms 70.312 ms 70.248 ms

0

Comment actions Permalink
rotblitz June 08, 2013 12:46

Your latency is still good, and quite a lot of hops (14) are involved. Either Google don't operate servers in this part of the Pacific region, or your ISP configured suboptimal routing. Due to the big distance to the OpenDNS location, you may get suboptimal IP address information, the ones from the US westcoast. After all, your problems are not so much DNS related, but have everything to do with network topology, being in a not so well supported area of the world, in the middle of the Pacific.

You may want to try with your ISP's DNS service to see if it becomes better then. If yes, you may want to operate an own DNS server and configuring zones like Google with your ISP's DNS service as forwarder, and for everything else OpenDNS as forwarder.

0

Comment actions Permalink
hawaiithad June 15, 2013 17:47

I cannot reach google's website at the moment. It seems to be the only site I cannot reach. I tried all the commands recommended before and the outputs are all just about the same as before except for traceroute. For that one, I get about a 30 second delay before I get the following. Any ideas?

Thads-iMac:~ Thad$ traceroute www.google.com
traceroute: unknown host www.google.com

0

Comment actions Permalink
hawaiithad June 15, 2013 17:58

I still can't get google.com or www.google.com to load, I can load mail.google.com with no problems!

0

Comment actions Permalink
rotblitz June 15, 2013 22:26

"traceroute: unknown host www.google.com"

This indicates a DNS response timeout, i.e. your DNS query has not been responded to in time.

I have explained above why these problems occur with your location and what you can do against it.

To get a better idea about the impact, you may run this DNS benchmark: https://www.grc.com/dns/benchmark.htm
(You must use a Windows computer for this.)

0

Comment actions Permalink
atook June 18, 2013 14:33

I've been having trouble with google.com, facebook.com & hotmail.com being blocked, but no records showing up for it in my dashboard.

Is this an issue with openDNS or no? If I set the DNS servers to google (8.8.8.8) I've got no problems.

0

Comment actions Permalink
rotblitz June 18, 2013 17:43

@atook
Your symptoms indicate that you haven't registered your current IP address with your OpenDNS network, but somebody else has, and therefore you are using someone else's settings and stats. Get this situation corrected.

https://dashboard.opendns.com/settings/

http://www.opendns.com/support/article/83 (Network Already Exists / IP Address Taken by Another User / !Yours)

0

Comment actions Permalink
atook June 18, 2013 18:27

@rotblitz

I thought that might be the problem, as I've had that occur before. But this time users were blocked, and I was logged into openDNS, onsite, with the correct IP showing up in the dashboard. Last time I had that issue, I couldn't reset the IP due to it being registered with another user.

Is there a way to set my openDNS account to a static IP so a user on my network can't take over our IP?

0

Comment actions Permalink
rotblitz June 18, 2013 23:40

IP addresses are assigned only by ISPs. A static IP address is usually associated with costs. Did you open a support ticket here to get your IP address released?

Further, you can try to reboot your ISP facing device to possible get another IP address assigned.

0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?