RFC 9499: DNS Terminology
In plain English — editorial summary, not part of the RFC
The Domain Name System (DNS) is defined in literally dozens of different RFCs. The terminology used by implementers and developers of DNS protocols, and by operators of DNS systems, has changed in the decades since the DNS was first defined. This document gives current definitions for many of the terms used in the DNS in a single document. This document updates RFC 2308 by clarifying the definitions of "forwarder" and "QNAME". It obsoletes RFC 8499 by adding multiple terms and clarifications. Comprehensive lists of changed and new definitions can be found in Appendices A and B.
Document record
- Document ID
- RFC9499
- Published
- March 2024
- Authors
- P. Hoffman; K. Fujiwara
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 45
- Also known as
- BCP219
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 7719 (2015)
- RFC 8499 (2019)
- RFC 9499 (2024)
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8553DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node NamesCurrent
March 2019
- RFC 8552Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute LeavesCurrent
March 2019
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 4697Observed DNS Resolution MisbehaviorUpdated
October 2006
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 10023The "_for-sale" Underscored and Globally Scoped DNS Node NameCurrent
July 2026
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?