Comment Re:Opposite Experience with Adobe Download (Score 1) 348
I have not read a more ignorant comment on how DNS works on slashdot in my entire history of reading slashdot.
Akamai is doing DNS geolocation. The solution is to use a combination of DNS geolocation combined with http redirects (also based on client IP geolocation) to attempt to find a good close server. If an end-user is using a remote DNS server. This can even be mostly invisible with a CDN like Akamai. DNS servers do not decide which 'Akamai' IP to give anyone. Akamai's forward resolving DNS servers return a response they have crafted as 'close' to the requesting DNS caching server (e.g. Google DNS, OpenDNS, your ISP, etc). The caching server caches the result and sends it to the DNS client on your local system. End of story. DNS does not forward or proxy the DNS client's address through the caching server to the forward resolving server. Ever.
For the record, using Akamai DNS *without* their CDN service (e.g. load balance/geolocate only) when redundant sites, AnyCast, and BGP should be standard operating procedure in enterprise network deployments is fucking stupid.