Skip to main content


Edit: issue seems fixed.

Looks like DE ccTLD is unresolvable due to DNSSEC issue:
dnsviz.net/d/nic.de/afpsNg/dns…

😬

🧵👇

#InfoSec #DNSSEC #DNS #Germany

This entry was edited (2 weeks ago)

reshared this

in reply to Michał "rysiek" Woźniak · 🇺🇦

If I am reading this correctly – and I might not, it's been a long day – the issue is not directly with DE itself, but with nic.de.

Which doesn't necessarily make it much better.

in reply to Michał "rysiek" Woźniak · 🇺🇦

And that's why it doesn't make it much better:

;; ANSWER SECTION:
de. 86400 IN NS a.nic.de.
de. 86400 IN NS f.nic.de.
de. 86400 IN NS l.de.net.
de. 86400 IN NS n.de.net.
de. 86400 IN NS s.de.net.
de. 86400 IN NS z.nic.de.

If nic.de. is down, nameservers in nic.de. are down. Which will cause issues for DE.

in reply to Michał "rysiek" Woźniak · 🇺🇦

At this moment, please send #HugOps to folks at DENIC. They are dealing with a really bad and stressful situation and I am sure they are doing their best to resolve it as soon as possible.

#DNS #DENIC

in reply to Michał "rysiek" Woźniak · 🇺🇦

Because it is DNS, everything is cached on multiple levels. Because there are nameservers in different TLDs (which is the correct thing to do!), combined with cache invalidation fun, this will keep looking like intermittent failures for a while most probably.
in reply to Michał "rysiek" Woźniak · 🇺🇦

Here's a thought:

The fact that people are experiencing issues with DE sites and asking if CloudFlare is down speaks volumes about the stability of DE ccTLD and the broader DNS compared to big cloud providers.

:blobcatcoffee:

#DNS #InfoSec #SysAdmin