Apply master-file units and defaults
05A zone master file is human-readable DNS data. LOC writes latitude, hemisphere, longitude, hemisphere, altitude and optional size/precision values.
Separate fragment ends with 0m 30m 200m. Size is 30 m and horizontal precision 200 m; vertical precision remains its 10 m default. No optional field shifts into a different role.
Source for this drawing: RFC 1876 · Read RFC section 3 ↗
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.
Minutes and seconds default to zero when omitted. Distances are meters, optionally followed by m; fractional seconds have thousandth-of-an-arcsecond resolution.
- Minutes and seconds default to zero when omitted. Distances are meters, optionally followed by m; fractional seconds have thousandth-of-an-arcsecond resolution.
- If omitted, size defaults to 1 m, horizontal precision to 10000 m, vertical precision to 10 m. Optional size, horizontal and vertical fields are positional.
- Parentheses may group multiline data under RFC1035§5.1. DNS owner, TTL and class are still record metadata; these are fictional offline examples.
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 ↗