In a CDN'd world, OpenDNS is the enemy

Re:In a CDN'd world, OpenDNS is the enemy by gdamjan on Monday July 23, 2012 @08:01AM (#4280516)

CDNs could solve this by using BGP anycast routing.

[ Parent | on HN ]

Re:In a CDN'd world, OpenDNS is the enemy by jemfinch on Monday July 23, 2012 @10:47AM (#4281219)

CDNs are typically used for transferring large objects, for whom the anycast routing instability is a real concern. If a client's anycast endpoint changes in the middle of a connect, the client will receive an immediate RST from the new server.

[ Parent | on HN ]

Re:In a CDN'd world, OpenDNS is the enemy by astrodust on Monday July 23, 2012 @10:45AM (#4281214)

Does this work with TCP? The only implementations I've seen are for UDP which is stateless and unaffected by route flap.

[ Parent | on HN ]

Re:In a CDN'd world, OpenDNS is the enemy by le on Tuesday July 24, 2012 @11:27PM (#4289221)

Major CDNs do use anycast routing, in conjunction with DNS/geolocation based routing in locations where anycast's results would be unpredictable (usually in locations where there are many POPs.)

[ Parent | on HN ]

Re:In a CDN'd world, OpenDNS is the enemy by amalcon on Monday July 23, 2012 @10:46AM (#4281218)

In theory yes, but BGP anycast routing is really bad in performance terms. BGP doesn't care about performance, only politics and cost, so you can get all sorts of weirdness.

[ Parent | on HN ]