Dieser Bereich kann Inhalte enthalten, die nicht für alle Nutzer geeignet sind. Dazu können unter anderem Texte, Medien oder Diskussionen gehören, die als beleidigend, extremistisch, gewaltbezogen oder anderweitig belastend empfunden werden. Wenn du solche Inhalte nicht sehen möchtest, nutze bitte die jeweiligen Filter- und Meldeoptionen der Plattform oder meide entsprechende Threads/Communities.
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).
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)
Nah it’s more like all the sites and services that used blocked links that you have to add to the whitelist or in some cases be able to turn the protection off and on. It’s a regular occurrence for me
deleted by creator
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”).