Welcome to WebmasterWorld Guest from 184.108.40.206
Google operates a number of datacenters around the world. I am not sure about the exact number, but at the moment there are about 15. Each datacenter has one or more clusters, and each clusters consists of thousands of computers calculating the SERPs for your search query. When you do a query, you are connected with one of these data centers. Which one is determined by the DNS settings of the nameservers of Google called ns1.google.com ... ns4.google.com.
The DNS servers play an important role in the load distribution and disaster recovery. When you request the IP address for www.google.com, the DNS server first replies with a canonical name. This name has the form www.X.google.com where X is a letter. At this moment the name www.l.google.com is returned from the location where I am working, but this can vary depending on location and time.
Then a second query is done to translate this canonical name to an IP address. Every canonical name of the form www.X.google.com returns 3 IP addresses which can be used by the browser to attach to the search engine.
Throughout the day, you are not connected to the same data center or cluster. This is, because Google has decided to set an extremely short TTL (time to live) time for the canonical name and IP address. They have a good reason for it. If a cluster is overloaded or brakes down, they can route requests to another cluster or datacenter. Within 5 minutes (the TTL of the IP addresses) all clients will request a new IP address for www.google.com and all traffic is rerouted.
Some tests you can do yourself. This works on Windows 2000, but probably also on XP.
Start the command line program nslookup
Type the command set d2
The program will now query the Google nameservers for the canonical name and the IP addresses for www.google.com. Because debugging is switched on with the set d2 command, you will also see the TTL times for the canonical name and IP's.