News for hackers. Stuff that matters.

A comment on 4.2.2.2: The Story Behind a DNS Legend. Parent comment

Re:4.2.2.2: The Story Behind a DNS Legend by nodesocket on Sunday September 22, 2013 @04:00PM (#6427776)
I am in DigitalOcean (San Francisco). The answer is simply distance/routing. I am guessing OpenDNS has an anycast node in DigialOcean (SF), where Google Public DNS does not. A ping tells the story.

ping 8.8.8.8 => 24ms

ping 208.67.222.222 => 1ms

[ Parent | on HN ]
Re:4.2.2.2: The Story Behind a DNS Legend by mburns on Sunday September 22, 2013 @05:03PM (#6428008)
A traceroute would tell the story better.
[ Parent | on HN ]
Re:4.2.2.2: The Story Behind a DNS Legend by dsl on Monday September 23, 2013 @02:27AM (#6429429)
From DigitalOcean in SF I'm hitting the OpenDNS Palo Alto datacenter. Google is going to San Jose.

Remember OpenDNS is a real business working to provide a service to real paying customers, Google DNS is just a fun little project of building an OpenDNS clone.

[ Parent | on HN ]
Re:4.2.2.2: The Story Behind a DNS Legend by adamseabrook on Monday September 23, 2013 @08:02AM (#6430235)
I believe all the DO droplets default to 8.8.8.8 so Google are probably applying some rate limiting across the DO network block during usage peaks.
[ Parent | on HN ]