corednsvsKnock-Knock
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | Knock-Knock | |
|---|---|---|
| Score | 76/100 | 48/100 |
| Rank in category | #5 of 41 in DNS | #49 of 78 in Security |
| GitHub stars | 14 399 | 214 |
| Stars, last 30 days | +59 | — |
| Stable releases, 12 months | 10 | 5 |
| Latest release | v1.15.0 · 21 Oct 2026 | v3.0.0 · 26 Jul 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Python |
Which one should you pick?
coredns scores 76/100 against 48/100 for Knock-Knock, so it is the safer default.
coredns ships more often: 10 stable releases in the past year, against 5 for Knock-Knock.
If you want the quickest setup, coredns is easier to run; Knock-Knock needs more configuration.
coredns is growing faster right now (+59 stars in 30 days).
coredns details →Knock-Knock details →
Swap a project
Keep coredns, compare it with
Keep Knock-Knock, compare it with