Hi @dunxd 

Thanks for posting in our business forum.

TBH, I don't wanna reply to this kind of thread as there is no other information provided. I don't think anyone else would provide a constructive suggestion.

How many devices do you have?

How do you even verify it is a DNS problem with the router itself?

And, free DNS servers may limit the queries speed with a daily threshold.

Have you Wiresharked to verify that the DNS query is not replied to timely and leading to the "stopped working"?

Hi @dunxd 

Thanks for posting in our business forum.

dunxd wrote

This is the first ER7212 I have deployed. I was at the site myself for the deployment and what I observed was as follows:

 

Initially internet access worked fine for clients. However, the following morning staff in the office reported no internet. I connected my laptop directly to the ER7212 by ethernet cable and websites were not available. nslookup resulted in no response from the DNS server - which was the ER7212s IP address. Pinging public IP addresses functioned fine, and the ER7212 was connected to the TP-Link cloud so clearly no issue with the internet connection. Ping to the IP address of the ER7212 worked, so no local connectivity issue. Restarting the ER7212 resolved the issue, but it repeated after an hour. At this point I changed the DHCP setting on the ER7212 to issue the upstream DNS servers' IP addresses to DHCP clients and we have seen no further issues. ISP DNS services, 8.8.8.8 and 1.1.1.1 have no limits so this isn't relevant.

 

Hence my conclusion that the ER7212 cannot reliably handle DNS functions for this location. There are 15 clients in the office so not particularly large. I have not seen any such problems with DNS on ER605 or ER7206 at other sites. I also note that the memory usage on the ER7212 is constantly around 80%, so perhaps there is a resource issue with a device running routing/firewall functions and a controller.

 

OC200, SG2210P and ER7206/ER605 has been reliable everywhere, but a single box is attractive. If others can report a more reliable experience I would certainly dig a bit deeper. Id love to see DNS Proxy on this device, but perhaps it is underpowered. Is the 1.6 hardware better than the v1 I received? Should I be exchanging?

Steps make sense.

192.168.0.1 can resolve but if the domain is not listed or cannot be answered, it'll query the upstream DNS server.

So what do you set on the upstream(WAN) DNS when the described issue happened?

Try to set the WAN DNS to the mentioned servers and will this be improved?

And as you can see the resources of this device are reaching their hardware limit, for this product, is approaching its end. We will have trouble adding more functions to it in future firmware upgrades.

V1.6 equals V1.