[Dnsmasq-discuss] Suggestion to increase default for max-tcp-connections

Simon Kelley simon at thekelleys.org.uk
Tue Apr 21 21:37:04 UTC 2026


I bumped the default to 30. That looks sensible?



Simon.

On 21/04/2026 14:17, reiner otto via Dnsmasq-discuss wrote:
> Scenario:
> dnsmasq running on openwrt box, to provide dhcp/dns for local network, Win 10/11 client machine, Chrome browser.
> Issue:
> child processes for TCP requests: in use 0, highest since last SIGUSR1 24, max allowed 30. #from dnsmasq.log on openwrt-box
> 
> Reason: Some recent change of Chrome, now to use built-in dns-client instead of OS-provided client. (This change rather tricky to be disabled.) In case, Chrome decides, that entropy of host system regarding outgoing udp-port for dns query is not good enough,
> Chrome switches to DNS via TCP.
> Which might cause bursts of DNS-requests, being throttled by actual default max-tcp-connections=20.
> Probably, this behaviour was introduced to make dns poisoning more difficult.
> 
> Regards,
> 
> Reiner
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
> 




More information about the Dnsmasq-discuss mailing list