It's Always DNS. Filtering with PiHole and Podman

danielpeck.com

2 points·dpeck··5 comments

I plan to followup later changing upstream DNS to use Cloudflare for Team over HTTPS to be able to do some customization and have some more privacy from the larger world while giving up some to cloudflare

I do DNS over TLS to Quad9 and Cloudflare just by configuring my resolver & pointing it to them. No accounts needed. I don't know what else Cloudflare for Teams might offer.

Logs, analytics, and more custom policies vs just the base filtering.

I’ve already added the cloudflare for teams through cloudflared and it’s working quite well over the last couple weeks.

I really do prefer local filtering, via lists I supply or create. A decade ago, I used OpenDNS's filtering but my wariness of surveillance capitalism has grown. I try to keep as much as I can in-house now.

That said, I use Cloudflare for DDNS because I needed it for LetsEncrypt cert autorenew.

That is fair, and an understandable position to have.

My thoughts are that if upstream can already see the requests coming from my network to be able to resolve them then I might as well get the benefits of having more visibility and customization of it since privacy has already been given up for the service.

pfSense shill here. I really like how PiHole fill the need between custom firewalls and consumer grade NAT devices. It might be the way I went, if I didn't need an edge box.

Reply on news.ycombinator.com