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.

Editor

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.

Blocky

Where Blocky is stronger

  • A single binary for a routerShips one binary for x86-64, ARM and MIPS and names Raspberry Pi and OpenWrt routers as targets.1
  • Metrics in Grafana dashboardsServes an optional Prometheus metrics endpoint and ships Grafana dashboards.2

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
PriceFreeFree
LicenceApache-2.0GPL-3.0
Web UINoYes
DockerYesYes
Linux packageYesYes
Windows–Yes
macOS–Yes
Tech stackGo.NET
Docker Containers1 (app only)1 (app only)
Databasenonefile only
Architecturex86 + ARMx86 + ARM

Common questions

Sources: Blocky docs and Technitium docs.

Updated