Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

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.

Domain Name System (DNS) troubles: Opendns killing my web browsing

Bottom of Page

1 to 26 of 26

  1.  
    • CommentAuthoralex1002
    • CommentTimeSep 15th 2009
     permalink
    For the past few days, I am unable to access many common websites, the site a.id.opendns.com takes too long to load and cannot continue to my wanted website. Even google or gmail cannot load properly. I think the opendns ads is causing my problems.
    Can someone advice, I have taken opendns off for now.
    Thankful People: mwhemus
  2.  permalink
    I've noticed the same thing. The problem, I believe, is because a.id.opendns.com resolves to 10.107.64.23, which is in an IANA-reserved private IPv4 network range (http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses). In other words, OpenDNS has assigned what is probably their internal address to what I suspect is the blocking message address.

    I've sent a couple of e-mails to Support about this just a few minutes ago. I suggest you do the same. The more complaints they get, the faster they will react.
    Thankful People: mwhemus
  3.  permalink
    Ha! Just before I checked your post, I experienced the very same problem. I assume that it was because the domain I was trying to visit is no longer valid for some reason, or down temporarily. It was directing me to the Guide, but nothing ever loaded. Other tries result in a straight timeout without attempting to load from a.id.opendns.com.

    For my example - adviserxp.com, cache Check shows SERVFAIL across the board.
    Domain & AS info here: http://www.robtex.com/dns/adviserxp.com.html

    A tracert to the nameserver succeeds, but with a heavy timeout. Some other domains controlled by the same nameserver do load normally, however.

    5 20 ms 20 ms 21 ms ex3-p8-1.eqchil.sbcglobal.net [151.164.191.250]
    6 19 ms 20 ms 20 ms te7-2.ccr02.ord03.atlas.cogentco.com [154.54.11.237]
    7 21 ms 20 ms 20 ms vl3498.ccr02.ord01.atlas.cogentco.com [154.54.5.1]
    8 44 ms 42 ms 42 ms te4-7.ccr02.ymq02.atlas.cogentco.com [154.54.28.6]
    9 49 ms 50 ms 50 ms 38.104.155.18
    10 * * * Request timed out.
    11 49 ms 50 ms 50 ms ns1.e-corp.net [216.95.221.11]


    This is the URL when a.id.opendns.com times out.
    http://a.id.opendns.com/?final=http%3A%2F%2Fguide.opendns.com%2F30167003%2Fadviserxp.com%2F
    • CommentAuthormaintenance
    • CommentTimeSep 15th 2009 edited
     permalink
    That's weird, Mark. *.id.opendns.com is 67.215.67.9
    Connecting via IP results in (a rather expected) 404.

    Running a tracert does indeed indicate [10.107.64.123], however.

    Cross reference http://forums.opendns.com/comments.php?DiscussionID=4892

    guide.opendns.com is itself timing out (Waiting for...). When reached, the page loads slowly and is incomplete (Transferring data from...).

    After 6 attempts at reloading, the logo finally appeared.

    Either this is the same problem that others were having with the Guide and Block pages previously, or the engineers are working on something.
  5.  permalink
    Guide has been timing out for me too. A ping of a.id.opendns.com reveals 10.107.64.23, although pinging just id.opendns.com reveals 67.215.77.130.

    I was going to try to work around the problem by adding "67.215.67.9 a.id.opendns.com" to my hosts file. But now the problem seems to be that guide.opendns.com is not responding.

    I've noticed that there were similar problems with Comcast a month ago. I'm a Comcast user. Could this be related to Comcast and not OpenDNS?
  6.  permalink
    It *may* have something to do with routing. Do your tracerts indicate Cogentco AS?

    I've been deprived of the Comcastic experience. I've got AT&T DSL.
    • CommentAuthorpachy
    • CommentTimeSep 15th 2009
     permalink
    I suspect that your ISP may be attempting to stealthily block OpenDNS for some stupid reason.
  8.  permalink
    Well, Mainenance, as you've got AT&T but your tracerts still showed 10.107.*.*, I guess it's not a Comcast issue. I'm not at home right now, but as I recall my tracerts did indicate Cogentco. Is there some signifigance to that?

    But it's probabaly moot - it appears to be fixed (http://forums.opendns.com/comments.php?DiscussionID=4892#Item_4). I'll check it out tonight.
    • CommentAuthorrotblitz
    • CommentTimeSep 15th 2009 edited
     permalink
    @Mark Tomlinson
    "Guide has been timing out for me too"
    It is known that the guide and block pages take too long to load nowadays.
    http://forums.opendns.com/comments.php?DiscussionID=4859
    http://forums.opendns.com/comments.php?DiscussionID=4667
  10.  permalink
    Yep, Rotblitz, but it seems to be fixed now. A support ticket I opened has been answered with "This should now be fixed. Sorry for any inconvenience." No explanation showed up on my RSS feed either. Seems like a pretty big oops to leave unexplained.
  11.  permalink
    @Mark Tomlinson

    It was explained in the cross reference thread I linked above.
    http://forums.opendns.com/comments.php?DiscussionID=4892#Item_4
    They were putting new code into production, with the commonly attendant server barfing known to occur in such situations.
    • CommentAuthorlogikcoder
    • CommentTimeSep 16th 2009
     permalink
    Im not sure if its the same issue, but since a few days ago i can not longer type lets say "youtube" in the safari url bar, though it used to work like charm. I thought it was some kind of virus or dns hijack installed on my mac, but after checking it throughly for some time i noticed that the "search domain" feature is either down or not working at all.

    Have a look at the following output:

    bash$ ping amazon
    PING amazon.guide.opendns.com (208.69.34.132): 56 data bytes
    ^C
    --- amazon.guide.opendns.com ping statistics ---
    63 packets transmitted, 0 packets received, 100% packet loss

    That IP address is no longer answering my ping requests, which i believe is the reason on why i cannot longer type "http://youtube/" or "http://amazon/" in the address bar.
    • CommentAuthorlogikcoder
    • CommentTimeSep 16th 2009
     permalink
    bash$ traceroute 208.69.34.132
    traceroute to 208.69.34.132 (208.69.34.132), 30 hops max, 40 byte packets
    1 xxx.xx.x.xxx (xxx.xx.x.xxx) 0.116 ms 0.117 ms 0.023 ms
    2 xxx.xx.xxx.xx (xxx.xx.xxx.xx) 0.454 ms 0.517 ms *
    3 te-8-4-1000.r00.chcgil09.us.bb.gin.ntt.net (128.242.180.33) 0.958 ms * *
    4 * * *
    5 * * *
    6 ae-0.r20.nycmny01.us.bb.gin.ntt.net (129.250.2.25) 43.177 ms * *
    7 as-1.r22.londen03.uk.bb.gin.ntt.net (129.250.3.255) 92.411 ms * *
    8 * po-4.r01.londen03.uk.bb.gin.ntt.net (129.250.5.234) 129.296 ms 97.770 ms
    9 83.231.146.198 (83.231.146.198) 98.427 ms 98.405 ms 95.670 ms
    10 * * *
    11 * * *
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * * *
    17 * * *
    18 * * *
    19 * * *
    20 * * *
    21 * * *
    22 * * *
    23 * * *
    24 * * *
    25 * * *
    26 * * *
    27 * * *
    28 * * *
    29 * * *
    30 * * *
    bash$
  14.  permalink
    You've got some bad routing there. Notice you've jumped to the U.K.
  15.  permalink
    why would amazon.guide.opendns.com or youtube.guide.opendns.com answer ping requests?
    they dont exist.. also, tracert is a better tool then ping.. as many webservers dont reply to ping due to ddos protection..
  16.  permalink
    why is it translating ping amazon to amazon.guide.opendns.com
    ping amazon should fail as amazon is not a domain name and ping doesnt understand keywords..
    as i get here

    Ping amazon
    Ping request could not find host amazon. Please check the name and try again.
    • CommentAuthorHan
    • CommentTimeSep 18th 2009 edited
     permalink
    The aim of this issue is user who under my control will see block page. And they may known that problem is not good for them and they will find a culprit software or something like that (now is OpenDNS Updater) and they try to delete it.


    Why do not you remove block page to make them do not know we are using OpenDNS?
    • CommentAuthorrotblitz
    • CommentTimeSep 18th 2009
     permalink
    @anhminh1232002
    Apply for this: http://blog.opendns.com/2009/09/14/introducing-opendns-deluxe-and-opendns-enterprise/
    There is possibly a fully customizable block page or none at all.
    • CommentAuthormwhemus
    • CommentTimeSep 18th 2009 edited
     permalink
    I am having the same problem, tried refreshing cachecheck but it still returns the intranet IP address for some of the opendns servers, here is the results :

    Results for a.id.opendns.com

    United StatesChicago, Illinois, USA Dallas, Texas, USA
    67.215.67.44 10.107.64.44
    Los Angeles, California, USA Miami, Florida, USA
    10.107.64.44 10.107.64.44
    New York, New York, USA Palo Alto, California, USA
    67.215.67.44 67.215.67.44

    Seattle, Washington, USA Washington, DC, USA
    10.107.64.44 67.215.67.44

    EuropeAmsterdam, The Netherlands London, England, UK
    10.107.64.44 67.215.67.44
    • CommentAuthorschafir
    • CommentTimeSep 18th 2009
     permalink
    I cannot search from my firefox location bar or access shortcuts. All attempts to go to
    "a.id.opendns.com" fail with a "problem loading page" error. Also does not work on my
    wife's macbookpro which has local opendns settings. I have followed all of the
    suggestions for fixing shortcuts and it still doesn't work. Is this an OpenDNS problem or
    a local problem on my machine/network?
    • CommentAuthorrotblitz
    • CommentTimeSep 18th 2009
     permalink
    After my experience it is a pure browser configuration issue.
    • CommentAuthorschafir
    • CommentTimeSep 18th 2009
     permalink
    To add to my situation above: opendns.com/welcome says I am using opendns. guide.opendns.com opens fine. Any search or shortcut from my firefox location bar fails with a "problem loading page error" with a.id.opendns.com failing to load. I cannot ping a.id.opendns.com.

    All Firefox settings are as prescribed by opendns.com shortcut troubleshooting.

    Could my ISP (Qwest) be messing things up on the way out from my dsl modem?
    • CommentAuthorrotblitz
    • CommentTimeSep 18th 2009
     permalink
    "All Firefox settings are as prescribed by opendns.com shortcut troubleshooting."
    I found those not really being accurate.
    Try this:
    1. Type "about:config" in the address bar
    2. Filter on "keyword". Find keyword.URL and keyword.enabled
    3. Set keyword.URL = http://guide.opendns.com/?url=
    4. Set keyword.enabled = true
    See if your OpenDNS shortcuts work then.

    Also, I never stumbled over this a.id.opendns.com. I would have seen this in my internal DNS traffic log.
    • CommentAuthorschafir
    • CommentTimeSep 18th 2009
     permalink
    Hi Rotblitz, thanks for the suggestions. I changed the keyword settings in Firefox
    as you suggested, but the shortcuts still don't work. Every time I search from the
    location bar or try a shortcut, the system can't find the domain a.id.opendns.com.

    I am at a loss at his point.
    • CommentAuthorrotblitz
    • CommentTimeSep 18th 2009 edited
     permalink
    I'm too. Open a ticket: http://www.opendns.com/support/contact/

    [Remainder removed, as my next message is replacing this.]
    • CommentAuthorrotblitz
    • CommentTimeSep 19th 2009 edited
     permalink
    Stange, I was looking further into it.

    "They were putting new code into production, with the commonly attendant server barfing known to occur in such situations." (@maintenance)
    It seems to me that they try this out on selected servers only, as I am far not impacted using the London/UK servers. This apparently new a.id.opendns.com technique does not seem to play a role at all here. It's also mentioned at http://forums.opendns.com/comments.php?DiscussionID=4916 and http://forums.opendns.com/comments.php?DiscussionID=4892

    And even more weird is that some of the OpenDNS servers point to the private IP address 10.107.64.44 for a.id.opendns.com, which certainly breaks surfing...
    http://www.opendns.com/support/cache/
    You should be able to see if you are impacted by entering
    nslookup a.id.opendns.com.
    dig a.id.opendns.com
    If this returns 10.107.64.44 or similar, you certainly have a problem.

    Best would be to also let us know the OpenDNS server you are using each time this problem is reported. I would think these are the locations where a.id.opendns.com points to 10.107.64.44.
    nslookup -type=txt which.opendns.com.
    dig +noall +answer which.opendns.com txt

    A workaround could be to appened the following line (only one) to the hosts file:
    67.215.67.14 a.id.opendns.com # for European OpenDNS servers
    67.215.67.9 a.id.opendns.com # for North American OpenDNS servers
    (Not sure if these are Anycast addresses, but I could find out those two.)

    Btw, for me the guide and block pages (I'm seeing them only rarely) are loading faster now, and I also do not currently have problems with my shortcuts and such. Maybe when they introduce the new technique for me as well, I might get troubles...
    Thankful People: maintenance

1 to 26 of 26

  1.  

This discussion has been inactive for longer than 30 days, and is thus closed.