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

[pgershon]

I just started to receive a few of these errors. I had a VPN running but turned it off because of DNS issues. WAN is set to use default ISP's DNS. As I said, VPN is off. DNS Director was inactivated. I am not sure why these messages would pop up. Here are the log entries for today:

Jul 31 21:37:34 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc 5C:3E:1B4:C1:1D, status: Successful (0), rssi:-63
Jul 31 21:38:26 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind 5C:3E:1B4:C1:1D, status: 0, reason: Disassociated due to inactivity (4), rssi:-80
Aug 1 00:00:00 vpnmgr: Refreshing NordVPN country data...
Aug 1 00:00:00 vpnmgr: No changes in NordVPN country data
Aug 1 00:00:00 vpnmgr: Refreshing OpenVPN file archives...
Aug 1 00:00:05 vpnmgr: No changes in PIA OpenVPN file archives
Aug 1 00:00:05 vpnmgr: No changes in WeVPN OpenVPN file archives
Aug 1 08:44:19 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind B0:60:88:C0:3E:5B, status: 0, reason: Disassociated due to inactivity (4), rssi:-41
Aug 1 09:04:46 wlceventd: wlceventd_proc_event(530): eth7: Auth B0:60:88:C0:3E:5B, status: Successful (0), rssi:-45
Aug 1 09:04:46 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc B0:60:88:C0:3E:5B, status: Successful (0), rssi:-45
Aug 1 09:07:04 wlceventd: wlceventd_proc_event(530): eth7: Auth B4:56:E3:AB:C3:C4, status: Successful (0), rssi:0
Aug 1 09:07:04 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc B4:56:E3:AB:C3:C4, status: Successful (0), rssi:-59
Aug 1 10:11:50 dnsmasq[4749]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 1 10:21:12 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind B4:56:E3:AB:C3:C4, status: 0, reason: Disassociated due to inactivity (4), rssi:-75
Aug 1 10:32:07 wlceventd: wlceventd_proc_event(530): eth7: Auth B4:56:E3:AB:C3:C4, status: Successful (0), rssi:0
Aug 1 10:32:07 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc B4:56:E3:AB:C3:C4, status: Successful (0), rssi:-53
Aug 1 11:30:18 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind B4:56:E3:AB:C3:C4, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:-56
Aug 1 11:30:18 wlceventd: wlceventd_proc_event(511): eth7: Disassoc B4:56:E3:AB:C3:C4, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8), rssi:-56
Aug 1 11:30:20 wlceventd: wlceventd_proc_event(530): eth7: Auth B4:56:E3:AB:C3:C4, status: Successful (0), rssi:0
Aug 1 11:30:20 wlceventd: wlceventd_proc_event(540): eth7: ReAssoc B4:56:E3:AB:C3:C4, status: Successful (0), rssi:-51
Aug 1 11:30:48 wlceventd: wlceventd_proc_event(530): eth7: Auth A4:83:E7:BC:AA:11, status: Successful (0), rssi:0
Aug 1 11:30:48 wlceventd: wlceventd_proc_event(559): eth7: Assoc A4:83:E7:BC:AA:11, status: Successful (0), rssi:-51
Aug 1 11:34:12 wlceventd: wlceventd_proc_event(494): eth7: Deauth_ind A4:83:E7:BC:AA:11, status: 0, reason: Disassociated due to inactivity (4), rssi:-81
Aug 1 13:01:07 dnsmasq[4749]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 1 13:04:04 kernel: SHN Release Version: 2.0.6 9d6bb506
Aug 1 13:04:04 kernel: UDB Core Version: 0.2.20
Aug 1 13:04:04 kernel: Registered DNS Req parsing
Aug 1 13:04:04 kernel: sizeof forward pkt param = 280
Aug 1 13:04:44 kernel: udb_core lock_num = 61
Aug 1 13:04:56 kernel: SHN Release Version: 2.0.6 9d6bb506
Aug 1 13:04:56 kernel: UDB Core Version: 0.2.20
Aug 1 13:04:56 kernel: Registered DNS Req parsing
Aug 1 13:04:56 kernel: sizeof forward pkt param = 280
Aug 1 13:05:06 kernel: udb_core lock_num = 46

 

[ColinTaylor]

You'll typically see that error message when dnsmasq's upstream DNS server is not replying to queries.

 

[pgershon]

Please clarify - what is "dnsmasq's upstream DNS server"? I am not sure what dnsmasq is or what device or software is using it.

Just to add, I see the /etc/resolv.conf contains two entries:
nameserver 167.206.13.180
nameserver 167.206.13.181

This makes sense for my ISP.

Does the error message suggest something went wrong with the ISP's DNS nameserver 167.206.13.180/1?

 

[ColinTaylor]

dnsmasq is the router's built-in DNS server. It forwards incoming DNS requests from your clients to the upstream DNS servers you have defined in the router's WAN DNS settings.

This is the default configuration of the router. If you are using any third party DNS services (e.g. adblocking scripts, VPN, Unbound, PiHole, etc.) then you may have modified this behaviour.

 

[pgershon]

I had modified last week when using VPN, but I reset the WAN DNS settings to blank (to force router to use ISP). There are no third party DNS services in place (or at least there should not be any).

 

[ColinTaylor]

If that was the only time you've seen that message then I'd ignore it. It suggests that your ISP was having a temporary issue.