What you're seeing is MS using Akamai's Edgesuite service. Basically, www.microsoft.com CNAMES to www.microsoft.akadns.net, which resolves to the "closest" Akamai server to the source IP on the DNS query. That box caches the content from the *real* www.microsoft.com, and serves it up. Nice concept, and a helluva lot easier to implement on the end user side than FreeFlow, IMHO... -Chris On Fri, Dec 28, 2001 at 01:40:48PM -0500, Ian A Finlay wrote:
On Fri, 28 Dec 2001, Christopher Schulte wrote:
Looks to me as if Microsoft is altering global delegation of their windowsupdate service. Maybe diversifying the dns structure as they did with microsoft.com after the attacks a while back? They now have 12 DNS servers scattered around the globe, just to serve microsoft.com dns.
Yeah, maybe they're moving they're update service from windowsupdate.microsoft.com to windowsupdate.com. Maybe they'll "Akamize" windowsupdate.com too...
bash-2.04$ host www.microsoft.com www.microsoft.com is a nickname for www.microsoft.akadns.net www.microsoft.akadns.net has address 207.46.230.218 www.microsoft.akadns.net has address 207.46.230.219 www.microsoft.akadns.net has address 207.46.230.220 www.microsoft.akadns.net has address 207.46.197.100 www.microsoft.akadns.net has address 207.46.197.101 www.microsoft.akadns.net has address 207.46.197.113 www.microsoft.akadns.net has address 207.46.197.102
bash-2.04$ host windowsupdate.microsoft.com windowsupdate.microsoft.com has address 207.46.106.88
bash-2.04$ host windowsupdate.com windowsupdate.com has address 207.46.106.88 windowsupdate.com has address 207.46.226.17 windowsupdate.com has address 207.68.131.27
-Ian
-- --------------------------- Christopher A. Woodfield rekoil@semihuman.com PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xB887618B