[GH-ISSUE #2608] Truncated responses may be cached #1026

New issue

Closed

opened 2026-03-16 01:18:48 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 01:18:48 +03:00

Owner

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

Currently, if NameServerPool gets a truncated response, it attempts to retry the query via TCP. However, if that fails, it returns the truncated response, and there is insufficient handling of truncated responses downstream. It may be cached and served in response to subsequent queries, which violates a 'should not' in RFC 1035 section 7.4.

Originally created by @divergentdave on GitHub (Nov 22, 2024). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2608 Currently, if `NameServerPool` gets a truncated response, it attempts to retry the query via TCP. However, if that fails, it returns the truncated response, and there is insufficient handling of truncated responses downstream. It may be cached and served in response to subsequent queries, which violates a 'should not' in RFC 1035 section 7.4.