Blocky vs Technitium
Editor take
Choose Blocky for a single binary that runs on an OpenWrt router. Choose Technitium for a recursive resolver that needs no upstream and for DHCP on the same box.
Where they differ
Only what is true of one of them and not the other. Each app's weak spots are the other app's strengths.
Technitium
Where Technitium is stronger
- Resolves queries itselfThe recursive resolver asks the root servers and needs no upstream provider; Blocky forwards DNS queries to the upstream resolvers in its config.3
- DHCP server on the same boxA built-in DHCP server can hand out leases for one or more networks; Blocky has no DHCP server and its docs leave leases to the router.4
Blocky vs Technitium: specs side by side
Every spec for both apps in one table, so you can check install options, hardware and client apps before you pick one.
| Spec | ||
|---|---|---|
| Price | Free | Free |
| Licence | Apache-2.0 | GPL-3.0 |
| Web UI | No | Yes |
| Docker | Yes | Yes |
| Linux package | Yes | Yes |
| Windows | – | Yes |
| macOS | – | Yes |
| Tech stack | Go | .NET |
| Docker Containers | 1 (app only) | 1 (app only) |
| Database | none | file only |
| Architecture | x86 + ARM | x86 + ARM |
Common questions
Does either one have a DHCP server?
Technitium does, and it can serve more than one network. Blocky has no DHCP server, so leases stay on the router and its DNS setting points at Blocky.
What does a recursive resolver do for my privacy?
It asks the root servers and follows the chain itself, so no single upstream provider sees the queries. Technitium does this; Blocky forwards to the upstream resolvers in its config.
Can I run either one on a router?
Blocky can: it ships a single binary for x86-64, ARM and MIPS and names OpenWrt routers as a target. Technitium builds for Windows, Linux, macOS and Raspberry Pi, and its portable app needs the .NET 10 runtime.
Sources: Blocky docs and Technitium docs.