Researchers at The Citizen Lab have for the first time released technical evidence of sophisticated mercenary spyware being distributed via online advertising.
I never understood pihole in the first place. It’s just a fancy web interface you do never look at if the thing does its job quietly in the background. And unbound alone is perfectly able to use blocklists with one line of configuration (and an onliner script to convert the common lists into the right format).
and an include blocklist.conf at the bottom of unbound.conf (awk to convert it from the “0.0.0.0 <site>” format to “local-zone: <site> always_refuse”).
Because you have to mess with it all the time. It’s easier to get in and get out to make changes with the nice interface. It’d be different if it was set it and forget it but realistically it’s not.
It literally is a cron job or systemd timer to load an updated blocklist from time to time and I haven’t looked at it for years (well… other an changing a path when I switched from unbound to dnsproxy, because that one is even simpler, doesn’t even need a config other than a few parameters at startup and can provide DoH, DoT and/or DoQ access for when I’m not at home)
It’s a more complete dns server. You can more easily do dns over https, set up zones, and custom dns entries are a lot easier imo.
In summary it’s more focused on being dns, the ad blocking is a feature on top. You also don’t have to manually configure unbound for recursive dns like you do pi hole. Etc etc
If you just want simple ad blocking you don’t actually need pi hole for it’s web interface you don’t ever look at once it runs. Unbound alone can do the job with minimal configuration.
Nowadays I even changed my setup to dnsproxy, which doesn’t even need any config. It’s just a handful parameters when you start it. And it does all the filtering for my home network as well as providing DoH access for when I’m not at home and connected from somewhere else.
Yeah but what you will eventually find, if reliability matters at all to you, is that the pihole isn’t the best for this. For one, many run on an SD card, which isn’t really stable long-term (I started here and had to fix it due to SD card corruption quite a few times). Second, you don’t have a backup. DNS not running when your machines depend on it equals an immediate outage across ALL devices (as long as you have it configured at your router level, which you should be doing, right?).
Technitium (and others) solve this problem gracefully.
I started with pihole (ad blocking) and unbound (recursive DNS), and that was a pain to set up properly.
Moved do technitium (which offers all of these in one package) plus the ability to natively cluster a second instance (so you have a backup load balanced instance for this critical service)
The best part is that setting it up if you have an old laptop or desktop running docker is incredibly simple. I had two nodes up and running clustered in less than 15 minutes. Took less time than setting up one pihole.
If you don’t have docker it may take more time, but that’s the slippery slope of setting up a homelab and running services like this.
My Pi hole has been up and solid for about a decade now, so not sure “isn’t really stable long term” is landing
Thank you for the in-depth explanation, Technitium sounds really involved. I just plunked down a pi hole, turned it on, and it’s been working for years and years. I’ll keep this in mind though if I ever want to drive myself nuts with networking
Good for you, many don’t have the same experience. Technitium is easier to set up in my experience, but you do you if it works for you. That’s the benefit of having free choices.
Just to be clear, I’m not trying to sell you or anyone on technitium over pihole or pihole+unbound, they’re all free and I don’t work for them or anything. However, as someone that has gone through this journey with all of them, I’ll never go back to pihole, especially with the features technitium has and the importance of DNS to my home lab plus the incredible ease of setup.
Technitium does this incredibly easily. I fiddled with pihole and unbound for so long to get them to coexist properly, and pihole alone before that. The pihole part was easy although unreliable on a raspberry pi due to the sd card. It was better once I added an ssd to the pi, but it didn’t have recursive DNS. Adding unbound and getting them configured properly and coexisting properly wasn’t an easy task. Technitium has all of this in one package and was trivial to set up one or more clustered nodes. You don’t need anything to ensure they both work together, the clustering feature does this incredibly easily. One goes down? No prob, I see a discord alert from uptime kuma letting me know. When it comes back up cluster mgmt syncs everything and they load balance again.
My current setup has an uptime of 210 days, and likely would be longer if it weren’t for a power outage.
It really is so simple, I’d suggest everyone try it out. You can always change it back if you don’t like it. And, like the pihole, you can load curated block lists.
I like technitium. Way better than pi hole.
In what way(s)?
The main way is it has a built in recursive DNS server so you don’t have to duct tape Pi Hole and Ubound together
I never understood pihole in the first place. It’s just a fancy web interface you do never look at if the thing does its job quietly in the background. And unbound alone is perfectly able to use blocklists with one line of configuration (and an onliner script to convert the common lists into the right format).
@Ooops @EncryptKeeper
Those scripts never worked for me… so pihole-unbound to the end…xddddddd
My “script” to update the blocklist from time to time was literally
curl <blocklist1 link> > templistcurl <blocklist2 link> >> templistgrep '^0\.0\.0\.0' templist | awk '{print "local-zone: \""$2"\" always_refuse"} > blocklist.confsystemctl restart unbound.serviceand an
include blocklist.confat the bottom ofunbound.conf(awk to convert it from the “0.0.0.0 <site>” format to “local-zone: <site> always_refuse”).Because you have to mess with it all the time. It’s easier to get in and get out to make changes with the nice interface. It’d be different if it was set it and forget it but realistically it’s not.
It literally is a cron job or systemd timer to load an updated blocklist from time to time and I haven’t looked at it for years (well… other an changing a path when I switched from unbound to dnsproxy, because that one is even simpler, doesn’t even need a config other than a few parameters at startup and can provide DoH, DoT and/or DoQ access for when I’m not at home)
It’s a more complete dns server. You can more easily do dns over https, set up zones, and custom dns entries are a lot easier imo.
In summary it’s more focused on being dns, the ad blocking is a feature on top. You also don’t have to manually configure unbound for recursive dns like you do pi hole. Etc etc
Oh. I guess if you just want dead simple ad blocking, pi hole is still the way
If you just want simple ad blocking you don’t actually need pi hole for it’s web interface you don’t ever look at once it runs. Unbound alone can do the job with minimal configuration.
Nowadays I even changed my setup to dnsproxy, which doesn’t even need any config. It’s just a handful parameters when you start it. And it does all the filtering for my home network as well as providing DoH access for when I’m not at home and connected from somewhere else.
I’d prefer Adguard Home. Does the same thing but also supports encrypted DoT/DoQ/DoH upstreams. And the UI looks a bit neater for me
AdGuard looks like a paid SaaS service though? No way am I paying for someone else running a device on my network, no friggin way
AdGuard Home is free. I’m running 2 redundant docker containers on separate hosts with adguard sync all for free.
https://adguard-dns.io/kb/adguard-home/getting-started/
Yup, I have it installed in my OPNSense and together they make a fucking fortress
Yeah but what you will eventually find, if reliability matters at all to you, is that the pihole isn’t the best for this. For one, many run on an SD card, which isn’t really stable long-term (I started here and had to fix it due to SD card corruption quite a few times). Second, you don’t have a backup. DNS not running when your machines depend on it equals an immediate outage across ALL devices (as long as you have it configured at your router level, which you should be doing, right?).
Technitium (and others) solve this problem gracefully.
I started with pihole (ad blocking) and unbound (recursive DNS), and that was a pain to set up properly.
Moved do technitium (which offers all of these in one package) plus the ability to natively cluster a second instance (so you have a backup load balanced instance for this critical service)
The best part is that setting it up if you have an old laptop or desktop running docker is incredibly simple. I had two nodes up and running clustered in less than 15 minutes. Took less time than setting up one pihole.
If you don’t have docker it may take more time, but that’s the slippery slope of setting up a homelab and running services like this.
My Pi hole has been up and solid for about a decade now, so not sure “isn’t really stable long term” is landing
Thank you for the in-depth explanation, Technitium sounds really involved. I just plunked down a pi hole, turned it on, and it’s been working for years and years. I’ll keep this in mind though if I ever want to drive myself nuts with networking
Good for you, many don’t have the same experience. Technitium is easier to set up in my experience, but you do you if it works for you. That’s the benefit of having free choices.
Just to be clear, I’m not trying to sell you or anyone on technitium over pihole or pihole+unbound, they’re all free and I don’t work for them or anything. However, as someone that has gone through this journey with all of them, I’ll never go back to pihole, especially with the features technitium has and the importance of DNS to my home lab plus the incredible ease of setup.
No backup with PiHole?
PiHole can run redundant if you want. Does Technitium do this differently? Or more easily?
Technitium does this incredibly easily. I fiddled with pihole and unbound for so long to get them to coexist properly, and pihole alone before that. The pihole part was easy although unreliable on a raspberry pi due to the sd card. It was better once I added an ssd to the pi, but it didn’t have recursive DNS. Adding unbound and getting them configured properly and coexisting properly wasn’t an easy task. Technitium has all of this in one package and was trivial to set up one or more clustered nodes. You don’t need anything to ensure they both work together, the clustering feature does this incredibly easily. One goes down? No prob, I see a discord alert from uptime kuma letting me know. When it comes back up cluster mgmt syncs everything and they load balance again.
My current setup has an uptime of 210 days, and likely would be longer if it weren’t for a power outage.
It really is so simple, I’d suggest everyone try it out. You can always change it back if you don’t like it. And, like the pihole, you can load curated block lists.
An ONT failure has me fiddling with my network this weekend and I might do this. Pihole is okay but having more power would be great.
This is the way