DNSSEC disruption affecting .de domains – Resolved
21–30 of 440 posts
Re: DNSSEC disruption affecting .de domains – Resolved
#22Looks like it failed after a maintenance: https://www.namecheap.com/status-updates/planned-denic-de-re...
Re: DNSSEC disruption affecting .de domains – Resolved
#23DNSSEC not working
If using an open resolver, i.e., a shared DNS cache, e.g., third party DNS service such as Google, Cloudflare, etc., then it might fail, or it might not. It depends on the third party DNS provider
https://datatracker.ietf.org/meeting/118/materials/slides-11...
Re: DNSSEC disruption affecting .de domains – Resolved
#24For me bmw.de works but www.bmw.de not
Re: DNSSEC disruption affecting .de domains – Resolved
#25Re: DNSSEC disruption affecting .de domains – Resolved
#26Whole .de TLD seems to go offline right now due to dnssec or missing nic.de nameservers?
This works: $ unbound-host -t A www.denic.de www.denic.de has address 81.91.170.12 This does not: $ unbound-host -D -t A www.denic.de www.denic.de has address 81.91.170.12 validation failure : signature crypto failed from 194.246.96.1 for DS denic.de. while building chain of trust So it does seem DNSSEC-related. EDIT My explanation was wrong, this is not how keytags work. The published keytag data is consistent: de.…
Re: DNSSEC disruption affecting .de domains – Resolved
#27Re: DNSSEC disruption affecting .de domains – Resolved
#28Re: DNSSEC disruption affecting .de domains – Resolved
#29Good news though, if you add domain-insecure: "de" to your unbound config everything works fine