On Wed, Jan 31, 2024 at 04:37:02PM +0200,
Phil Kulin wrote
a message of 56 lines which said:
> Done. New serial number 4058860. New active ZSK
> https://dnsviz.net/d/ru/ZbpWZg/dnssec/
There is now a detailed technical post-mortem. These official
explanations fit the facts that we observed.
Done. New serial number 4058860. New active ZSK
https://dnsviz.net/d/ru/ZbpWZg/dnssec/
On Wed, Jan 31, 2024 at 4:34 AM Phil Kulin wrote:
>
> Timeline:
> 2024-01-30 12:29:44 UTC: Last correct answer before outage (SOA SN:
> 4058855): https://dnsviz.net/d/ru/ZbjruA/dnssec/
> 2024-01-30 15:27:27
On Wed, Jan 31, 2024 at 04:34:40AM +0200,
Phil Kulin wrote
a message of 45 lines which said:
> Timeline:
Thanks.
I'm not convinced that the subject of this thread is useful. The chain
of keys was always correct (unlike many DNSSEC problems, the DS, and
DNSKEY were always in sync), the
Timeline:
2024-01-30 12:29:44 UTC: Last correct answer before outage (SOA SN:
4058855): https://dnsviz.net/d/ru/ZbjruA/dnssec/
2024-01-30 15:27:27 UTC: First bad answer (SOA SN: 4058857):
https://dnsviz.net/d/ru/ZbkVXw/dnssec/
2024-01-30 17:27:35 UTC: Resigning attempt (SOA SN: 4058857 and
https://dnsviz.net/d/ru/ZbjruA/dnssec/
https://dnsviz.net/d/ru/ZbkVXw/dnssec/
And there is about 1hr outage by now
--
Sergey
___
dns-operations mailing list
dns-operations@lists.dns-oarc.net
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
