Your IP:

Our Forums Have Moved!

Visit our new forums at https://community.opendns.com/forums/ to post on topics and read the latest content. These forums are now read-only archives.

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.
    • CommentAuthormacunix5
    • CommentTimeApr 7th 2012
     permalink
    Hello,
    OpenDNS was working fine for me for a long time. In the past view months the following behavior has developed. I click on a link, Safari searches for a few minutes, and then I get the OpenDNS error page saying the site couldn't be found. Then I click on the link again, and I get the page immediately, no problem.

    This happens seemingly at random, and not all the time, but enough to be annoying. I'm on verizon DSL with an old Westell modem.

    TIA for any suggestions
    Tom
    • CommentAuthorrotblitz
    • CommentTimeApr 7th 2012 edited
     permalink
    Can you provide an exact example of such a site, and how exactly you're trying to reach it, e.g. entering something in the browser's address line or what.

    Also, tell use where you are located, and copy & paste the plain text output of the following commands here:
    nslookup -type=txt which.opendns.com.
    tracert 208.67.222.222
    • CommentAuthormacunix5
    • CommentTimeApr 7th 2012 edited
     permalink
    Thanks for the reply. I'm in downtown Boston....Tom

    For example just now

    "You tried to visit www.huffingtonpost.com, which is not loading." But if I try again, it will load immediately.

    But again, it can be any site on any day, apparently random.

    nslookup -type=txt which.opendns.com
    Server: 208.67.222.222
    Address: 208.67.222.222#53

    Non-authoritative answer:
    which.opendns.com text = "3.nyc"

    Authoritative answers can be found from:



    traceroute 208.67.222.222
    traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
    1 192.168.1.1 (192.168.1.1) 24.209 ms 7.824 ms 8.253 ms
    2 * * *
    3 * * *
    4 * * *
    5 * * *
    6 * * *
    7 * * *
    8 * * *
    9 * * *
    ^C
    • CommentAuthorrotblitz
    • CommentTimeApr 7th 2012
     permalink
    It seems to me your router is defective. Try another one. Or it is an ISP problem.

    But let's try something different:
    ping -n 10 -f -l 1462 192.168.1.1
    ping -n 10 -f -l 1462 www.google.com
    • CommentAuthormacunix5
    • CommentTimeApr 17th 2012
     permalink
    Hi again, sorry for the slow response....Tom

    Let me say again: I get this "website not loading" message and when I try again it loads immediately. Doesn't that indicate something?

    my Ping doesn't like all your options, but


    ping 192.168.1.1
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=4.899 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=4.478 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=4.558 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=4.446 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=4.291 ms
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=4.492 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=4.439 ms

    ping www.google.com
    PING www.l.google.com (173.194.73.99): 56 data bytes
    Request timeout for icmp_seq 0
    Request timeout for icmp_seq 1
    Request timeout for icmp_seq 2
    Request timeout for icmp_seq 3
    Request timeout for icmp_seq 4
    Request timeout for icmp_seq 5
    Request timeout for icmp_seq 6
    Request timeout for icmp_seq 7
    • CommentAuthorrotblitz
    • CommentTimeApr 17th 2012
     permalink
    "traceroute to 208.67.222.222 (208.67.222.222), 64 hops max, 52 byte packets
    1 192.168.1.1 (192.168.1.1) 24.209 ms 7.824 ms 8.253 ms
    ...
    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=4.899 ms"

    The latency between your computer and your router is far too high, 5-24 milliseconds.
    A normal value would be 0-2 milliseconds. This indicates something bad!
    It indicates a problem with your LAN connection. Try with another router maybe, if you have one lying around or can one borrow from someone else.

    Btw, what OS is on your computer?
  1.  permalink
    Or try a different Ethernet cable or adjust your position in relation to the AP if wireless.
    • CommentAuthorblfarris
    • CommentTimeMay 5th 2012
     permalink
    I am frequently having these issues as well.

    Pages load partially and then fail, or they fail to load at all, but then when reloaded they will come up. This is happening from all the laptops in the house (all Macs on wi-fi).

    Netflix is failing regularly from my WII as well.

    I'm in Chicago.

    nslookup -type=txt -timeout=12 which.opendns.com. 208.67.222.222
    Server: 208.67.222.222
    Address: 208.67.222.222#53

    Non-authoritative answer:
    which.opendns.com text = "5.ash"

    64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=3.844 ms
    64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.287 ms
    64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.785 ms
    64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=6.621 ms

    PING www.l.google.com (74.125.225.112): 56 data bytes
    64 bytes from 74.125.225.112: icmp_seq=0 ttl=55 time=11.490 ms
    64 bytes from 74.125.225.112: icmp_seq=1 ttl=55 time=11.057 ms
    64 bytes from 74.125.225.112: icmp_seq=2 ttl=55 time=13.437 ms
    64 bytes from 74.125.225.112: icmp_seq=3 ttl=55 time=13.167 ms
    • CommentAuthorrotblitz
    • CommentTimeMay 5th 2012
     permalink
    http://system.opendns.com/

    OpenDNS location Chicago is currently offline, and you're rerouted to WDC ("5.ash").
    http://system.opendns.com/2012/05/05/460/
    This may be the reason for your problems.

    Your ping to the router is suboptimal, but your ping to Google is good.
    • CommentAuthorblfarris
    • CommentTimeMay 5th 2012
     permalink
    This problem is occurring regularly -- it's bad this morning, but had trouble last night, and several times earlier this week. It seems to be worse since we switch to Comcast about 3 months ago, but it's an ongoing recurring issue.
    • CommentAuthorrotblitz
    • CommentTimeMay 5th 2012
     permalink
    Yes, then it's most likely an ISP problem, unrelated to DNS.
    If you think it is related to OpenDNS, switch to your ISP's DNS to see if it is any better.
    • CommentAuthorblfarris
    • CommentTimeMay 5th 2012
     permalink
    Just switched to 8.8.8.8 for DNS and netflix now works fine (hasn't worked at all for several days). It's definately an OpenDNS issue.
    • CommentAuthorrotblitz
    • CommentTimeMay 5th 2012
     permalink
    Ok, then open a support ticket: https://dashboard.opendns.com/support/
    We users definitely can't help you.

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