4 ms·
You can avoid the bogus DNS server by manually choosing Google's alternate server 8.8.4.4 (They intercept the primary one 8.8.8.8 as well as 4.2.2.2.)
by eli 12y ago
You can avoid the bogus DNS server by manually choosing Google's alternate server 8.8.4.4 (They intercept the primary one 8.8.8.8 as well as 4.2.2.2.)
- jevinskie 12y agoThey do MITM of custom DNS servers? Despicable! I wish DNSCrypt support was more widespread.
- eli 12y agoYup, that's what it looks like. I just encountered it last week: https://gist.github.com/cjp/f4dda3cc0f26ad10a3fe https://gist.github.com/cjp/f4dda3cc0f26ad10a3fe Been meaning to try to dump some traffic so I can see more of what's going on.
- jevinskie 12y agoThat is pretty incredible. I knew about ISP's DNS servers that hijacked NXDOMAIN but I've never before heard of MITMing of third party DNS servers! Wow! Have you contacted T-Mobile about it?
- dylz 12y agocomcast does/did the same.
- eli 12y agoI haven't, but that's a good idea. I'm guessing there are semi-legitimate reasons beyond just forcing people to the stupid NXDOMAIN search page. But I agree that it's pretty unpleasant.
- eli 12y agoJust FYI, I wrote this up (http://esd.io/blog/t-mobile-dns-hijack.html http://esd.io/blog/t-mobile-dns-hijack.html) and I'm told off the record that T-Mobile intends to fix it.
- jevinskie 12y agoAwesome, thank you for going the extra mile and reaching out to T-Mobile! I hope they really do fix it. =)
- spacefight 12y agoThis is really really bad.