Comment on Self-Hosting a DNS Sinkhole is really important

• Ooops@feddit.org ⁨4⁩ ⁨days⁩ ago

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

  original

  • EncryptKeeper@lemmy.world ⁨4⁩ ⁨days⁩ ago

    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.

    original

    • Ooops@feddit.org ⁨4⁩ ⁨days⁩ ago

      It literally is cron job or systemd timer to load an updated blocklist from time to time and I haven’t looked at it for years.

      original

      • EncryptKeeper@lemmy.world ⁨4⁩ ⁨days⁩ ago

        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

        original
  • awelo@tuiter.rocks ⁨4⁩ ⁨days⁩ ago

    @Ooops @EncryptKeeper
    Those scripts never worked for me....... so pihole-unbound to the end......xddddddd

    original

    • Ooops@feddit.org ⁨4⁩ ⁨days⁩ ago

      My “script” was literally

      curl *<blocklist1 link>* > templist
curl *<blocklist2 link>* >> templist
grep ‘^0\.0\.0\.0’ templist | awk '{print “local-zone: \”“$2”\" always_refuse"} > blocklist.conf
systemctl restart unbound.service

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

      original