corednsvsmikrotik-dns
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| coredns | mikrotik-dns | |
|---|---|---|
| Score | 76/100 | 41/100 |
| Rank in category | #4 of 41 in DNS | #39 of 47 in Network Monitoring |
| GitHub stars | 14 426 | 143 |
| Stars, last 30 days | +63 | +7 |
| Stable releases, 12 months | 10 | 0 |
| Latest release | v1.15.0 · 21 Oct 2026 | — |
| Setup | Moderate | Easy |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | GPL-3.0 |
| Main language | Go | Typescript |
Which one should you pick?
coredns scores 76/100 against 41/100 for mikrotik-dns, so it is the safer default.
coredns ships more often: 10 stable releases in the past year, against 0 for mikrotik-dns.
If you want the quickest setup, mikrotik-dns is easier to run; coredns needs more configuration.
coredns is growing faster right now (+63 stars in 30 days).
Key differences
- License: coredns is Apache-2.0, mikrotik-dns is GPL-3.0.
- Language: coredns is written mainly in Go, mikrotik-dns in Typescript.
- Platforms only coredns lists: Build from Source, Linux.
- Features only coredns lists: Access control lists, Authoritative zone serving from files, DNS64 IPv6 translation, Forwarding to upstream resolvers and 11 more.
- Features only mikrotik-dns lists: Automatic data purging, Click-to-copy functionality, Client analysis, Complete query log and 7 more.
coredns details →mikrotik-dns details →
Swap a project
Keep coredns, compare it with
Keep mikrotik-dns, compare it with