10db2a80df
* Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compress and scrubbed so it will fit the specific client asking for it. * first simple test, less exporting of stuff * more * Add middleware/cache Add a caching middleware that caches nxdomain, nodata and successful responses. It differentiates between DNSSEC on normal DNS replies. Each reply is compressed and scrubbed so it will fit the specific client asking for it. The TTL is decremented with the time spend in the cache. There is syntax that allows you to cap the TTL for all records, no matter what. This allows for a shortlived cache, just to absorb query peaks. +Tests * cache test infrastructure * Testing |
||
|---|---|---|
| core | ||
| middleware | ||
| server | ||
| test | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTING.md | ||
| Dockerfile | ||
| LICENSE | ||
| main.go | ||
| main_test.go | ||
| Makefile | ||
| middleware.md | ||
| README.md | ||
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) and DNS is supported.
- Retrieve zone data from primaries, i.e. act as a secondary server.
- Loadbalancing of responses.
- Allow for zone transfers, i.e. act as a primary server.
- Use etcd as a backend, i.e. a 94.5% 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 (A/AAAA shuffling) of returned responses.
- Has support for the CH class:
version.bindand friends.
There are still few issues, and work is ongoing on making things fast and reduce the memory usage.
All in all, CoreDNS should be able to provide you with enough functionality to replace parts of BIND9, Knot, NSD or PowerDNS. 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?
- Optimizations.
- Load testing.
- The issues.