Domain Name System Structure and Delegation
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
J. Postel · 1994-03
Abstract
RFC 1591 describes the overall structure of the Domain Name System, explains the concept of delegation from parent to child zones, and documents the original purpose and intended use of the generic top-level domains (gTLDs) such as .com, .net, .org, and .edu, as well as two-letter country-code TLDs (ccTLDs). It outlines responsibilities of domain name registries and registrars.
Why This RFC Matters
RFC 1591 established the conceptual foundation for DNS naming hierarchy and delegation that remains in use today. Its description of gTLD purposes—.com for commercial entities, .org for non-profits, .net for network operators—shaped two decades of domain policy even as those boundaries eroded in practice. The delegation model described (parent authorizes child zone, child operates independently) is the fundamental architectural principle behind the scalability of DNS to hundreds of millions of names.