# 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 Kubernetes and self-hosted networks. It is open source and self-hosted, installable on Docker Hub, Proxmox and Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4486/coredns

## Description

CoreDNS is a flexible, plugin-based DNS server and forwarder that chains plugins for service discovery, metrics, query rewriting, and zone file serving in Kubernetes and self-hosted networks.

## Platform availability

Available on 2 of 10 platforms: Proxmox, Helm.

## Health score

81/100 (Excellent), based on 4 of 5 factors.
- Maintained: 100 (last commit 6 days ago)
- Popular: 83 (14,436 GitHub stars)
- Easy to install: 35 (2 install platforms, install notes)
- Security check: 88 (no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 8/10)

## Links

- Official website: https://coredns.io
- Docker Hub: https://hub.docker.com/r/coredns/coredns
- Documentation: https://coredns.io/manual/toc
- GitHub: https://github.com/coredns/coredns
- Proxmox: https://community-scripts.github.io/ProxmoxVE/scripts?id=coredns
- Kubernetes (Helm): https://artifacthub.io/packages/helm/coredns/coredns

## 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.

## Alternatives

- Technitium DNS Server: Technitium DNS Server is an open source tool that can be used as a personal local DNS server for privacy &amp; 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…

---
Source: Our Local Host (https://ourlocalhost.com/app/4486/coredns), the self-hosted and open-source app directory.
