Cloudflare DNS 1.1.1.1
No written verdict yet. Here is what commenters said.
Why people recommend it
“What about Cloudflare’s public DNS?”
“I think changing your default DNS servers to Google 8.8.8.8 or Cloudflare 1.1.1.1 might bypass the spanish sunday ban on Cloudlflare.”
Show 2 more
“I've switched to 1.1.1.1 simply because it annoys me that Comcast is doing this.”
“I use Cloudflare's DNS and it works fine for me.”
Caveats and dissent
“the price of having to measure how many people had ignorantly or lazily put four ones”
“you are using Cloudflare DNS”
Show 2 more
“CF refuses to forward EDNS Client Subnet information and so they return bogus information”
“My ISP’s google global cache is broken every time I use cloudflare.”
Often compared with
Who recommends it in their own words
Threads where it came up
- Cloudflare flags archive.today as "C&C/Botnet"; no longer resolves via 1.1.1.2 5 mentions
- Choosing a Public DNS Resolver 4 mentions
- Cloudflare CEO on the Italy Fines 4 mentions
- Shutting down our public encrypted DNS 2 mentions
- FBI tries to unmask owner of archive.is 2 mentions
- Example.com just launched the biggest redesign in decades 1 mention
Also written as 1.1.1.1, Cloudflare DNS 1.1.1.1, Cloudflare DNS (1.1.1.1). Data: cloudflare-dns-1-1-1-1.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 35
“the price of having to measure how many people had ignorantly or lazily put four ones”
“I use .lan.<domain>.net for my internal servers at work, through cloudflare dns.”
“you are using Cloudflare DNS”
“I use Clouldflare DoT and enabled validation in systemd-resolved”
“What about Cloudflare’s public DNS?”
“CF refuses to forward EDNS Client Subnet information and so they return bogus information”
“Cloudflare explicitly does not use ECS”
“CloudFlare has had some independent auditing done, by an accountancy firm.”
“Cloudflare is very robust but I just don't like them.”
“My ISP’s google global cache is broken every time I use cloudflare.”
“they will rewrite your CAA record”
“Could I use Cloudflare's free nameservers instead of Amazon Lightsail?”
“even though I use 1.1.1.1”
“I think changing your default DNS servers to Google 8.8.8.8 or Cloudflare 1.1.1.1 might bypass the spanish sunday ban on Cloudlflare.”
“I think Cloudflare dns stopped resolving it”
“It won't work if you use 1.1.1.1 for DNS. They're blocking it again.”
“I've switched to 1.1.1.1 simply because it annoys me that Comcast is doing this.”
“I had issues more than once with domain name resolution when I used 1.1.1.1.”
“Many years ago I used Cloudflare, and more than once I had issues with them blocking websites I wanted to access.”
I use cloudflare DNS because it’s faster. But should I worry, having read your comment? What is the downside to using it? What would you recommend instead?
The "censored" part of archive.today seems unrelated to the filtering itself. 1.1.1.3 flags Pornhub.com as "EDE(17): Filtered" but archive.today is "EDE(16): Censored". Supposedly it should be an external party that's requiring Cloudflare not to publish the DNS record. https://www.rfc-editor.org/rfc/rfc8914.html#name-extended-dns-error-code-16-
“we use to enable cloudflare DNS in front of AWS infra”
“incredibly poorly researched feature to just return CNAME records at a domain apex”
Want to mention that not all German ISPs participate in IP-infringing content blocking. I use one that does not.
“Wasn't 1.1.1.1 explicitly created to help people in countries”
“Currently it is as nice registry for pirating sites for anyone using 1.1.1.1”
“Cloudflare argued that filtering its global 1.1.1.1 DNS resolver would be "impossible"”
“I don't think cf would work but still”
“It's just another VC-backed company and 1.1.1.1 is a free service.”
“My domain runs on Cloudflare DNS”
“Try changing your DNS to something other than Cloudflare”
“I will never use Cloudflare.”
“Now I'm on quad1 :(”
“That may be a Cloudflare DNS specific issue”
“I use Cloudflare's DNS and it works fine for me.”