NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Intermittent DNS Errors and WiFi Issues
I have had the Orbi AX6000 for a few months now. While there are many things I love about it (great wifi coverage, great speed, looks nice, software, ease of setup, etc.), there are two very frustra...
I am experiencing DNS issues with the RBK752 on all firmwares used since purchase. Currently running the latest: V3.2.17.12_1.4.14.
On occassion the DNS request will fail and a DNS timeout error will be displayed. Causing the browser to not load the webpage. Depending on the browser, for example Chrome, the browser will do a retry.Typically then the DNS look-up will succeed and the webpage will load. However, a browser like Firefox does not attempt a second try. So you're stuck with an error page.
At first I thought it might be because of the DNS servers of my ISP. Changed the DNS settings to various public DNS servers on the router (Google/Cloudfare/etc.). However this didn't fix it. I even ran my own DNS server on a NAS to see if that would fix it. That also didn't fix the issue. The only fix currently is to bypass the entire DNS look-up done by the RBS750 by directly configuring the DNS server settings on the client device (laptop/mobile phone etc.). Or else instead of using the RBS750 in router mode, set it to AP mode. Which also bypasses the DNS server.
So the problem is actually directly related to the DNS server used by RBS750.
This could be a potential fix:
I yet have to try this. However it seems to be the most logical solution. Any solution / advice that is aimed at bypassing the DNS server on the router is not a fix nor a solution to the actual problem.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Please try the suggestion to see if it helps you out.
energie wrote:I am experiencing DNS issues with the RBK752 on all firmwares used since purchase. Currently running the latest: V3.2.17.12_1.4.14.
On occassion the DNS request will fail and a DNS timeout error will be displayed. Causing the browser to not load the webpage. Depending on the browser, for example Chrome, the browser will do a retry.Typically then the DNS look-up will succeed and the webpage will load. However, a browser like Firefox does not attempt a second try. So you're stuck with an error page.
At first I thought it might be because of the DNS servers of my ISP. Changed the DNS settings to various public DNS servers on the router (Google/Cloudfare/etc.). However this didn't fix it. I even ran my own DNS server on a NAS to see if that would fix it. That also didn't fix the issue. The only fix currently is to bypass the entire DNS look-up done by the RBS750 by directly configuring the DNS server settings on the client device (laptop/mobile phone etc.). Or else instead of using the RBS750 in router mode, set it to AP mode. Which also bypasses the DNS server.
So the problem is actually directly related to the DNS server used by RBS750.
This could be a potential fix:
I yet have to try this. However it seems to be the most logical solution. Any solution / advice that is aimed at bypassing the DNS server on the router is not a fix nor a solution to the actual problem.
The modem/router of my ISP that the RBS750 is connected to is unrelated to the problem. The modem/router from my ISP is Compal CH7465-LG (https://deviwiki.com/wiki/Compal_Broadband_Networks_CH7465LG-LC). The DNS server of the modem/router from my ISP is not in use.
I also don't have any option to enable Telnet on the RBS750. So I cannot apply the manual fix from that other thread.
Netgear should fix the DNS server on the RBS750 / firmware.
energie Completely agree that NetGear needs to fix the DNS issue in firmware.
What I think is also important to remember is I don't think the development teams drop by the forums but use support tickets. FURRYe38 I belive this is why you keep reminding us to open a support ticket besides just posting in this community forum.
I have opened a support ticket. Hopefully all the others that have posted about this issue has as well and hopefully Netgear is seeing it as a priority focus due to support count.
Fortunately the work around I've implemented, while not resolving the original issue at all, provides me a workable "work around". However, I don't want to use the work around long term as I suspect it prevents a feature of the NetGear Armor, for which I have a subscription, from providing the full benefits. Currently I suspect it's only the anti-virus software since I'm hardcoding a seperate DNS server on the workstations rather than allowing the Router to process the DNS requests and potentially using Armor filtering.
FURRYe38 I appreciate your efforts.
energie and the others, this likely is going to take some time. If the work arounds are not an acceptable solution, I'd not hesitate to return your products so you don't miss that window. Perhaps the refund process helps NetGear realize the issue is a focus item and helps with resource allocation to that issue.
