[Dnsmasq-discuss] Adding support for new Options request

Hello! I want to modify dnsmasq to add support for Options 161 ( the new Options request as defined in the IETF MUD standard ). For this, the client sends the Options along with URL (a cstring). I am trying to find a similar function in dnsmasq (one that receives some information from the

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?

[Dnsmasq-discuss] dnssec queries with --bogus-priv

Here’s another one of those innocent questions caused by looking at a logfile :-) I have ‘—bogus-priv’ set so in theory I’m not going to ask upstream questions about RFC1918 addresses, which I don’t, except I see these…. dnssec-query[DS] 10.in-addr.arpa to 8.8.8.8 dnssec-query[DS]

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