I haven’t change my DNS back to Charter’s servers but a post in this thread seems to indicate that the problem has been resolved. http://www.dslreports.com/forum/r20199048-Charter-Google-Chicago~start=20
OpenDNS seems to be working well for me and I must might leave it set up for a few days to see if I continue to like it.
Agile Ajax: Ajax Testing: Doubling Down with Selenium and JMeter
This could be a solution for our automated testing issues. Use Selenium IDE to record and test and then play back the test while JMeter is watching your HTTP traffic.
Over the last week I’ve had trouble hitting Google with the address www.google.com. The following is what I see:
I decided to use OpenDNS as indicated below. It seemed to work at first but then an hour later I’m having the problem again – the following solution actually may not work. Upon reviewing the thread below, it seems the issue is routing of some sort and pointing at OpenDNS may not fix the problem. At this point the only fix seems to be to use the one of Google’s numeric IP address such as 64.233.167.99.
It appears to be a problem with Charter’s DNS as seen in this thread:
Google and Charter DNS Thread – Broadband Reports
Hitting the IP address 64.233.167.99 seems to work fine. Some solutions:
Use a host table entry for www.google.com to the IP 64.233.167.99 or point your DNS to Open DNS:
208.67.222.222
208.67.220.220It is definitely annoying and others have reported that Charter support does not accept responsibility for this issue.