Anyone else see strange issues trying to lookup download.microsoft.com?
My DNS servers seem to mostly fail when looking that up. Though sometimes 1 of 4 dns servers can resolve it for a few minutes at a time.
Also noticed odd results occasionally when using 1.1.1.1 as the DNS server, but 8.8.8.8 seems to work all the time.
I also see the same issue if using IPv6 DNS servers.
Weird. So far I am blaming either MS or Akami.
@jelle Thanks. Yeah, its weird and sporadic.
Most of the time our DNS servers just return
"download.microsoft.com is an alias for dlc-shim.trafficmanager.net."
And die there. But when it does work, yikes, there are a lot of CNAMES to follow before it gets an IP address.
@doachs @jelle 1 out of 4 is strangely specific since there are 4 NS records in each CNAME.
the domain is quite interesting since the CNAME has 4 different domains. which might need 4 NS lookups to resolve the CNAME chain. (Please correct me if I am wrong)
I just quickly tested from my side and did not see any issues. If theres a NS issue I might not see it, since lot of NS servers are anycasted.
@miyuru @jelle Yeah, my guess right now is that it is some odd issue with Akamai trying to direct us to the best local cache for downloads.
At the moment, all 4 DNS servers can resolve an IP address for download.microsoft.com. So either I got lucky, or maybe someone fixed something.
We first discovered the issue when a co-worker needed to download something yesterday.
Seems related to it being a CNAME for dlc-shim.trafficmanager.net, which then does not resolve some times.
Dan Oachs
Jelle
Miyuru Sankalpa