I used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is [1]. I don't particularly care what the details are, whose fault it is, etc., but as an end user, I see this a major problem because with 1.1.1.1 if my browser is unable to resolve a domain, I wouldn't know if it's my DNS's fault or if it's the site's without an explicit check. I also don't care much for family "protection", so right now I don't see a good reason for using Cloudflare over Quad9.
1.1.1.1 for Families
11–20 of 171 posts
Re: 1.1.1.1 for Families
#12This was published on `01-April-2020`. So was it a joke or was it not?
Not a joke.
Re: 1.1.1.1 for Families
#13*for "dysfunctional" families.
It's not even blocking TikTok! :D
Re: 1.1.1.1 for Families
#14This was published on `01-April-2020`. So was it a joke or was it not?
It's adressed in the article
> However, we've made it a tradition every April 1 to launch a new consumer product that leverages our network to bring more speed, reliability, and security to every Internet user.
Re: 1.1.1.1 for Families
#15One should use DNS servers offered by one's VPN provider. Otherwise, it leaks to both VPN provider and DNS provider.
Re: 1.1.1.1 for Families
#16I used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is [1]. I don't particularly care what the details are, whose fault it is, etc., but as an end user, I see this a major problem because with 1.1.1.1 if my browser is unable to resolve a domain, I wouldn't know if it's my DNS's fault or if it's the site's without an explicit check. I also don't care much for family "protection", so right now…
> I don't particularly care what the details are, whose fault it is, etc.
Re: 1.1.1.1 for Families
#17I had to stop using 1.1.1.1 because I am getting rate limited when using their “cloudflared” dns-over-https proxy. My pretty modest home network and the various services running make 20-25k queries per day and I get a lot of REFUSED responses. Google on the other hand has no problem serving all of them. I even set a local cache to bypass the dns TTL but the problem is that sometimes 10 or more queries arrive at the same moment from a service.
Re: 1.1.1.1 for Families
#18One should use DNS servers offered by one's VPN provider. Otherwise, it leaks to both VPN provider and DNS provider.
This is irrelevant, no one using a VPN is also configuring a 'family-friendly' DNS resolver.
Re: 1.1.1.1 for Families
#19One should use DNS servers offered by one's VPN provider. Otherwise, it leaks to both VPN provider and DNS provider.
Don’t most vpn providers encapsulate both udp and tcp?
Re: 1.1.1.1 for Families
#20I used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is [1]. I don't particularly care what the details are, whose fault it is, etc., but as an end user, I see this a major problem because with 1.1.1.1 if my browser is unable to resolve a domain, I wouldn't know if it's my DNS's fault or if it's the site's without an explicit check. I also don't care much for family "protection", so right now…
So if archive.is decided to also return garbage DNS results to Quad9 you would stop using them too?
I get your sentiment, but allowing one single webpage on the internet to dictate who you are allowed to use for DNS is going too far in the other direction, IMHO