[GH-ISSUE #178] [Resolver] Promote to TCP on truncated responses #83

Closed
opened 2026-03-07 22:18:39 +03:00 by kerem · 1 comment
Owner

Originally created by @bluejekyll on GitHub (Aug 22, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/178

Some upstream resolvers/servers will respond with truncation specified if a dns packet is larger than 512 bytes. The resolver should be configured to switch to TCP in these cases. This requires adding some logic to limit the request to TCP only nameservers from the NameServerPool.

Originally created by @bluejekyll on GitHub (Aug 22, 2017). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/178 Some upstream resolvers/servers will respond with truncation specified if a dns packet is larger than 512 bytes. The resolver should be configured to switch to TCP in these cases. This requires adding some logic to limit the request to TCP only nameservers from the NameServerPool.
kerem 2026-03-07 22:18:39 +03:00
Author
Owner

@bluejekyll commented on GitHub (Sep 21, 2017):

Fixed in #189

<!-- gh-comment-id:331055554 --> @bluejekyll commented on GitHub (Sep 21, 2017): Fixed in #189
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#83
No description provided.