• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Comcast DNS issues

Markbnj

Elite Member <br>Moderator Emeritus
Moderator
Actually not DNS issues per se, but they are having problems with routing, and apparently you can't get ports 53, 443, and some others out to certain large chunks of the net. 53 is DNS, so if you're using an external DNS provider (as I was) then it may not work. If you're using Comcast's DNS, and they have to forward the request outside their network, it may not work.
 
Connectivity to openDNS on port 53 appears to be working again. 4.2.2.2 and .1 servers are also accessible.
 
A year or so ago Comcast DNS got flaky for several days and I originally set the DNS to 4.2.2.x, and then a few months back I read someone's recommendation to give OpenDNS a try. Don't really have a particular reason for using their servers. Comcast and other ISPs have been messing around with capturing failed DNS queries and returning search pages, so I wanted to avoid that as well.

In other words, no particular reason 🙂. Is there a better choice?
 
Originally posted by: Markbnj
A year or so ago Comcast DNS got flaky for several days and I originally set the DNS to 4.2.2.x, and then a few months back I read someone's recommendation to give OpenDNS a try. Don't really have a particular reason for using their servers. Comcast and other ISPs have been messing around with capturing failed DNS queries and returning search pages, so I wanted to avoid that as well.

In other words, no particular reason 🙂. Is there a better choice?

I was doing the same for the same reasons. I kept getting spam bot hits after their search pages as well which went away when I started using open DNS.
 
Check the pings to variety of places to make sure that OpenDNS does not slow you down.

OpenDNS is Not just straight DNS, it depends on your surfing Style and Habits. Some times using it adds time to the DNS process.
 
You know, reading up on it they actually do more than I thought they did. I really just want fast access to a straight-up external DNS server that won't mess with results. I use squidGuard with a nightly blacklist update to protect my network, so I don't really need the extra filtering Open DNS is doing.

I guess I will point everything at 4.2.2.1 and 4.2.2.2 for now. Is that the best choice?

Thanks for the tip, Jack. I hadn't really paid close attention to what they were doing before.
 
Back
Top