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.

OpenDNS services: Problems w/ Comcast & OpenDNS

Bottom of Page

1 to 28 of 28

  1.  
  1.  permalink
    I am experiencing trouble when using OpenDNS' DNS servers with my Comcast high-speed cable modem. The symptom is that web sites take a long time to resolve or fail to resolve at all. I have isolated the issue to using OpenDNS' DNS servers by attaching my laptop directly to my cable modem and turning off all firewall services. When I allow the cable modem to default to Comcast's DNS servers, the problem does not occur. The problem began to occur Friday 2/29 in the morning (Pacific Time) and has been occuring consistently since then. The problem occurs regardless of what the OS is on the host computer. Comcast tells me that they have not made any changes recently to prevent or slow down 3d party DNS servers. Has anyone else been experiencing this problem?
  2.  permalink
    I have the same problem as well. I sent in a tkt to support to see if anything can be done.
    • CommentAuthortsalzer
    • CommentTimeMar 2nd 2008 edited
     permalink
    Same problem here with Comcast cable, and it is not consistent. Some days DNS resolution of URLs is extremely fast; other days, some URLs (not all) are very slow to resolve or I get the OpenDNS notice of a failed nameserver. Google and Flickr are two popular sites that sometimes do not resolve.
    • CommentAuthorbrijam
    • CommentTimeMar 3rd 2008
     permalink
    Same issue here on Comcast. For the last few days it is taking 1-5 seconds to resolve domains. Google seems the hardest hit, but all domains are sluggish - even OpenDNS.com itself. It is definitely DNS resolution - I tested by adding a direct google IP in my /etc/hosts, which cleared up the speed issues (for google at least).

    I'd love to get some kind of resolution on this rather than move back to Comcast DNS.
    • CommentAuthordaenigma
    • CommentTimeMar 3rd 2008
     permalink
    I am having the exact same trouble... I first thought it may be a problem with custom firmware on my router so I began the tedious job of reloading equipment ect. After resetting re-flashing and rebooting all network equipment it was the same. I am begining to wonder if Comcast has gotten jerky about using opendns and is having Sandvine reset requests.


    Anyway I hope it is resolved soon...
    • CommentAuthorpencoyd
    • CommentTimeMar 3rd 2008
     permalink
    Thanks for the reports. This is strange, and we appreciate any/all details. Don't have any explanation yet... this is the first we've heard of any problems w/r/t Comcast. if you don't mind sharing your location (however generally) that may help, since Comcast is all over the US, and would be curious to know if this is localized or nationwide.
  7.  permalink
    Same situation for me- just filed a support ticket too...I'm in Seattle (Ballard neighborhood) on a residential Comcast cable line. By my estimates, connectivity to opendns (208.67.xxx.xxx) has been buggy since ~Noon today. I'm getting >50% packet loss pinging either of the NS's. Pings to yahoo and google IP's are still fine.

    HTH get things sorted out.
    • CommentAuthoranidiot
    • CommentTimeMar 3rd 2008
     permalink
    I have been experiencing the same issue. I connect to Comcast from Mount Vernon, WA. After I found this post I switched back to Comcast's DNS servers and everything sped up again.
    • CommentAuthorexi1ed0ne
    • CommentTimeMar 3rd 2008
     permalink
    I was also experiencing this yesterday from WildBlue's network and had to revert to their DNS servers. I haven't checked today though.
  10.  permalink
    I am the OP. I am located in the South Sound region of Washington State.
    •  
      CommentAuthordavidu
    • CommentTimeMar 3rd 2008
     permalink
    Administrator
    It sounds like you are all talking to our Seattle location. I'm investigating now.
    • CommentAuthorbrijam
    • CommentTimeMar 3rd 2008
     permalink
    We're in Portland, Or on a residential line. I'd be happy to provide my IP offline and/or share logs, do testing, etc.
    • CommentAuthorpencoyd
    • CommentTimeMar 3rd 2008
     permalink
    David took action: http://system.opendns.com/2008/03/03/60/

    Please let us know if the problems are resolved.
    Thankful People: loudmtn, whiskeygolf
  14.  permalink
    Seems to have cleared it up for me...

    --- 208.67.222.222 ping statistics ---
    74 packets transmitted, 74 packets received, 0% packet loss
    round-trip min/avg/max = 30.5/36.2/80.1 ms

    --- 208.67.220.220 ping statistics ---
    31 packets transmitted, 31 packets received, 0% packet loss
    round-trip min/avg/max = 30.7/36.0/48.7 ms

    Thanks for the quick response!
    Mark
  15.  permalink
    Working like a charm again, thank you for your help.
    • CommentAuthorloudmtn
    • CommentTimeMar 3rd 2008
     permalink
    I'm in Seattle (Queen-Anne) and noticed the DNS issues last night. Pages were taking a long time to load, and my requests to some big sites like google and yahoo were being resolved to 64.15.175.5.

    I was then redirected from there to www.netidentity.com/FileNotFound.aspx?d=www.google.com&mp=404

    I saw this netidentity.com site "Whoops, can't find the page you are looking for (or something like that) for several sites, somewhat intermittantly also. Cleared my dns cache and it would start working again, but the problem returned later.

    This morning, I tried to reproduce it while running the proper tcpdumps. I couldn't reproduce the redirection to the netidentity.com site, but it was running slow. This was several hours ago however, it looks like work has been done since then.

    If anyone at openDNS would like the tcpdumps I took, just let me know. I took dumps last night on tcp port 80, and this morning on ports 80 and 53 (tcp and udp).
    • CommentAuthordaenigma
    • CommentTimeMar 3rd 2008 edited
     permalink
    I am in Portland, Oregon also.

    http://forums.opendns.com/comments.php?DiscussionID=1028&page=1#Item_4

    I changed from opendns to Comcast dns last night and all was fine. I will switch back now and test it out again...

    Ok changed back to opendns and it looks like something was fixed! If an opendns employee could confirm if they did or did not fix something that would be great.

    My bad I did not read the previous post...

    http://system.opendns.com/2008/03/03/60/
    • CommentAuthorloudmtn
    • CommentTimeMar 4th 2008
     permalink
    I just got home, and things appear to be back to normal.
    Thanks guys!

    Can anyone let me in on what the problem was?

    Thanks,
    • CommentAuthorbrijam
    • CommentTimeMar 4th 2008
     permalink
    Thank you, issue solved here!
    • CommentAuthortsalzer
    • CommentTimeMar 4th 2008
     permalink
    Located near Olympia, Washington, and the problem I noted earlier are gone. I, too, had temporarily switched over to Comcast DNS and found no long lag in their DNS. I am impressed with the follow-up by OpenDNS. Where do we buy our orange "I love OpenDNS" t-shirts? ;)
    • CommentAuthormckayc
    • CommentTimeJun 12th 2008
     permalink
    I am also in the Portland area and OpenDNS is not working for me. Perhaps it is because I have a Belkin router?
    • CommentAuthormamazitta
    • CommentTimeJun 12th 2008 edited
     permalink
    @mckayc
    OpenDNS should work with Belkin router. Here are instructions:
    https://www.opendns.com/start?device=belkin

    Also, if you want all computers on your network to use OpenDNS, then router is best place for it. Each individual computer should have "obtain DNS servers automatically" set. If you enter any other DNS servers here, they will override the router DNS settings. XP example setup:
    https://www.opendns.com/start?device=windows-xp

    You should have gone through these processes when you first opened your account.
    If you don't get the OpenDNS Welcome page, I suggest you check settings again.
    http://www.opendns.com/welcome/

    edit: typo
  23.  permalink
    Administrator
    mckayc - If you continue to have trouble open a support ticket.
    • CommentAuthorsynaptyx
    • CommentTimeSep 13th 2008
     permalink
    Want t-shirt! :)
    • CommentAuthorrotblitz
    • CommentTimeSep 13th 2008
     permalink
    • CommentAuthordonevco1
    • CommentTimeSep 13th 2008
     permalink
    I'm using the Earthlink-provided Netopia dsl router. Do I need setup instructions?
    • CommentAuthordonevco1
    • CommentTimeSep 13th 2008
     permalink
    Oops - Netopia is the modem -- Linksys router. I'll look up instructions for that router. Sorry.
    • CommentAuthorrotblitz
    • CommentTimeSep 13th 2008
     permalink
    If you can see from the user interface or the manual, how to change the settings for the DNS servers (primary and secondary), then you probably do not need special instructions, and you can go straight forward.
    General instructions for routers can be found here: https://www.opendns.com/homenetwork/start/device/router

1 to 28 of 28

  1.  

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