Domain Names — Implementation and Specification
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.
P. Mockapetris · 1987-11
Abstract
RFC 1035 specifies the implementation details and wire format of the Domain Name System (DNS), defining the message format for DNS queries and responses, resource record types (A, NS, MX, CNAME, SOA, PTR, and others), and the operational requirements for name servers and resolvers. It defines the binary protocol used over UDP and TCP on port 53.
Why This RFC Matters
RFC 1035 is arguably one of the most consequential protocol specifications ever published. Its compact binary wire format, label compression scheme, and resource record structure have remained remarkably stable over nearly four decades despite the enormous growth of the Internet. Every DNS query and response exchanged today still conforms to the message format defined in this document. Extensions such as EDNS0 (RFC 6891) and DNSSEC (RFC 4033–4035) were carefully designed to be backward compatible with the original RFC 1035 message structure.