Microsoft just showed why not to screw up your DNS records

Discussion in 'Resources' started by Prashant Sharan, May 4, 2019.

  1. Prashant Sharan

    Prashant Sharan India Active Member

    Joined:
    Oct 1, 2018
    Messages:
    1,172
    Likes Received:
    17
    Trophy Points:
    38
    Location:
    India
    Okay, this might actually be worse than the infamous “blue screen of death” that people used to tease Microsoft about. Yesterday, a huge array of core Microsoft services like Azure, Microsoft 365, Dynamics, DevOps and more went down…for two grueling hours.

    How did it happen?

    Like the title of my post says, someone made a big mistake while updating DNS records, here’s the scoop:

    Summary of impact: Between 19:43 and 22:35 UTC on 02 May 2019, customers may have experienced intermittent connectivity issues with Azure and other Microsoft services (including M365, Dynamics, DevOps, etc). Most services were recovered by 21:30 UTC with the remaining recovered by 22:35 UTC.

    Preliminary root cause: Engineers identified the underlying root cause as a nameserver delegation change affecting DNS resolution


    Full article