Description

DNS servers such as ISC bind support redundancy by returning records in a round-robin fashion:

server    A    231.5.240.145 ; country 1
server    A    228.45.123.45 ; country 2

when a client requests the A records above, multiple times, bind permutes the addresses and returns them in a round-robin fashion.

An idea would be to return multiple records based on the geolocation of an incoming request and the destination IP address. This could majorly increase the speed between a server and a client given that metropolitan speed is much faster than international speed.

One could elaborate a little and perhaps determine distances as well, so that the “closest” IP is returned. As for “closest”, perhaps a hop-based estimation would suffice.

Benefits

  • It does not impose an RFC change (an additional RFC, perhaps) and does not require for bind servers to cooperate.

Disadvantages

  • There is still the problem whether a service is up or down, but round-robin does not know that either.

Possible Avenues

bind accepts connections directly, so bind can tell the origin of a request. If that is so, then a bind patch would suffice. Possibly easy by leveraging the already existing code for delivering round-robin records.


incubator/dns_geolocation_load-blancing.txt · Last modified: 2017/02/22 18:30 (external edit)

Access website using Tor


For the copyright, license, warranty and privacy terms for the usage of this website please see the license and privacy pages.