CoreDNS
CoreDNS is a flexible, plugin-based DNS server and forwarder that chains plugins for service discovery, metrics, query rewriting, and zone file serving in…
Platform availability
Available on 2 of 10 platforms
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
81/100 Excellent
- Maintained
- 100last commit 6 days ago
- Popular
- 8314,436 GitHub stars
- Easy to install
- 352 install platforms, install notes
- Light to run
- No data
- Security check
- 88no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 8/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked today
- GitHub stars
- 14,436
- Open issues
- 279
- Last commit
- 2026-11-15
- Latest release
- v1.15.0
- License
- Apache-2.0
- Activity
- steady
Checked 4 days ago - source: GitHub (coredns/coredns)
Resources & Compatibility
Requirements not published yet.
First-install notes
- Set up a simple Corefile first Write a minimal Corefile that listens on :53 and forwards normal lookups to a resolver such as 8.8.8.8 before starting CoreDNS. Without a valid Corefile, the server may not answer correctly and your normal browsing can stop resolving names. source
- Check it answers on port 53 After starting CoreDNS, test it with `dig @127.0.0.1 -p 53 www.example.com` to confirm it is listening on the standard DNS port (53) and returning answers. If this fails, clients pointed at CoreDNS will likely get no results either. source
- Do not swap ports during a reload If you edit settings and need a reload, avoid changing a port to one that is already in use. A failed reload can leave the DNS service half-broken, with old settings gone but the new listener not started. source
Fetched 53 days ago - each note links to its source
Variants
Alternatives (3)
- Technitium DNS Server - Technitium DNS Server is an open source tool that can be used as a personal local DNS server for privacy & security.
- Unbound - Unbound is a validating, recursive, and caching DNS resolver that you can self-host to run your own DNS server at home.
- dnsmasq - Dnsmasq is a lightweight Domain Name System (DNS) forwarder and Dynamic Host Configuration Protocol (DHCP) server designed for small to med…
Checked 54 days ago - source: AlternativeTo
Common questions
How can I confirm a basic CoreDNS configuration is working before pointing clients at it?
Create a minimal Corefile that listens on :53 and forwards normal lookups to a resolver such as 8.8.8.8, then test it with dig @127.0.0.1 -p 53 www.example.com. If the test fails, clients pointed at CoreDNS may get no results.
What should I avoid when reloading CoreDNS configuration?
Do not change a port to one that is already in use during a reload. A failed reload can leave the DNS service half-broken, with old settings gone but the new listener not started.
Can CoreDNS forward DNS queries to another recursive resolver?
Yes, CoreDNS can act as a proxy and forward queries to another recursive nameserver using the forward plugin.
What Kubernetes DNS symptoms should I check when CoreDNS resolution is failing?
Check for NXDOMAIN, SERVFAIL, I/O timeouts, loop detected, ndots latency, and NetworkPolicy blocking port 53.
From which Kubernetes version is CoreDNS the recommended default DNS server?
From Kubernetes v1.13, CoreDNS is the recommended default DNS server in Kubernetes.
Answers sourced from github.com, github.com, github.com, github.com, kubernetes.recipes
Community
- Coredns for local DNS resolution and forwarding over TLS (with ... - Reddit (reddit)
- Coredns vs powerdns vs bind : r/selfhosted - Reddit (reddit)
- CoreDNS and Caching best practices? - Netgate Forum (forum)
- Coredns Issue on Kubernetes Cluster - General Discussions - Discuss ... (forum)
- CoreDNS will fail you at scale (with default settings) (reddit)
Collected 48 days ago - public community threads