09-10-2012 01:52 PM
I was having frequent (several times a day) problems with DNS Server not responding. My IPV4 was configured to obtain a DNs server dynamically. I did some searching on the internet, and found a recommendation to hard code DNS servers in my IPV4 configuration. The primary and alternate DNS servers that I used are from OpenDNS. They are 220.127.116.11 and 18.104.22.168, respectively. Since I made that change 3 days ago, I have not had any problems with DNS server not responding.
Others with this problem might want to consider this solution.
Solved! Go to Solution.
09-10-2012 09:47 PM
I'm running Windows7 through a wireless connection. To change the IPV4 configuration to hard code DNS servers I: navagated Network and Sharing Center -> Change Adapter Setting -> Wireless Network Connection -> Properties -> Networking tab -> Internet Protocol Version4 -> Properties -> Use the Following DNS Server Address. Entered the 2 IP addresses.
Does this answer your question?
09-10-2012 11:43 PM - edited 09-10-2012 11:46 PM
O/k. Some routers have difficulties performing *proxy / relay DNS* which many do by default. That said, FWIW, in this age of CDN's, streaming video content, gaming, and other services, it is typically better to use the ISP's provided by default DNS servers. Even if their IP's need to be *hardcoded*.
09-18-2012 05:36 PM
Thank you for giving me the Comcast DNS server addresses. As I said before, I'm currently using OpenDNS as the DNS servers in my IPV4 configuration. Before switching to the Comcast servers, I tried some ping tests. Pinging of 22.214.171.124 for 10 reps with a 8192 message size and a 10-second timeout period, resulted in about 50% of the pings timing out. Pinging the OpenDNS addresses resulted in no time outs.
The bottom line: I'm sticking with the OpenDNS servers 126.96.36.199 and 188.8.131.52. I have had no DNS failures since I hard coded these addresses over 1 week ago.
09-18-2012 05:43 PM - edited 09-18-2012 05:50 PM
That's your choice of course but FWIW, pinging a Comcast DNS server is not a good measure of performance or an accurate troubleshooting tool as these servers are configured to de-prioritize / rate limit ICMP packet based ping probes / requests. This will cause them to show packet loss / slow response times when the are actually performing normally for real traffic / DNS requests.
10-21-2012 11:02 AM
So what is the solution? I had some previous addresses from Comcast that worked fine until I reconfigured my router and it came up with 184.108.40.206 and its brother 220.127.116.11. I am just not getting satisfactory performance and frequent timeouts just doing normal traffic to the Comcast.Net site.
10-30-2012 01:52 PM
Since my original posting on this thread on 9/10/12, I am using OpenDNS servers 18.104.22.168 and 22.214.171.124, and have had no DNS issues. You might want to give it a try.
Steve Schaaf - a Comcast Customer
©2011 Comcast | Investor Relations | Press Room | Corporate Blog | Privacy Statement | Visitor Agreement | Comcast.com Feedback | Site Map