Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #13069
| From | Joshua Cranmer <Pidgeot18@verizon.invalid> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Toward faster international server selection using clever DNS. |
| Date | 2012-03-19 22:23 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <jk8t7c$hj5$1@dont-email.me> (permalink) |
| References | <4cp8m79d7p7mu5dkoikgmnb5obtgiqrldd@4ax.com> <jk25t9$edm$1@dont-email.me> <rd7dm7d3f4s3aund90quf4ac3f61rml531@4ax.com> |
On 3/18/2012 9:46 PM, Roedy Green wrote: > On Sat, 17 Mar 2012 09:08:39 -0500, Joshua Cranmer > <Pidgeot18@verizon.invalid> wrote, quoted or indirectly quoted someone > who said : > >> Note that people already use DNS to point you to the closest physical >> servers you have access to, along with load balancing tricks. Basically, >> the problem you are trying to solve is already more or less solved. > > Oddly though, Google does not do this. I watched it with Wireshark. > So there still might be value is localising Google links in your JSP. What do you mean by this? If, for example, I do a traceroute to google.co.at and another to google.com, the route is exactly the same except for the final server. Judging from whois data, the servers for both domains are located in Wisconsin, whereas the host computer I queried from is in Illinois. Given the politics of how ISPs connect to each other, this is not an unreasonable result (the traffic is forwarded via what appear to be primarily academic transit links, so I presume that the amount of money that changes hands for the bandwidth in question is exactly $0). Repeating a traceroute from a computer located in another state for the same domain name produced a different IP address, accessed via a different set of intermediate hops. I can't map these to physical server locations, but knowing a little about ISP infrastructures, I suspect that the server is likely within 20 miles of my location (I happen to be geographically close to a cluster of major internet exchanges--over half of the DNS root nameservers have a home in the area). -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Donald E. Knuth
Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Toward faster international server selection using clever DNS. Roedy Green <see_website@mindprod.com.invalid> - 2012-03-17 03:36 -0700
Re: Toward faster international server selection using clever DNS. Jeff Higgins <jeff@invalid.invalid> - 2012-03-17 08:17 -0400
Re: Toward faster international server selection using clever DNS. Roedy Green <see_website@mindprod.com.invalid> - 2012-03-17 05:45 -0700
Re: Toward faster international server selection using clever DNS. Joshua Cranmer <Pidgeot18@verizon.invalid> - 2012-03-17 09:08 -0500
Re: Toward faster international server selection using clever DNS. Roedy Green <see_website@mindprod.com.invalid> - 2012-03-18 19:46 -0700
Re: Toward faster international server selection using clever DNS. Joshua Cranmer <Pidgeot18@verizon.invalid> - 2012-03-19 22:23 -0500
Re: Toward faster international server selection using clever DNS. RedGrittyBrick <RedGrittyBrick@spamweary.invalid> - 2012-03-27 14:51 +0100
csiph-web