News for hackers. Stuff that matters.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by davidu on Thursday December 03, 2009 @12:19PM (#974683)
I'll do a blog post about this later today for those interested in my perspective on them entering the DNS space.

:-)

Edit: Here it is: http://blog.opendns.com/2009/12/03/opendns-google-dns/

Re:Introducing Google Public DNS: A new DNS resolver from Go... by dannyr on Thursday December 03, 2009 @03:59PM (#975224)
From the blog post: "Third, Google claims that this service is better because it has no ads or redirection. But you have to remember they are also the largest advertising and redirection company on the Internet. To think that Google’s DNS service is for the benefit of the Internet would be naive. They know there is value in controlling more of your Internet experience and I would expect them to explore that fully. And of course, we always have protected user privacy and have never sold our DNS data. Here’s a link to our privacy policy."

davidu,

You have excellent points but you could have made them without bashing your competitor.

This response makes me think that you are afraid of your competition and using fear to convince people to use OpenDNS.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jamesbritt on Thursday December 03, 2009 @04:23PM (#975253)
" ... and using fear to convince people to use OpenDNS."

Is the fear justified? Is it plausible enough that people should take it into account when picking a DNS service?

Google's self-interest is a legitimate factor to consider.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by hop on Thursday December 03, 2009 @02:34PM (#975028)
it’s not the same as OpenDNS. When you use Google DNS, you are getting the experience they prescribe. When you use OpenDNS, you get the Dashboard controls to manage your experience the way you want for you, your family or your organization.

Not mentioned was OpenDNS sends failed requests be default to a search page full of ads... Google appears to not be monetizing this.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by myared on Thursday December 03, 2009 @02:59PM (#975100)
Not monetizing this? Where do you think their motivation is coming from (to make the world a better place?)

Google Analytics falls into the same category. You're not paying currency to use the service; you're paying with your metrics. When you think about it in terms of scale, this is way worse. Google is great at taking this data and using it to generate revenue in a number of other ways. Any smart advertiser who uses Google Adwords to buy traffic knows to stay away from Google Analytics. Why would you let the company you're buying traffic from know how that traffic behaves?

The DNS project takes this a step further by giving Google a world of new data. Now you don't have to use Google or be on a site with Google Analytics for Google to know where you're going.

Seems harmless, but I bet they can't wait for this to be adopted by the masses.

With all that being said, 8.8.8.8 is a damn cool IP address and I'm sure my Google-powered Droid already uses it. /rant

Re:Introducing Google Public DNS: A new DNS resolver from Go... by rpdillon on Thursday December 03, 2009 @03:27PM (#975160)
I love how everyone comes down on Google for collecting data about net traffic, as though no other company on the internet ever thought of collecting traffic metrics. What is your current DNS provider's policy on DNS data collection? In the case of OpenDNS, sure, they have a privacy policy, but they also proxy Google's results and serve up ads. How's that so much better?

I'm perfectly happy to have my DNS data be collected (which I assume my ISP is already collecting) in exchange for ad-free, fast name resolution. Plus, now I don't ever need to look up a DNS server again, Google's is 8.8.8.8. Sweet.

EDIT: looks like Google's not collecting so much information anyway. http://code.google.com/speed/public-dns/privacy.html

Re:Introducing Google Public DNS: A new DNS resolver from Go... by skolor on Friday December 04, 2009 @09:03AM (#976332)
Looking at that privacy policy, and it looks like exactly what they should be doing. There isn't much of a point in keeping personally identifiable information beyond a certain point, at least not something which directly leads back to you.

The only data analysis that would benefit from keeping identifying information would be to create a model for how users go about the internet, and google already has some very good models of that. This is just conjecture, but I would assume that being able to create geographic based models is far more useful than per-user models, which is something they keep.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @03:52PM (#975211)
> Plus, now I don't ever need to look up a DNS server again, Google's is 8.8.8.8. Sweet.

My DNS servers have been 4.2.2.[1-4] for a long time. They aren't that hard to remember.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by akamaka on Thursday December 03, 2009 @04:15PM (#975243)
I tried using those servers, and they didn't work. If I do an nslookup or dig through them, it's fine, but when I use them as the default nameservers in my network configuration, they seem to reject my requests.

Anyone know why?

Re:Introducing Google Public DNS: A new DNS resolver from Go... by thaumaturgy on Thursday December 03, 2009 @07:31PM (#975523)
Try `nslookup -vc [hostname]` after setting your name servers to the Level3 IP.

Just a wild guess. I can't remember off the top of my head if nslookup or dig, when specifying an alternate server, use TCP or UDP. But, if it uses TCP for those, then it's possible that your ISP is blocking UDP DNS traffic that's not destined for their DNS servers. It wouldn't be the first time.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by akamaka on Friday December 04, 2009 @03:50PM (#977173)
Weird. It works now, unlike the last time I checked. Something must have changed, but I don't know what.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @04:30PM (#975270)
Don't know. I usually set them as the default DNS servers for my router to hand out through DHCP.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by Kadrith on Thursday December 03, 2009 @04:59PM (#975329)
> Not monetizing this? Where do you think their motivation is coming from (to make the world a better place?)

One thing I like about Google is that they research and share infrastructure technologies. Why is there any reason to think that they would not be interested in improving DNS if it makes the Internet a better place for applications?

They would likely benefit if more applications are moved to the Internet but that does not make this an "evil" or deceptive tactic. What other company today would improve an Internet protocol or create a new protocol (Wave) and release it openly in an effort to move the Internet forward?

Sure you need to be mindful of how data is used and the services you sign up for but that applies to any service, including OpenDNS.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jimmybot on Thursday December 03, 2009 @11:15PM (#975792)
I'm sure they will try to do something with the data, but Google's problem these days is that it's been so successful and gotten so big that it's incentivized to basically make the Internet bigger, better, faster in order to continue to grow. Chrome (and Firefox with the Chrome whip behind it) is another example of this.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by bcl on Thursday December 03, 2009 @01:14PM (#974855)
Note that they don't seem to be proxying opendns's domain...
Re:Introducing Google Public DNS: A new DNS resolver from Go... by blasdel on Thursday December 03, 2009 @02:20PM (#974995)
For those who don't know about the referenced shenanigans, OpenDNS proxies google search traffic onto its own servers.

OpenDNS: It's neither 'open' nor DNS!

Re:Introducing Google Public DNS: A new DNS resolver from Go... by gojomo on Thursday December 03, 2009 @06:43PM (#975479)
I knew OpenDNS redirected host-not-found traffic to their results page, but hadn't heard of them "prox[ying] google search traffic onto its own servers". Do you have more details?
Re:Introducing Google Public DNS: A new DNS resolver from Go... by bcl on Thursday December 03, 2009 @07:49PM (#975545)
Here is what google is serving up:

    [bcl@lister tmp]$ dig www.google.com
    ; <<>> DiG 9.6.1-P2-RedHat-9.6.1-7.P2.fc11 <<>> www.google.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33790
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;www.google.com.			IN	A

    ;; ANSWER SECTION:
    www.google.com.		603958	IN	CNAME	www.l.google.com.
    www.l.google.com.	300	IN	A	74.125.53.106
    www.l.google.com.	300	IN	A	74.125.53.103
    www.l.google.com.	300	IN	A	74.125.53.147
    www.l.google.com.	300	IN	A	74.125.53.105
    www.l.google.com.	300	IN	A	74.125.53.99
    www.l.google.com.	300	IN	A	74.125.53.104

    ;; Query time: 52 msec
    ;; SERVER: 192.168.101.20#53(192.168.101.20)
    ;; WHEN: Thu Dec  3 16:44:24 2009
    ;; MSG SIZE  rcvd: 148
Here is what opendns serves up:

    [bcl@lister tmp]$ dig www.google.com @208.67.222.222

    ; <<>> DiG 9.6.1-P2-RedHat-9.6.1-7.P2.fc11 <<>> www.google.com @208.67.222.222
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54658
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;www.google.com.			IN	A

    ;; ANSWER SECTION:
    www.google.com.		30	IN	CNAME	google.navigation.opendns.com.
    google.navigation.opendns.com. 30 IN	A	208.67.216.230
    google.navigation.opendns.com. 30 IN	A	208.67.216.231

    ;; Query time: 26 msec
    ;; SERVER: 208.67.222.222#53(208.67.222.222)
    ;; WHEN: Thu Dec  3 16:47:25 2009
    ;; MSG SIZE  rcvd: 104

All your queries are belong to us.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by gojomo on Friday December 04, 2009 @04:38AM (#976065)
Wow. I had no idea; that goes way beyond what I expected based on OpenDNS's promotion of their free servers. No more OpenDNS for me.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by poutine on Friday December 04, 2009 @06:19AM (#976158)
Re:Introducing Google Public DNS: A new DNS resolver from Go... by rpdillon on Friday December 04, 2009 @01:51PM (#976941)
I think I commented on that post when it was first posted in 2007, but here it is again: sure, I don't like what Dell/Google did on the new Dell machines. Meh. But that post is filled with so many absurd inaccuracies that I have to simply disregard it. Most prominently:

At the top of the page, he shows the exact text that appears on the "horrible" search results page. That text explains exactly how to remove that functionality:

"This program can be uninstalled from the Control Panel "Add/Remove Programs" in Windows XP or "Control Panel > Program > Programs and Features" in Windows Vista. Look for the application named "Browser Address Error Redirector". Older versions may be called "GoogleAFE" or "URL Assistant"."

He says this statement is "ambiguous". I have no idea how it is ambiguous, but ok. He then goes on to say the software is "hard to remove", and later that "users can't get rid of it!", both of which are outright lies. Installing and uninstalling software is a normal part of owning a computer, and as you can see above, Google's message tells users exactly what to uninstall. The entire process could be completed in 30 seconds.

But I have to ask myself every time I read this article: why is this guy going to so much effort to spread inaccuracies that demonize Google for trapping search results and presenting ads?

Well, because that is exactly how OpenDNS makes money, and Google threatened their business model. The entire first portion of the post, attacks and all, is present to justify this:

"we’ve stretched a bit beyond DNS itself to work around Google’s mis-directed efforts."

By going on the offensive, he now tries to justify providing a DNS service that OpeDNS doesn't just resolve hostnames anymore...instead, OpenDNS makes moral judgments about the domains you visit, and, as they trumpet so loudly, "we have a fix which does not require more client software". What this means to me is that whatever OpenDNS is doing, I can't uninstall it, because they own it -- it's not on my machine, it's on theirs.

Listen, when I use DNS, there's a contract I expect DNS to fulfill: I give you a name, and you resolve it to an IP or tell me it can't be resolved. It is an outright violation of the contract to resolve a hostname I give you to an address other than that with which it is associated, which is exactly what OpenDNS is doing.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by gojomo on Saturday December 05, 2009 @05:53PM (#978776)
Very helpful to understand their motivation, thanks. Unfortunately their rationale still amounts to: others are doing something sleazy, so we have to do something sleazy, too, to defend ourselves.

I don't own a Dell or run with any toolbars. I would find the "Browser Address Error Redirector" and remove it if I faced that warped experience.

So for me, this unrequested proxying isn't help, it's collateral damage from two competing typosquatters/querysquatters each trying to one-up the other.

A harder, but classier, way for OpenDNS to escalate their battle with Google would have been to offer a different set of DNS server IP addresses for customers who may want OpenDNS to trump Google/Dell.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by mahmud on Thursday December 03, 2009 @01:06PM (#974840)
No need David, we're keeping the faith in this shop.

ns[1-4].everydns.net, the first thing I do to a domain name that comes under my control.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by colbyolson on Thursday December 03, 2009 @02:19PM (#974994)
Who owns/is EveryDNS? They have a node in SanJose,CA (where I live) and I've never heard of them.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by jf on Thursday December 03, 2009 @05:00PM (#975332)
"I'm David Ulevitch. I have a website at http://david.ulevitch.com/ I am the founder and CTO of OpenDNS. I also started and run EveryDNS.Net. You should be using both of them."

via: http://news.ycombinator.com/user?id=davidu

Re:Introducing Google Public DNS: A new DNS resolver from Go... by aaronblohowiak on Thursday December 03, 2009 @03:20PM (#975140)
I'm not entirely sure, but I used to go to high school with a kid (a different Dave) that was absolutely brilliant and did some work with them. When I was looking for a dns provider, he showed me their site and I've referred them to everyone I know since. They really run an excellent service at top-notch quality. Probably time for me to donate again..
Re:Introducing Google Public DNS: A new DNS resolver from Go... by jeff18 on Thursday December 03, 2009 @02:07PM (#974958)
My comment on your blog is being moderated, but here's what I said:

I think it’s a little naive to think it is a good thing for you. How are you going to compete with Google’s infrastructure and get your response times down to Google DNS’? I would expect many people will switch away as I just have until you can roll out an extremely expensive upgrade.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by davidu on Thursday December 03, 2009 @02:10PM (#974967)
Their datacenter deployment is actually focused on large scale computing datacenters, not tons of footprint. It's widely deployed, and better in Asia than us, but that's not for long.

Update: I approved your comment.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by jeff18 on Thursday December 03, 2009 @02:17PM (#974987)
Really? I could have sworn that Google was all about local content distribution, to the point of creating new fundamental internet infrastructure to reduce latency.

Learn something new every day.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by socratees on Thursday December 03, 2009 @06:19PM (#975456)
Your post seems like anti-Google to me. Aren't people free to choose the service they like? The one with the best service should be the market leader. On what basis will you separate the ownership of internet apps? Saying Google has the whole internet stack, so its evil is naive. :)
Re:Introducing Google Public DNS: A new DNS resolver from Go... by marltod on Thursday December 03, 2009 @02:15PM (#974981)
Your fifth point is the most important one for me. Once they know your DNS data they can make make very educated guesses about the rest of your internet traffic. Google knows what is hosted at the servers you are looking up.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @03:55PM (#975215)
> Google knows what is hosted at the servers you are looking up.

And so does every other DNS provider so long as the pages are public and if your ISP is your DNS provider then they can directly sniff your (non-encrypted) traffic too.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by thaumaturgy on Thursday December 03, 2009 @07:38PM (#975534)
Well, your ISP potentially has access to your DNS lookups regardless of whether you're using Google's DNS servers or theirs or someone else's. That is, assuming the ISP owns the fiber that you're connected through. Small ISPs don't.

But now you're adding yet another party in the mix -- Google, who already have a lot of information about your interests and habits. At the very very least, you're inviting an interested third party to have a look at your traffic.

Most of davidu's response was kind of a waste of time, but the one thing that made an impression on me was when he referred to Google as an advertising company. He's right; they're the most technologically advanced advertising company in the world.

So if this conversation was about "an unnamed technologically savvy advertising company", instead of Google, would you still be interested in giving them your DNS traffic?

Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @08:11PM (#975581)
> So if this conversation was about "an unnamed technologically savvy advertising company", instead of Google, would you still be interested in giving them your DNS traffic?

So... you're saying that reputation counts for nothing? Google sort of evolved into an advertising company because of the position that they held as the most popular search engine.

Most advertising companies are companies that started out trying to be an advertising company. Most of them probably had to be cut-throat to make it out of obscurity.

This isn't to say that anyone should place blind trust in Google, but if -- as you're implying -- reputation counts for nothing, then what's the point in trying to maintain a reputation at all?

See my other reply in this thread too. You completely misinterpreted my post (or just used it as a soapbox to insert your views into the discussion). The post I was replying too said nothing about Google pulling all the information on you together. The poster seemed to be irked that your DNS provider also had access to the content of the pages you were using DNS lookups to view. I was pointing out that this is true of any DNS provider.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by thaumaturgy on Thursday December 03, 2009 @08:22PM (#975601)
That's one of the things I'm saying, yes.

Google does not have a spotless track record in customer privacy issues, nor is there any reason to believe that because they're behaving in a particular way now, they'll behave the same later.

It's as simple as this: while I'm a fan of most of Google's products and services, I also think there's a point at which it's no longer smart to put all of your eggs into one internet company's basket, and I think we've reached that point.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @09:49PM (#975697)
> Google does not have a spotless track record in customer privacy issues, nor is there any reason to believe that because they're behaving in a particular way now, they'll behave the same later.

True, but most of the records are deleted after 48 hours, meaning that they no longer exist for Google to decide to mine years later once they change their policy. Other than that, this only becomes an issue if the entire internet starts pointing their DNS queries at GoogleDNS, which I doubt will happen.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by ericd on Thursday December 03, 2009 @04:25PM (#975258)
I don't think any existing DNS providers have other sources of data like Google does. It's when it all comes together (search+analytics+adsense+Google Account reporting your trail, indexed website content and your email for profiling you) to make a dataset with potentially unprecedented cleanliness/completeness that it becomes interesting/scary. They can likely draw much stronger conclusions than most.

Not sure if their privacy policy lets them exercise their power fully in this field, though.

Re:Introducing Google Public DNS: A new DNS resolver from Go... by pyre on Thursday December 03, 2009 @04:34PM (#975277)
I was specifically addressing his post, not every possibility. He was claiming this was bad because Google has access to the content at each of the servers you lookup through their DNS service. My point was that so does everyone else on the internet, including other DNS providers that you might use.

(i.e. If I go to sws.example.com which hosts a Secret Warez Stash, unless it's password-protected everyone has access to it, not just Google.)

Re:Introducing Google Public DNS: A new DNS resolver from Go... by stuff4ben on Thursday December 03, 2009 @01:05PM (#974835)
Ha! I was wondering in my head what OpenDNS would say about this when I read the article. Had no idea you were the founder of the company. That's pretty cool that you're on here.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by noelchurchill on Thursday December 03, 2009 @12:26PM (#974702)
I was wondering what you'd think :)
Re:Introducing Google Public DNS: A new DNS resolver from Go... by huherto on Thursday December 03, 2009 @01:32PM (#974890)
I didn't know who you were, but now I am very curious about what you think.
Re:Introducing Google Public DNS: A new DNS resolver from Go... by known on Saturday December 05, 2009 @06:51AM (#978025)
Did you anticipate Google will launch public DNS resolvers?
Re:Introducing Google Public DNS: A new DNS resolver from Go... by auston on Thursday December 03, 2009 @12:25PM (#974700)
please do!