Pi-hole. You’ll want to run two, because machines will use both a primary and a secondary server for their DNS requests. If you don’t want to buy a pair of raspberry pi’s, you can run it in Docker, which basically keeps it isolated to its own tiny virtual machine. So you’d just need to spin up a pair of docker containers to run the pair of pi-holes. If you’re using Docker, they’ll need a pair of volumes too, or else they’ll lose all of their data every time they reboot.
You’ll want this to be on a machine that is running 24/7, because any time it shuts down, your internet will essentially stop working. That’s why lots of people end up just throwing a few raspberry pis in a closet and forgetting about them.
Once it’s installed, you’ll need to load it with block lists. The default ones are pretty basic. I’d just google something like “pihole blocklists” and figure it out from there. Each list will be a URL, which allows the pihole to pull updates, (which you can tell it to do via the built-in web UI).
Jason2357@lemmy.ca 10 months ago
Besides Pi-hole, there’s Adguard. The “home” version works just like Pi-hole on a device on your network (but is a little slicker in my opinion), and a DNS service where you just set your router’s or devices DNS to their service (less private, but no dedicated device required). That’s an option that is not ideal, but far better than not blocking at the DNS level for anyone uncomfortable configuring a device on their network.