
I’ve been using Pi-hole for more than 8 years now. In all that time, I haven’t had a single problem with the software itself or with updates. The only annoyance was that I only had one instance, and I couldn’t use the internet properly while updating my Proxmox host or the LXC container where Pi-hole was running. That’s why I’ve now installed a second Pi-hole instance on my TrueNAS server. Originally, I didn’t really want to run any additional software on my NAS, but since installation with TrueNAS Scale is so easy and my NAS has nearly 100% uptime throughout the year, it makes sense.
After setting up and importing the configuration from my primary Pi-Hole instance via Teleporter I checked if there are any new relevant blocklists. I listed my used blocklists in an earlier post here. Of course, I’ve added a few more lists over the past few years, but I never updated that post. I found the following helpful repository
https://github.com/hagezi/dns-blocklists
And also this site to test the blocking, but not sure how meaningful the result is…
As last step, I added my second Pi-hole instance as alternative DNS-Sever in my FritzBox.
