Re: [Dnsmasq-discuss] upstream server selection algorithm - bug?

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

Re: [Dnsmasq-discuss] upstream server selection algorithm - bug?

> On 15 May 2018, at 17:00, Dominik DL6ER 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?

Re: [Dnsmasq-discuss] upstream server selection algorithm - bug?

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

[Dnsmasq-discuss] upstream server selection algorithm - bug?

This is one of my classic ‘look in a logfile…. h’ moments. dnsmasq is configured with 4 upstream resolvers, google, both IPv4 & 6. Manpage states: -o, --strict-order By default, dnsmasq will send queries to any of the upstream servers it knows about and tries to favour servers that are