-
-
Save hdais/3e9681fdeecfbea19ebe to your computer and use it in GitHub Desktop.
| options { | |
| // Enable DNSSEC validation | |
| dnssec-validation auto; | |
| // set NTA to dnssec-failed.org | |
| // BIND9.10 and higher implements disable-ds-digests | |
| disable-ds-digests dnssec-failed.org { SHA-1; SHA-256; }; | |
| }; |
Description
You can configure NTA for BIND 9.10, though only BIND 9.11 implements NTA officially.
BIND9.10 performs DNSSEC validation as if there's none of DS digest algorithms for the domain specified in disable-ds-digests. For DS digest algorithm mainly SHA-1 and SHA-256 are used. So in this configuration (nta-for-bind910.conf) BIND9.10 performs validation as if dnssec-failed.org has no DS records, which means the domain is "insecure".
A few domains are using other algorithms such as SHA-384 or GOST. For such domains, specify these algorithm e.g. disable-ds-digests example.com { SHA-384; };
This didn't work for insecure TLDs for me:
dnssec: validating tld/SOA: got insecure response; parent indicates it should be secure
So yes, this disables the DNSSEC validation for that domain, but if the parent mandates it to be secure, this doesn't help.
without NTA
BIND9.10 determines that "dnssec-failed.org" is bogus, and returns SERVFAIL.
with NTA
BIND9.10 doesn't perform DNSSEC validation for dnssec-failed.org and returns "insecure" (ad=0) answer.