Issue mentioned above seems to be the consequence of a new feature of Chrome: Using its own, integrated dns-client, instead of relying on the OS provided one.. Which can not be disabled, in recent Chrome versions. And this integrated dns-client does something called “supervise UDP-entropy”. Which checks the entropy of used UDP-ports. If considered to be too low, switch to TCP. And on my Win 10 (and on Win 11, too, I guess), this check hits. Thus, either to drop Chrome, or to live with it. BUT then, max no. of parallel TCP conns for dnsmasq to be increased, i.e. “max-tcp-connections=30”, cause I see in my logs:
Apr 15 03:00:00 dnsmasq[15177]: child processes for TCP requests: in use 0, highest since last SIGUSR1 23, max allowed 30.