Learn/ Docs/ Reference/ Rfc Index

reference

RFC Index

Curated index of essential DNS RFCs — the foundational specifications, security extensions, encrypted transport, and modern operational standards

The DNS specification landscape

DNS is the most extensively specified protocol in the IETF ecosystem. As of 2022, approximately 297 approved RFCs and over 2,300 Internet-Drafts relate to DNS. No other protocol — not HTTP, not TLS, not BGP — has as many RFCs.

This index covers the essential RFCs organized by category, with the ones you are most likely to need highlighted.

Foundational specifications

RFCYearTitleNotes
RFC 8821983Domain Names — Concepts and FacilitiesOriginal DNS architecture by Paul Mockapetris. Obsoleted by RFC 1034
RFC 8831983Domain Names — Implementation and SpecificationOriginal wire protocol. Obsoleted by RFC 1035
RFC 10341987Domain Names — Concepts and FacilitiesCurrent base spec (concepts). Describes the design, architecture, and delegation model. Still canonical after nearly 40 years
RFC 10351987Domain Names — Implementation and SpecificationCurrent base spec (wire protocol). Defines the message format, record types (A, NS, CNAME, SOA, PTR, MX, TXT), and query/response mechanism
RFC 21811997Clarifications to the DNS SpecificationResolved 8 ambiguities in RFC 1034/1035 including RRset TTL consistency, zone cuts, and valid label characters
RFC 94992023DNS TerminologyComprehensive glossary of DNS terms. The definitive reference for DNS vocabulary

Record types

RFCYearTitleNotes
RFC 10351987(see above)Defines A, NS, CNAME, SOA, PTR, MX, TXT, HINFO
RFC 27822000A DNS RR for Specifying the Location of Services (SRV)Service discovery via DNS. Updated SRV spec (obsoletes RFC 2052)
RFC 35962003DNS Extensions to Support IP Version 6Defines the AAAA record type for IPv6 addresses
RFC 66722012DNAME Redirection in the DNSDelegates entire subtrees to another domain
RFC 86592019DNS Certification Authority Authorization (CAA)Specifies which CAs may issue certificates for a domain
RFC 94602023Service Binding and Parameter Specification via DNSDefines SVCB and HTTPS record types for modern service discovery

DNSSEC

RFCYearTitleNotes
RFC 20651997Domain Name System Security ExtensionsFirst DNSSEC attempt. Obsoleted
RFC 25351999Domain Name System Security Extensions (revised)Second attempt. Also obsoleted
RFC 40332005DNS Security Introduction and RequirementsDNSSEC-bis: introduction and threat model
RFC 40342005Resource Records for DNS Security ExtensionsDNSSEC-bis: defines DNSKEY, RRSIG, NSEC, DS records
RFC 40352005Protocol Modifications for DNS Security ExtensionsDNSSEC-bis: resolver and server behavior. Defines AD and CD header bits
RFC 51552008DNS Security (DNSSEC) Hashed Authenticated Denial of ExistenceNSEC3: prevents zone enumeration via hashed names
RFC 66982012The DNS-Based Authentication of Named Entities (DANE) TLSABinds TLS certificates to domain names via DNSSEC
RFC 76722015SMTP Security via Opportunistic DANE TLSDANE for email transport security

Extension mechanisms

RFCYearTitleNotes
RFC 26711999Extension Mechanisms for DNS (EDNS0)Original EDNS spec by Paul Vixie. Obsoleted by RFC 6891
RFC 68912013Extension Mechanisms for DNS (EDNS(0))Current EDNS spec. Introduces OPT pseudo-record, extends UDP payload beyond 512 bytes
RFC 78712016Client Subnet in DNS QueriesEDNS Client Subnet (ECS) for CDN geolocation
RFC 78732016Domain Name System (DNS) CookiesLightweight transaction authentication against spoofing
RFC 78302016The EDNS(0) Padding OptionPrivacy-preserving message padding for encrypted DNS
RFC 84672018Padding Policies for EDNS(0)Recommends block-length padding (128-byte blocks)

Encrypted DNS transport

RFCYearTitleNotes
RFC 78582016Specification for DNS over Transport Layer Security (DoT)Encrypted DNS on dedicated port 853/TCP. Easy to identify and block
RFC 84842018DNS Queries over HTTPS (DoH)DNS over HTTPS on port 443. Indistinguishable from web traffic
RFC 92502022DNS over Dedicated QUIC Connections (DoQ)QUIC-based encrypted DNS on port 853/UDP. Eliminates TCP head-of-line blocking
RFC 92302022Oblivious DNS over HTTPS (ODoH)Adds proxy layer between client and resolver for privacy

Transport and operations

RFCYearTitleNotes
RFC 19951996Incremental Zone Transfer in DNS (IXFR)Efficient zone synchronization via deltas
RFC 19961996Prompt Notification of Zone Changes (NOTIFY)Push-based zone change signaling
RFC 21361997Dynamic Updates in the DNSProgrammatic record modification (OPCODE 5)
RFC 59362010DNS Zone Transfer Protocol (AXFR)Formalized full zone transfer specification
RFC 59662010DNS Transport over TCP — Implementation RequirementsMade TCP mandatory. Obsoleted by RFC 7766
RFC 77662016DNS Transport over TCP — Implementation RequirementsUpdated TCP requirements. Connection reuse via pipelining
RFC 84902018DNS Stateful Operations (DSO)Persistent session management for DNS (OPCODE 6)
RFC 91032021DNS Zone Transfer over TLSEncrypted AXFR/IXFR

Authentication

RFCYearTitleNotes
RFC 28452000Secret Key Transaction Authentication for DNS (TSIG)Original TSIG. Obsoleted by RFC 8945
RFC 36452003GSS-TSIGKerberos-based TSIG authentication (used by Active Directory)
RFC 89452019Secret Key Transaction Authentication for DNS (TSIG)Current TSIG spec. Shared-secret HMAC authentication

Modern operational improvements

RFCYearTitleNotes
RFC 80202016NXDOMAIN: There Really Is Nothing UnderneathAggressive NXDOMAIN caching. An NXDOMAIN means nothing exists below
RFC 81982017Aggressive Use of DNSSEC-Validated CacheAggressive NSEC/NSEC3 caching to synthesize negative answers
RFC 87672020Serving Stale Data to Improve DNS ResiliencyServe-stale: return expired cache entries when authoritative servers are unreachable
RFC 91562021DNS Query Name Minimisation to Improve PrivacyQNAME minimization: send only minimum labels at each resolution step
RFCYearTitleNotes
RFC 72082014Sender Policy Framework (SPF)Validates email sender IP against domain policy via TXT records
RFC 63762011DomainKeys Identified Mail (DKIM) SignaturesCryptographic email signing with public key published in DNS
RFC 74892015Domain-based Message Authentication, Reporting, and Conformance (DMARC)Policy framework combining SPF and DKIM

Service discovery

RFCYearTitleNotes
RFC 27822000SRV Records(see Record types above)
RFC 67622013Multicast DNS (mDNS)Zero-configuration name resolution on local networks (.local domain)
RFC 67632013DNS-Based Service Discovery (DNS-SD)Service discovery using PTR, SRV, and TXT records

IETF working groups

DNS standards are developed within these IETF Working Groups:

Working groupFocusStatus
DNSOPDNS Operations — operational practices, protocol clarificationsActive. 70+ RFCs published
DPRIVEDNS PRIVate Exchange — transport confidentiality (DoT, DoH, DoQ)Active
ADDAdaptive DNS Discovery — client-side resolver selectionActive
DNSSDDNS-based Service Discovery — mDNS, Bonjour at scaleActive

The RFC lifecycle

  1. Internet-Draft (I-D): Individual or WG-adopted draft, versioned, expires after 6 months
  2. Working Group Last Call: Rough consensus within the WG
  3. IETF Last Call: Broader community review
  4. IESG Review: Internet Engineering Steering Group approves publication
  5. RFC Publication: Permanent number assigned

Standards-track documents progress through: Proposed Standard then Internet Standard. The old “Draft Standard” level was eliminated by RFC 6410 in 2011.

The “-bis” pattern: when a DNS RFC needs substantial revision, the replacement is informally called a “-bis” document (e.g., “DNSSEC-bis” for RFC 4033-4035 replacing RFC 2535).