Maximum number of concurrent DNS queries reached about docker-dnsmasq HOT 6 CLOSED

I can see
using nameserver 192.168.92.1#53

This could be part of the problem, because 192.168.92., my router 1 is also using nameserver 192.168.92.125 (docker). Could this be causing loops? if so, when starting the container can I get it to explicitly not use 192.168.92.1?

Currently my router has two DNS listed for DHCP.
192.168.92.125 (docker)
192.168.92.1 (itself)

from docker-dnsmasq.

I agree that this is a loop issue unless you have a massive amount of queries going on.

• Does the error show up immediately?
• What is the router and its configuration (does itself run dnsmasq or other DNS forwarder to upstream)?

from docker-dnsmasq.

Thanks for the reply Andy, the error does show up immediately. The router is an Ubiquiti ER-x. Apart from the DNS entries provided, I dont know of any other configuration options for its own DNS that it runs.

from docker-dnsmasq.

If dnsmasq is reading /etc/resolv.conf for the upstream then maybe this host has a loop?

• Can you confirm the output of /etc/resolv.conf on the host?
• Can you try setting --dns for the container runtime to just your ISP upstream?

I'm assuming you want: client -> router -> Docker container -> upstream.

from docker-dnsmasq.

This could be part of the problem, because 192.168.92., my router 1 is also using nameserver 192.168.92.125 (docker). Could this be causing loops? if so, when starting the container can I get it to explicitly not use 192.168.92.1?

You could specify no-resolv and add server=192.168.92.125 to set upstream server list manually.

There is a dns-loop-detect option that could be tried too.

http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html

from docker-dnsmasq.

I'm going to close this as I think it is a loop issue outside the scope of this image. But feel free to reopen if you have more information and think it is an image issue still.

from docker-dnsmasq.