My ISP (Telefonica) currently doesn't return addresses for login.microsoftonline.de (cloud Germany) while Google's DNS servers do. I wonder if that's related.
Interesting, I suspecting their 'restart' of 'authentication infrastructure' may be a rolling restart and perhaps they have not got to Germany yet, perhaps by using Google's DNS different 'authentication infrastructure' is being provided?
Moving to another Provider might involve shifting to other ips. Probably sucks to be working there right now.
We thought that too - gwmigprda.aadg.windows.net.nsatc.net seems / seemed to be failing to resolve, but then it seemed like it was internal to their infrastructure - which they later added to their status page (and clarified it was their authentication infrastructure which needed to be 'rebooted').
Perhaps it's related to the DNS flag day [0] that's coming up on Friday?
Not certainly not. Hypothetical scenario: realise something in your infrastructure will have problems in a few days’ time, and so make changes, which accidentally break things.
You've never made a change in advance of an upcoming problem that accidentally broke something else? Lucky...
I don't understand, could you explain? Level3 may be the biggest backbone provider but I doubt that Microsoft is peering only with them are they? This is maybe something that a smaller company might do but Microsoft seems too large for that.
Wording of the communication to my organization indicated that Level 3 is handling some subset of Azure-internal networking. I don't think it's a peering issue.
Thanks!
Why would Microsoft be using a third parties DNS? It’s trivial to host it yourself.
Ouch, level3 is pretty big. How could they have an outage?