Slashdot Mirror
Google Launches Public DNS Resolver
AdmiralXyz writes "Google has announced the launch of their free DNS resolution service, called Google Public DNS. According to their blog post, Google Public DNS uses continuous record prefetching to avoid cache misses — hopefully making the service faster — and implements a variety of techniques to block spoofing attempts. They also say that (unlike an increasing number of ISPs), Google Public DNS behaves exactly according to the DNS standard, and will not redirect you to advertising in the event of a failed lookup. Very cool, but of course there are questions about Google's true motivations behind knowing every site you visit."
Would be interesting to know how much Google paid for those two 256 ranges to Level 3. One would think simple ip's like 8.8.8.8 would cost some nice amount too.
Or maybe they should had used the coolest ip on the net, aka
> host 69.69.69.69
69.69.69.69.in-addr.arpa domain name pointer the-coolest-ip-on-the-net.com.
but they didn't want too much brilliance all in one place.
Their they're doing there hair.
fEEL FREE TO OPT OUT AT ANY TIME.
They have a great program for that!
If I had a nickel for every time I had a nickel, I'd be richcursive!
We put a cache in your cache so you can browse while you browse.
Their pipes, their rules. Feel free to buy service from another last mile provider.
Underwear and t-shirt? Why would I need underwear and a t-shirt?
Free Martian Whores!
This is a good think
It's also double plus ironic.
Of course you can still have cache misses.
You: Gimme goat.se
Google: That's not in my cache, hold on.
Google: Hey auth DNS gimme goat.se
Auth: K, here.
Google: Hey you, here.
You: K.
Your mom: Gimme goat.se:
Google: Yeah, I have that, here.
Your mom: K.
Your dad: I NEED the goat.se !
Google: Yeah I have that, but I need to recache it. Here's what I already have, it's probably still good.
Google: Hey auth DNS gimme goat.se
Auth: K, here.
Your dad: WTF? Where's the gaping anus?!
Google: Yeah, looks like the one I gave you before was wrong. No worries, this one is fresh.
Your dad: Sweet mother of corn holes.
Updating your cache early doesn't solve anything. You get less of a chance of misses only because you've checked more frequently. This comes at a performance cost on Google's end. Any DNS provider can cache anything for however long they want and return whatever result they think is valid.
The obvious thing to do is return your most recent authoritative result for cached domains or get one if it's not a cached domain. Choosing to empty out your cache after something has expired vs. refreshing it from auth is a performance decision. As is choosing whether or not to dump something when updating, or keep it around in case you get requests for it while you're updating. As is the overall frequency with which you update your cache.
No magic, brilliance, or good will on Google's part here - just horsepower and the willingness to operate at a financial loss in order to mine more data.