Read the sixteen-byte location record
01A LOC resource record stores a location, its size and its uncertainty. Type 29 identifies LOC; the version-zero record data has sixteen octets.
Separate input begins with version 1. The implementation checks the version and makes no assumption that the remaining bytes use version 0’s layout.
Source for this drawing: RFC 1876 · Read RFC section 2 ↗
New to this? Start hereA quick picture + helpful background
A message needs an address.
Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.
Helpful first, if these ideas are unfamiliar
These pictures are analogies to help you learn. The linked RFC explains the actual rules.
Terms in this drawing
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
Four one-octet fields precede three four-octet integers: VERSION, SIZE, horizontal precision, vertical precision, latitude, longitude and altitude.
- Four one-octet fields precede three four-octet integers: VERSION, SIZE, horizontal precision, vertical precision, latitude, longitude and altitude.
- Version must be zero. Implementations are required to check it and make no format assumptions for unrecognized versions.
- The drawing shows RDATA only. DNS owner name, type, class, TTL and RDLENGTH belong outside these sixteen octets.
Examples are fictional, offline teaching fixtures. RFC1876 is Experimental; its classful IPv4 fallback is historical, not universal current geolocation. Follow the linked official sections for full requirements.
Read the RFC section ↗