Ondřej Surý 4f54328eaf 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. (cherry picked from commit 3e364aec2b)		2026-05-06 15:05:48 +02:00
..
ns1	Replace .in with .j2 templates for cases with namedX.conf	2025-12-10 13:43:52 +01:00
ns2	Use sequential per-dispatch message IDs for TCP	2026-05-06 15:05:48 +02:00
ns3	Replace .in with .j2 templates for cases with namedX.conf	2025-12-10 13:43:52 +01:00
ns4	Replace .in with .j2 templates for cases with namedX.conf	2025-12-10 13:43:52 +01:00
setup.sh	Replace .in with .j2 templates for cases with namedX.conf	2025-12-10 13:43:52 +01:00
tests.sh	Replace .in with .j2 templates for cases with namedX.conf	2025-12-10 13:43:52 +01:00
tests_sh_masterformat.py	Incrementally apply AXFR transfer	2024-11-26 07:17:06 +00:00