Google Public DNS

So, Google have launched a public DNS.

Quickly for those who don't understand this DNS can be considered like a phone book. Computers network each other by try to reach IP addresses, for example Da Cheese is 87.98.140.36 (try pasting that number into your browser address bar and you'll see what I mean). Since such addresses are hard for humans to remember we came up with host names.

So when you type www.shootingthecheese.ch in your browser your computer looks up www.shootingthecheese.ch in DNS and DNS says ok, go to 87.98.140.36.

Normally your ISP tells your computer which DNS servers to use, but some people choose to use other DNS servers. I use OpenDNS at home because the lookup is very fast, the DNS "directory" is always very up to date and it protects me and my family from Phishing and malware.

How does it protect from malware? Well they maintain a list of sites they consider to be infected, and when i type the name of the affected site rather than telling my computer the real IP address they tell me another IP address which is a site warning me the one I wanted was blocked.

So why are Google offering this and why is it scary? Google already know what people are searching for, this would let them know every single web page you visit, every one, it would also give them control over which sites you are allowed to see.

Maybe their intentions are good, but are we putting them in so much control that should their intentions change they could do catastrophic harm to us?

More on the OpenDNS blog:
OpenDNS Blog Some thoughts on Google DNS

You are really brainy Peachy.

__________________
One should either be a work of art or wear a work of art.

Well, of course the OpenDNS people are going to think this is bad, at least because 8.8.8.8 is easier to remember than 208.67.222.222. Next we'll be hearing from Microsoft about how awful it is that Google offers, well, anything really.

I personally am really glad that there exists a fall-back DNS server that I know I'm allowed to use, probably isn't going to have performance problems, and the address of which is really easy to remember.

yeah you are right that an easy to remember DNS server IP is useful but just imagine the amount of data Google will have if e.g. routers start shipping with this preconfigured.

I think it's pretty unlikely that routers will ship configured to use Google DNS, considering that DHCP works pretty well for this. A publicly available DNS server is a useful fallback for those who discover that their ISP's servers are under-performing, or as in the case of Bluewin, mis-configured - they have a .local. entry which screws up Zeroconf.

I've been using OpenDNS for years for this exact reason, and also use it when I run across a wireless access point which has run out of leases (pretty common in cafés). Having another option is fine by me.

I tend to dismiss the "Google has too much information" meme, at least in part because that's exactly what Microsoft want you to think.

Well there was the case of D-Link routers which were wrongly configured for time servers link. In contrast to that episode, I wouldn't be surprised if Google were to encourage router manufacturers to use their addresses.

I've never needed it myself, though I will admit that for a long time after switching ISPs, I "forgot" to change my DNS servers from the old ISP.

I don't dismiss it, though in my case it is partly a negative reaction to some of Microsoft's previous actions. Microsoft Passport anyone?

Joel Spolsky:

__________________
October. This is one of the peculiarly dangerous months to speculate in stocks. Other dangerous months are July, January, September, April, November, May, March, June, December, August and February.
-Mark Twain-

I think the difference is that MS was opt in with passport, if a router or even a laptop was shipped with Googles public DNS servers set (as I'm sure Chrome OS netbooks will be) the average computer user won't have a clue what this means for them and probably won't care.

I actually believe that Google does not intend to do evil, but as a publicly listed company they are (unintentionally?) putting themselves in a position to do great evil if they so wished.

I think these companies know exactly what they are doing: from bundling browsers with operating systems (MS) to putting photos of your house on the internet (Streetview) to using your words and creations to make money (Facebook/Myspace).

As you say, if companies can get their configuration preainstalled on equipment delivered to a customer it will be the holy grail of internet marketing tracking the user behaviour throughout the net and not just over one site. Unlike a home page- few people will have the knowledge or inclination (or nerve) to change the DNS settings.

BigD

__________________
You make your own luck.

www.shootingthecheese.ch
The place for fun and chat in Switzerland.

I'm generally suspicious of using someone elses nameserver which is supposedly better. As mentioned previously on this thread, you become extremely transparent, and at the very least your marketing profile leaks to whoever pays most.

retto and me are therefore using our own, DNSSEC-enabled nameservers. We don't get the warning pages about fishing sites peachy gets, but then I tend to think that DNS is the wrong place to do that. I don't like MS, Google or OpenDNS deciding how DNS should be used by me.

Running your own caching nameserver is not that hard, requires very little maintenance and makes you totally independent from ISP's botched up idea of DNS (which can still be used as a fallback). I bet there's some pre-packaged stuff to be found on the web. Otherwise, I'm happy to help.