Looks like DE ccTLD is unresolvable due to DNSSEC issue:https://dnsviz.net/d/nic.de/dnssec/
-
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.
@rysiek Why are the nic.de servers' addresses not glued to the root zone? I thought that was standard practice even if you have nameservers in other zones, too
-
@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.@rysiek@mstdn.social well, but denic.net has glue records. and so does de.net. so those fields don't really matter much, it's still resolvable
-
Looks like DE ccTLD is unresolvable due to DNSSEC issue:
https://dnsviz.net/d/nic.de/dnssec/
-
@rysiek@mstdn.social well, but denic.net has glue records. and so does de.net. so those fields don't really matter much, it's still resolvable
@domi fair enough
-
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.
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).
-
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.
-
Looks like DE ccTLD is unresolvable due to DNSSEC issue:
https://dnsviz.net/d/nic.de/dnssec/ From a users perspective some .de domains are not available on one connection but on another connection?
At least that's what I'm experiencing currently.
-
@rysiek@mstdn.social True experts questioned their home infra first, because that is obviously the most stable culprit
-
From a users perspective some .de domains are not available on one connection but on another connection?
At least that's what I'm experiencing currently.
@stekopf read the thread, I explain why this is going to feel intermittent
-
@rysiek the last failure of DE I recall was in May (hmm) 2010 (or 2012) when the zone exporter failed because of a file-system full error which wasn’t caught before the zone was shipped out to DE’s secondaries. That caused (alphabetically) all zones > a certain letter (ISTR it was ‘m’) to fail. Quite funny on one hand, sad on another, and hugely embarrassing to the DENIC people
-
@rysiek Good pun.
-
@rysiek the last failure of DE I recall was in May (hmm) 2010 (or 2012) when the zone exporter failed because of a file-system full error which wasn’t caught before the zone was shipped out to DE’s secondaries. That caused (alphabetically) all zones > a certain letter (ISTR it was ‘m’) to fail. Quite funny on one hand, sad on another, and hugely embarrassing to the DENIC people
@jpmens any public failure of a TLD, especially a ccTLD, is hugely embarrassing…
-
@rysiek Good pun.
@extmind what pun?
-
@extmind what pun?
@rysiek ...to *resolve* it as soon as possible.
-
@rysiek last notable outage at denic was almost 16 years ago, when they moved servers from amsterdam to frankfurt.
-
@rysiek ...to *resolve* it as soon as possible.
@extmind oh damn! I did not do this on purpose. ha!
-
@rysiek last notable outage at denic was almost 16 years ago, when they moved servers from amsterdam to frankfurt.
@yetzt this is… how many nines?
-
@yetzt this is… how many nines?
-
@yetzt I ded.
-
@rysiek last notable outage at denic was almost 16 years ago, when they moved servers from amsterdam to frankfurt.
@yetzt Since that day, all my domains have name servers assigned, which are under two distinct TLDs. And this is the reason, that all my domains (except for .de) still resolve at the moment.
