TrueCloudLab/coredns
16
0
Fork 2
Code Issues Pull requests 3 Projects Releases Packages Wiki Activity Actions
CoreDNS is a DNS server that chains plugins
157 commits 2 branches 70 tags 128 MiB
Go 99.9%
Find a file
Miek Gieben 09207867e4 Add missing test file and fix notify 
We should not check the port of the request, we *should* actually
normalize it to port 53 - as that will probably be the address of
the server. Still need to double check if this will work if the
axfr should actually be done from a different port. That will come
later, this is good enough for now.
2016-04-07 08:03:57 +01:00
core A health middleware 2016-04-06 09:21:46 +01:00
middleware Add missing test file and fix notify 2016-04-07 08:03:57 +01:00
server Add AXFR test 2016-04-06 22:29:33 +01:00
.gitignore First commit 2016-03-18 20:57:35 +00:00
.travis.yml Add Benchmark functions 2016-03-31 22:10:17 +01:00
CONTRIBUTING.md Cleanups, removing Caddy name a bit more 2016-03-19 07:42:21 +00: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
middleware.md Proxy cleanups 2016-03-19 20:53:37 +00:00
README.md beef up some examples 2016-04-03 20:30:37 +01:00

README.md

CoreDNS

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

Status

Currently CoreDNS is able to:

  • Serve zone data from a file, both DNSSEC (NSEC only atm) and DNS is supported.
  • 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 90% replacement for SkyDNS.
  • Serve as a proxy to forward queries to some other (recursive) nameserver.
  • Prove metrics (by using Prometheus)
  • Rewrite queries (both qtype and qname).
  • Provide Logging.

There are corner cases not implement and some blatantly missing functionality; i.e. the secondary implementation does not requery the primary -- ever, leading to stale data if the server is not restarted.

CoreDNS is running on port 1053 on linode.atoom.net. This is one step from being run on port 53. See this blog article on this, or this bug on the progress of running CoreDNS as my production nameserver.

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

CoreDNS is still in the early stages of development and should not be used on production servers yet. 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/