[Dnsmasq-discuss] Adding support for new Options request

[M. Ranganathan]

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 client, on a dns request, processes it and returns an
address to the client). What's a good place to start?

If anybody on this list is already doing this, please let me know.

Thanks,

Ranga

-- 
M. Ranganathan
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

[Kevin Darbyshire-Bryant]

> 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 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


signature.asc
Description: Message signed with OpenPGP
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

[Kevin Darbyshire-Bryant]

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] 168.192.in-addr.arpa to 8.8.8.8

You get the idea.

So, should I?


Cheers,

Kevin D-B

012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A



signature.asc
Description: Message signed with OpenPGP
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

[Dominik DL6ER]

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


On 15.05.2018 17:27, Kevin Darbyshire-Bryant wrote:
> 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 known to be up. Setting this flag 
> forces dnsmasq to try each query with each server strictly in the order they 
> appear in /etc/resolv.conf
> --all-servers
> By default, when dnsmasq has more than one upstream server available, it will 
> send queries to just one server. Setting this flag forces dnsmasq to send all 
> queries to all available servers. The reply from the server which answers 
> first will be returned to the original requester.
>
> I have neither of these flags set, so I’d expect dnsmasq to choose one of the 
> servers, hopefully the fastest and stick with that. 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?
>
>
> Cheers,
>
> Kevin D-B
>
> 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A
>
>
>
> ___
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss@lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

[Kevin Darbyshire-Bryant]

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 known to be up. Setting this flag 
forces dnsmasq to try each query with each server strictly in the order they 
appear in /etc/resolv.conf
--all-servers
By default, when dnsmasq has more than one upstream server available, it will 
send queries to just one server. Setting this flag forces dnsmasq to send all 
queries to all available servers. The reply from the server which answers first 
will be returned to the original requester.

I have neither of these flags set, so I’d expect dnsmasq to choose one of the 
servers, hopefully the fastest and stick with that. 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?


Cheers,

Kevin D-B

012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A



signature.asc
Description: Message signed with OpenPGP
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss