Files
coredns/middleware/dnssec
Miek Gieben 9ac3cab1b7 Make CoreDNS a server type plugin for Caddy (#220)
* Make CoreDNS a server type plugin for Caddy

Remove code we don't need and port all middleware over. Fix all tests
and rework the documentation.

Also make `go generate` build a caddy binary which we then copy into
our directory. This means `go build`-builds remain working as-is.

And new etc instances in each etcd test for better isolation.
Fix more tests and rework test.Server with the newer support Caddy offers.

Fix Makefile to support new mode of operation.
2016-08-19 17:14:17 -07:00
..
2016-04-26 17:57:11 +01:00
2016-04-26 17:57:11 +01:00
2016-04-26 17:57:11 +01:00
2016-08-14 07:30:41 -07:00
2016-04-26 17:57:11 +01:00
2016-04-26 17:57:11 +01:00

dnssec

dnssec enables on-the-fly DNSSEC signing of served data.

Syntax

dnssec [zones...]
  • zones zones that should be signed. If empty the zones from the configuration block are used.

If keys are not specified (see below) a key is generated and used for all signing operations. The DNSSEC signing will treat this key a CSK (common signing key) forgoing the ZSK/KSK split. All signing operations are done online. Authenticated denial of existence is implemented with NSEC black lies. Using ECDSA as an algorithm is preferred as this leads to smaller signatures (compared to RSA).

A signing key can be specified by using the key directive.

WARNING: when a key is generated there is currently no way to extract any key material from CoreDNS, this key only lives in memory. See issue https://github.com/miekg/coredns/issues/211.

TODO(miek): think about key rollovers.

dnssec [zones... ] {
    key file [key...]
}
  • key file indicates key file(s) should be read from disk. When multiple keys are specified, RRset will be signed with all keys. Generating a key can be done with dnssec-keygen: dnssec-keygen -a ECDSAP256SHA256 <zonename>. A key created for zone A can be safely used for zone B.

Examples