Visual RFC.
ALL RFCs / RFC 1876
Read the RFC ↗
RFC 1876 / DNS LOCATION

Search the most specific recorded network first

07

The historical IPv4 fallback discovers network/subnet names into a stack, then checks the most specific name first. This is not a modern CIDR or IPv6 geolocation algorithm.

RFC 1876 · § 5.2.3EXAMPLE
5 / 5
Search the most specific recorded network firstPop lab.example.org next; its LOC is present. Use it as an approximation and stop. Even if campus.example.org has LOC, it does not replace this more-specific subnet result.Historical classful discovery → stack → LOCpopped: lab.example.orgMore-specific lookup already absentcampus.example.orgLOC? foundUse lab approximation; stopCampus LOC is not selectedOptional fallback: SHOULD algorithm; not a modern CIDR/IPv6 rule
05
Use the first less-specific location found

Pop lab.example.org next; its LOC is present. Use it as an approximation and stop. Even if campus.example.org has LOC, it does not replace this more-specific subnet result.

Source for this drawing: RFC 1876 · Read RFC section 5.2.3 ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
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.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

The specified algorithm starts from a class-A/B/C host-zero address, queries reversed-octet IN-ADDR.ARPA for PTR and A, pushes the returned name, and uses any returned A value as the next subnet mask.

  • The specified algorithm starts from a class-A/B/C host-zero address, queries reversed-octet IN-ADDR.ARPA for PTR and A, pushes the returned name, and uses any returned A value as the next subnet mask.
  • When no further mask A record is present, pop names from most specific to least specific until a LOC record is found. A subnet result takes priority over a broader network result.
  • The fictional 172.20.2.17 fixture uses the historical class-B start and masks 255.255.255.0 then 255.255.255.240. A records at these special nodes are masks, not host address answers. This RFC defines no extensions for other addressing schemes.
DETAILS

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 ↗

All chapters in RFC 1876

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗