Article 3PDWQ AT&T explains why it blocked Cloudflare DNS: It was just an accident

AT&T explains why it blocked Cloudflare DNS: It was just an accident

by
Jon Brodkin
from Ars Technica - All content on (#3PDWQ)
spraypainted-1.1.1.1-800x506.jpg

Enlarge / Cloudflare's DNS service uses the 1.1.1.1 address. (credit: Cloudflare)

AT&T has been blocking the new Cloudflare DNS service, but AT&T says the blocking was unintentional and that it will fix the problem soon.

The blocking is affecting AT&T home Internet customers who use an AT&T gateway. Cloudflare unveiled its DNS service on April 1, and users in DSLReports forum threads almost immediately started complaining that they couldn't access it. One thread began on April 1, within hours of Cloudflare's announcement.

"I am now unable to reach 1.1.1.1 and 1.0.0.1, which is unfortunate because those are the DNS servers I use," one user wrote.

Read 21 remaining paragraphs | Comments

index?i=M2BV6YwCL0Q:D7OcP9BWtlY:V_sGLiPB index?i=M2BV6YwCL0Q:D7OcP9BWtlY:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments