Provide DS records to act a trust anchors for DNSSEC
Provide DS records to act a trust anchors for DNSSEC
...
@@ -724,17 +721,19 @@ key(s) (KSK) of the root zone,
...
@@ -724,17 +721,19 @@ key(s) (KSK) of the root zone,
but trust anchors for limited domains are also possible. The current
but trust anchors for limited domains are also possible. The current
root-zone trust anchors may be downloaded from https://data.iana.org/root-anchors/root-anchors.xml
root-zone trust anchors may be downloaded from https://data.iana.org/root-anchors/root-anchors.xml
.TP
.TP
.B --dnssec-check-unsigned
.B --dnssec-check-unsigned[=no]
As a default, dnsmasq does not check that unsigned DNS replies are
As a default, dnsmasq checks that unsigned DNS replies are
legitimate: they are assumed to be valid and passed on (without the
legitimate: this entails possible extra queries even for the majority of DNS
zones which are not, at the moment, signed. If
.B --dnssec-check-unsigned=no
appears in the configuration, then such replies they are assumed to be valid and passed on (without the
"authentic data" bit set, of course). This does not protect against an
"authentic data" bit set, of course). This does not protect against an
attacker forging unsigned replies for signed DNS zones, but it is
attacker forging unsigned replies for signed DNS zones, but it is
fast. If this flag is set, dnsmasq will check the zones of unsigned
fast.
replies, to ensure that unsigned replies are allowed in those
zones. The cost of this is more upstream queries and slower
Versions of dnsmasq prior to 2.80 defaulted to not checking unsigned replies, and used
performance. See also the warning about upstream servers in the
.B --dnssec-check-unsigned
section on
to switch this on. Such configurations will continue to work as before, but those which used the default of no checking will need to be altered to explicitly select no checking. The new default is because switching off checking for unsigned replies is inherently dangerous. Not only does it open the possiblity of forged replies, but it allows everything to appear to be working even when the upstream namesevers do not support DNSSEC, and in this case no DNSSEC validation at all is occuring.
.B --dnssec
.TP
.TP
.B --dnssec-no-timecheck
.B --dnssec-no-timecheck
DNSSEC signatures are only valid for specified time windows, and should be rejected outside those windows. This generates an
DNSSEC signatures are only valid for specified time windows, and should be rejected outside those windows. This generates an