The progression of a Google Dance could basically be watched by querying the IP addresses of Google's data centers. But queries on the IP addresses are normally redirected to www.google.com. However, Google has domains which resolve to the single data centers' IP addresses. These domains as well as their IP addresses are shown in the following list.
| Domain | IP-Adresse |
| www-ex.google.com | 216.239.33.100 |
| www-sj.google.com | 216.239.35.100 |
| www-va.google.com | 216.239.37.100 |
| www-dc.google.com | 216.239.39.100 |
| www-ab.google.com | 216.239.51.100 |
| www-in.google.com | 216.239.53.100 |
| www-zu.google.com | 216.239.55.100 |
| www-cw.google.com | 216.239.57.100 |
| www-fi.google.com | 216.239.41.100 |
| www-gv.google.com | 216.239.59.100 |
| www-kr.google.com | 66.102.11.100 |
| www-mc.google.com | 66.102.7.100 |
| www-lm.google.com | 66.102.9.100 |
The index updates at the single data centers seem to happen at one point in time. As soon as one data center shows results from the new index, it won't switch back to the old index. This happens most likely because the index is redundant at each data center and at first, only one part of the servers (eventually half of them) is updated. During this period, only the other half of the servers is active and provides search results. As soon as the update of the first half of servers is finished, they become active and provide search results while the other half receives the new index. Thus, from the user's perspective, the update of one data centers happens at one point in time.
Finally, it shall be noted that the access to the single data centers is generally controlled by the DNS only, but sometimes queries are redirected. However, this is easy to detect: When for a query at one of the domains listed above, the links to Google's cache do not comply with the IP address that belongs to the domain, then the query is redirected. If this happens, Google inhibits - for whatever reason - the access to one data center.
Copy rights by google
putas valencia putas sevilla
0 comments:
Post a Comment