[GH-ISSUE #2572] RFC 8906: Correctly responding to queries in the presence of internal errors #1016

New issue

Closed

opened 2026-03-16 01:17:38 +03:00 by kerem · 1 comment

kerem commented

2026-03-16 01:17:38 +03:00

Owner

Originally created by @divergentdave on GitHub (Nov 12, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2572

RFC 8906/BCP 231 discusses the failure of DNS servers to respond to queries, or respond with the correct status code, flags, etc. Not responding to a query requires the client to wait until it times out. Incorrect handling of unrecognized query types, record types, or EDNS options requires clients to implement fallback logic, and impedes protocol evolution.

Section 8 of the document provides an extensive list of tests to perform. I spot checked Hickory DNS against 8.1.4, "Testing Unknown Opcodes", and the request timed out. I have noticed previously that errors decoding messages result in dropping them, which may result in failing other tests. These could be added to the conformance test suite.

Originally created by @divergentdave on GitHub (Nov 12, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2572 [RFC 8906/BCP 231](https://datatracker.ietf.org/doc/html/rfc8906) discusses the failure of DNS servers to respond to queries, or respond with the correct status code, flags, etc. Not responding to a query requires the client to wait until it times out. Incorrect handling of unrecognized query types, record types, or EDNS options requires clients to implement fallback logic, and impedes protocol evolution. Section 8 of the document provides an extensive list of tests to perform. I spot checked Hickory DNS against 8.1.4, "Testing Unknown Opcodes", and the request timed out. I have noticed previously that errors decoding messages result in dropping them, which may result in failing other tests. These could be added to the conformance test suite.