News for hackers. Stuff that matters.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by stirfrykitty on Wednesday April 10, 2019 @10:25AM (#19624941)
Why not run a Pi-hole? You only stand to benefit. Whilst it doesn't address DoH, it does go a long way in preventing the tracking you mention. It also saves on bandwidth. And because it works at the DNS level, you benefit from the calls not even being made. The Pi-hole can be customized with an endless set of rules to block about any ads, beacons, trackers. Couple this with uBlock Origin, Privacy Badger, Decentraleys, Referer Block, and some creative browser settings (about:config) and you are largely safe from prying eyes. JS can be whitelisted, etc. You have nothing to lose.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by Nas808 on Wednesday April 10, 2019 @11:01AM (#19625370)
You can do both, I have a Pi-Hole running alongside the “Cloudflared” package so Dnsmasq forwards lookups to Cloudflare over DoH.
Re:DNS-over-HTTPS Policy Requirements for Resolvers by KitDuncan on Wednesday April 10, 2019 @12:14PM (#19626117)
My setup is similar. Pihole with dnssec and dnscrypt-proxy connected to cloudflare. Didn't see a reason to use the cloudflared package instead of dnscrypt-proxy.