How Akamai points you to a node might as well be black magic, It's not entirely based on the IP prefix's as by simply changing our DNS servers to point Akamai zones to other DNS servers in NZ we can adjust where our Akamai traffic is coming from. Not announcing your range is only an option where the network hosting the node you want to avoid ISN'T your upstream provider's transit carrier, I'm looking at you Kordia. -- Tristram Cheer Network Architect Tel. 09 438 5472 Ext 803 | Mobile. 022 412 1985 Fax. | tristram.cheer(a)ubergroup.co.nz | www.ubergroup.co.nz PS: Follow us on facebook: www.ubergroup.co.nz/fb or twitter https://twitter.com/#!/ubergroupltd -----Original Message----- From: Nathan Ward [mailto:nznog(a)daork.net] Sent: Tuesday, 28 February 2012 12:05 p.m. To: Tristram Cheer Cc: Tim Price; Barry Murphy; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Async Routing across ape to pipe return via vocus &Internode speedtest In order for a node to be available in the Akamai systems for your prefixes (or rather the prefixes where your DNS servers live), the provider hosting the cluster needs to advertise your prefix over a BGP session to Akamai (it's multi hop over the Internet, and not used for IP routing, just as a good way to dynamically inform Akamai of what prefixes you want them to server through your cluster). If you don't want your prefixes being seen by that cluster, ask whoever hosts the cluster to not advertise them to Akamai. If it's a common request, maybe they have a community you can use, or maybe they can create one? Google GGC is similar, except it's based on client IP addresses not DNS servers, and the eBGP session goes to their local server and not over the internet. The same challenges no doubt impact you though. I'd suggest avoiding ASPATH poisoning, because in some cases your preferred CDNs aren't going to have the content you want, and your customers will go to the CDN's global servers instead of the next best. On 28/02/2012, at 10:09 AM, Tristram Cheer wrote:
Hey All,
We had the same issue last year, Akamai decided to point us at Vocus's node and Akamai traffic coming from AKL server's under Vocus's control were returning our data over our International. We of course were very unhappy about this but we got nowhere with Vocus or Akamai about it (Basically told to sod off), The only way we found to fix it was to point the DNS zones for akamaitech.net and akamai.net to another DNS server in NZ that stayed pointed to CallPlus's Akamai node.
Very frustrating given and difficult to resolve, The offending parties always seem to be of zero help in these sorts of cases.
Cheers
--
Tristram Cheer Network Architect
Tel. 09 438 5472 Ext 803 | Mobile. 022 412 1985 Fax. | tristram.cheer(a)ubergroup.co.nz | www.ubergroup.co.nz
PS: Follow us on facebook: www.ubergroup.co.nz/fb or twitter https://twitter.com/#!/ubergroupltd -----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Tim Price Sent: Tuesday, 28 February 2012 9:59 a.m. To: 'Barry Murphy'; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] Async Routing across ape to pipe return via vocus &Internode speedtest
I've seen something similar to this whereby traffic to Vocus egresses APE and ingresses International via Kordia. I was told by various parties that it is because Vocus sets a higher local preference on it's 'customer' routes (Kordia being a customer of Vocus) than on the peering exchanges. The only way that we could force the routes to be synchronous again was to drop all Vocus routes received across APE which would seem counter productive.
-----Original Message----- From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Barry Murphy Sent: Tuesday, 28 February 2012 9:53 a.m. To: nznog(a)list.waikato.ac.nz Subject: [nznog] Async Routing across ape to pipe return via vocus & Internode speedtest
Hey Guys,
I just saw Glen Eustace's post which reminded me of an issue we have seen of late with regards to 'my internet seems slow'. Just wondering if anyone else has seen this similar issue since PIPE joined the APE, then again it's not just PIPE, but a mixture of Oz providers accepting traffic over the APE and then returning the transit via international links such as Vocus.
I have a few customers that buy dedicated international and dedicated domestic bandwidth. These customers have a stub address that resides in the Domestic VRF & another stub in the International VRF. Since PIPE came on-board we have noticed that customers trying to do a whois (whois.apnic.net) using their router that connects the stubs, that the traffic goes out thinking its Domestic, but then gets no response because it attempts to return in via the International (Transit) VRF to which has no access to stubs in the Domestic VRF.
Another issue we see where 'slow' comes into play is internode have recently been added to speedtest.net as a NZ speedtest server in Auckland. While tracing to this node it does appear to go across APE, the return path is via Vocus. When a customer attempts a speed test and they see they are only able to obtain say 30mbps rather than the 100mbps they would expect from a "NZ" server they start thinking something is broken, when actually it's because the server is International and they are in a pool of bandwidth.
I've tried to contact internode & so has a colleague of mine but with no luck. We've tried to pre-pend AS's to the vocus communities but again this hasnt helped at all.
Just wondering if anyone else has seen issues arise since ASYNC routing between Oz & NZ, to do with either STUBs getting no internet due to VRF nature, or these 'slow' speeds being reported.
thanks Barry
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog
_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog