RFC 1712:DNS Encoding of Geographical Location
RFC-Ref

DNS


Click on the red underlined text to get to the source

... The DNS [Mock87a][Mock87b] represents an existing system ideally ...
... Mock87b] represents an existing system ideally suited to the provision of host specific information. The DNS is a widely used and well-understood mechanism for providing a distributed database ...
... database of such information and its extensible nature allows it to be used to disseminate virtually any information. The most commonly used DNS implementation is the Berkeley Internet Name Domain server ...
... be updated locally but available globally; a perfect match with the services provided by the DNS. Current DNS servers provide a variety of useful information about hosts ...
... services provided by the DNS. Current DNS servers provide a variety of useful information about hosts in their domain ...


... Each host requires its own GPOS field in the corresponding DNS RR to explicitly specify its geographical location ...
... explicitly specify its geographical location and altitude. If the GPOS field is omitted, a DNS enquiry will return no position information for that host. ...
... configuration files, most vendor implementations seem to ignore whatever is not understood upon startup of the DNS. Usually this will result in a number of warnings appearing in system log files, but in no way alters naming information or impedes the DNS ...
... DNS. Usually this will result in a number of warnings appearing in system log files, but in no way alters naming information or impedes the DNS from performing its normal duties. ...


... Once information has been entered into the DNS, it is considered public. ...



Google
Web
RFC-Ref