[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why are there no GeoDNS solutions anywhere in sight?
- Subject: Why are there no GeoDNS solutions anywhere in sight?
- From: mureninc at gmail.com (Constantine A. Murenin)
- Date: Thu, 21 Mar 2013 00:16:23 -0700
- In-reply-to: <[email protected]>
- References: <CAPKkNb63hqpT4CLcQ-TiMfYZtrqqT=1TRouKkQGn-QwdHCJO3g@mail.gmail.com> <[email protected]>
On 20 March 2013 20:57, Seth Mattinen <sethm at rollernet.us> wrote:
> On 3/20/13 8:28 PM, Constantine A. Murenin wrote:
>>
>> Why even stop there: all modern browsers usually know the exact
>> location of the user, often with street-level accuracy. It should be
>> possible to say that you have a server in Fremont, CA and Toronto, ON
>> or Beauharnois, QC, and automatically have all East Coast users go to
>> Toronto, and West Coast to Fremont. Why is there no way to do any of
>> this?
>>
>
> I guess there could be with LOC records.
>
> ~Seth
Apart from not being supported by anyone, it's also broken by design
in regards to the "Searching by Network or Subnet" section (e.g. the
party who controls 0.0.0.88.in-addr.arpa is not at all related to the
party that has 88.198.0.0/16), and also has no IPv6 support:
http://tools.ietf.org/html/rfc1876#section-5.2.2
C.