Ondřej Surý 3e364aec2b Use sequential per-dispatch message IDs for TCP ... TCP dispentries no longer use the global QID hash table at all. Responses are matched by scanning disp->active, and sequential per-dispatch IDs (bounded by the pipelining limit) are unique within a single dispatch by construction. Since TCP delivers only data we asked for on a specific connection, the per-peer uniqueness that the global table enforced was never actually needed for TCP. DNS_DISPATCHOPT_FIXEDID is plumbed through dns_request_createraw -> get_dispatch -> dns_dispatch_createtcp so FIXEDID TCP requests always get a fresh isolated dispatch — the caller-supplied ID then cannot collide with any other in-flight query either.		2026-04-14 17:48:21 +02:00
..
formerly-text.db.in	Remove license headers from test zone files	2026-03-31 17:57:58 +02:00
named.args	Use sequential per-dispatch message IDs for TCP	2026-04-14 17:48:21 +02:00
named.conf.j2	Remove license headers from named.conf test files	2026-03-31 17:57:58 +02:00