I've been using it for a few years, and recently saw the following in my logs:
user.err ddns-scripts[11182]: glddns: cURL Error: '6'
daemon.warn dnsmasq[14661]: Maximum number of concurrent DNS queries reached (max: 150)
The reason I was even looking at logs is because of serious network problem that have been esacalating over the past few months. I think it's been related to my router, but I can't be sure yet.
I am using the DNS, he's. At different GL.iNet routers.
But 150 concurrent queries seems very a lot.
I don't know if the message comes from the DDNS or the DNS service at the router. I would say the last one.
Seems the DNS requests reach the max limitation.
Pls run this command to restart this service and try again:
/etc/init.d/dnsmasq restart
I'm not really interested in a one-time fix, is there any way to prevent this?
I'm having so much network trouble that I hard-reboot at least once a day anyway.
I've disabled dynamic DNS too until I sort out reliability problems.
Not a one-time fix, this command is just used to restart the dnsmasq process, which used to handle dns request.
In this case, there are too many dns request in your local network that this process would not handle the others, which result in the dynamic DNS fail to get the reply.
May I know if you have too many clients, or IoT devices that requesting the DNS at the same time? Or maybe the DNS server you setup is a bit slower to give the reply.
I wouldn't say I have unusually many clients, but if too many DNS requests, how do I know where there're coming from?
Anyway, this is getting off-track from my real issue, as it seems I may have categorized this wrongly. I'm not concerned with dynamic DNS specifically (although I may be in future), but I've disabled it in meantime.
I'm getting internet outages at least every day, that I think may be due to the router, so could the error I listed initially be a possible cause?