Akamai ipv6.akamai.net changes

[Patrick W. Gilmore]

If anyone has issues with the way Akamai maps their v6 (or v4 for that matter), please send the results of "host whoami.akamai.net" along with a dig/host against the Akamai hostname you think is being mis-mapped to NetSupport-tix at akamai.com.  They will research why you are mapped where you are mapped and either fix it or explain the issue.

Please realize that v6 traffic is both tiny (yes, still) and highly unreliable.  As a result, nodes frequently have v6 turned off when performance measurements show loss or high latency, and sometimes they do not get turned back on right away.  As with any massive system, there are times when the queue gets long, and v6 tickets are not handled as quickly as v4 tickets.

Sorry, but that's reality in a for-profit company.

-- 
TTFN,
patrick

P.S. Don't send me the info personally unless you like waiting for the longest queue ever - my inbox. :)


On Aug 18, 2012, at 15:13 , "Frank Bulk" <frnkblk at iname.com> wrote:

> Sorry, I meant ipv6.akamai.com. 
> 
> And those have changed since I last checked:
> 
> nagios:/# dig AAAA ipv6.akamai.com +short
> ipv6.akamai.com.edgesuite.net.
> a152.i6g1.akamai.net.
> 2001:418:2401:1::9dee:4a23
> 2001:418:2401:1::9dee:4a3b
> nagios:/#
> 
> Frank
> 
> -----Original Message-----
> From: Brian E Carpenter [mailto:brian.e.carpenter at gmail.com] 
> Sent: Saturday, August 18, 2012 2:09 AM
> To: frnkblk at iname.com
> Cc: ipv6-ops at lists.cluenet.de
> Subject: Re: Akamai ipv6.akamai.net changes
> 
> *** ordns.he.net can't find ipv6.akamai.net: Non-existent domain
> 
> Regards
>   Brian Carpenter
> 
> On 17/08/2012 23:04, Frank Bulk wrote:
>> What about ipv6.akamai.net?
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: Brian E Carpenter [mailto:brian.e.carpenter at gmail.com] 
>> Sent: Friday, August 17, 2012 1:54 PM
>> To: frnkblk at iname.com
>> Cc: ipv6-ops at lists.cluenet.de
>> Subject: Re: Akamai ipv6.akamai.net changes
>> 
>> I'm seeing
>> 
>>> www.akamai.com
>> Server:  ordns.he.net
>> Address:  2001:470:20::2
>> 
>> Non-authoritative answer:
>> Name:    a152.dscb.akamai.net
>> Addresses:  2001:450:2002:384::40d6:ce1b
>>          2001:450:2002:384::40d6:ce28
>> 
>> and it redirects me to
>> 
>>> uk.akamai.com
>> Server:  ordns.he.net
>> Address:  2001:470:20::2
>> 
>> Non-authoritative answer:
>> Name:    a1835.dspb.akamai.net
>> Addresses:  2001:450:2002:384::40d6:ce0a
>>          2001:450:2002:384::40d6:ce12
>> 
>> when it figures out where I am (i.e. geolocation is working).
>> 
>>    Brian
>> 
>> On 17/08/2012 18:16, Frank Bulk wrote:
>>> Just after midnight Central Akamai changed their AAAA records from 
>>> 	2001:418:2401:9::8367:8929
>>> 	2001:418:2401:9::8367:8940
>>> 	(NTT address space)
>>> to
>>> 	2600:1407:1:2::b833:9cb9
>>> 	2600:1407:1:2::b833:9ca9
>>> 	(Akamai's own ARIN-assigned address space)
>>> 
>>> Wonder if that's indicative of anything going on with their IPv6 rollout.
>>> 
>>> Frank
>>> 
>>> 
>> 
>> 
>> 
> 
>