CoreDNS is a DNS server that chains plugins
Find a file
2016-04-15 20:14:04 +01:00
core Fix parsing of transfer lines 2016-04-15 17:08:31 +01:00
middleware Clean paths 2016-04-15 20:14:04 +01:00
server Allow more than 1 address for transfer (#121) 2016-04-14 19:57:39 +01:00
test Failed startup was not flagged (#118) 2016-04-13 20:13:55 +01:00
.gitignore Clean up some references to Caddy 2016-04-11 07:59:30 +01:00
.travis.yml Use IsDomainName (#119) 2016-04-13 23:23:35 +01:00
CONTRIBUTING.md Clean up some references to Caddy 2016-04-11 07:59:30 +01:00
Dockerfile Add Dockerfile (#116) 2016-04-13 20:14:13 +01:00
LICENSE Cleanups, removing Caddy name a bit more 2016-03-19 07:42:21 +00:00
main.go Fix Corefile parsing 2016-04-03 15:52:23 +01:00
main_test.go First commit 2016-03-18 20:57:35 +00:00
Makefile Add Dockerfile (#116) 2016-04-13 20:14:13 +01:00
middleware.md Clean up some references to Caddy 2016-04-11 07:59:30 +01:00
README.md Use IsDomainName (#119) 2016-04-13 23:23:35 +01:00

CoreDNS

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

Status

I'm using CoreDNS is my primary, authoritative, nameserver for my domains (miek.nl, atoom.net and a few others). CoreDNS should be stable enough to provide you with a good DNS service.

Currently CoreDNS is able to:

  • Serve zone data from a file, both DNSSEC (NSEC only atm) and DNS is supported. Delegation are not supported as yet.
  • Retrieve zone data from primaries, i.e. act as a secondary server.
  • Allow for zone transfers, i.e. act as a primary server.
  • Use Etcd as a backend, i.e. a 92% replacement for SkyDNS.
  • Serve as a proxy to forward queries to some other (recursive) nameserver.
  • Rewrite queries (both qtype, qclass and qname).
  • Provide metrics (by using Prometheus).
  • Provide Logging.
  • Provide load-balancing of returned responses.
  • Has support for the CH class: version.bind and friends.

There are corner cases not implemented and a few issues.

But all in all, CoreDNS should already be able to provide you with enough functionality to replace parts of BIND9, Knot, NSD or PowerDNS.

However CoreDNS is still in the early stages of development. For now most documentation is in the source and some blog articles can be found here. If you do want to use CoreDNS in production, please let us know and how we can help.

https://caddyserver.com/ is also full of examples on how to structure a Corefile (renamed from Caddyfile when I forked it).

Examples

Start a simple proxy:

Corefile contains:

.:1053 {
    proxy . 8.8.8.8:53
}

Just start CoreDNS: ./coredns. And then just query on that port (1053), the query should be forwarded to 8.8.8.8 and the response will be returned.

Serve the (NSEC) DNSSEC signed miek.nl on port 1053, errors and logging to stdout. Allow zone transfers to everybody.

miek.nl:1053 {
    file /var/lib/bind/miek.nl.signed {
        transfer to *
    }
    errors stdout
    log stdout
}

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

.:1053 {
    rewrite ANY HINFO
    proxy . 8.8.8.8:53

    file /var/lib/bind/miek.nl.signed miek.nl {
        transfer to *
    }
    errors stdout
    log stdout
}

All the above examples are possible with the current CoreDNS.

What remains to be done

  • Website?
  • Logo?
  • Code simplifications/refactors.
  • Optimizations.
  • Load testing.
  • All the issues.

Blog

https://miek.nl/tags/coredns/