A policy layer for
the network you run.

Built around your resolver

Your DNS server sends query metadata to Blockinator’s authenticated HTTP or HTTPS API. Blockinator evaluates policy and returns an allow/block decision. The resolver integration enforces the answer. You keep control of the policy service and its database.

The application lives in blockinator-web. The separate blockinator-technitium project connects Technitium DNS Server. This website documents and introduces both parts.

How a request moves

1. A client sends a DNS request to Technitium.
2. The plugin sends client and question metadata to the policy endpoint.
3. Blockinator evaluates ignored types, pause state, matching targets, schedules, and eligible lists.
4. Blockinator returns the decision and matching context.
5. Technitium continues normal resolution or the plugin generates a blocked response.

Where your data lives

Use SQLite by default or a MySQL backend. Configuration, policy, credentials, and retained query history stay in the selected database. TLS material and Caddy state also need persistent local storage. The management console offers system, dark, and light themes.

Open source, maintained in public

Blockinator is a project by Bob Cronin, available under the GNU General Public License v3.0. Explore the source, review releases, or report a reproducible issue on GitHub.