Yet another example of how nobody, regardless of size, resources nor expertise, is immune from DNS outages.
Last week several Microsoft systems experienced a global outage when the company made a configuration error whilst migrating some legacy, infrastructure domains, to their own Azure platform. The errors had second-order effects within the Azure ecosystem itself, impacting Azure compute, storage, App service, Azure Identity, and SQL storage.
At some point, everybody has a DNS outage and it doesn’t even matter what the reason is. The way to mitigate this is proactively, by having alternate DNS solutions set up in advance, and by maintaining vigilance through monitoring of your naming processes, vendors and infrastructure.