Post
Replies:
16
@rysiek Yep. Have had several problems with uncached de-Domains (amongst others hhsocial.de this instance's domain)
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 Also looks like dnsviz.net has been hugged to death by everyone hitting it.
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.
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.
@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 Good pun. :)
@rysiek while I'm taking this as a cue to just go to bed and leave computering for tomorrow... RIP to all the shoddily written automations and batch jobs that will fail tonight 🫡
May their knock-on effects be mild tomorrow
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 Weirdly enough, after a hickup about 20 minutes ago, everything seems to work for me (for now).
@rysiek yeah there is some weird sh!t going on lately yesterday when I checked dnscheck.tools and also mullvad.net/en/check I got the firts time an DNS error. Not quite sure what to make out of that 🤔
