namebench should use geolocation to reduce querying far away nameservers

[GoogleCodeExporter]

namebench currently pings 4,000 nameservers around the world. This is a bit
excessive, and causes 155 bytes of extra traffic to be sent to the 90% of
nameservers that will never be considered for further health tests.

One solution is to use geolocation. namebench could limit the pinging to a
combination of:

- servers within the same country as the client
- servers within 1000mi. of the client
- servers within 500mi. of the current DNS servers (if they are not global).
- servers within the same Class A/B/C of the client
- servers within the same Class A/B/C of the client of the current DNS servers.

The tricky part to solve is: What is a robust method to determine where the
user is located to do all of this? We could use GeoIP, if we knew the
external IP the user was using.

Original issue reported on code.google.com by tstromb...@google.com on 2 Mar 2010 at 2:35

[GoogleCodeExporter]

perhaps issues 104, 105 and 106 could be combined into one site/project?

client connects to get an updated list of dns servers, upon connection server 
will see 
client's IP and do geolocation lookup, based on that it will return an updated 
relevant list for that user's location(ie users in US won't get Asian dns 
servers) and 
upon completion of the benchmark submit the results to central repository for 
personal 
and/or aggregate stats.

Original comment by mxx...@gmail.com on 30 Mar 2010 at 3:31

[GoogleCodeExporter]

This is done as r1045

Original comment by helixblue on 15 Jul 2010 at 1:14

• Changed state: Fixed