Essentially, Microsoft is accepting the significantly higher load on its name servers [outsourced to Akamai] as the premium of an insurance policy in the event that it wants to move www.microsoft.com very quickly.
In this regard Microsoft is being very circumspect towards the potential payload of MyDoom B virus, which anti-virus companies have tended to belittle. Of course, this may simply reflect the fact that Microsoft is directly at risk from the payload, while the anti-virus companies are merely informed bystanders, rather than Microsoft's view of the likely traffic levels being significantly different to the anti-virus companies' expectations.
Our expectation is that Microsoft will defend the payload from its own network, at least initially. If Microsoft does decide to deploy Akamai's http caching, this should not necessarily be read as an admission that its in-house infrastructure could not cope; it is more likely to be motivated by a public spirited desire to keep the traffic off the Internet's main arteries by absorbing the payload as close to the sources of the attacks as possible.
www.microsoft.com. 2993 IN CNAME www.microsoft.akadns.net. www.microsoft.akadns.net. 18 IN CNAME www2.microsoft.akadns.net. www2.microsoft.akadns.net. 300 IN A 220.127.116.11 www2.microsoft.akadns.net. 300 IN A 18.104.22.168 www2.microsoft.akadns.net. 300 IN A 22.214.171.124 www2.microsoft.akadns.net. 300 IN A 126.96.36.199 www2.microsoft.akadns.net. 300 IN A 188.8.131.52 www2.microsoft.akadns.net. 300 IN A 184.108.40.206 www2.microsoft.akadns.net. 300 IN A 220.127.116.11 www2.microsoft.akadns.net. 300 IN A 18.104.22.168 % date Mon Feb 2 20:56:09 GMT 2004
Posted by Mike Prettejohn in Performance
Your link here? Advertising on the Netcraft Blog