Yes, send more data to big companies like cloud front and google. They need it.
This has nothing to do with either of them?
Setting Up 1.1.1.1 for Families on a Pi-Hole
51–60 of 82 posts
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#52Anybody know from where does CF get the domains to block on 1.1.1.2 (malware) and 1.1.1.3 (porn)?
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#531.1.1.3 for blocking also adult content, could be even faster than commonly used 1.1.1.1
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#54I wonder how much ICMP is going to those IPs. I ping 1.0.0.1 ("ping 1.1") as a quick check to ensure my internet is working a lot, far quicker and less stretching than typing ping 8.8.8.8. When I'm tracing a fault I'll ping 1.1.1.x as I can then tcpdump on a spanport against that IP and be fairly confident any traffic is from my test point and not from another device.
I'm sure I'm not the only one.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#55I did test 1.1.1.1 and found it to be pretty slow on long tail domains (obviously everyone is caching popular ones). I bascially ran a 'dig' with multiple DNS providers and CloudFlare was slowest among the bunch for long-tail domains. Here are the details: https://twitter.com/vladquant/status/1428761979808669704 CloudFlare never responded to this tweet.
That particular domain is sluggish from the UK, but other domains, but my route53 hosted domains - including ones never before used (wildcard subdomain) - are all fine - around 5ms.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#56Why do parents feel the need to control what their children do online? I had unrestricted internet access as a child and turned out fine. Although I must say, a DNS based approach is more benign than some of the horrendously invasive alternatives.
I'm nearly 40, the internet that I grew up with, is vastly different to the internet my kids are growing up with. Heck, the internet the 15 year old grew up with is vastly different to his 4 year old sister's experience.
I see nothing wrong with blocking access to certain sites by default - protects us as well - if anyone of them have a problem with it, they can come and ask why it is blocked. Simples.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#57Earlier quoted context omitted.
Why aren't they just called infrequently used domains then?
>Why aren't they just called infrequently used domains then? You could call them "infrequent" but "long-tail" is also a common description to convey a Power Law distribution: https://en.wikipedia.org/wiki/Long_tail I think in this case about DNS caching, "long tail" is better than "infrequent". In the wikipedia graph, some of the domain lookups in yellow may be "frequent" (absolute sense) but simultaneously but much…
DNS is essentially a cache. I've never once in my life heard of infrequently accessed cache items as "long-tail". This is definitely a dumb phrase that should be avoided.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#58I did test 1.1.1.1 and found it to be pretty slow on long tail domains (obviously everyone is caching popular ones). I bascially ran a 'dig' with multiple DNS providers and CloudFlare was slowest among the bunch for long-tail domains. Here are the details: https://twitter.com/vladquant/status/1428761979808669704 CloudFlare never responded to this tweet.
When I tried, Quad9 (9.9.9.9) resolved enigma.rs in 5.2 s.
I'm happy with Cloudflare, even if it's slightly slower.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#59Why do parents feel the need to control what their children do online? I had unrestricted internet access as a child and turned out fine. Although I must say, a DNS based approach is more benign than some of the horrendously invasive alternatives.
We use the Google Families setup to provide some safety features (location), and have device schedules to limit constant use. Families also shows which apps are used, and for how long. We don't track websites, or filter them other than for ads. I also use the similar setup on the google wifi (now nest) mesh devices, to have schedules so that time limits are enabled for all children's/media devices. They often ask for overrides, or extra time, and that's fine - interactivity over health boundaries. We don't collect any data on content, contacts, etc. Just apps and how long per day/week/month, so we can share that with them.
We have to teach our children to be good people, and how to process the world, and what we've already managed to process out of what we've seen throughout our own lives. If your strategy depends on censorship to provide a healthy path, I don't think it's going to be that healthy of an outcome.
Re: Setting Up 1.1.1.1 for Families on a Pi-Hole
#60The one thing Cloudflare DNS is missing is providing something like NextDNS. Choose your own filter lists (that are constantly updated), create multiple profiles to use according to the target device/location and enjoy as blocking at the DNS level. It’s not a complete match for something like uBlock Origin, but a lot of stuff still gets blocked with DNS filters.
Have you checked out Cloudflare Gateway? We used that to do DNS filtering on some iPads we deployed
Thanks for pointing that out. I hadn't known about Cloudflare Gateway and am exploring at now. Preliminary thoughts: it seems a lot more complex than configuring and setting up NextDNS. Had a look at setting up policies, and it doesn't seem to support adding ad-blocking lists (like the ones used in uBlock Origin) easily. In NextDNS these are just checkboxes for each filter list.