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."
> They also say that (unlike an increasing number of ISPs), Google Public DNS behaves exactly according to the DNS standard.
Congratulations, this would then be the first free service that I know of which doesn't do redirect ! ;-)
I setup my own DNS but I guess it is a little overkill for the common every day user. Setting your own DNS means you have to go to the network (e.g. internet) less often because your locally hosted DNS caches the already visited sites for a TTL period of time. This is especially true if you have several computers and that they tend to visit the same sites.
Let me add that if your ISP or firewall intercepts requests to port 53, you will still be stuck with it ;-(
Everything I write is lies, read between the lines.
But I thought open recursive DNS servers were bad -- haven't you heard of DNS DDoS amplification attacks? Why would Google's open recursive DNS service be any better in this regard?
Follow your Euro bills at EBT
They state very bluntly that IP addresses are expunged from the logs after 48 hours, and that no data is shared with Google Accounts or other Google services. They still get to play with a lot of aggregated data, but this seems like a fairly non-evil way to do it. Good for them. http://code.google.com/speed/public-dns/faq.html#privacy
But it sure seems like they're getting more and more of my personal information lately. What I search for, where I surf to, with my Droid where I navigate to, my e-mails, my documents. WOW.
But why would one change to use Google's DNS? If you're technical enough and care about such, you're way better off setting up your own recursive DNS server.
Google is just datamining from DNS requests here, it's another source of information. At least with your own ISP you can reasonably think that theres no datamining going on (excluding US ISP's, of course, who serve ads on non-existing domains for their users anyway)
I'd definitely consider switching to this. Better to have Google know all of the sites I visit than to be constantly redirected to Rogers advertising when I mistype a URL.
"To try it out:
Configure your network settings to use the IP addresses 8.8.8.8 and 8.8.4.4 as your DNS servers..."
Simple enough to remember which is great. Also - could this be used to circumvent some of the internet security at some workplaces where they seem to run a blacklist of specific sites?
But I doubt it'll be as memorable as 4.2.2.2 for those emergency DNS outages.
They were limited to knowing only about the sites you searched for, can't have that, bad for business. Now they can track all of the sites you visit. Since Google is our warm fuzzy giant corporation that we can trust, there is no problem.
8.8.8.8, 8.8.4.4.
The World Wide Web is dying. Soon, we shall have only the Internet.
Wow the people at OpenDNS are going to be pissed by this.
Still 8.8.8.8 is a bit more memorable than 208.67.222.222
Online & Feelin' Fine
# nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> slashdot.org
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: slashdot.org
Address: 216.34.181.45
Forget everyday use, but on public wifi, I'm all about this!
But it sure seems like they're getting more and more of my personal information lately. What I search for, where I surf to, with my Droid where I navigate to, my e-mails, my documents. WOW.
fEEL FREE TO OPT OUT AT ANY TIME.
...but of course there are questions about Google's true motivations behind knowing every site you visit.
No there aren't. You'd have to have been living under a rock for the past decade to have any questions about their motives. It's dead simple - they want to know what people are looking at so that they can better target people with advertising thereby increasing the value of their service. In return for offering various free services, all they ask for is some information on you so that they can better target advertising that interests _YOU_. It's not rocket science - it's just incredibly effective marketing.
but they didn't want too much brilliance all in one place.
Their they're doing there hair.
Look.. Google's in the advertising and data aggregation business, yes. But ... there is a level of suspicion and fear directed at Google that just seems extreme. Has Google actually done something "Evil" that I missed? Or it is just paranoia? I personally think that it's much more likely that OpenDNS or my ISP would do something crazy with this sort of information than Google.
"He who would learn astronomy, and other recondite arts, let him go elsewhere. " -- John Calvin, commenting on Genesis 1
OpenDNS is hurting them for some reason.
From que FAQ: "Google Public DNS never blocks, filters, or redirects users, unlike some open resolvers and ISPs"
Other than discovering new sites for their spiders to crawl and index, what's in it for Google??
I've abandoned my search for truth; now I'm just looking for some useful delusions.
They don't publish own IPv6 records via this resolver :-(
I get 48 to 88ms look-up times.
Excuse me, but please get off my Pennisetum Clandestinum, eh!
What would be the benefit of this as opposed to using the Level3 DNS servers?
The NTP pool (which probably needs even more NTP servers, btw) was recently changed so that the project's DNS servers return a list of nearest available NTP servers when queried. If you change your settings to use Google's DNS servers, the pool will now respond with a list of NTP servers close to Google's DNS servers, which may not be what you wanted.
Follow your Euro bills at EBT
The Google is not providing malware & phishing blocks and parental/SFW controls.
DynDNS's redirects are honest searches, not ad-choked.
https://www.dyndns.com/services/dynguide/
http://www.opendns.com/
Set up your own DNS server and point it at google's.
Then you can take advantage of your cache and their cache.
google could do us a great service by also making it available on some other port, that way we can get around the ISP interception of DNS requests.
So not only as memorizable, but explicitly public, whereas 4.2.2.2 and 4.2.2.1 are both technically being abused when you do that.
Don't thank God, thank a doctor!
RTT to my own resolver: microseconds
RTT to my ISP's resolver (Speakeasy = no redirect and such): ~21ms
RTT to Google's: 80+ms
No-brainer for me.
If you're on $garbage_DNS and you're served an advertisement/search page instead of NXDOMAIN, you (or your browser's auto-search) won't search Google. For that matter, just having something like this around will discourage $garbage_DNS.
Google cares about the Internet. It's where they make their money.
The World Wide Web is dying. Soon, we shall have only the Internet.
So...
Google voice first for voice. Last week Gizmo5 for voip and now rolling out their own DNS?
Looks like all the infrastructure pieces are in place for the mass change of how cell phones are going to work.
For years I've wondered why we still have phone numbers. With address books stored on the phones to map names (hosts) to phone numbers (ip's).
With all the phones these days having decent data connections as standard, looks like we're going to get a central way of handling this.
So my phone contact will be 'Fred@Domain.com' If I send an email with that address, it gets sent to their mail. If I make a call to that address, does the DNS lookup, finds out their phone number (that we can re-configure our end to handle calling home phone or cell phone, and with location based rules on an android phone, you'd be able to automate it as you left your house, it lets the phone DNS know to call the cell phone, then as you get to your desk location, remap to office phone for non-personal calls). All possible as standard.
We're not going to get phone and choose to have a dataplan, we're going to have phones + dataplans and that's it.
telcoms industry HAVE to know this surely?
(personal wish, as calls are made to someone, there's a quick lookup for capabilities of the device you're calling, then popup the choices to make normal call, send a text, allow the webcam to work, or most importantly, present a URL to an MP3 that's YOUR ringtone, so you can set up a theme tune and as you call people, they hear your tune (as long as they've not turned that off))
Waiting for an amusing sig.
everything resolves to Google's proxies.
Really?
You, sir, are a liar.
Cue *whoosh* in 3..2.. actually, I still don't get it. Either you're trolling because you hate Google, or there's some obscure joke that I still don't understand. I really don't get how your list of crap it requires (most of which doesn't exist or doesn't apply to DNS) is funny -- are Google known for requiring random stuff like that?
I mean, they don't even touch NX:
That's more than you can say for most ISP-level resolvers.
Don't thank God, thank a doctor!
If google really wants to speed up the browsing experience, they would work on speeding up the slow ad servers.....
...same as the old Borg?
I'll bet he's re-thinking the concept of writing an OS vs. doing a massive search engine. (Not calling it bing - maybe Life the Universe and Everything.)
The Kai's Semi-Updated Website Thingy
Well the ping times are still almost twice what they are for the old GTE/Verizon 4.2.2.1 4.2.2.2 and 4.2.2.3
Get a web developer
I don't suppose their DNS supports RFC 4398: Storing Certificates in the Domain Name System?
I'd would *really* like to see Little Billy's stranglehold on SSL broken....
Regards;
I wonder how they got that nice legacy IP
...and OpenNIC has no interest in maintaining records of your visits.
Google is beginning to get scary.
GOOGLE IS SKYNET!
Why me worry with OpenDNS or GoogleDNS or sumudduh DNS, when I can use TorDNS!
The tor network is far better than any public DNS.
I can think of one: it allows them to see which websites are popular?
Or another one: it allows them to match & check advertisement click throughs?
there's a huge source of information in DNS lookups. The CIA and NSA wants you to use *their* DNS server too.
Google + Apple + Linux - Microsoft - DRM == /. Nirvana. I haven't read up on /. in a few years, but coming back to it seems like catching up on an old soap opera I've missed for a few years. The story lines are much the same...
I seem to recall that there are a few ISPs that are threatening to block all requests to Google sites because of the bandwidth that is being used. I think it stands to reason that the reason Google is running an free DNS is so that people can still access their sites, no matter what their ISP does.
Microsoft, Apple, Google, Amazon what's the difference? All steal money from devs and control with walled gardens.
From TFA: "but of course there are questions about Google's true motivations behind knowing every site you visit."
If you can't answer these questions yourself, you're an idiot. Google is, first and foremost, an ad service seller who base their business on being the best at providing context specified, directed ads. They are, true, a search engine among many other useful end-user apps too.. but their business is ads. So in that context, it's pretty damned obvious why they'd like to know every site people visit (and not just every site they visit via searches). Duh?
Down with the career politician! SUPPORT TERM LIMITS
With IP like that who needs domain names ? :)
Based on stuff like this, Google seem to be looking for ways to exploit (marketing-wise) every step of the interaction between users and Google (or users and Google customers, i.e., advertisers). Their devious secret is that they actually bring improvements as part of the deal. "No more spam for you! We make the internet fun again!" and while everybody's rolling around in that, they are presenting this huge portfolio of collected user data to megacorps around the world. Or anybody who can afford to hire all that data. Which isn't exactly going to be the small bookstore down the street.
I wonder if they will see the kind of occasional attack I see. Our recursive name servers occasionally get very hard by a botnet looking up ridiculous numbers of mx records. I wonder if they will do anything to prevent it.
If you use this than Google has access to every single site or service you visit or use, even without the browser. For doing behavorial targetting of ads this is key. Most commercial behavior happens outside of the search engine and on a third party site. This gives them some of the ability to do what the folks at Nebuad wanted to achieve by doing deep packet inspection. If you use Google's DNS, they get to do tracking without having to get an ISP agreement and they'll say that your agreement to use implies consent to use the data "for their own use". SInce their use is to sell ads that can be finely targetted, they are in effect gainig the ability to offer an advertiser "for people who search for camera and have visited newegg or amazon..." or "for people who visit planned parenthood, put up this anti-abortion ad".
I will still use my free http://www.opendns.com/ servers. The only redirect you get is a search page with is this what you mean. Other than that it will still try and get you where you want to be while also blocking a variety of sites, by your own choosing.
Question: To use Google's DNS service, is it enough to change your DNS settings in your router? Doesn't each computer get the DNS settings from the router, if no specific DNS address has been configured?
Or, must you use specific DNS settings in each operating system?
In Windows XP, does the following configuration cause a computer to get the DNS address from the router to which the computer is connected? Start/ Settings/ Network Connections/ Choose the connection/ Internet Protocol (TCP/IP)/ Properties/ General/ Obtain DNS server address automatically/ ??
And they're going to own NBC.
I'm looking for it to go up in [internet] flames in about six months.
Channel 4 already looks like a rinky-dink cable station operation in the NYC market.
Marry this to ComCast (who'll probably try to block all other stations and multimedia sites with traffic shaping,) and we'll probably all sue the FCC to rescind the decision before the next World Series.
MSBPodcast.com The opinions expressed here are my own. If you don't like 'em... Think up your own stuff.
first thing that popped into my head was that chrome os could default to google's dns for lookups
this could be just another way to market chrome os netbooks as faster for web surfing
Very cool, but of course there are questions about Google's true motivations behind knowing every site you visit.
Nonsense.
They want to cut the ISPs and other DNS providers out of their (dishonest) ad revenue streams. For a lot of competitors, this is virtually the only straw left (AOL, anyone? I know at least in Germany if they hadn't forced the marketing of the "Alice" ISP to add such a DNS-misdirect, their portal and search space would be able to count its visits in "hits per hour").
It hurts their competitors while giving Google an image plus. And the amount of overhead and traffic is neglectable if you already operate on the scale that Google does.
Assorted stuff I do sometimes: Lemuria.org
I'm just not sure it's a very good one.
Platform advocacy is like choosing a favorite severely developmentally disabled child.
Countdown to Dan Kaminsky abusing it.... 5.... 4.... 3....
The wheel is turning, but the hamster is dead.
Hmmmm, does not seem to work at all:
~> host slashdot.org ;; connection timed out; no servers could be reached
slashdot.org has address 216.34.181.45
slashdot.org mail is handled by 10 mx.corp.sourceforge.com.
~> host slashdot.org 8.8.8.8
Overloaded already?
I think the absurd list of requirements (bzip3?) was supposed to tip you off that it was a joke post.
For once its a good thing that most folk don't know anything about DNS.
My first thought was: "I hope it's a nice, easy-to-remember address..."
8.8.8.8
ObCartman: Schweeet
No sig today...
I discovered this web page: How To Find Out What My DNS Servers Address Is.
For windows, it says to run
which outputs the DNS server addresses actually being used.
There are instructions for Linux, also.
Ekde vi ne havas la oftan entilecon al klarig vian mesaon skribitan en neklara mortinta lingvo, Mi estas respond al vi en alia mortinta lingvo.
The entire world now knows you don't bother reading articles before posting.
No sig today...
Technically, they only get to track the sites that you access by domain name. You can always punch an IP address in and circumvent the DNS system. Start memorizing those porn IPs now!
I love this, really. Now when doing DNS testing from any location I can always test using 8.8.8.8, that's a huge benefit to me.
However, They're telling end-users to "try" their DNS service and giving basic instructions.
Their geo-location is no-where near complete, for end-users in (for example) New Zealand who follow their instructions they'll have:
* Pro: A DNS Server that will most likely have nearly all results cached, quicker overall response.
* Pro: DNS Infrastructure redundency through Google.
But...
* Con: A DNS System with higher latency.
* Con: A DNS System where if using only those two servers (through Googles instructions) when International connectivity dies, so does all your DNS.
I've moved my home server over to 8.8.8.8, 8.8.4.4, ISPDNS1, ISPDNS2 to negate these issues and provide better DNS service than my ISP.
I honestly would have expected more from Google, at the very least a geo-location test to ensure they have DNS servers in your "region" before advising to "Try" their system.
If you have a typical (linksys) router and it grabs dhcp address, I don't know how you can have it registered and update them unless you do it through a workstation/computer. Kind of a flaw in OpenDNS's service I always thought.
I just tried it and it's *WAY* faster than my ISP - simple web pages now appear *instantly*.
No sig today...
They only know the addresses you resolve. Visitation is a completely different matter. I resolve things without visiting all the time. For instance, ping. or maybe someone visited me and I want to know who they were.
And if you're so concerned, I don't know why you don't set up a DNS pool and resolve though multiple servers, so none except your local (which may be on your own machine) will know the full picture.
Slashdot's rate-of-post filter: Preventing you from posting too many great ideas at once.
I just tried it and it's *WAY* faster than my ISP - web pages start loading a couple of seconds sooner than before.
No sig today...
Business logic.
Apart from data mining, Google sees the opportunity to decrease the ad revenue from any ISP that actually uses DNS redirects. They don't like competition in the advertisement market and they'll do anything to demotivate other companies to enter the market.
C.
I guess for me it's clear: I'll skip it for now.
Thanks again for your help.
Another question: In Windows XP, what does this setting mean:
"Register this connection's addresses in DNS"
I found that at Start/ Settings/ Network Connections/ Choose the connection/ Internet Protocol (TCP/IP)/ Properties/ General/ Advanced/ DNS/
In the same tab, what do these settings mean?
"Append primary and connection specific DNS suffixes"
"Append parent suffixes of the primary DNS suffix"
No, but we're smart enough to realize that no one is going to pay out of pocket to provide all the services that Google does for free with no revenue model at all, not even to pay for the infrastructure servers and network necessary to do it.
I'll make you a deal. Multi-billionaire technology philanthropist that you seem to be, you set up a company to compete with Google, one that provides all that they do and that has exactly zero sources of revenue, and I'll willingly become your fanboy.
The practical situation is that there ain't no such thing as a free lunch. When Google came along, we were headed towards every web site--especially search engines and directories--pushing out more and more pop-ups, pop-unders, interstitials, graphics-heavy, annoying ads, and they changed that. God forbid any of them actually contribute back to the community in the form of numerous open source projects and free services.
Google changed all that by providing a much more customer-friendly "less is more" philosophy, and their customers have supported their efforts in a very free market-friendly way. So while you can take potshots at targeted advertising if you want, I honestly can't think of a less obtrusive and relatively harmless revenue model that can support all that Google does and how much they are contributing to advancing technology.
While I'd love for someone to volunteer to do all that Google does without making money for it, given that that's not going to happen, yeah, targeted advertising is about the least annoying way I can think of to get the bills paid and continue providing service.
I seriously doubt this has anything to do with Google wanting to save the Internet. It is about them seeing what web sites users are going to by mining dns queries. There is a huge amount of marketing data to be had. If they wanted to save the Internet, they would put up some sort of DNS filtering that would knock out all of the Nigerian Princes and Fake-Alert Antivirus programs.
Wow, the quadruple good luck Google DNS server!
For those too lazy to run whois:
...
...
spliffy@localhost:~$ whois gtei.net
Registrant:
Verizon Trademark Services LLC
Verizon Trademark Services LLC
1320 North Court House Road
Arlington VA 22201
US
domainlegalcontact@verizon.com +1.7033513164 Fax: +1.7033513669
I've never personally heard of Google doing anything with people's data that I'd mind terribly.
Most notably I use their email service, I'll use my Wave account if and when it becomes particularly useful, and I just might use their DNS server because I am pretty tired of my ISP's slow responses. So if they decided to at some point they could do some serious damage to my privacy.
But up to this point they've only provided services that I find useful and generally superior to other free alternatives and have only asked for statistics and a reasonable amount of screen real estate for ads. I'm definitely not one to trust a company with too much information, but so far that's perfectly acceptable to me.
If someone can give me a good, currently applicable, practical reason to, though, I'll avoid their DNS like the plague.
I'm a worried surprised that you think bzip3 is less likely than "rot13 transcryption"...qb lbh abeznyyl ernq guvatf yvxr guvf?
Ng yrnfg EBG13 rkvfgf!
C:\Users\*****>ping -a 8.8.8.8
Pinging google-public-dns-a.google.com [8.8.8.8] with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=82ms TTL=244
Reply from 8.8.8.8: bytes=32 time=79ms TTL=244
Reply from 8.8.8.8: bytes=32 time=80ms TTL=244
Reply from 8.8.8.8: bytes=32 time=81ms TTL=244
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 82ms, Average = 80ms
C:\Users\*****>ping -a 208.67.222.222
Pinging resolver1.opendns.com [208.67.222.222] with 32 bytes of data:
Reply from 208.67.222.222: bytes=32 time=51ms TTL=53
Reply from 208.67.222.222: bytes=32 time=48ms TTL=53
Reply from 208.67.222.222: bytes=32 time=49ms TTL=53
Reply from 208.67.222.222: bytes=32 time=61ms TTL=53
Ping statistics for 208.67.222.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 61ms, Average = 52ms
Get your free Dropbox account with 2 GB Free storage!
Google is datamining everywhere and everything already.
When I first read about this, I immediately thought about datamining. But after another second, I figured that I would prefer Google to have this information than Verizon (where my caching DNS server currently forwards to). It is true that Google is better at datamining, but do keep in mind that whoever is providing your DNS service has the information about your DNS requests.
Another difference between Google and your ISP is that your ISP knows who you are from your IP address. So they can link DNS resolution requests to specific, named, customers. Google can't do that directly.
Prime numbers are exactly what Alan Greenspan says they are -S. Minsky
You're right, it is bzip2 not 3 in tar...I guess that's minus geek points for me...
Maybe. I still don't get why it's funny...
I guess the biggest reason I replied is, there are entirely too many people who would read that and believe it, without understanding what it all means. Routing everything through Google's proxies isn't that far-fetched.
Don't thank God, thank a doctor!
Videotron ( in Canada, Quebec) was so slow - this is MUCH faster.
Since they'll now know what I search for *and* all the sites I visit do you think the Google Blackmail application will infringe on Amazon's 1-click patent?
$ host aoeusnth.com
You must use Dvorak ^_^
Last I checked, it worked.
How long does it take to 'turn off public access', if it's been going on for a while?
Is it a threat? A rumour?
Skynet saw what happened to it in the movies so changed its name to Google to fly under the radar. Be afraid be very afraid
Yup, YouTube magically started working for me when I switched my nameserver to not use my ISP as a forwarder. And that is with a business account. Unfortunately, I'm in NYC which according to slashdot-group-think is simply not built densely enough to allow for competition like they have in the places where sheep outnumber people.
I don't see what's so bad in having Google know what you have visited today, as they probably already have your (almost) complete list of contacts, emails and online documents. and how is that better than letting your average wet-pants ISP know it instead or, in 90% of the cases, Microsoft know it as well...?
For me.
- ISP's DNS server - 23 ms
- OpenDNS - 264 ms
- Google DNS - 367 ms
I have read the expression "rocket science" at least 4 or 5 times during this discussion, and no, nothing that has been discussed here is rocket science. Rockets are not hard anymore! Even my 5 year old kid was able to build one and he launched it on the beach this summer. So just stop it please.
So I'll be reconfiguring the home router tonight. It's that simple. Ad services on the search pages aren't just annoying - they're a security risk.
Help stamp out iliturcy.
I don't know everything. I thought the DNS address came from the router and not the ISP, but I wasn't sure. I thought possibly an ISP would have some way of forcing control. Apparently that is not common.
Most people don't know it but: - Rogers does deep packet inspection and throttling - they transparently proxy all html and can insert an advertisement in any page they wish (when you're near the banwidth limit you'll get notices embedded in your completely unrelated websites they you're at 75% or 90% of the limit). - they hijack dns and put up those horrific search engine + ads pages Thumbs up to google. But, I will curse rogers even more when they find out and start redirecting dns requests back to their own servers. Evil, evil companies.
Selah.ca. Pause, and calmly think on that.
I used to use you but how can I resist
http://code.google.com/speed/public-dns/docs/using.html
http://askaralikhan.blogspot.com/
David Ulevitch, Founder of OpenDNS blogs on the issue.
Candle burns its brightest in the dark
I have to say: Thanks, but NO thanks.
Monoculture is bad. Google is trying to bypass/replace internet and open source. Free/open source coders should be start using Affero GPLv3 license in every piece of software (starting by gcc, and the linux kernel) to stop this madness.
What's in a sig?
Some communities have their own DNS. Indeed, emails can nicely be done only with DNS MX records. Hope google will stick to the current DNS protocol. If they want to extend the protocol... it has to be extremely simple to implement and go throught classic normalization processes.
Very cool, but of course there are questions about Google's true motivations behind knowing every site you visit."
Almost everyone at work practically uses Google to find their site anyhow. Instead of typing the URL into the address bar, they Google site they are going to and click on the link. It's like DNS anyhow for them and Google knows where they are going already!
Google's main reason for DNS service is to provide a fast responding DNS. Google has been focusing on fast searches and fast responding web pages (they found that users can in fact tell and care about 0.3 vs. 0.7 second response for web page load). Most ISP's DNS servers are horrible in terms of performance. From personal experience, when I moved a couple of years ago I experienced first had the difference. Initially upon moving I did not have time to connect my entire home network which includes own internal DNS servers - I simply pointed the computers at the recommended Verizon DNS. The web searching experience was horrible compared to what I was used to (other members of the family also noticed), especially considering that the new connection was a 25Mbps/15Mbps fiber to the home FIOS solution. After powering up local DNS servers, web surfing was fast again. So why does google care about speeding up your connection (and with their resources, geographic load distribution and such they really can)? Well, they want everything on the web, they want everything to live in the cloud, hence Chromium OS! They want web apps and surfing to appear as applications do in desktop OS's today. Data mining from DNS queries will happen, statistics will be collected before the IP log disappears after 24hrs, but that's only a secondary benefit to google.
I'm surprised Alexa didn't do it earlier.
-- I was raised on the command line, bitch
Thanks.
I also found this: How to configure TCP/IP to use DNS in Windows XP.
I'd suggest you pick the best DNS from http://www.manu-j.com/blog/opendns-alternative-google-dns-rocks/403/ or http://www.dnsserverlist.org/indexbeta.php?oby=Q_RTT depending on the Country you're residing.
I'd like to buy homeland for our 10 million people. http://twitter.com/mahadiga