RFC 9199: Considerations for Large Authoritative DNS Server Operators
In plain English — editorial summary, not part of the RFC
Recent research work has explored the deployment characteristics and configuration of the Domain Name System (DNS). This document summarizes the conclusions from these research efforts and offers specific, tangible considerations or advice to authoritative DNS server operators. Authoritative server operators may wish to follow these considerations to improve their DNS services. It is possible that the results presented in this document could be applicable in a wider context than just the DNS protocol, as some of the results may generically apply to any stateless/short-duration anycasted service. This document is not an IETF consensus document: it is published for informational purposes.
Document record
- Document ID
- RFC9199
- Published
- March 2022
- Authors
- G. Moura; W. Hardaker; J. Heidemann; M. Davids
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3172Management Guidelines & Operational Requirements for the Address and Routing Parameter Area Domain ("arpa")Updated
September 2001
- RFC 3152Delegation of IP6.ARPAObsoleted
August 2001
- RFC 3026Liaison to IETF/ISOC on ENUMCurrent
January 2001
- RFC 1982Serial Number ArithmeticCurrent
August 1996
- RFC 6382Unique Origin Autonomous System Numbers (ASNs) per Node for Globally Anycasted ServicesCurrent
October 2011
- RFC 3254Definitions for talking about directoriesCurrent
April 2002
- RFC 3197Applicability Statement for DNS MIB ExtensionsCurrent
November 2001
- RFC 3130Notes from the State-Of-The-Technology: DNSSECCurrent
June 2001
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?