Menu
What's new
By:
Filters Better Search

Maximum number of concurrent DNS queries reached (max: 150)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

H

hazartilirot

Occasional Visitor
Good day,

I've upgraded our router to the latest firmware 384.19. Could any one tell me what the messages mean? I'm a non-linux user.... Does it mean that one of devices is flooding? How can I figure out which device is flooding? Thanks

Code: 
Aug 28 17:41:13 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:19 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:51 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:57 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:03 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:13 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:36 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:41 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:02 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:10 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:16 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:22 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:28 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:07 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:30 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:40 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:47 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:53 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:04 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:10 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:18 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:24 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:42 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:00 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:06 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:16 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:22 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:28 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:35 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:41 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:47 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:03 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:11 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:18 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:27 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:33 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:39 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:45 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:51 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:57 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:48:07 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
 
Something is spamming the router's DNS server. That could be a rogue device on your network in which case the quickest way to identify it would be to power off all of your clients and then turn them back on one at a time. Alternatively it might indicate that there is something wrong with your internet connection and your clients are having to resend their queries because they are not getting a response quickly enough.
 
Thank you for your reply. Yep, I do have some issues with ISP. For some reason DNS I get from my Internet provider doesn't resolve URL. However, I solved the issue when I selected DNS-over-TLS (DoT) in DNS Privacy Protocol and added Google's DNS addresses.
Everything seems to be working.... but my router is overwhelmed with those messages. I think.... my ISP is spamming my router. Dunno.
 
Your router should not be responding to any DNS requests from outside of your private network. So, ISP couldn't spam your DNS server.
 
hazartilirot said:
Good day,

I've upgraded our router to the latest firmware 384.19. Could any one tell me what the messages mean? I'm a non-linux user.... Does it mean that one of devices is flooding? How can I figure out which device is flooding? Thanks

Code: 
Aug 28 17:41:13 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:19 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:51 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:41:57 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:03 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:13 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:36 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:42:41 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:02 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:10 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:16 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:22 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:28 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:43:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:07 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:30 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:40 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:47 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:44:53 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:04 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:10 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:18 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:24 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:42 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:45:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:00 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:06 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:16 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:22 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:28 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:35 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:41 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:47 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:46:54 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:03 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:11 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:18 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:27 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:33 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:39 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:45 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:51 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:47:57 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 28 17:48:07 dnsmasq[237]: Maximum number of concurrent DNS queries reached (max: 150)
Click to expand...
which model router? that might help...
 
If you install AMTM (over SSH) it makes it pretty straightforward editing your DNSmasq config to up the maximum. There might also be a spot somewhere in the GUI to do it.
 
Do you have any DNS blocking scripts or a pi hole by any chance?

I'd check the DNS filter option under LAN to see if there is anything used.
 
Vexira said:
Could you test something like changing wan DNS to open DNS see if that makes a difference.
Click to expand...
Well, I added dns-forward-max=1024 into dnsmasq.conf.add the problem has gone.

Those queries sends my QNAP (nas)..... I don't know the reason though when I switched it off from the LAN port - messages with DNS queries stop appearing.
 
hazartilirot said:
Well, I added dns-forward-max=1024 into dnsmasq.conf.add the problem has gone.

Those queries sends my QNAP (nas)..... I don't know the reason though when I switched it off from the LAN port - messages with DNS queries stop appearing.
Click to expand...
Did you try rebooting the Nas?
 
hazartilirot said:
Well, I added dns-forward-max=1024 into dnsmasq.conf.add the problem has gone.

Those queries sends my QNAP (nas)..... I don't know the reason though when I switched it off from the LAN port - messages with DNS queries stop appearing.
Click to expand...
So the problem hasn't actually gone you've just hidden it. Presumably the NAS is still spamming the DNS server.

You could temporarily add the following line to your dnsmasq.conf.add file to see what it is doing in the router's syslog.
Code: 
log-queries
Be warned that is will create a lot of log entries normally so it's best to do this with all your other clients disconnected from the network.
 
That address seems to be related to an open source anti-virus product (ClamavNet). I've never used that and I don't own a QNAP so I don't know whether that amount of DNS traffic is normal. It would be worth checking the AV settings on the NAS to ensure it's configured correctly.

Is the address returned in the log a valid address or is it being blocked by the router (e.g. returns 0.0.0.0 or 192.168.x.y)?
 
Well, I think I figured out what causes the issue. It seems to be Resilio Sync (a kind of a backup application working on Bittorrent protocol)

I've already turned off all Aniviruses, also Resilio Sync though.... those lines are still coming:

192.168.10.9 - is IP address of QNAP

Code: 
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[PTR] 49.10.168.192.in-addr.arpa from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: DHCP 192.168.10.49 is notebook-pc.anika.local
Aug 31 19:43:41 dnsmasq[238]: query[PTR] 221.10.168.192.in-addr.arpa from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: config 192.168.10.221 is NXDOMAIN
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.15.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.15.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.ip.188.230.15.16.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.ip.188.230.15.16.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: Maximum number of concurrent DNS queries reached (max: 150)
 
hazartilirot said:
Well, I think I figured out what causes the issue. It seems to be Resilio Sync (a kind of a backup application working on Bittorrent protocol)

I've already turned off all Aniviruses, also Resilio Sync though.... those lines are still coming:

192.168.10.9 - is IP address of QNAP

Code: 
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[PTR] 49.10.168.192.in-addr.arpa from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: DHCP 192.168.10.49 is notebook-pc.anika.local
Aug 31 19:43:41 dnsmasq[238]: query[PTR] 221.10.168.192.in-addr.arpa from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: config 192.168.10.221 is NXDOMAIN
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.15.17.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.15.17.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: query[SRV] _bittorrent-tracker._tcp.ip.188.230.15.16.volia.net from 192.168.10.9
Aug 31 19:43:41 dnsmasq[238]: forwarded _bittorrent-tracker._tcp.ip.188.230.15.16.volia.net to 127.0.1.1
Aug 31 19:43:41 dnsmasq[238]: Maximum number of concurrent DNS queries reached (max: 150)
Click to expand...
By default NXDOMAIN lookups are not cached. To avoid NXDOMAIN lookups from being unnecesarily forwarded, I added the following to /jffs/scripts/dnsmasq.postconf
Code: 
pc_append "neg-ttl=3600" $CONFIG
pc_delete "no-negcache" $CONFIG
 
You must log in or register to reply here.

Similar threads

B
Maximum number of concurrent DNS queries reached (max: 150)
Replies
5
Views
1K
heysoundude
heysoundude
P
dnsmasq: Maximum number of concurrent DNS queries reached (max: 150)
Replies
5
Views
3K
ColinTaylor
C
P
AC86U loosing internet despite saying it has internet
Replies
0
Views
619
PT25
P
L
"Maximum number of concurrent DNS queries" with strange lb._dns-sd._udp. ... .in-addr.arpa reverse DNS queries (has Pi running Adguard Home + Unbound)
Replies
2
Views
715
loveleeyoungae
L
T
New error message
Replies
15
Views
2K
Kal1975
K
Similar threads
Thread starter Title Forum Replies Date
B Maximum number of concurrent DNS queries reached (max: 150) Asuswrt-Merlin 5
L "Maximum number of concurrent DNS queries" with strange lb._dns-sd._udp. ... .in-addr.arpa reverse DNS queries (has Pi running Adguard Home + Unbound) Asuswrt-Merlin 2
vlord Wireguard max number of clients Asuswrt-Merlin 3
J Max number of open NAT connections on GT-AXE16000 and GT-BE98 Asuswrt-Merlin 9

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 699 (members: 20, guests: 679)
Top