1.1.1.1 for Families • Hacker News Board

Re: 1.1.1.1 for Families

#81

Post by kgwxd » Thu, Oct 28, 2021, 2:00 PM UTC

codetrotter wrote: post #16

b215826 wrote: post #11

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 particularly care what the details are, whose fault it is, etc. https://jarv.is/notes/cloudflare-dns-archive-is-blocked/

Is archive.is the only major site using that line of reasoning?

Re: 1.1.1.1 for Families

#82

Post by zrobotics » Thu, Oct 28, 2021, 2:01 PM UTC

nobody9999 wrote: post #78

gsa wrote: post #64

Earlier quoted context omitted.

Cloudflare DNS also broke Spotify for me in a way that took me a while to discover. The Spotify desktop app would randomly stop playing music with no error message. I traced the issue back to changing my Pi-Hole upstream DNS to Cloudflare few days earlier. Switching to another DNS provider fixed the issue right away. [0] https://community.spotify.com/t5/Desktop-Windows/Random-Stop...

>I traced the issue back to changing my Pi-Hole upstream DNS to Cloudflare few days earlier. Switching to another DNS provider fixed the issue right away. Since you're already using a pi-hole, why not just roll your own recursive DNS server. The additional network traffic to do so is insignificant. That way, you don't have to rely on someone else to resolve your DNS queries -- or deal with spats like that. I've been…

Eh, not the GP but I had tried that and switched back to 1.1.1.1 with hosts rules for specific sites to fallback to 8.8.8.8.

Running my own DNS just proved to be too much of a troubleshooting headache, since if a site was broken it was one additional step. The pihole itself has been almost no trouble, but the diy DNS would occasionally fail to resolve a site. If I'm at home, the last thing I really want to do in the evening is troubleshoot network issues.

It was a fun project to setup, and I did learn more than I expected I would. I can recommend it as a weekend project, but not as a long-term solution.

Re: 1.1.1.1 for Families

#83

Post by kayodelycaon » Thu, Oct 28, 2021, 2:02 PM UTC

cnst wrote: post #62

smt88 wrote: post #50

Earlier quoted context omitted.

Millions of people in the US can't change their ISP. I live in a major city and would have to drop my speed by 90% if I switched to my other option. I have two options total.

Doesn't T-Mobile US offer home internet over 4G and 5G in most of the US now? I've actually been using tethering for home internet, and it's often faster and cheaper than landline alternatives. Easily get 100Mbps in my location over 4G LTE on an old phone.

For the curious: https://www.t-mobile.com/coverage/coverage-map

Re: 1.1.1.1 for Families

#84

Post by nkrisc » Thu, Oct 28, 2021, 2:11 PM UTC

Any tips/ideas for configurations for selective content blocking by device? I'd like to block content on the kids' devices, but not for the adults in the household. I'm not concerned about circumvention at this point. I'm currently using a pi-hole for ad blocking, so I'd like to configure something at that level, unless there's a better way.

Re: 1.1.1.1 for Families

#85

Post by mlac » Thu, Oct 28, 2021, 2:12 PM UTC

FunnyLookinHat wrote: post #67

drexlspivey wrote: post #17

I 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…

That's not too many requests, but running any form of a home network would still benefit moderately from a local DNS server. You could even install something like dnsmasq on the most heavy-using boxes to cache lookups locally. Granted, I'm saying this as yet another home-network admin who hasn't quite... ahem... gotten around to installing a DNS server. ^_^; I'm mostly sharing this here in case someone else has a sim…

Pi-hole with Tailscale checking in here. Easy to set up.

Re: 1.1.1.1 for Families

#86

Post by p4bl0 » Thu, Oct 28, 2021, 2:13 PM UTC

Are there some DNS services that block ads and trackers (or at least as much ads and trackers as possible) at the DNS level?

Re: 1.1.1.1 for Families

#87

Post by jamroom » Thu, Oct 28, 2021, 2:15 PM UTC

p4bl0 wrote: post #86

Are there some DNS services that block ads and trackers (or at least as much ads and trackers as possible) at the DNS level?

https://nextdns.io

Re: 1.1.1.1 for Families

#88

Post by dcow » Thu, Oct 28, 2021, 2:15 PM UTC

This is from April last year and needs a 2020 tag.

Re: 1.1.1.1 for Families

#89

Post by notRobot » Thu, Oct 28, 2021, 2:15 PM UTC

p4bl0 wrote: post #86

Are there some DNS services that block ads and trackers (or at least as much ads and trackers as possible) at the DNS level?

Yep! https://nextdns.io

And they have a super generous free tier!

Re: 1.1.1.1 for Families

#90

Post by nobody9999 » Thu, Oct 28, 2021, 2:17 PM UTC

zrobotics wrote: post #82

nobody9999 wrote: post #78

Earlier quoted context omitted.

>I traced the issue back to changing my Pi-Hole upstream DNS to Cloudflare few days earlier. Switching to another DNS provider fixed the issue right away. Since you're already using a pi-hole, why not just roll your own recursive DNS server. The additional network traffic to do so is insignificant. That way, you don't have to rely on someone else to resolve your DNS queries -- or deal with spats like that. I've been…

Eh, not the GP but I had tried that and switched back to 1.1.1.1 with hosts rules for specific sites to fallback to 8.8.8.8. Running my own DNS just proved to be too much of a troubleshooting headache, since if a site was broken it was one additional step. The pihole itself has been almost no trouble, but the diy DNS would occasionally fail to resolve a site. If I'm at home, the last thing I really want to do in the…

>Running my own DNS just proved to be too much of a troubleshooting headache, since if a site was broken it was one additional step. The pihole itself has been almost no trouble, but the diy DNS would occasionally fail to resolve a site. If I'm at home, the last thing I really want to do in the evening is troubleshoot network issues.

A fair point.

That said, note the edit on the comment to which you replied.

I've been running my own authoritative DNS for (personal) domains I own for 15 years or so and have spent very little time managing that. I also run my own internal DNS servers (hybrid BIND/AD DNS) without issue.

As such, I don't expect to have many issues with a simple recursive resolver.

That said, I understand your point of view and know that managing DNS isn't for everyone.

However, I'd rather perform my own DNS lookups rather than relying on my ISP(s), Google or Cloudflare. Yes, my ISP could capture every single recursive query, but I'd rather have them do that than just log every DNS query I make.

No, it doesn't significantly add to my privacy, but (IMHO) it's better than the alternative.