Akamai is a caching service. Looks like Mcafee has contracted with them to host they're updates. The IP address is the closets/least loaded akamai cluster, which could be anywhere. Akamai delivers between 10% and 20% of all internet traffic. (Windows Update used to run on akamai. I don't know if they still do)
I just checked Akamai's site, and it does list McAfee.com as a new customer. On Mon, Mar 16, 2009 at 10:53 AM, Brian Beausoleil < [email protected]> wrote: > Greetings everyone! > > > > Over the past few weeks our trouble tickets have increased for the AV > Update requirement. The common cause is that McAfee Enterprise is failing > to automatically update. Our workers have been updating McAfee manually, > but it is becoming repetitive now. I began looking into our User Role > policies, and what sites the auto-date service was using. A simple netstat > reveals that the McAfee Update utility is no longer pointing to nai.combut > rather to > *a<ipaddress>.deploy.akamaitechnologies.com*. I notice the ip address > changes, and an nslookup on the servers by name are returning errors “** > server can't find a72-246-94-51.deploy.akamaitechnologies.com: NXDOMAIN”. > Has anyone else seen this? What are you doing to combat this issue? The > best I can do for now is add 72.246.94.0/24 to ports 21 and 80 to my > temporary role until a solution is found by Cisco that is more > dynamic/automatic. > > > > Thanks in advance… > > Brian >
