Hello CDN, bye bye OpenDNS
There was a time when using OpenDNS was of amazing help, a time when CDNs and geoIP were just emerging. Now those technologies are mandatory for our social media lifes. So some weeks ago I have experienced issues accessing many sites that used Akamai CDN: facebook.com, apple.com to highlight some. Then, after googling for a while, found some interesting articles:
In short, I'm back to local DNS and trusting my ISP DNS. Just noticed that I were using many wifi networks: at the coffee, at work, at home, at the airport, etc. And never minded that I were not using OpenDNS, actually I was complaining about websites not using a CDN, even when Cloudflare is a free CDN that just works (unless you live in China).
So, that is it. Thanks OpenDNS for the last amazing 6 years, you saved me lots of time!
Blessings!

develCuy's blog por Fernando Paredes Garcia se encuentra bajo una Licencia Creative Commons Atribución-NoComercial-CompartirIgual 2.5 Perú.





Did you read "Akamai vs
Did you read "Akamai vs public DNS servers"?
http://00f.net/2012/02/22/akamai-vs-public-dns-servers/
Some of this info is out of
Some of this info is out of date. Akamai is using legacy techniques -- it never made sense to just use the location of the customer resolver to direct traffic. That was never an acceptable proxy for customer location.
We've been combatting this with http://www.afasterinternet.com/ which Google and many CDNs are now actively supporting, but Akamai still has not.
I think your pressure should be directed at Akamai and Akamai customers, rather than innovative DNS services (not simply including my own). We're pushing the technology stack ahead, rather than accepting things as they are. Things like edns-client-subnet (in link) push the state of the art forward considerably.
Enviar un comentario nuevo