Commentary

Allen Stern
 

Two Predictions For DNS In 2010

Earlier this week Google announced the launch of Google DNS. I'd like to share my two predictions for DNS in 2010.

Earlier this week Google announced the launch of Google DNS. I'd like to share my two predictions for DNS in 2010.Back in 2007, James Thomas attempted to use the Web without ever touching a Google service. He was able to do it for a short while but eventually gave in. Last year I took a look at just how much Google knows about you. Today Google even knows where we are physically located.

What Google DNS will do is basically sit between your computer and the computer you want to reach. When we type in "moo.com", a computer has to translate that to computer-speak and then send us on our way to the computer that holds the moo.com files. This middle-man computer is called a DNS or domain name server.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Google says they can do DNS faster than anyone else and that since we all want to load webpages very fast, people will want to switch.

Jesse Stay says that DNS will become the new browser war and compares today's announcement to the fight between Netscape and Microsoft. Steve Rubel notes that the Google DNS is all about ads. You might be wondering why Steve says that this is an ad-play. It's simple. Using my example above with moo.com, let's say you accidentally type in "moopiet29595.com". Since there is no website at that address, the DNS server is lost out there in cyberspace. When that happens, most DNS servers will reroute you to a page that typically is a search page with search results that match the name you typed in plus ads.

OpenDNS, the popular DNS service, has a post that discusses the Google DNS launch.

Based on the Google DNS announcement, here are my top two predictions for 2010 with regards to DNS.

Google Will Own ISP DNS It's simple - most Internet providers will outsource their DNS functions to Google. I predict that this will happen by the end of June 2010. Google has the cash and will make it super sweet for the ISPs to switch. This will also help Google take the main market share for DNS. Changing your DNS servers on your computer is not that easy and most Internet users will never do it. But if Google partners with say Comcast or Time Warner, they can make the change at the server level and it will be done automatically. The ISPs get major cash, Google gets the overwhelming share of the DNS function and users never know anything changed.

For years I thought Google would acquire the big ISPs. Now they have no need to - just take over the DNS and they get control without having to deal with the other ISP operations (e.g. billing, customer service, etc.).

Microsoft Will Acquire OpenDNS If we go with Jesse's argument above that DNS will be the warzone for position next year, Microsoft will want a hand in the pot. OpenDNS won't be able to resist the bucket of cash that Microsoft will bring. At that point, Microsoft will go after the partnerships I noted above that Google will most likely make. And Jesse will be right - it will be a bloodbath.

I can't tell you whether to switch to Google DNS or not. The bottom line is that Google knows just about everything you do online already.

Is today's announcement a bad thing? I can't answer that question but my guess is that once the government gets past the health care issues, they may just come knocking. I'd love to get a reaction from the President's CTO and tech team.

If you decide to setup Google DNS, Amit has a great post with videos on how to make the switch. And if you decide to switch, leave a comment with your reasoning for switching.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links