[Dnsmasq-discuss] Max num of concurrent dns reached troubleshootting

[john doe]

Hi Simon, bottom posting.

On 1/18/2018 11:16 PM, Simon Kelley wrote:
> Use log-queries to see what's happening. You should be looking for
> outgoing queries which don't see an answer.
> 
> 
> Cheers,
> 
> Simon.
> 
> 
> On 16/01/18 15:34, john doe wrote:
>> Hi,
>>
>> First of all a big thank you for dnsmasq.
>> It's an easy dhcp, dns, read only tftp server to configure.
>>
>>
>> On a perimeterfirewall the logs gets flutted with the following:
>> Jan 15 22:32:23 dnsmasq[546]: Maximum number of concurrent DNS queries
>> reached (max: 150)
>> Jan 16 00:06:34 dnsmasq[546]: Maximum number of concurrent DNS queries
>> reached (max: 150)
>>
>> Note that only one server (gateway) is connected to the perimeterfirewall.
>>
>> How can I determine wherein lies  the problem (perimeterfirewall or
>> gateway)?
>>
>> In other words: what should I do to understand what's triggering those
>> messages.
>>
>> Both the gateway and the perimeterfirewall are on Debian 9 using:
>> dnsmasq, systemd-resolved and resolvconf(8).
>>
>> -John
> 
> 
> 
> 
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
> 

Thanks for your answer.
The issue I'm facing is not occuring all the time and I'm wandering if 
'log-queries' could be only passed to dnsmasq when those messages are 
logged.

In other words: How can I pass options to an already running instance of 
dnsmasq.

I really appriciate any help! :)

-- 
John Doe