API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 1035
[ACTIVE] [AMENDED]

Domain names - implementation and specification

Metadata

Publisher
IETF
Doc Type
Standard
Pages
55
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
ISSN
2070-1721
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:
  • IETF RFC 1101 [Active*]
  • 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 — IETF RFC 2136, Dynamic Updates in the Domain Name System (DNS UPDATE) EXTERNAL
  • RFC2181 — IETF RFC 2181, Clarifications to the DNS Specification EXTERNAL
  • RFC2137 NOT IN REGISTRY
  • RFC2308 NOT IN REGISTRY
  • RFC2535 NOT IN REGISTRY
  • RFC2673 — RFC2673 EXTERNAL
  • RFC2845 NOT IN REGISTRY
  • RFC3425 NOT IN REGISTRY
  • RFC3658 NOT IN REGISTRY
  • RFC4033 NOT IN REGISTRY
  • RFC4034 — IETF RFC 4034, Resource Records for the DNS Security Extensions EXTERNAL
  • 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 — Solomon 82 EXTERNAL
  • 10.1145-6617.6618 — Quarterman 86 EXTERNAL
  • ISI.IEN116 — IEN-116 EXTERNAL
  • MIT.PATP.sE23.1987 — Dyer 87 EXTERNAL
  • RFC1001 — RFC-1001 EXTERNAL
  • RFC1002 — RFC-1002 EXTERNAL
  • RFC1010 — RFC-1010 EXTERNAL
  • RFC1031 — RFC-1031 EXTERNAL
  • RFC1032 — RFC-1032 EXTERNAL
  • RFC1033 — RFC-1033 EXTERNAL
  • RFC742 — RFC-742 EXTERNAL
  • RFC768 EXTERNAL
  • RFC793 EXTERNAL
  • RFC799 — RFC-799 EXTERNAL
  • RFC805 — RFC-805 EXTERNAL
  • RFC810 — RFC-810 EXTERNAL
  • RFC811 — RFC-811 EXTERNAL
  • RFC812 — RFC-812 EXTERNAL
  • RFC819 — RFC-819 EXTERNAL
  • RFC821 — RFC-821 EXTERNAL
  • RFC830 — RFC-830 EXTERNAL
  • RFC882 — RFC-882 EXTERNAL
  • RFC883 — RFC-883 EXTERNAL
  • RFC920 — RFC-920 EXTERNAL
  • RFC952 — RFC-952 EXTERNAL
  • RFC953 — RFC-953 EXTERNAL
  • RFC973 — RFC-973 EXTERNAL
  • RFC974 — RFC-974 EXTERNAL
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 Tree
Reference 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 Icon SMPTE's HTML Pub

Preview:
IETF RFC 1035, Domain names - implementation and specification
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