Files
coredns/middleware/dnssec
Miek Gieben 7a8d943bcc Bail out on failure when starting up
Don't silently hide failures, barf on startup. Also add more integration
tests that should catch some of these things.
2016-04-27 10:48:22 +00: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-04-26 17:57:11 +01:00
2016-04-26 17:57:11 +01:00
2016-04-27 10:48:22 +00: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-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.

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