pihole-regex VS blocky

There are wrappers for updating regex lists that can be modified with other URLs. This was floating around for a while: https://github.com/mmotti/pihole-regex/blob/master/install.py and this is another method: https://www.bentasker.co.uk/posts/documentation/general/refreshing-piholes-regex-block-list-from-external-sources.html With enough regex tweaking I bet you could shave at least tens of thousands of lines off your list, and it could be divided into regex entries for domains where it makes sense, with the rest being non-regex domain entries. Simple regex that is functionally equivalent to AdBlock style wildcard blocks won't notably bog down the system either. It might take a few hours to get a workflow going to streamline producing such a list, but it can be done.

I also have a bunch of RegEx blacklisted from this pihole-regex/regex.list at master · mmotti/pihole-regex · GitHub and these:

Here's a list of domains I've used for years. All of which have been collected from different websites and sources such as https://firebog.net/ and https://github.com/mmotti/pihole-regex.

I also suggest these regex blocks

Your mileage may vary, but a combination of the default pi-hole list, the firebog.net lists (green, checkmark lists only), and the https://github.com/mmotti/pihole-regex/blob/master/regex.list do a pretty complete job for me.

While not perfect, and does not directly address the YouTube ads, I can suggest setting up mmotti's Regex Filters for Pi-hole.

I did also find these as well: https://github.com/mmotti/pihole-regex/blob/master/regex.list

Maybe this help: https://github.com/mmotti/pihole-regex

This might be of interest to you:

https://github.com/0xERR0R/blocky

Want to throw in blocky (https://github.com/0xERR0R/blocky). Supports modern protocols and easy to configure in one file. Migrated to this from pi-hole and never looked back.

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!