blocky VS Pi-hole

I run multiple blocky instances in a kubernetes cluster. I don't know if it makes sense ... but I'm running kubernetes cluster at home, so making sense is relative ;p

The PI is running a DNS proxy (https://github.com/0xERR0R/blocky) and not much else at the moment.

I switched from pihole to https://github.com/0xERR0R/blocky for internal DNS, and I found it to be a lot easier to use compared to pihole. Setting up DNS entries was as easy as typing a single line in their config.yml, and restarting the service.

You could try using blocky instead of pihole. It's stateless and much more friendly to run.

Link to the Projects' GitHub pages: 1. https://github.com/0xERR0R/blocky [Blocky] 2. https://github.com/AdguardTeam/AdGuardHome [AdguardHome] 3. https://github.com/pi-hole/pi-hole [Pi-hole]

Any specific feature you need from pihole that Blocky doesn't have? Blocky is a much nicer tool for AdBlocking especially if deployed in k8s because it's stateless and configured via a single config file. Plus it's written in Go!

Still, to answer the question: https://github.com/0xERR0R/blocky

There is also blocky. I like it because it is light, declarative, stateless, can use redis as cache and has prometheus integration. This plays really nicely with my setup.

Si te preguntas, ¿por qué no usar Adguard o Pihole? 🤔

This is an overreaction, almost to the point of absurdity.

Risks inherent to pipe installers are well understood by many. Using your logic, we should abandon Homebrew [1] (>38k stars on GitHub), PiHole [2] (>46k stars on GitHub), Chef [3], RVM [4], and countless other open source projects that use one-step automated installers (by piping to bash).

A more reasonable response would be to coordinate with the developers to update the docs to provide alternative installation methods, rather than throwing the baby out with the bathwater.

[1] https://brew.sh/

[2] https://github.com/pi-hole/pi-hole

[3] https://docs.chef.io/chef_install_script/#run-the-install-sc...

[4] https://rvm.io/rvm/install

Pi-hole to block ads and tracking for my less technically savvy relatives

https://pi-hole.net/

I ran a competing project[0] on my home network for a few years before I discovered NextDNS[1]. What I lost in performance (requests don't leave my house) I gained in portability: ALL my devices can take advantage – at home and away – and time-saved. PiHole works 90% of the time, but when it did stop working, I'd have to spend a bit of time fixing it. At $20/year, I simply couldn't compete with NextDNS.

Note: This isn't a shill for NextDNS; I love these kinds of projects and think they absolutely should exist, but NextDNS just happens to be one of those dead-simple SaaS tools that is an insanely good value.

0 - https://pi-hole.net/

1 - https://nextdns.io

It definitely IS an option, but at the network level.

https://pi-hole.net/

It runs on damn near everything, and is a DNS level adblocker for the whole network.

I recently switched to Wipr [0]. It’s dead simple to use, and will auto update its filter lists in the background.

Adguard [1] is a decent free option.

I also use a Pi-hole [2] on my network.

[0] https://kaylees.site/wipr.html

[1] https://adguard.com/en/adguard-safari/overview.html

[2] https://pi-hole.net/

Are you trying to build a DNS proxy (similar to Pi-hole) that intercepts DNS requests and checks for the ones that look harmful? If so, I would suggest trying to separately build a DNS client and a DNS server, before trying to integrate them together. Start with Beej's Guide to Network Programming if you need to learn the basics of sockets, and then take a look at the documents that define the DNS protocol itself (RFC1034 and RFC1035).

Setup a pi-hole.

It's definitely not as simple as installing an app on your phone, but I run a Pi-hole on my home network, and it does block ads in many games.