All Entries Tagged With: "Google DNS"

Can Google Handle Google DNS?

From Google;

Why does DNS matter?

The DNS protocol is an important part of the web’s infrastructure, serving as the Internet’s phone book: every time you visit a website, your computer performs a DNS lookup. Complex pages often require multiple DNS lookups before they start loading, so your computer may be performing hundreds of lookups a day.

Google Public DNS is a free, global Domain Name System (DNS) resolution service, that you can use as an alternative to your current DNS provider.

Why should you try Google Public DNS?

By using Google Public DNS you can:

• Speed up your browsing experience.
• Improve your security.
• Get the results you expect with absolutely no redirection.

My issue is this. I’ve been testing Google Chrome as my browser. After long use during the day, it freezes. The software isn’t really totally frozen. I can still type a web address in the address bar. It just won’t take me there when I hit enter.

If I close Google Chrome and wait a few minutes, then restart it, it works fine. That tells me there is a caching issue after using it for a long time. It could also be a server issue as if I’ve used the alloted cache for the day or something.

If Google can’t keep Google Chrome running, then how can it keep serving DNS for thousands or potentially hundreds of thousands of people.

You may say one has nothing to do with the other and you may be technically correct. I’m not sure. But given the enormity of running DNS services for that many people and Google’s inability to make Google Chrome work properly, it seems to me that they are not ready to run DNS.

DNS is complicated and resource intensive. I’d like to hear comments from anyone who has used Google DNS to see what their experience has been.

Related articles by Zemanta

• Try Google Public DNS for Faster Web Access (techmadly.com)
• Geez, Google Wants to Take Over DNS, Too (wired.com)
• Introducing Google Public DNS: A new DNS resolver from Google (googlecode.blogspot.com)
• Google Public DNS is About Algorithms and Ads, Not Just Speed (steverubel.com)
• Google DNS – Speed up surfing (mrpant.com)
• Google Continues Eating the Internet With Google Public DNS [Google] (gizmodo.com)
• Google Public DNS: Wonderful Freebie or Big New Menace? (sfgate.com)
• Google’s New DNS Service Has One Major Flaw: Poor Performance (seekingalpha.com)
• What Google Public DNS Actually Means To You? (shankrila.com)

Google DNS, Google Caffiene & Google Local Search?

Google didn’t get where they are by being stupid. Those guys at Google really know what they are doing and they are usually able to do things before anyone saw it coming too. They are full of surprises.

Hopefully, you already know about Google Caffeine and Google Local Search. You may have already heard about Google DNS as well. But read this about Google DNS from the Google Code Blog.

A proposal to extend the DNS protocol Wednesday, January 27, 2010Today a group of DNS and content providers, including Neustar/UltraDNS and Google are publishing a proposal to extend the DNS protocol. DNS is the system that translates an easy-to-remember name like www.google.com to a numeric address like 74.125.45.104. These are the IP addresses that computers use to communicate with one another on the Internet.

ICANN has to approve it before it happens, but ICANN usually signs off on whatever these companies wants to do, so don’t expect a long debate. Vint Cerf, (the inventor of email), used to run ICANN and now works for Google.

By returning different addresses to requests coming from different places, DNS can be used to load balance traffic and send users to a nearby server. For example, if you look up www.google.com from a computer in New York, it may resolve to an IP address pointing to a server in New York City. If you look up www.google.com from the Netherlands, the result could be an IP address pointing to a server in the Netherlands. Sending you to a nearby server improves speed, latency, and network utilization.

Sounds really good doesn’t it? We all want more speed. But there’s more. Right now when that load is balanced, none of your IP Address is passed along from your ISP to the other resolver.

Our proposed DNS protocol extension lets recursive DNS resolvers include part of your IP address in the request sent to authoritative nameservers. Only the first three octets, or top 24 bits, are sent providing enough information to the authoritative nameserver to determine your network location, without affecting your privacy.

That part, as the post states, will not reveal to your whole IP Address to Google, so they won’t know exactly who you are. As long as the agreement ICANN approves does not include some obscure legal clause that states this can change later. As long as Google maintains the “Do no evil” policy.

But this post isn’t about privacy issues. With the launch of Google Caffeine and with Google Local Search becoming more popular, I suspect that Google DNS is part of an overall strategy to make local search even more powerful.

I’m not a DNS expert, but it seems very logical that with Google having the ability to know your general location combined with the ability to send you to the server they want to send you to will have a major impact on Google Search results.

What do you think?