Post B603i4a1gV1y0xVjTE by rysiek@mstdn.social
 (DIR) More posts by rysiek@mstdn.social
 (DIR) Post #B5zxi9ZMXEFHlOr6Xo by rysiek@mstdn.social
       0 likes, 0 repeats
       
       Looks like DE ccTLD is unresolvable due to DNSSEC issue:https://dnsviz.net/d/nic.de/dnssec/😬 #InfoSec #DNSSEC #DNS #Germany
       
 (DIR) Post #B5zxiA24oTDLCSI2Ii by rysiek@mstdn.social
       0 likes, 0 repeats
       
       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.
       
 (DIR) Post #B5zxiALDfIWi9pFK8e by rysiek@mstdn.social
       0 likes, 0 repeats
       
       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.
       
 (DIR) Post #B5zxiAcaciQB1hNCDI by domi@donotsta.re
       1 likes, 0 repeats
       
       @rysiek i mean, they do have de.net, so it’s not an irrepairable level of a fuckupdon’t look at dig NS pl now…
       
 (DIR) Post #B5zxiAk2B2NNOmr8oi by rysiek@mstdn.social
       0 likes, 0 repeats
       
       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
       
 (DIR) Post #B5zyN2F8g7JyultFT6 by rysiek@mstdn.social
       1 likes, 0 repeats
       
       @domi guess what are the NSes for de.net. though…;; ANSWER SECTION:de.net.                 86400   IN      NS      ns1.denic.de.de.net.                 86400   IN      NS      ns2.denic.de.de.net.                 86400   IN      NS      ns3.denic.de.de.net.                 86400   IN      NS      ns4.denic.net.
       
 (DIR) Post #B5zyN2NeAU7vL9s2jI by domi@donotsta.re
       0 likes, 0 repeats
       
       @rysiek well, but denic.net has glue records. and so does de.net. so those fields don’t really matter much, it’s still resolvable
       
 (DIR) Post #B603i4a1gV1y0xVjTE by rysiek@mstdn.social
       0 likes, 0 repeats
       
       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.
       
 (DIR) Post #B603i4mQwMxIdRJdoG by rysiek@mstdn.social
       0 likes, 1 repeats
       
       DENIC's status page:https://status.denic.de/Screenshot below in case you're not able to load it (as I said, stuff is going to be intermittently failing).#DNS #DENIC #DNSSEC #InfoSec #SysAdmin
       
 (DIR) Post #B603i5J2z72kGaZge0 by rysiek@mstdn.social
       1 likes, 0 repeats
       
       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
       
 (DIR) Post #B608IBAD5FuAftuLJ2 by yetzt@yetzt.me
       1 likes, 0 repeats
       
       @rysiek last notable outage at denic was almost 16 years ago, when they moved servers from amsterdam to frankfurt.