I know they consider "1.1.1.1" to also be a product name, but it's very confusing when the text says 1.1.1.1 50 times, and then there's 2 mentions of "Oh, the service is at 1.1.1.2".
1.1.1.1 for Families
21–30 of 171 posts
Re: 1.1.1.1 for Families
#22How about 1.1.1.3, pi-hole?
Re: 1.1.1.1 for Families
#23For the most up to date information about 1.1.1.1 for Families, here's their product page:
https://1.1.1.1/family/
Re: 1.1.1.1 for Families
#24DNS filters are a joke, too easy to bypass.
Re: 1.1.1.1 for Families
#25I know they consider "1.1.1.1" to also be a product name, but it's very confusing when the text says 1.1.1.1 50 times, and then there's 2 mentions of "Oh, the service is at 1.1.1.2".
The name they could have used:
1.1.1.2 (1.1.1.1 for families)
Or more correct:
1.1.1.3 (1.1.1.1 for families)
Re: 1.1.1.1 for Families
#26I 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
It's a little ironic complaining about a single webpage on the internet, when you're suggesting that we use a single resolver on the internet instead of a distributed resolver system that we have otherwise.
FWIIW, I use the resolver of my ISP, and 100% happy with the results. If your ISP provides incorrect and fake data to make extra money on advertising, maybe you should vote with your wallet and change the ISP.
Re: 1.1.1.1 for Families
#27I 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 used to use 1.1.1.1 till the day I realized that it doesn't resolve archive.is.
It does resolve archive.is, it’s just the archive.is nameservers return garbage if the source if CloudFlare. CloudFlare could simply fix this their end if they wanted but haven’t done so out of integrity. This looks good for CloudFlare and bad for archive.is from where I’m sitting.
Re: 1.1.1.1 for Families
#28I 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. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/
Thank you! This is incredibly informative on the situation and makes sense. It also makes me happy with clouflare's choice
Re: 1.1.1.1 for Families
#29I 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 s…
Did you talk to someone at Cloudflare about this? That sounds... odd.
Re: 1.1.1.1 for Families
#30I 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…
CloudFlare is in the right. This is for privacy.
Just put the IPs on your hosts file, it's easy. https://dns.google/query?name=archive.is
54.37.18.234 archive.today
54.37.18.234 archive.is
http://someonewhocares.org/hosts/
https://github.com/jmdugan/blocklists/tree/master/corporatio...
etc