* Fix EDNS0 compliance Do SizeAndDo in the server (ScrubWriter) and remove all uses of this from the plugins. Also *always* do it. This is to get into compliance for https://dnsflagday.net/. The pkg/edns0 now exports the EDNS0 options we understand; this is exported to allow plugins add things there. The *rewrite* plugin used this to add custom EDNS0 option codes that the server needs to understand. This also needs a new release of miekg/dns because it triggered a race-condition that was basicly there forever. See: * https://github.com/miekg/dns/issues/857 * https://github.com/miekg/dns/pull/859 Running a test instance and pointing the https://ednscomp.isc.org/ednscomp to it shows the tests are now fixed: ~~~ EDNS Compliance Tester Checking: 'miek.nl' as at 2018-12-01T17:53:15Z miek.nl. @147.75.204.203 (drone.coredns.io.): dns=ok edns=ok edns1=ok edns@512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok docookie=ok edns512tcp=ok optlist=ok miek.nl. @2604:1380:2002:a000::1 (drone.coredns.io.): dns=ok edns=ok edns1=ok edns@512=ok ednsopt=ok edns1opt=ok do=ok ednsflags=ok docookie=ok edns512tcp=ok optlist=ok All Ok Codes ok - test passed. ~~~ Signed-off-by: Miek Gieben <miek@miek.nl> Signed-off-by: Miek Gieben <miek@miek.nl> * typos in comments Signed-off-by: Miek Gieben <miek@miek.nl> |
||
---|---|---|
.. | ||
black_lies.go | ||
black_lies_bitmap_test.go | ||
black_lies_test.go | ||
cache.go | ||
cache_test.go | ||
dnskey.go | ||
dnssec.go | ||
dnssec_test.go | ||
handler.go | ||
handler_test.go | ||
log_test.go | ||
OWNERS | ||
README.md | ||
responsewriter.go | ||
rrsig.go | ||
setup.go | ||
setup_test.go |
dnssec
Name
dnssec - enable on-the-fly DNSSEC signing of served data.
Description
With dnssec any reply that doesn't (or can't) do DNSSEC will get signed on the fly. 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). NSEC3 is not supported.
This plugin can only be used once per Server Block.
Syntax
dnssec [ZONES... ] {
key file KEY...
cache_capacity CAPACITY
}
The signing behavior depends on the keys specified. If multiple keys are specified of which there is at least one key with the SEP bit set and at least one key with the SEP bit unset, signing will happen in split ZSK/KSK mode. DNSKEY records will be signed with all keys that have the SEP bit set. All other records will be signed with all keys that do not have the SEP bit set.
In any other case, each specified key will be treated as 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). NSEC3 is not supported.
If multiple dnssec plugins are specified in the same zone, the last one specified will be used (See bugs).
-
ZONES zones that should be signed. If empty, the zones from the configuration block are used.
-
key file
indicates that KEY file(s) should be read from disk. When multiple keys are specified, RRsets will be signed with all keys. Generating a key can be done withdnssec-keygen
:dnssec-keygen -a ECDSAP256SHA256 <zonename>
. A key created for zone A can be safely used for zone B. The name of the key file can be specified in one of the following formats- basename of the generated key
Kexample.org+013+45330
- generated public key
Kexample.org+013+45330.key
- generated private key
Kexample.org+013+45330.private
- basename of the generated key
-
cache_capacity
indicates the capacity of the cache. The dnssec plugin uses a cache to store RRSIGs. The default for CAPACITY is 10000.
Metrics
If monitoring is enabled (via the prometheus directive) then the following metrics are exported:
coredns_dnssec_cache_size{server, type}
- total elements in the cache, type is "signature".coredns_dnssec_cache_hits_total{server}
- Counter of cache hits.coredns_dnssec_cache_misses_total{server}
- Counter of cache misses.
The label server
indicated the server handling the request, see the metrics plugin for details.
Examples
Sign responses for example.org
with the key "Kexample.org.+013+45330.key".
example.org {
dnssec {
key file Kexample.org.+013+45330
}
whoami
}
Sign responses for a kubernetes zone with the key "Kcluster.local+013+45129.key".
cluster.local {
kubernetes
dnssec {
key file Kcluster.local+013+45129
}
}