Does Cloudflare's 1.1.1.1 DNS Block Archive.is?
tl;dr: No. Quite the opposite, actually — Archive.is’s owner is intentionally blocking 1.1.1.1 users.
CloudFlare's CEO had this to say on HackerNews:
We don’t block archive.is or any other domain via 1.1.1.1. [...] Archive.is’s authoritative DNS servers return bad results to 1.1.1.1 when we query them. I’ve proposed we just fix it on our end but our team, quite rightly, said that too would violate the integrity of DNS and the privacy and security promises we made to our users when we launched the service. [...] The archive.is owner has explained that he returns bad results to us because we don’t pass along the EDNS subnet information. This information leaks information about a requester’s IP and, in turn, sacrifices the privacy of users.
I am mainly making this post so that admins/moderators at BeeHaw will consider using archive.org or ghostarchive.org links instead of archive.today links.
Because anyone using CloudFlare's DNS for privacy is being denied access to archive.today links.
what else is on your list?
Quad9 is pretty good, too.
https://www.quad9.net/
https://www.quad9.net/about/transparency-report
9.9.9.9
Do they have servers in the US?
https://www.quad9.net/service/locations/
Looks like they do.
Sweet. Just changed my servers now.
I do CloudFlare first and Google as backup.
So privacy first first and privacy last second, interesting combo
yeah 1.1.1.1 then 8.8.8.8
LOL that's not a bad way of explaining it. My reasoning is that I like CloudFlare, so I'll default to them, but if CF goes down I want DNS to continue working. I figure Google is one of the servers that's LEAST likely to go down.
https://european-alternatives.eu/category/public-dns
I used to use Cloudflare and recently switched to NextDNS for more control.