When the hickory-resolver name server pool implementation receives an upstream response with the TC (truncated) header bit set, it re-queues the request to the same nameserver to retry with UDP transport disabled. However, the retry arm never inspects the transport that just answered and carries no iteration counter. An authoritative server that sets TC=1 on every available transport keeps the resolver spinning on one persistent TCP connection until the 5s per-request wall-clock deadline expires.
Qifan Zhang, Palo Alto Networks
{
"cwe_ids": [
"CWE-400",
"CWE-406",
"CWE-835"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-05T22:55:10Z",
"nvd_published_at": null,
"severity": "HIGH"
}