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: "Hmm, <website> isn't loading right now...."

Bottom of Page

1 to 13 of 13

  1.  
    • CommentAuthorkyleve
    • CommentTimeAug 20th 2008
     permalink
    For the past few weeks, I've been getting this error for about 60% of the websites I visit. Other DNS providers can resolve the domains fine, it seems OpenDNS is the one having issues..

    "Hmm, <website> isn't loading right now.

    The computers that run <website> are having some trouble. Usually this is just a temporary problem, so you might want to try again in a few minutes.

    Want more detail? See which nameservers are failing."

    Any ideas what is causing this? Is it a known issue? It's rather irritating.

    (As a sidenote, it seems to happen to a domain for about 20 minutes, then the domain is fine for a day or so, then it happens again.)
    • CommentAuthormiked
    • CommentTimeAug 20th 2008
     permalink
    What does it say when you click the "Want more detail?" link?
    • CommentAuthorkyleve
    • CommentTimeAug 22nd 2008 edited
     permalink
    That's the odd part..

    Sometimes it says both nameservers are unreachable, but the other 50% of the time it says there is nothing wrong... (IE: no nameserver failures)
    • CommentAuthorrotblitz
    • CommentTimeAug 22nd 2008
     permalink
    I would have the following questions:
    1. What part of the world are you located?
    2. What OpenDNS server location do you use? See http://www.opendns.com/support/article/208
    3. What does 'tracert 208.67.222.222' return? And 'tracert 208.67.220.220'?
    4. Do you or your ISP use a proxy?
    • CommentAuthoreltekgroup
    • CommentTimeAug 27th 2008
     permalink
    Hi, this is the main problem that I still have from several months and that does not permit to my company to regularly use opendns servers.

    dig +noall +answer which.opendns.com txt @208.67.222.222

    returns

    which.opendns.com. 0 IN TXT "1.lon"
    • CommentAuthoreltekgroup
    • CommentTimeAug 27th 2008
     permalink
    For example this morning I have the error:

    -------------------------------------------

    Hmm, www.ducati.com isn't loading right now.

    The computers that run www.ducati.com are having some trouble. Usually this is just a temporary problem, so you might want to try again in a few minutes.

    Sponsored Resource

    Want more detail? See which nameservers are failing.
    Nameserver trace for www.ducati.com:

    * Looking for who is responsible for root zone and followed h.root-servers.net.
    * Looking for who is responsible for com and followed g.gtld-servers.net.
    * Looking for who is responsible for ducati.com and followed ns.infuturo.it.

    Nameservers for www.ducati.com:

    * ns.infuturo.it
    * ns.iunet.it

    The servers listed are working, but something else might have gone wrong.
    • CommentAuthorDavid
    • CommentTimeAug 27th 2008
     permalink
    I have been having this issue also. Its completely random, one day it works, the next day it doesnt. I moved back to my ISP while they fix this problem.
  8.  permalink
    Administrator
    When this issue occurs can you check to see if the domain is having trouble at any of our locations via Cache Check (http://www.opendns.com/support/cache/)? Also, if you open a support ticket with the following outputs it will help us locate the source of the issue:

    1. Send us a traceroute to the domain when using the OpenDNS servers.

    2. Send us the traceroute to both 208.67.222.222 and 208.67.220.220 when using the OpenDNS servers.

    3. Send us traceroute to domain when using your ISP's default DNS servers

    4. Send us the output of the instructions at http://www.opendns.com/support/article/208 AND http://www.opendns.com/support/article/224 when using the OpenDNS servers.
    • CommentAuthorDavid
    • CommentTimeAug 29th 2008
     permalink
    umm... I am having the same problems on multiple websites... Is opendns gettings tooo big for its own good? :-\

    Here are a few sites that will not load with OpenDNS:
    http://www.lotroabc.com/
    http://mittoes.com/
    http://www.massively.com/
    etc, etc, etc...


    Why does this happen all the time now? My ISP's dns works great, opendns is messing up... :-\
    • CommentAuthorDavid
    • CommentTimeAug 29th 2008 edited
     permalink
    erase... kept saying dns website was down, but posted it anyway...
  11.  permalink
    We started seeing this problem today too. Our setup is different. I have Windows Domain Servers with DNS, and the DNS is using OpenDNS for all fowarding lookups. What's interesting is when one of my users gets this error, the user next to them does not. The web pages we are trying to hit are just fine, load quickly and have no apparent problems. They are usually ones that are frequently used too. On a machine with the problem, I can remove our DNS servers and put in a generic one provided by our ISP and they can get the web page just fine. But when I put back in our DNS servers with OpenDNS fowarding they get the error again, while other computers may never see it. What's up? Is OpenDNS having problems. Is there a way to clear any bad information on the computer if that's the issue? I've tried the "ipconfig /flushdns" command, but that had no effect.
    Thankful People: fastoffice
    • CommentAuthorrotblitz
    • CommentTimeSep 19th 2008 edited
     permalink
    I would really like to recommend to follow OpenDNS' instructions above.
    http://forums.opendns.com/comments.php?DiscussionID=1888&page=1#Item_8
  13.  permalink
    We found our problem. It turned out to be a caching feature on our router/edge device. I cleared the cache and all web links started working again for all users.

1 to 13 of 13

  1.  

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