I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry wolf prematurely. The technical details here strongly suggest a bug rather than intentional blocking of 1.1.1.1 DNS traffic.
AT&T updates firmware to block access to 1.1.1.1
71–80 of 382 posts
Re: AT&T updates firmware to block access to 1.1.1.1
#72Re: AT&T updates firmware to block access to 1.1.1.1
#73My guess is this is just incompetence and not intentionally made to block CloudFlare. I have one of those routers, and I couldn't use 1.1.1.1 because it was routing to an internal interface on the router. I confirmed this with ping, I was getting microsecond response times from 1.1.1.1. Under the new firmware, 1.1.1.1 is just dead. So it's probably still connected to the local interface, and nothing is listening.
Re: AT&T updates firmware to block access to 1.1.1.1
#74Earlier quoted context omitted.
Are they blocking 8.8.8.8? Why do you think they're blocking 1.1.1.1?
Because users were able to connect and after the firmware update they are not? And also because they didn't even let you change this setting to begin with. There is not enough data to attribute this to malice yet, but it does not look good (see CloudFlare's tweet).
Re: AT&T updates firmware to block access to 1.1.1.1
#75FWIW, it’s possible to bypass AT&T’s router:
https://github.com/jaysoffian/eap_proxy
That said, I tried 1.1.1.1 and found I had to switch back to Google DNS since Cloudflare intentionally doesn’t support EDNS Client Subnet which was causing my AppleTV’s to have trouble loading content.
Re: AT&T updates firmware to block access to 1.1.1.1
#76As a consumer, you are free to switch to a different provider. I'm not saying what they're doing is ok, but let's not neglect the opportunity to vote with our $$$.
Re: AT&T updates firmware to block access to 1.1.1.1
#77Re: AT&T updates firmware to block access to 1.1.1.1
#78Re: AT&T updates firmware to block access to 1.1.1.1
#79My guess is this is just incompetence and not intentionally made to block CloudFlare. I have one of those routers, and I couldn't use 1.1.1.1 because it was routing to an internal interface on the router. I confirmed this with ping, I was getting microsecond response times from 1.1.1.1. Under the new firmware, 1.1.1.1 is just dead. So it's probably still connected to the local interface, and nothing is listening.
They started blocking 1.0.0.1 and CF ipv6 DNS too. This has to be intentional.
Re: AT&T updates firmware to block access to 1.1.1.1
#80As a consumer, you are free to switch to a different provider. I'm not saying what they're doing is ok, but let's not neglect the opportunity to vote with our $$$.