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)
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)