[ad_1]
On May 2, Microsoft Azure suffered a worldwide outage for nearly two hours from 19:43 UTC. Although the services were partially restored at 21:30 UTC, the problem was not fully resolved. The Azure connectivity issue was primarily related to Microsoft services, including Microsoft 365, Dynamics, and DevOps, and its customers were affected around the world.
The giant in Redmond has released an update explaining why the problem has occurred.
According to Microsoft, the preliminary root cause of the generalized problem seems to be a problem of "name server delegation". The firm said:
Engineers identified the underlying root cause as a name server delegation change affecting DNS resolution and having a downstream impact on computing, storage, application service, and other services. AAD and SQL database. When migrating from a legacy DNS system to Azure DNS, some domains for Microsoft Services have been updated incorrectly. No client DNS records were affected during this incident, and the availability of the Azure DNS remained at 100% throughout the incident. The problem was only for Microsoft service records.
According to the company's statement, although the engineers identified and solved the problem in a matter of hours, some systems that accessed domains with incorrect configurations stored this information, resulting in longer recovery times than expected. the faulty cache expires.
That being said, Microsoft is still studying the problem and has promised that a detailed root cause analysis (RCA) would be released within 72 hours. This is not the first time that Azure is affected by a worldwide outage. In 2016, a worldwide DNS failure affected several Azure-based services, including the SQL database, Web / App applications, API management, service bus, HDInsight, Media Services, and Visual Studio Team Services. Earlier this year, many Office 365 users could not access their mailboxes because of a similar failure.
Source: Microsoft via ZDNet
[ad_2]
Source link