OK, I can belive that behaves in the way you've seen, and there's not
way to alter that.
You should try the latest release, and also configure fast-retry, that
might give your better behaviour. It's still the case that
"strict-order" is not really compatible with dealing with unreliable
upstream servers. Dnsmasq does much better at that when it can try for
an answer from any server.
Simon.
On 22/02/2023 03:38, Gomathi Shankar P S wrote:
Hi Simon,
We are using Dnsmasq v2.83
Thanks
Gomathi Shankar P S
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
