This is a quirk of dnstt: dnstt fills each DNS response with as many downstream packets as fit, stashing overflow, and waits up to maxResponseDelay for data. /dnstt/dnstt-server/main.go:81 /dnstt/dnstt-server/main.go:700
- Benefit: (possibly) improves downstream goodput and reduces response count by amortizing TXT and header overhead.
/dnstt/dnstt-server/main.go:734
- Benefit: fewer responses can reduce resolver rate-limit pressure and server CPU per byte.
- Risk: adds latency and jitter (up to the delay timer) and can hurt interactive traffic and mislead congestion control algorithm.
/dnstt/dnstt-server/main.go:81
- Risk: larger responses are more likely to hit payload limits, causing truncation or wasted data.
/dnstt/dnstt-server/main.go:805
This is a quirk of dnstt: dnstt fills each DNS response with as many downstream packets as fit, stashing overflow, and waits up to maxResponseDelay for data.
/dnstt/dnstt-server/main.go:81/dnstt/dnstt-server/main.go:700/dnstt/dnstt-server/main.go:734/dnstt/dnstt-server/main.go:81/dnstt/dnstt-server/main.go:805