Post #2245615
2026-05-08 18:33 UTC
Replies (5)
-
@leah@blahaj.social 2026-05-08 18:35
@jpmens@mastodon.social Now if it answered the question "why did it take 3 hours to roll this back"...
-
@R1Rail@pouet.chapril.org 2026-05-08 18:38
@jpmens@mastodon.social generation of key id is indeed (for me) a cloudy part of DNSSEC.
-
@shaft@piaille.fr 2026-05-08 18:47
@jpmens@mastodon.social As expected, it was not a #DNS problem. :)
-
@byteborg@chaos.social 2026-05-09 03:52
@jpmens@mastodon.social "During the implementation of improvements, a faulty piece of code was incorporated into the in-house development which was not fully covered by the test scenarios…" Was it "AI" code?
-
@winfried@fosstodon.org 2026-05-09 07:18
@jpmens@mastodon.social "particularly when the absence of the DS record must be ‘proven’ for an unsigned child zone." I wonder when and how often a resolver checks for the presence of the DS in a parent zone. Because it escalated very quickly