Google is a one-stop site for just about everything you could possibly want to do on the 'net. It goes way beyond a search engine; you can use Google as an online word processor, calendar, personal finance tracker, map and travel assistant, shopping site, bookstore, web mail application, streaming video clearinghouse (it owns YouTube)...you get the picture. Google's got a feature for just about everything.
Now, Google is premiering its own DNS! Now, any of you who aren't hopeless geeks like myself might ask the question: what on earth is DNS? It's an abbreviation for Domain Name System, and its workings can get a wee bit complicated, but the simplest metaphor is that of a phone book. If you want to call a person, but you don't know the number, you grab a phone book and look up the number by the name of the person or business you're looking for. Many people don't realize that the internet also accesses websites by NUMBER, not by the name of the website (or URL). When you want to do a web search, you go up to your address bar and type in http://www.google.com. After you hit enter, your ISP (Internet Service Provider) says "ok this guy wants to navigate to Google. What's the IP address for that-what's it's number?" Then it uses its DNS like an internet phone book. It queries a few servers to find that numeric IP address (this is referred to as "resolving the host"), and navigates there for you. (If you want a far more technical breakdown of DNS, Wikipedia has a mind-numbing amount of info on the subject. Just click here. )
Luckily computers, servers and connections are pretty fast these days, and the resolving process typically runs quickly. However, lesser-quality DNS servers out there (some smaller ISPs have sort of mediocre DNS) can get a wee bit bogged down. Part of this is because of caching-the process by which a system stores recently or often-requested IP addresses in memory for quicker recall when subsequent requests come in. Rather than having to scour the net looking for the proper address, it's already queued up. Caching is great, but it takes memory. Smaller ISP's might not have the ability to cache vast amounts of DNS data for very long--it gets deleted more often because there just isn't the room. The DNS "phone book" thus has to rebuild itself more often, and this takes time. That translates into longer page loads for the person browsing the 'net. It should be said that this will only pose a potential problem for you if you 1) have a slow connection and 2) are using a dinky little ISP with a poor quality DNS server that has bad security protocols and insufficient space for caching. If you're on a broadband connection with a large ISP (something like Comcast, for example), I doubt you'd have enough DNS problems to justify shopping for a different solution.
A second concern with conventional DNS is security. You would be amazed how simple it is to dupe a DNS into going to the wrong IP address for a given website. When your DNS server goes out to query other DNS servers to find an IP address, ingenious hackers can poison the process by having their computers pose as DNS servers, and give false IP addresses back to your ISP's DNS server. Let's say I want to do some online banking. I type in the address for my bank's online banking service. My ISP's DNS server kicks into action, consulting other DNS servers on the 'net to correctly resolve the host for my bank's site. In this process, a hacker jumps in and sends out the message: "Hey! I'm a DNS server! The IP address you're looking for is xx.xxx.xxxx.x.xx." My DNS server falls for it, and navigates to the false address. The page that comes up looks just like my real online banking website, but in reality it's been counterfeited by the hacker. Unknowingly I enter my username and password, and presto! The hacker now has all he needs to log into my bank account and transfers all my money to his account. Now that's a simplified example, because the use of SSL certificates, and making sure your address bar displays "https:" at the beginning means that the data you enter will be encrypted, thus appearing as gobbledy-gook gibberish to the hacker. But if you're not watching for this stuff, you can mistakenly enter your personal data on a nonsecure site!
Google has entered the fray, claiming that its DNS will be the answer to everyone's problems. Google has an ENORMOUS infrastructure, as you can well imagine. Vast amounts of available memory means that Google will be able to maintain a staggeringly huge cache of DNS data, and that cache can stay around for much longer before being purged and re-built. Because of this they promise to deliver much faster browsing. They also seek to address the security issue by the way their DNS servers will request host data from other DNS servers. The Google DNS will send its requests along with some unique "junk" data that would be next to impossible to replicate. When another DNS server sends back an IP address, yet doesn't contain the random "junk" data generated by the Google DNS, then Google will know its likely hacker activity and throw out that result.
So speed, convenience, and security are what Google DNS offers. Sounds good on the face of it, right? But there are big concerns out there about Google's move. The question on many people's lips is: "Google already has its fingers in so many aspects of the internet; do we really want it making itself even MORE indispensable to the 'net's infrastructure?" The fear is that many Internet Service Providers (ISP's) will say, "why even bother with our own DNS? Why not just direct our clients' traffic to the Google DNS servers?" If that were to happen with enough internet companies, then Google itself would become inextricably integrated within the infrastructure of the entire internet. This notion is setting off the antitrust radars of many 'net watchdogs, and even the government is watching. Another big concern is privacy. Many feel uncomfortable with the idea of Google having their internet browsing patterns stored in a DNS cache somewhere. Google has assured everyone that they'll take steps not to abuse privacy, but the distrust persists. Perhaps with good cause.
So what do you think? Are the speed, convenience and security offered by Google DNS significant enough that other concerns are mitigated, or is this a disturbing trend that ought to be nipped in the bud before it gets out of hand? I must say that I'm not quite comfortable with Google's move, but I'm willing to get more facts before making my judgment on the issue final. Any input from the techies out there would be welcome.
Interested in some further reading? I would recommend this article by CNET's Stephen Shankland. Also check out Topher Kessler's look at the problems faced by DNS servers, and the pros and cons of using an alternative DNS like Google or the current first-place holder, OpenDNS. If you want the viewpoint of OpenDNS's founder, David Ulevitch, about the downsides of Google's new DNS, check out his blog on the subject. (Just remember to take it with a grain of salt; this guy is obviously biased since his livelihood is dependent on Google NOT having success with this. OpenDNS has a free version, but it's chock full of ads. They also have paid services with more features. The corporate version of OpenDNS costs a whopping $2000/year!)
Last, how about a video link that discusses all these pros and cons? Check out this episode of CNET's show "Buzz Out Loud." Stephen Shankland, mentioned above, is a major contributor to this discussion. Enjoy!


Recent Comments