问题原文
原帖链接 · jmw · CC BY-SA 3.0
I have a forward-only BIND9 server running on the LAN and it logs hundreds of errors per day like:
Aug 29 18:38:29 nuc named[850]: error (no valid RRSIG) resolving 'ubuntu.com/DS/IN': 75.75.75.75#53
Aug 29 18:38:31 nuc named[850]: validating @0x7fc6d826ed50: com SOA: got insecure response; parent indicates it should be secure
Aug 29 18:38:31 nuc named[850]: error (no valid RRSIG) resolving 'medium.com/DS/IN': 75.75.75.75#53
Aug 29 18:38:31 nuc named[850]: validating @0x7fc6d4014b80: com SOA: got insecure response; parent indicates it should be secure
It appears clients are still getting results, but these messages are filling up the logs. Relevant lines in named.conf:
forwarders {
# Comcast
2001:558:feed::1;
2001:558:feed::2;
75.75.75.75;
75.75.76.76;
};
forward only;
dnssec-enable yes;
dnssec-validation auto;
dnssec-lookaside auto;
What do these errors really mean is happening? Is this a misconfiguration on my end or Comcast's?
已采纳解答
原帖链接 · Calle Dybedahl · CC BY-SA 3.0
It looks like Comcast's servers are deliberately stripping out DNSSEC signatures from the responses they're giving you, so your server cannot validate com. (in this case) even though it knows that one should be signed. This is unlikely to cause any directly noticeable problems, it just leaves you and your users wide open for all the attacks that DNSSEC was created to protect against.
Exactly why Comcast want to reduce your level of security you will have to ask them.
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
