<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><br><div><br><blockquote type="cite"><div>On Jul 11, 2023, at 8:24 PM, Gavin McCullagh <gmccullagh@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta charset="UTF-8"><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;">That is true of course, but the magnitude of this event was made much worse by dnssec. The entire COM and NET zones being bogus (including the unsigned delegations) is very different to the few that saw record changes in the prior 1-2 days. </span></div></blockquote></div><div><br></div><div>As explained in other messages this is not true due to the rolling expiry </div><div>but on the other hand DNSSEC may have exposed the problem much sooner than otherwise, I once helped a TLD operator to find a single anycast instance that they assumed was off line for the few weeks but it was still serving an expired zone. </div><div><br></div><div> Olafur</div><div><br></div></body></html>