A Common Operational Problem in DNS Servers: Failure to Communicate
RFC 8906
also known as BCP 231
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['conformance', 'compliance']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "R. Bellis": changed name from "Ray Bellis" to "R. Bellis", changed affiliation from "Internet Systems Consortium" to "ISC", cleared country (was "US"), changed … Changed author "R. Bellis": changed name from "Ray Bellis" to "R. Bellis", changed affiliation from "Internet Systems Consortium" to "ISC", cleared country (was "US"), changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "M. Andrews": changed name from "Mark Andrews" to "M. Andrews", changed affiliation from "Internet Systems Consortium" to "ISC", cleared country (was "US"), changed … Changed author "M. Andrews": changed name from "Mark Andrews" to "M. Andrews", changed affiliation from "Internet Systems Consortium" to "ISC", cleared country (was "US"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2023-12-12
|
(System) | Imported membership of rfc8906 in bcp231 via sync to the rfc-index |
|
2023-12-12
|
(System) | No history of BCP231 is currently available in the datatracker before this point |
|
2021-12-15
|
(System) | Received changes through RFC Editor sync (added Errata tag, added Verified Errata tag) |
|
2020-09-22
|
(System) | Received changes through RFC Editor sync (created alias RFC 8906, changed title to 'A Common Operational Problem in DNS Servers: Failure to Communicate', changed … Received changes through RFC Editor sync (created alias RFC 8906, changed title to 'A Common Operational Problem in DNS Servers: Failure to Communicate', changed abstract to '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.', changed pages to 24, changed standardization level to Best Current Practice, changed state to RFC, added RFC published event at 2020-09-22, changed IESG state to RFC Published, created alias BCP 231) |
|
2020-09-22
|
(System) | RFC published |