![](https://secure.gravatar.com/avatar/525b753cdab1ce5aa413fda336740455.jpg?s=120&d=mm&r=g)
and they work well!
even when you don’t sloppily flag the example host as being in the middle of Hudson’s Bay!
adam.example.org. IN LOC 55 09 51.243 N 01 41 38.836 W 53m 10m 10m 10m
:-D
bonus: for folks in the UK, there’s even direct lookup by postcode
$ dig loc NE612LL.find.me.uk ;; ANSWER SECTION: NE612LL.find.me.uk. 2592000 IN LOC 55 9 51.264 N 1 41 38.106 W 0.00m 0.00m 0.00m 0.00m
although, to satisfy those nasty OCD twinges, still have to fish out the proper altitude and tighten up D/M/S accuracy.
DNS LOC records are still a thing.
https://en.wikipedia.org/wiki/LOC_record https://en.wikipedia.org/wiki/LOC_record https://www.daftlogic.com/sandbox-google-maps-find-altitude.htm https://www.daftlogic.com/sandbox-google-maps-find-altitude.htm https://www.fcc.gov/media/radio/dms-decimal https://www.fcc.gov/media/radio/dms-decimal
R.
e.g.
adam.example.org http://adam.example.org/. IN LOC 55 35 58.449 N 79 38 15.811 W 53m 10m 10m 10m
On Apr 23, 2016, at 11:26, observium-request@observium.org mailto:observium-request@observium.org wrote:
It ends up on the canary islands, which is where we put devices we can't find a location for.