4

A few of my friends experienced the glory of PiHole in my home network and asked, if I could install such a thing in their networks as well.

Which I obviously could, but none of them are interested in updating/maintaining such a device. So I would like to collect some suggestions on how to deploy such a box with (ideally) zero interaction from my side until the end of times.

My hardware platform of choice would be a cheap thin client (Futro s920 or something like that) running Ubuntu with unattended updates enabled.

Pihole itself seem to offer an auto-updater, but I'm not sure how stable that runs in the long run - maybe Docker would be better suited here?

you are viewing a single comment's thread
view the rest of the comments
[-] francis@lemmy.world -1 points 1 year ago* (last edited 1 year ago)

Spitballing ideas:

  • ~Run PiHole on a public facing server/port. You'll probably need to plan out the security aspects of it, but then your friends could then just set their devices to use the PiHole DNS (much like how people can set their devices to use 1.1.1.1 or 8.8.8.8).~
  • Drop a Pi with PiHole in their network that is managed with some fleet/IOT management platform like Balena. That'll in theory get you PiHole running in a container, and you'll have a management platform to actually remotely connect to the Pi to manage it.

You may be already aware, but be mindful of the danger associated with having an ounce of responsibility for their DNS uptime. The bonus of option #1 is that you could also empower your friends to "bypass" PiHole should it go belly up.

Edit: Don't do #1 unless you can properly secure it.

this post was submitted on 30 Jun 2023
4 points (83.3% liked)

Selfhosted

39677 readers
336 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS