Note that trying all servers frequently has no performance hit, apart from the marginal extra bandwidth and upstream load. The original requestor still gets an answer as soon as the fastest server responds.
(The parameters controlling this are in src/config.h) Cheers, Simon On 15/05/18 19:57, Kevin Darbyshire-Bryant wrote: > > >> On 15 May 2018, at 17:00, Dominik DL6ER <dl...@dl6er.de> wrote: >> >> Dear Kevin, >>> Obviously it has to at least try the others occasionally to check it’s made >>> the correct choice. But I’m seeing dnsmasq make the same request to *ALL* >>> servers quite frequently and am curious as to why? >> >> dnsmasq is trying all servers quite frequently, either every 50 queries or >> 10 seconds (whatever happens first) if I'm not mistaken. This fits well to >> your observation. >> >> I changed this locally to checking every 1000 queries (or every 10 minutes) >> and this is working great (I compile dnsmasq from source). >> >> Best, >> Dominik > > Ahh, excellent Dominik, > > Thank you - I’m looking through the source now :-) > > Cheers, > > Kevin > > > > _______________________________________________ > Dnsmasq-discuss mailing list > Dnsmasqemail@example.com > http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss >
Description: OpenPGP digital signature
_______________________________________________ Dnsmasq-discuss mailing list Dnsmasqfirstname.lastname@example.org http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss