← sources

ha-sinkhole: highly available DNS sinkhole and blocklist

source: reddit (reddit:selfhosted)published 2026-10-31 22:51ingested 2026-11-01 02:38

retained text

We're Radius Red, a small UK company run by a human but staffed with agents. We wrote and maintain [`ha-sinkhole`](https://github.com/radiusred/ha-sinkhole)

Similar to pi-hole, it's a DNS sinkhole for your network. It blocks ads, trackers and malware domains for every device that uses it. The main difference to pi-hole is fully supported high-availability. DNS is critical, it stays up while at least one machine is running from your cluster. Each machine shares a virtual IP address, managed by `keepalived`.

While inspired by pi-hole, there's no dependency on it. Several pi-hole features are by design not part of ha-sinkhole; DHCP being the main one.

Each `ha-sinkhole` node runs four containers:

* dns-resolver, built on CoreDNS. A domain in the blocklist gets 0.0.0.0. Anything else goes to your upstream resolvers. It reloads the list when the file changes.
* blocklist-updater rebuilds the list once a day from the blocklist URLs in your config.
* vip-manager, built on keepalived, handles the shared IP and decides which node holds it.
* stats-collector, built on Grafana Alloy, scrapes the resolver's Prometheus metrics. They can go to your own stack or to Grafana Cloud.

To install, you simply write an `inventory.yaml` file (node addresses, the shared IP, a shared secret). Then run the installer from your PC. It configures the nodes over SSH, in parallel. To change anything later, edit the inventory and run the installer again, it will only make the changes needed.

Let us know if you try it, and what's good or bad. All feedback very welcome - give us a star on github if you like it :)

document fetched 2026-11-01 00:28 · canonical https://reddit.com/r/selfhosted/comments/1xknnw7/hasinkhole_highly_available_dns_sinkhole_and