Our take
- Activity
- 67
- Community
- 79
- Issues
- 51
- Pull requests
- 82
+79 stars in the last 30 days
- Merges more pull requests than 92% of the projects we track
- More contributors than 76% of the projects we track
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
7,107Forks
321Change since Nov 14, 2026: +2 stars·0 forks
Overview
Blocky sits between devices on a local network and their DNS resolvers. It can filter queries using external blocklists and allowlists, while also handling custom domain resolution, conditional forwarding, caching, and client-specific DNS settings.
It is suited to people who want to manage DNS filtering and resolution for a household, homelab, or small network from one service. It is stateless and configurable through YAML, and supports deployment as a binary or Docker image.
Key Features
- Block domains using external lists, allowlists, regular expressions, and client groups.
- Inspect CNAME chains and response IP addresses when applying blocking rules.
- Configure custom DNS records, conditional forwarding, and upstream resolvers per client group.
- Use DNS over UDP, TCP, HTTPS, TLS, QUIC, and HTTPS/3.
- Cache and prefetch DNS answers, and query multiple upstream resolvers.
- Export Prometheus metrics, use Grafana dashboards, and log queries to CSV or supported databases.
- Provide a DNS-over-HTTPS endpoint and REST API, with no user-data collection or telemetry according to the project README.
Use Cases
- A household can block advertising and malware domains for devices across its local network.
- Parents can apply distinct allowlists or denylists to a client group for children's devices.
- Homelab operators can direct selected domains to custom resolvers while forwarding other queries upstream.
- Network administrators can monitor DNS activity through metrics and query logs, and use encrypted DNS between Blocky and upstream resolvers.
Getting Started
See the installation documentation for setup instructions. The repository README links to the full documentation and configuration examples.
Considerations
Blocky is a DNS service to deploy and configure, not a browser extension or a ready-made blocklist. Its filtering depends on the lists and rules you configure, and managing it requires configuring a YAML file. The README describes Docker and single-binary deployment options, as well as support for multiple CPU architectures. The project reports no telemetry or user-data collection.
Found this useful?
Share it with someone who would like blocky.