30 Jul
2024
30 Jul
'24
2:39 p.m.
On Jul 28, 2024, at 9:34 PM, Peter Potvin <peter.potvin@accuristechnologies.ca> wrote:
We were actually having this same issue earlier tonight, though across .com and .is domains as well. Interesting to see it's not just us.
That’s an interesting observation, Peter. I hadn’t seen it outside of the .ca zone personally, but I just received a response back from CIRA that tracks with what you saw.
This was actually a legit and ongoing issue with a third-party anycast DNS provider for .CA. It also impacted ~100+ other top-level domains and their dnssec-validation in the Toronto-Niagara region.
Anyways, it’s nice to finally have a resolution to this. Cheers.