You're probably already aware of these tools but just in case Wireshark is my sniffer of choice, Microsoft's msconfig utility can help you temporarily disable drivers, services and start-up programs. A packet analyzer should be able to tell you the real IP address of the server responding to your DNS queries. The symptoms you are describing sound a lot like the typical behavior of spyware programs. You sound very well versed in networking technologies but it's happened to the best of us. Since and have confirmed that they're not having this issue in their region and Comcast denies using a transparent DNS proxy, or the leak test tool does not point to obvious issues, you may want to consider that you've got some form of malware on your computer. They're usually pretty willing to disclose that information. Thanks for making it to the Thanks for the DNS leak test link, I'm having fun playing with Out of curiosity have you tried contacting Comcast and asking them if they are indeed using a transparent proxy? I'd bet $ that first level support would have no clue about what a transparent DNS proxy is so insist on talking to 2nd level support. Has anyone else experienced this? Is anyone else in the Minneapolis, MN area able to check for this on his or her own Comcast connections for this?Īny ideas why they are doing this? DNSChanger mitigation? DNSSEC improvements? SPYING? The same behavior is not occurring there thankfully. The WAN provider there is Comcast as well, but it’s a business class account. Just to confirm, I ran the same tests on my desktop at work.
So it APPEARS that Comcast has a transparent DNS proxy running on my WAN. I connected my laptop directly to the gateway modem just to be sure. Off I went to the router config to see if it was something I had done. I tried a number of direct IP requests to random non-existent DNS servers with nslookup and dig. Please adjust your router configuration or file a support request with your ISP.'
This means you cannot benchmark or utilize alternate DNS servers. 'Your router or Internet Service Provider appears to be intercepting and redirecting all outgoing DNS requests. When I ran Namebench I was immediately greeted with this ominous dialog box. I figured that way I could test several servers and determine the best source. So I turned to a tool that I have used in the past to determine the fastest DNS response for the various networks I administer at work. I figured it would have shown SOME measurable difference, better or worse. I thought, “Gee, Google DNS isn’t what it used to be.” So I decided to switch over to OpenDNS to see if that affected the response times. After further investigation, I determined that slow DNS queries were, at least, part of the problem.
Over the past month or so I noticed that I was starting to get some serious lag during network requests. I also set the DNS server to forward non-authoritative queries to Google DNS, and set my DHCP server to hand out the local DNS to clients on the network. About a year ago, I set up a local DNS server to facilitate file sharing/VNC etc. While troubleshooting slow DNS response on my home network I came across this problem. Which responded to invalid DNS queries with a server hosting a branded search page. A practice they cleverly marketed as "Domain Helper". Spiceheads are more than likely familiar with the DNS redirecting that used to be standard practice on the Comcast network. Sorry about the lengthly post, but I felt like I needed extra verbiage to help suppress my blind rage.Ĭomcast has recently started playing with my DNS traffic, and not in the usual clumsy Comcastic manner.
0 kommentar(er)
