Mastodawn

Stéphane Bortzmeyer Oct 29

"disabling a problematic route that we found to be related to this"

It was not #DNS, it was #OSPF! (Or IS-IS?)

https://azure.status.microsoft/en-us/status

Azure status

Check the current Azure health status and view past incidents.

Show thread

Robert Edmonds Oct 29

@bortzmeyer There is a critical domain involved in the resolution of the CNAME chains used in Azure-related services, t-msedge.net. It has two nameserver IPs, both in the same /24. Hasn't been responding to me for a couple hours.

I think this is pretty fairly attributable as a "DNS failure" even if the underlying cause of the failure of the DNS service was a network failure.

Show thread

Robert Edmonds

@bortzmeyer Although, I guess in theory if DNS is a small part of the services that are affected by a network outage and those services wouldn't have worked anyway, had DNS been functional, it would be fair to say "not really a DNS outage, but a network outage".