Careful about using remote DNS caches. Sometimes remote content distribution services won't serve up content to users when there is a content device much closer. I commonly have this issue with large clients who are in multiple countries. Typically they use Microsoft's AD, and although a country has a local Internet gateway the name resolution is sometimes all done out of one country. The results being some of the countries can't get to the websites of some pretty major companies. I have a classic example that happens to me regularly. I have a client in the UK. If I VPN into their site, so I am using their DNS servers but my local Internet connection, I can't get to some sections of Microsoft's web site. -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Lincoln Reid Sent: Wednesday, 19 May 2010 2:28 p.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Akamai cache selection Hi all, Does anyone know if there is a method I can use to influence which Akamai cabinet serves up content to our networks? I have had a bit of a hunt on the Akamai site and I seem to be getting lost in sales pitches for hosting for my content. Currently there are at least five Akamai caches that are only one AS hop away from us but we consistently get directed to the most expensive one with the worst latency for us and our user base. I'd hope that there was something less ugly than putting in forwarders for "akamai.net" to dns servers that give an answer that I like. Cheers, -- Lincoln Reid Head of Networks ACSData - AS18119 lincoln(a)acsdata.co.nz Phone: +64 4 939 2200 Fax: +64 4 939 2201 _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog