corednsvsquackback
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | quackback | |
|---|---|---|
| Score | 76/100 | 50/100 |
| Rank in category | #5 of 41 in DNS | #9 of 14 in Customer Support |
| GitHub stars | 14 398 | 331 |
| Stars, last 30 days | +55 | +0 |
| Stable releases, 12 months | 10 | 15 |
| Latest release | v1.15.0 · 21 Oct 2026 | v0.14.1 · 7 Oct 2026 |
| Setup | Moderate | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | Typescript |
Which one should you pick?
coredns scores 76/100 against 50/100 for quackback, so it is the safer default.
quackback ships more often: 15 stable releases in the past year, against 10 for coredns.
coredns is growing faster right now (+55 stars in 30 days).
coredns details →quackback details →
Swap a project
Keep coredns, compare it with
Keep quackback, compare it with