June 27th, 2024

Issues with 1.1.1.1 public resolver in multiple locations

Cloudflare faces problems with 1.1.1.1 public resolver in various locations. Fix in progress. Investigation ongoing. Users can subscribe for updates. Cloudflare working on resolving the issue.

Read original articleLink Icon
Issues with 1.1.1.1 public resolver in multiple locations

Cloudflare is currently experiencing issues with its 1.1.1.1 public resolver in multiple locations. The problem has been identified, and a fix is being implemented. Cloudflare is actively investigating the issue, which may affect multiple users in various locations relying on the 1.1.1.1 public resolver service. More details will be provided as the investigation progresses. Users can subscribe to email and text message notifications for updates on the incident. Cloudflare assures users that they are working on resolving the issue and will provide further information as it becomes available.

Link Icon 6 comments
By @xnx - 5 months
Use 8.8.8.8 to switch to Google DNS.

Also just learned that Google has this web service https://dns.google/

By @blacksmith_tb - 5 months
For CF DNS I find 1.0.0.1 generally to work better, too many systems in past used 1.1.1.1 as a magic value.
By @Zekio - 5 months
that explains why I had to switch to google dns to access hacker news
By @stonegray - 5 months
It’s not DNS.

There’s no way it’s DNS.

It was DNS.

By @nevxlig - 5 months
Always a good idea to include test values to your IRR registry `whois -h rr.Level3.net 1.1.1.0/24`