A fast, lightweight DNS proxy and ad-blocker for local networks with advanced DNS configuration and privacy features.
Blocky is a DNS proxy and ad-blocker for local networks that blocks unwanted content like ads and malware while improving DNS resolution speed. It supports advanced features such as custom DNS rules, multiple protocols (DoH, DoT), and integration with monitoring tools. It is designed to be fast, lightweight, and privacy-focused, with no data collection.
Network administrators, home users, and developers looking to enhance local network privacy and performance, especially those running networks on devices like Raspberry Pi or in Docker environments.
Developers choose Blocky for its combination of ad-blocking, advanced DNS configuration, and privacy features in a single, stateless tool. Its lightweight design, support for modern DNS protocols, and easy integration with monitoring stacks make it a versatile alternative to simpler ad-blockers or commercial DNS services.
Fast and lightweight DNS proxy as ad-blocker for local network with many features
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports external blocklists with regex, per-client group rules, and deep CNAME inspection, enabling precise control over ads and malware.
Features customizable caching, prefetching, and low memory footprint to speed up DNS resolution and reduce external queries.
Implements DNS over HTTPS (DoH) and TLS (DoT), along with DNSSEC validation, ensuring secure and private communications.
Provides Prometheus metrics, Grafana dashboards, and database logging for straightforward DNS traffic analysis and monitoring.
Management relies solely on YAML files and CLI, which can be less intuitive compared to GUI-based tools like Pi-hole.
As a DNS proxy, it blocks at the domain level, which may miss ads or content using IP-based methods or advanced bypass techniques.
Setting up advanced features like per-client groups or external list integration requires familiarity with DNS concepts and YAML syntax, posing a barrier for novices.