OpenDNS Forums
The official support and discussion site of OpenDNS
Support
K-12 Forums
Categories
- Administrative
- Adult site blocking
- DNS-O-Matic / dynamic IPs
- Domain blocking
- Domain Name System (DNS) troubles
- Mobile instructions
- OpenDNS services
- Proxies, accelerators, and more
- Router instructions
- Satellite
- Shortcuts
- Wishlists and feature requests
-
Feeds
Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.
This discussion has been inactive for longer than 30 days, and is thus closed.
-
- CommentAuthordevilboy3007
- CommentTimeMay 12th 2009
Is it down for you or it is it just me?Thankful People: mitchflorida -
- CommentAuthortracymckibben
- CommentTimeMay 12th 2009
It's google.navigation.opendns.com that is down. I can get to google.com just fine if I bypass OpenDNS. Started about 20 minutes ago. -
Same for me.
-
- CommentAuthoraramis34143
- CommentTimeMay 12th 2009
Same here - and not the first time for me since I started using opendns. This alone may be enough to convince me to stop using the service.
Google of all things? Seriously?!? -
Confirmed, only openDNS is not resolving this domain. I am sure it has todo with the way OpenDNS blocks googles privacy flaws.
-
Same thing for me, moved off opendns and google worked
-
yeah, discovered this a few minutes ago. 74.125.67.100 gets to google, so it is the opendns blocking it
-
- CommentAuthorpsmantaring
- CommentTimeMay 12th 2009
I've got the same thing going on... I moved off of opendns and it works again... any new why? -
Considering this started no more then 30 minutes ago I would say wait for an official update.
-
- CommentAuthormaintenance
- CommentTimeMay 12th 2009
Seems to be down. No, not just you. -
psmantaring:
OpenDNS employs a special way for resolving google to protect your privacy. This seams to be broken ATM. -
You can turn off proxy if you have an account and it will temporarily fix the issue.Thankful People: Nils Lorvick, Jared Petry, Mark, iengine, aramis34143
-
Open DNS resolving to google.navigation.opendns.com
What's up with that?!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Program Files\Windows Resource Kits\Tools>ping www.google.com
Pinging google.navigation.opendns.com [209.69.36.231] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 209.69.36.231:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Program Files\Windows Resource Kits\Tools>ping news.google.com
Pinging news.l.google.com [72.14.205.147] with 32 bytes of data:
Reply from 72.14.205.147: bytes=32 time=34ms TTL=244
Reply from 72.14.205.147: bytes=32 time=34ms TTL=244
Reply from 72.14.205.147: bytes=32 time=46ms TTL=244
Reply from 72.14.205.147: bytes=32 time=40ms TTL=244
Ping statistics for 72.14.205.147:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 46ms, Average = 38ms
C:\Program Files\Windows Resource Kits\Tools> -
- CommentAuthorturbogizzmo
- CommentTimeMay 12th 2009
Weeee fielding calls from multiple people that I recommended OpenDNS to that cant get to google....and to think today wasnt busy enough...ha!
-
Guess it is back to using my ISP for DNS... Come on OpenDNS! As aramis34143 points out GOOGLE of all things!! I've got a line of people at my office door...
-
- CommentAuthorturbogizzmo
- CommentTimeMay 12th 2009
go go gadget dnsmgmt, good thing i keep my ISP dns at the bottom....bump them to the top and OpenDNS to the bottom...for now. -
Ok, using the same concept as the folks above, I went to my win 2000 DNS consol and added a new site "google.com" with a new host "www" point to 74.125.67.100. Worked like a champ.
Good quick (temporary) fix until opendns fixes this.Thankful People: turbogizzmo -
I am also unable to get to google.com or gmail.com with OpenDNS settings in my DNS. Switching to any other DNS server works fine. This should be classified as an outage as google is a main site on the web.
-
So how do I fix this short of taking opendns out?
-
- CommentAuthorsmcculley_ddb
- CommentTimeMay 12th 2009
Turn off proxy and auto-correct. Worked for me. -
Where?
I have just created account on opendns otherwise I am using the openDNS ip addresses for a while. -
- CommentAuthordl-itstaff
- CommentTimeMay 12th 2009
Turn off proxy and auto-correct. also Worked for me. -
we should not have to do that to make it work. OpenDNS should get this problem fixed immediately!!!
-
########################################
#### TEMPORARY FIX FOR GOOGLE ISSUE ####
########################################
Click Dashboard (top Menu)
Click Settings (middle menu near the top)
Click Advanced Settings (left Menu)
Scroll down to Network Shortcuts
Uncheck: Enable OpenDNS proxy
Click Apply (make sure you apply it to the correct network or all networks if you have more than one)
In 3-5 minutes goggle should be reachable again.
Thanks to laurenec for pointing out the original fix.
-
Problem is, our network admin is out of the country. We don't have the login for OpenDNS to make this change. What else can we do?
-
I just changed my dns back (was on my way to uncheck proxy) but I think its working like normal again.
...........
edit - nevermind -
- CommentAuthorJared Petry
- CommentTimeMay 12th 2009
jbeckh2: Just wait it out, OpenDNS will fix it.. hopefully.
iengine: Thanks, that solution worked perfect! -
- CommentAuthorhalonut558
- CommentTimeMay 12th 2009
I am not switching my network back to opendns until they admit that they dropped the ball on what is most likely the hardest target address to overlook. shame shame. -
I'm not having any problems with Google. I'm using the London/UK server.
And if I had, who cares, I take my privacy very serious and therefore use:
https://ssl.scroogle.org/
https://ixquick.com/
I don't understand why one is keen to get any movement on the internet tracked... -
I agree, yes this is an inconvenience, however people please tone down the negativity towards OpenDNS. Considering they are providing a free service that you could otherwise pay thousands of dollars for, you have nothing to gripe about.
As well, if you don't have a backup plan to mitigate these type of issues, the shame is on you.
(Use iengine's fix if you have an OpenDNS account and can log in; paste below)
Click Dashboard (top Menu)
Click Settings (middle menu near the top)
Click Advanced Settings (left Menu)
Scroll down to Network Shortcuts
Uncheck: Enable OpenDNS proxy
Click Apply (make sure you apply it to the correct network if you have more than one)
In 3-5 minutes Google should be reachable again. -
- CommentAuthormaintenance
- CommentTimeMay 12th 2009
I've read in a couple fora (with no sources) including another thread here, that it is a routing issue, and not an OpenDNS problem.
Haven't seen anything solid yet, though. -
I took the opendns addresses out as well, not worth going through something new here by setting up network (I'm not sold on why I should do that).
Google is unfortunately too big for it to be down. Will check back later to see if opendns is fixed. -
Thanks again to those who posted some fix ideas.
-
Found a work around for now. I entered the following in my HOSTS file:
74.125.67.100 google.com
74.125.67.100 www.google.com
74.125.67.100 skins.gmodules.com
74.125.67.100 gmodules.com
The gmodules entries are for the iGoogle page. -
same problem - I changed the settings but it hasn't taken effect yet.
While troubleshooting the problem though I tried some public DNS servers that worked, and found they are much faster on all sites than OpenDNS. Why is OpenDNS so slow? I might not switch back now that I see this new speed. -
- CommentAuthorhardinginst
- CommentTimeMay 12th 2009
Turned off OpenDNS proxy as per above and that fixed it for us.
This is the 2nd time in the last couple of weeks that google has been "down" for us. I didn't even think to check OpenDNS the first time but I'm wondering if this proxying was the cause as well. What does it do exactly? -
- CommentAuthorURL Examiner
- CommentTimeMay 12th 2009
Looks like a routing problem at NTT (https://ws.arin.net/whois/?queryinput=209.69.36.230) as the trace routes from two different ISP die at NTT.Thankful People: maintenance -
- CommentAuthorchristiann
- CommentTimeMay 12th 2009
Here is my trace route:
Hop Hostname IP Time 1 Time 2
1 Home.local 192.168.1.101 0.256ms LN
1 192.168.1.1 192.168.1.1 1.778ms LN
1 192.168.1.1 192.168.1.1 1.341ms LN
2 ppp-70-132-145-30.dsl.hstntx.swbell.net 70.132.145.30 6.656ms R
2 ppp-70-132-145-254.dsl.hstntx.swbell.net 70.132.145.254 43.412ms LN
3 dist2-vlan50.hstntx.sbcglobal.net 151.164.11.125 47.178ms LN
4 bb2-g2-0.hstntx.sbcglobal.net 151.164.43.42 46.932ms LN
5 69.220.8.57 69.220.8.57 54.402ms LN
6 asn6395-broadwing.eqdltx.sbcglobal.net 151.164.249.82 50.878ms LN
7 ae-1.r21.dllstx09.us.bb.gin.ntt.net 129.250.4.181 53.635ms LN
8 as-0.r21.chcgil09.us.bb.gin.ntt.net 129.250.3.16 75.036ms LN
9 no reply *
and here is my second trace route:
Hop Hostname IP Time 1 Time 2
1 Home.local 192.168.1.101 0.161ms
1 192.168.1.1 192.168.1.1 1.416ms
1 192.168.1.1 192.168.1.1 1.452ms
2 ppp-70-132-145-30.dsl.hstntx.swbell.net 70.132.145.30 1.392ms R
2 ppp-70-132-145-254.dsl.hstntx.swbell.net 70.132.145.254 43.300ms K
3 dist2-vlan50.hstntx.sbcglobal.net 151.164.11.125 45.309ms
4 bb2-g2-0.hstntx.sbcglobal.net 151.164.43.42 47.200ms
5 69.220.8.57 69.220.8.57 52.390ms
6 asn6395-broadwing.eqdltx.sbcglobal.net 151.164.249.82 51.552ms
7 ae-1.r21.dllstx09.us.bb.gin.ntt.net 129.250.4.181 52.645ms
8 as-0.r21.chcgil09.us.bb.gin.ntt.net 129.250.3.16 77.290ms
9 no reply *
10 fa-9-16.r01.chcgil09.us.ce.gin.ntt.net 128.242.180.46 266.552ms
11 no reply *
12 no reply *
13 no reply *
14 no reply *
15 no reply *
16 no reply *
17 no reply *
18 no reply *
19 no reply *
20 no reply *
21 no reply *
22 no reply *
23 no reply *
24 no reply *
25 no reply *
26 no reply *
27 no reply *
28 no reply *
29 no reply *
30 no reply *
31 no reply *
OpenDNS or has the internet broken in half? -
- CommentAuthorJared Petry
- CommentTimeMay 12th 2009
christiann: A router is down on the way to the OpenDNS server, so the request your browser is sending is being rejected. That's why you get connection errors for Google. -
Looks like opendns is directing www.google.com traffic to a CNAME of google.navigation.opendns.com. The server and/or connection the CNAME is going to is down.
The question is why is opendns directing www.google.com there in the first place. -
@tehgeek
Then the proxy the CNAME is pointing to is down. -
I'd really like to get some input from OpenDNS here. I can confirm that I could not access Google for a while. An official statement on the situation would be great.
-
AdministratorThis was a serious bug in our system and we resolved it. We are sincerely sorry for causing it and unfortunately it took about 90 minutes to fix.
We love Google as much as the next person. We're also investigating how this possibly eluded our monitoring system which should have tipped us off within minutes of it occurring.Thankful People: newhopenet, Mark, tehgeek, maintenance, btnet, kai0126 -
Ok, Google is apparently back for me. But I'm getting random internet spikes. Sometimes is good, other times it's extremely slow.
-
david,
thanks for the update. Things happen, I'm sure you still have a pretty big fan base.
-C -
- CommentAuthorURL Examiner
- CommentTimeMay 13th 2009
DavidU, I am glad you found and corrected the problem. Maybe your future solution could include an automated means to change the IP addresses to that of the real google servers in the event of equipment/software failure on your proxy's. Better to resolve and not be proxied than not to resolve at all.
Thanks for the prompt repairs.
1 to 48 of 48
This discussion has been inactive for longer than 30 days, and is thus closed.
