Domain names - implementation and specification
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Abstract
- This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication.
- Publication Date
- 1987-11-01
- Status Note
- Internet Standard
- DOI
10.17487/RFC1035- Link
- https://doi.org/10.17487/RFC1035
- Author(s)
- P. Mockapetris
- Keyword(s)
- Domain, DNS
- Details
- need to add amendedBy docs
Latest version of IETF RFC 1035
Document Versions — IETF RFC 1035
-
▶ IETF RFC 1035 (1987-11-01)THIS DOC [ACTIVE] [AMENDED] [LATEST VERSION]
Amended by:
- RFC1101 NOT IN REGISTRY
- RFC1183 NOT IN REGISTRY
- RFC1348 NOT IN REGISTRY
- RFC1876 NOT IN REGISTRY
- RFC1982 NOT IN REGISTRY
- RFC1995 NOT IN REGISTRY
- RFC1996 NOT IN REGISTRY
- RFC2065 NOT IN REGISTRY
- RFC2136 NOT IN REGISTRY
- RFC2181 NOT IN REGISTRY
- RFC2137 NOT IN REGISTRY
- RFC2308 NOT IN REGISTRY
- RFC2535 NOT IN REGISTRY
- RFC2673 NOT IN REGISTRY
- RFC2845 NOT IN REGISTRY
- RFC3425 NOT IN REGISTRY
- RFC3658 NOT IN REGISTRY
- RFC4033 NOT IN REGISTRY
- RFC4034 NOT IN REGISTRY
- RFC4035 NOT IN REGISTRY
- RFC4343 NOT IN REGISTRY
- RFC5936 NOT IN REGISTRY
- RFC5966 NOT IN REGISTRY
- RFC6604 NOT IN REGISTRY
- RFC7766 NOT IN REGISTRY
- RFC8482 NOT IN REGISTRY
- RFC8490 NOT IN REGISTRY
- RFC8767 NOT IN REGISTRY
- RFC9619 NOT IN REGISTRY
Bibliographic Reference(s)
- 10.1145-1024840.1035268 NOT IN REGISTRY
- 10.1145-6617.6618 NOT IN REGISTRY
- ISI.IEN116 NOT IN REGISTRY
- MIT.PATP.sE23.1987 NOT IN REGISTRY
- RFC1001 NOT IN REGISTRY
- RFC1002 NOT IN REGISTRY
- RFC1010 NOT IN REGISTRY
- RFC1031 NOT IN REGISTRY
- RFC1032 NOT IN REGISTRY
- RFC1033 NOT IN REGISTRY
- RFC742 NOT IN REGISTRY
- RFC768 NOT IN REGISTRY
- RFC793 NOT IN REGISTRY
- RFC799 NOT IN REGISTRY
- RFC805 NOT IN REGISTRY
- RFC810 NOT IN REGISTRY
- RFC811 NOT IN REGISTRY
- RFC812 NOT IN REGISTRY
- RFC819 NOT IN REGISTRY
- RFC821 NOT IN REGISTRY
- RFC830 NOT IN REGISTRY
- RFC882 NOT IN REGISTRY
- RFC883 NOT IN REGISTRY
- RFC920 NOT IN REGISTRY
- RFC952 NOT IN REGISTRY
- RFC953 NOT IN REGISTRY
- RFC973 NOT IN REGISTRY
- RFC974 NOT IN REGISTRY
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC1035.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 1035, Domain names - implementation and specification. Available at https://doi.org/10.17487/RFC1035
Snippet:
IETF RFC 1035, Domain names - implementation and specification. Available at https://doi.org/10.17487/RFC1035
HTML (ISO 690 compliant)
Preview:
IETF RFC 1035, Domain names - implementation and specification. Available at https://doi.org/10.17487/RFC1035
Snippet:
<span class="citation"><cite>IETF RFC 1035</cite>, Domain names - implementation and specification. Available at <a href="https://doi.org/10.17487/RFC1035" target="_blank" rel="noopener">https://doi.org/10.17487/RFC1035</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 1035, Domain names - implementation and specification
doi: 10.17487/RFC1035
url: https://doi.org/10.17487/RFC1035
doi: 10.17487/RFC1035
url: https://doi.org/10.17487/RFC1035
Snippet:
<li> <cite id="bib-rfc1035">IETF RFC 1035</cite>, Domain names - implementation and specification <span class="doi">10.17487/RFC1035</span> </li>
Referenced By
- IETF RFC 1123 [Active*]
- SMPTE ST 2098-2:2022 [Active]