you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 9 hours ago (4 children)

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

  • source
  • parent
  • hideshow 4 child comments
  • [–] 0 points 4 hours ago (1 child)

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

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 hours ago*

    My "script" to update the blocklist from time to time 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 " format to "local-zone: always_refuse").

  • source
  • parent
  • [–] 1 point 6 hours ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 4 hours ago* (last edited 4 hours ago)

    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)

  • source
  • parent