It's an interesting idea, but based on some early tests it looks like a losing b... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		cscotta on Dec 3, 2009 \| parent \| context \| favorite \| on: Google Public DNS It's an interesting idea, but based on some early tests it looks like a losing bet to me. My ping from a dedicated 15mb Qwest circuit to 8.8.8.8 and 8.8.4.4 is between 57ms and 75ms. However, cached DNS resolutions run at around 12ms from our default DNS servers. Even uncached resolutions are still way faster than the round-trip to Google. Google Public DNS might be worth it if every single one of your DNS queries would result in a cache miss, but otherwise I don't see the performance improvement Google is gunning for. That said, it is nice to have a public option.

windsurfer on Dec 3, 2009 | [–]

That's funny. I'm with Rogers in Canada, and their DNS requests can take 2000 ms on a normal day.

sp332 on Dec 3, 2009 | | [–]

That's not funny.

mrtron on Dec 3, 2009 | | | [–]

Also on Rogers - and get a noticeable improvement.

jokergd on Dec 4, 2009 | [–]

funny enough, I get an average of 8ms ping from 8.8.8.8 (9 hops) from my co-lo server

quite happy with that

Consider applying for YC's Summer 2026 batch! Applications are open till May 4
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact