A Common Operational Problem in DNS Servers: Failure to Communicate
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 24
- Abstract
- The DNS is a query/response protocol. Failing to respond to queries, or responding incorrectly, causes both immediate operational problems and long-term problems with protocol development. This document identifies a number of common kinds of queries to which some servers either fail to respond or respond incorrectly. This document also suggests procedures for zone operators to apply to identify and remediate the problem. The document does not look at the DNS data itself, just the structure of the responses.
- Publication Date
- 2020-09-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC8906- Link
- https://doi.org/10.17487/RFC8906
- Author(s)
- Mark P. AndrewsRay Bellis
- Keyword(s)
- Conformance, Compliance
Latest version of IETF RFC 8906
Document Versions — IETF RFC 8906
-
▶ IETF RFC 8906 (2020-09-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 1034 [Active*]
- IETF RFC 1035 [Active, Amended*]
- IETF RFC 3225 [Active*]
- IETF RFC 4035 [Active*]
- IETF RFC 6840 [Active*]
- IETF RFC 6891 [Active*]
- IETF RFC 6895 [Active*]
- IETF RFC 7766 [Active*]
Bibliographic Reference(s)
- "Internet Systems Consortuim", <https://www.isc.org/>. EXTERNAL
- IANA, "Domain Name System (DNS) Parameters", <https://www.iana.org/assignments/dns-parameters/>. EXTERNAL
- IETF RFC 2671 [Superseded*]
- IETF RFC 3597 [Active*]
- IETF RFC 5001 [Active*]
- RFC7314 — RFC7314 EXTERNAL
- IETF RFC 7871 [Active*]
- IETF RFC 7873 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC8906.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 8906, A Common Operational Problem in DNS Servers: Failure to Communicate. Available at https://doi.org/10.17487/RFC8906
Snippet:
IETF RFC 8906, A Common Operational Problem in DNS Servers: Failure to Communicate. Available at https://doi.org/10.17487/RFC8906
HTML (ISO 690 compliant)
Preview:
IETF RFC 8906, A Common Operational Problem in DNS Servers: Failure to Communicate. Available at https://doi.org/10.17487/RFC8906
Snippet:
<span class="citation"><cite>IETF RFC 8906</cite>, A Common Operational Problem in DNS Servers: Failure to Communicate. Available at <a href="https://doi.org/10.17487/RFC8906" target="_blank" rel="noopener">https://doi.org/10.17487/RFC8906</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 8906, A Common Operational Problem in DNS Servers: Failure to Communicate
doi: 10.17487/RFC8906
url: https://doi.org/10.17487/RFC8906
doi: 10.17487/RFC8906
url: https://doi.org/10.17487/RFC8906
Snippet:
<li> <cite id="bib-rfc8906">IETF RFC 8906</cite>, A Common Operational Problem in DNS Servers: Failure to Communicate <span class="doi">10.17487/RFC8906</span> </li>
Referenced By
- IETF RFC 9210 [Active*]
- IETF RFC 9619 [Active*]