CoreDNS is a DNS server that chains plugins
John Belamaric 37d06f382a Warn if the hosts file is a directory (#1126) 7 months ago
.github Add Pull Request templates (#1086) 8 months ago
.travis/kubernetes Add k8s external service CNAMEs (#677) 11 months ago
core core: drop invalid packets (#1123) 7 months ago
coremain Release 011 8 months ago
hooks Update DockerHub build hook with golang 1.9 (#998) 8 months ago
pb core: add more transports (#574) 1 year ago
plugin Warn if the hosts file is a directory (#1126) 7 months ago
request Remove the word middleware (#1067) 8 months ago
test test: remove -v output of test_readme.go (#1115) 7 months ago
vendor plugin/kubernetes: Enable protobuf, Update client api package (#1114) 7 months ago
.gitignore Add processing with travis-ci integration. (#269) 1 year ago
.travis.yml Remove the word middleware (#1067) 8 months ago Update (#1059) 8 months ago Add CNCF Code of Conduct (#565) 1 year ago doc update (#703) 11 months ago
Dockerfile update dockerfile to allow use of https_google - fixes #738 (#739) 11 months ago
Gopkg.lock plugin/kubernetes: Enable protobuf, Update client api package (#1114) 7 months ago
Gopkg.toml Stop vendoring go dns and context (#794) 10 months ago
LICENSE Cleanups, removing Caddy name a bit more 2 years ago
MAINTAINERS Maintainer update (#670) 1 year ago
Makefile Use gometalinter and enforcing go fmt/lint/vet (#1108) 8 months ago
Makefile.fuzz Add fuzzing infrastructure (#1118) 7 months ago
Makefile.release core: check for gh-release (#1079) 8 months ago cleanup readme (#1087) 8 months ago
codecov.yml Disable codecov/patch and codecov/changes status report (#758) 11 months ago
coredns.go Fix import path `` -> `` (#547) 1 year ago
directives_generate.go Remove the word middleware (#1067) 8 months ago
plugin.cfg Remove the word middleware (#1067) 8 months ago More Middleware -> Plugin conversions (#1088) 8 months ago


Documentation Build Status Code Coverage Go Report Card FOSSA Status CII Best Practices

CoreDNS is a DNS server that started as a fork of Caddy. It has the same model: it chains plugins.

CoreDNS is a Cloud Native Computing Foundation inception level project.

CoreDNS is the successor to SkyDNS. SkyDNS is a thin layer that exposes services in etcd in the DNS. CoreDNS builds on this idea and is a generic DNS server that can talk to multiple backends (etcd, kubernetes, etc.).

CoreDNS aims to be a fast and flexible DNS server. The keyword here is flexible: with CoreDNS you are able to do what you want with your DNS data. And if not: write a plugin!

CoreDNS can listen for DNS request coming in over UDP/TCP (go'old DNS), TLS (RFC 7858) and gRPC (not a standard).

Currently CoreDNS is able to:

  • Serve zone data from a file; both DNSSEC (NSEC only) and DNS are supported (file).
  • Retrieve zone data from primaries, i.e., act as a secondary server (AXFR only) (secondary).
  • Sign zone data on-the-fly (dnssec).
  • Load balancing of responses (loadbalance).
  • Allow for zone transfers, i.e., act as a primary server (file).
  • Automatically load zone files from disk (auto).
  • Caching (cache).
  • Health checking endpoint (health).
  • Use etcd as a backend, i.e., a 101.5% replacement for SkyDNS (etcd).
  • Use k8s (kubernetes) as a backend (kubernetes).
  • Serve as a proxy to forward queries to some other (recursive) nameserver (proxy).
  • Provide metrics (by using Prometheus) (metrics).
  • Provide query (log) and error (error) logging.
  • Support the CH class: version.bind and friends (chaos).
  • Profiling support (pprof).
  • Rewrite queries (qtype, qclass and qname) (rewrite).
  • Echo back the IP address, transport and port number used (whoami).

Each of the plugins has a of its own.


CoreDNS can be used as an authoritative nameserver for your domains. All in all, CoreDNS should be able to provide you with enough functionality to replace parts of BIND 9, Knot, NSD or PowerDNS and SkyDNS. Most documentation is in the source and blog articles can be found here. If you do want to use CoreDNS in production, please let us know.


CoreDNS (as a servertype plugin for Caddy) has a dependency on Caddy, but this is not different than any other Go dependency. If you have the source of CoreDNS checked out in the appropriate place in your GOPATH, get all dependencies:

go get ./...

(You can do the checkout and dependency resolution as a single step with: go get

And then go build as you would normally do:

go build

This should yield a coredns binary.

Compilation with Docker

CoreDNS requires Go to compile. However, if you already have docker installed and prefer not to setup a Go environment, you could build coredns easily:

$ docker run --rm -i -t -v $PWD:/go/src/ \
      -w /go/src/ golang:1.9 make

The above command alone will have coredns binary generated.


When starting CoreDNS without any configuration, it loads the whoami plugin and starts listening on port 53 (override with -dns.port), it should show the following:

2016/09/18 09:20:50 [INFO] CoreDNS-001

Any query send to port 53 should return some information; your sending address, port and protocol used.

If you have a Corefile without a port number specified it will, by default, use port 53, but you can override the port with the -dns.port flag:

./coredns -dns.port 1053, runs the server on port 1053.

Start a simple proxy, you'll need to be root to start listening on port 53.

Corefile contains:

.:53 {
    proxy .

Just start CoreDNS: ./coredns. Then just query on that port (53). The query should be forwarded to and the response will be returned. Each query should also show up in the log.

Serve the (NSEC) DNSSEC-signed on port 1053, with errors and logging sent to stdout. Allow zone transfers to everybody, but specifically mention 1 IP address so that CoreDNS can send notifies to it. {
    file /var/lib/coredns/ {
        transfer to *
        transfer to 2001:500:8f::53

Serve on port 1053, but forward everything that does not match to a recursive nameserver and rewrite ANY queries to HINFO.

.:1053 {
    rewrite ANY HINFO
    proxy .

    file /var/lib/coredns/ {
        transfer to *
        transfer to 2001:500:8f::53

IP addresses are also allowed. They are automatically converted to reverse zones: {
    # ...

Means you are authoritative for

The netmask must be dividable by 8, if it is not the reverse conversion is not done. This also works for IPv6 addresses. If for some reason you want to serve a zone named add the closing dot: as this also stops the conversion.

Listening on TLS and for gRPC? Use:

tls:// grpc:// {
    # ...

Specifying ports works in the same way:

grpc:// {
    # ...

When no transport protocol is specified the default dns:// is assumed.



Examples for deployment via systemd and other use cases can be found in the deployment repository.