2 ms·
> ... a simple CDN that uses it to provide the locality. If I'm understanding you correctly, you mean to tell the end user where the host (being reached via an
by jlgaddis 14y ago
> ... a simple CDN that uses it to provide the locality.
If I'm understanding you correctly, you mean to tell the end user where the host (being reached via anycast) is physically located?
This exists as part of the AS112 Project[0], assuming server operators have created/edited the appropriate resource record.
From a machine in my data center (Midwest):
$ host -t txt hostname.as112.net prisoner.iana.org | tail -n 2
hostname.as112.net descriptive text "ICANN DNS Operations"
hostname.as112.net descriptive text "Culpeper, VA, USA"
From a machine in One Wilshire (L.A.):
host -t txt hostname.as112.net prisoner.iana.org | tail -n 2
hostname.as112.net descriptive text "ICANN DNS Operations"
hostname.as112.net descriptive text "Los Angeles, CA, USA"
Those of you in other geographic areas will likely hit other servers.
On a side note, if you manage your own DNS servers, consider adding the relevant .in-addr.arpa zones to them and help alleviate some of the load. Or, if you have bandwidth to spare, bring up your own AS112 server. I work for an ISP and will bringing one on-line in the near future.
[0]: http://public.as112.net/ http://public.as112.net/
(Note: After lurking for a few years, I finally created an account here so I apologize if the formatting of this "first comment" is wonky.)