NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
msinex
Jul 27, 2020Apprentice
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 frustrating issues that pop up intermittently across my network that are extremely frustrating and causing me to consider taking the unit back.
I am continuing to have intermittent DNS errors across multiple devices and different web browsers. I basically receive some sort of name resolution error based on the system (have seen in on Windows 10, my work win7 device, a Rasberry Pi device, even once on my Nintendo switch). This has occured on mahcines both on WiFi and connected via ethernet. All I have to do is refresh the browser and it usually connects immediately. I have upgraded the router and satellites up to V3.2.15.25 and still facing the same issue. I downgraded back to my old Nighthawk router, and didn't see the same issue, so it's definately the router. I shifted the DNS from my ISP (Spectrum gigabit) to google DNS, and faced the same issue. It certainly isn't constant, but maybe happens once every 15-30 minutes. I leave my Raspberry Pi on because it runs a bulletin board display that refreshes every five minutes, and I come back to it and see a DNS error 1-2 times a day.
As of a few weeks ago, I'm not also getting WiFi issues with multiple different iOS devices (5 different ones). I will pick up a device and try to connect to the internet, and it times out even though it is connected to the wifi. I can turn on Airplane mode for a split second and turn it back off, and when it reconnects back to the WiFi I can connect to the internet just fine.
I have tried to powercycle everything and even tried to reset and rebuild the router setup, and still run into the same issues. Any advice you can offer here would be greatly appreciated!
578 Replies
I and other Orbi AX owners have seen these intermittent DNS failures as well: https://community.netgear.com/t5/Orbi-AX/RBR850-frequently-issuing-DNS-REFUSED-responses/m-p/1926207/highlight/true#M4399
I don't believe that there is a fix available yet. For my Windows laptop I'm able to work around the issue by changing the Windows network's TCP/IP properties to not obtain a DNS server automatically (i.e., use the Orbi's DNS settings) and instead hardcoded 8.8.8.8 / 8.8.4.4 (Google DNS). Someone else in the above thread said they did the same for their iPhone and saw similar improvement.
- msinexApprentice
Thanks for the reply Mikey94025 , I will try that solution today on my main PC and see if that helps and make sure to add myself to the other discussion as well. It's both reassuring and frustrating that I'm not the only one with the DNS issues. It sounds like it isn't just me, but pretty frustrating to get bugs with something as basic as DNS from such an expensive router option. I will come back and let you know how this solution works at least on the one computer, but hopefully netgear can address the issue.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
- msinexApprentice
Thanks for the reply FURRYe38 , my ISP is spectrum and the modem is a Spectrum branded with model e31u2v1. This link shows the picture and an overview from someone else - https://larrytalkstech.com/the-spectrum-mystery-modem-e31_2v1/
Some DNS issues come from the ISP side. I would make contact with the ISP to see if they are noticing anything. Make changes on the Orbi RBR for custom DNS addresses as well to see if this changes anything.
I don't see any DNS issues with mine however I'm on a different ISP and use a different modem.
:smileywink:
FURRYe38 wrote:msinex Ace321 filmnikon rgautier arlomike Blanca_O
New FW however nothing mentioned about DNS issues. Maybe something to try:
I just upgraded to V3.2.16.22_1.4.9 and soon encountered the intermittent DNS issue, so doesn't appear fixed for me. I have a browser bookmark for this forum and when I visit it, intermittently see a Netgear "authentication failed" page instead of the list of discussions. I believe this intermittent behavior corresponds to the intermittent DNS issue. I also see various browser links fail, or retry and then succeed, due to this issue.
Has a factory reset and setup from scratch been performed since last FW update?
Mikey94025 wrote:I just upgraded to V3.2.16.22_1.4.9 and soon encountered the intermittent DNS issue, so doesn't appear fixed for me. I have a browser bookmark for this forum and when I visit it, intermittently see a Netgear "authentication failed" page instead of the list of discussions. I believe this intermittent behavior corresponds to the intermittent DNS issue. I also see various browser links fail, or retry and then succeed, due to this issue.
- FarmerBob1Luminary
For a long time there have been DNS issues with Centurylink on all service levels, mostly DSL and vDSL. I learned about it when I stumbled on a thread on DSLReports(dot)com discussing it. Since I use a secure private DNS on my Fiber service, I have not had any DNS issues. The only connection problems I have had are browsers not functioning properly. That in itself can be misconstruded as DNS issues. I have noticed this more so with the Firefox family and spinoffs. Chrome, Opera, Brave, Vivaldi, Canari and other non-FF have been good at dealing with most anything.
When I have suggested trying a non-CL DNSs, it seemed to be the solution. So as Furry suggested that many DNS issues are ISP related. I have found and seen others find that is mostly true. Although when troubleshooting every so often I have to set my RBR850 in default "get what is given out" to connect. But that is not often and I change it soon after.
I have enough devices and applications that would fail letting me know there is an issue and to date I haven't seen anything that would lead me to think I have a problem. There's other more obvious things that have been popping up.
- msinexApprentice
Only thing I would add is that it was a combination of the Orbi and the cable ISP. I had the same ISP/Model with a Nighthawk mesh setup and had absolutely no issue whatsoever. The DNS issues only came up once I shifted to Orbi. Now that I have shifted to the fiber ISP, I haven't had any DNS issues for a full week now. I still don't understand what the issue was, though.
- rgautierApprentice
I'm on Verizon FiOS - never had a problem with my Nighthawk, and am still getting dropouts. I've tried disabling IPv6, I've tried switching DNS to CloudFlare, I've completely reset the router after the last flash update and re-set it up. Looking at the debug outputs, it appears that the daemons for the Armor stuff is still running, even though I have that disabled, and it's probably got something to do with the issues - but I don't know enough to say so for sure.
Still get random freezes and DNS dropout that last about 2 seconds per happenstance.
Would love to get into the router to watch the debug logs and fix the broken thing (whatever it is), but have been unable to enable telnet or otherwise connect to it except through the interface.
Again, LOVE the radio coverage and the backhaul speeds of WiFi6 - but SOMETHING is broken in this, and my money is on dnsmasq.
Also my 8 series didn't come with Armor, it was adding in FW later on.
Anyone with a 8 series Orbi having this problem wanna give this a try?
- Ace321ApprenticeI have been testing beta version (same version number) on 753 series and my dns issues seem to be resolved
Checking to see how yours is working and are you still seeing any DNS issue?
Ace321 wrote:
I have been testing beta version (same version number) on 753 series and my dns issues seem to be resolved
- DNS_PROBE_FAILLuminary
Interesting. When I try updating from the web interface on my orbis, it shows no firmeware update available when I'm on V3.2.16.22_1.4.9
This link shows 3.2.17.12 is available and it's not marked as beta, it's an official release.
Orbi RBK852 | WiFi System | NETGEAR Support
I'll test later today with IPv6 enabled first, then disable IPv6, leaving AX enabled and see how things go.
IT may not be up on there auto update servers yet. But its available for manual download and manual installation. It's not a beta.
- GarwoofooApprentice
I just wanted to add my voice to those affected by this problem. I've had the Orbi RBR850 with two satellites for a couple of months now, and while the coverage and speed is everything I hoped it would be, I'm getting constant DNS issues of the type described in this thread. The issues are so apparent, and so consistent, that I'm surprised the product is sold in this state, least of all that they can issue new firmware releases that don't resolve this issue.
I'm still using the latest firmware available through the device itself (3.2.16.22) - I see from comments here that the newer version available for download doesn't resolve this issue so I haven't yet installed that one. If it did fix this, I would install it right away.
For now the only fix I've found (and it is a 100% fix) is to manually set the DNS servers on each device rather than relying on the Orbi to do it. I'm using Google's DNS servers (8.8.8.8 and 8.8.4.4). That's obviously a nuisance and shouldn't be necessary but I'm gradually getting round all the devices in my house. At least that fix makes this product usable, as without it, I'd say it certainly is not fit for purpose.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
Try the newer FW version and see.
Please make contact with NG support to express your concerns and them them know what your having problems with.
Garwoofoo wrote:I just wanted to add my voice to those affected by this problem. I've had the Orbi RBR850 with two satellites for a couple of months now, and while the coverage and speed is everything I hoped it would be, I'm getting constant DNS issues of the type described in this thread. The issues are so apparent, and so consistent, that I'm surprised the product is sold in this state, least of all that they can issue new firmware releases that don't resolve this issue.
I'm still using the latest firmware available through the device itself (3.2.16.22) - I see from comments here that the newer version available for download doesn't resolve this issue so I haven't yet installed that one. If it did fix this, I would install it right away.
For now the only fix I've found (and it is a 100% fix) is to manually set the DNS servers on each device rather than relying on the Orbi to do it. I'm using Google's DNS servers (8.8.8.8 and 8.8.4.4). That's obviously a nuisance and shouldn't be necessary but I'm gradually getting round all the devices in my house. At least that fix makes this product usable, as without it, I'd say it certainly is not fit for purpose.
- GarwoofooApprentice
It's a Virgin Media Superhub 3 (I'm in the UK).
I'll upgrade the firmware and see what happens but I haven't seen anyone at all reporting that it fixes this problem so I'm not expecting anything. I'll let support know of my issues.
At this point I'm wondering if I'd be better off running the Orbi in AP mode and letting the Virgin Media router handle DNS requests.
- GarwoofooApprentice
So over this weekend I have reverted to using my Virgin Media Superhub as my main router, and configured my Orbi as an access point. Everything is now working fine and I have no DNS issues any more. Wireless speeds are at least as fast as they were before (in fact the Orbi app is reporting slightly faster link speeds for many of my devices). I've got all my wired devices coming into my Orbi so I can still use the Orbi app to monitor what is attached to my network; the only functionality I've lost is the ability to control internet access on a per-device basis, which isn't something I will particularly miss.
I'm frustrated I've had to do this but at least my network is all working now and I still have the mesh functionality of the Orbi for my wifi connections. Good luck to everyone else out there still struggling with this very significant fault with the Orbi equipment.
(Weirdly, the first time I set this configuration up, my Xbox was reporting Double NAT issues. That should have been impossible with my Orbi set to AP mode. I factory reset everything and set it all up carefully in the right order one device at a time, and now it's all working OK. There is something very strange going on here, maybe some incompatibility between the Virgin Media equipment and the Orbi, but I have no idea what it might be).
- DNS_PROBE_FAILLuminary
To date the only things that provide a workaround are:
1 - Use IPv6 for clients that support it (doesn't work for IPv4 clients, which include many TV's, media players, thermostats, BBQ grills, home automation, internet filters and other IoT devices)
2 - Bypass/disable DNS functionality of the Orbi system entirely. (Basically using another system for DNS such as your internet router/modem, or manually assigning DNS servers on each client which has it's own downsides)
(FYI, My much older Orbi RBR50 system has none of these DNS issues, it's just slower.)
RUSHING WIFI6 SYSTEMS TO MARKET is the root cause of these problems.
Other companies have also rushed their code development in the goldrush to sell consumers WiFi6 gear. I tried Asus's incredible mesh wifi system and the interface and controls were unreal... light years beyond the Orbi interface and far better security. But the entire system reset several times per day, dropping every client off of the network due to it's own bugs (NTP/time issues causing router to reset date and blow it's own mind).
Apparently also the Alien mesh system from Ubiquity has it's share of stability problems as well.
This is what happens when you rush products to market, thinking you'll just fix the issues in later code. That is easier said than done.
Netgear, it's time to fix this. Everyone still in the free 90 day support window should open a support case with Netgear on this.
Well the first time this was reported was last summer, 7/2020. Orbi AX released fall/winter of 2019. This particular problems hadn't been seen back then. So this would not be a rush to market relation.
Also most of these issues seem mostly with users having gateway modems vs stand alone modems. Since I first go Orbi AX, it has never experienced any problems with NGs stand alone modems or the CAX80 that i have and tested with in both router and modem only modes.
Ya, NG needs to get this fix for those having this problem with either gateway modems or not.
- energieLuminary
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.
- energieLuminary
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.
- TobamoryTutor
I have to admit guys I bought 2 RBK852 a few months ago and it's been nothing but junk, constant DNS issues even when using cloud flare or Google it's still an issue, the main issue is WiFi drops, all devices are still connected but just no internet at all only off and on of the WiFi does it come back alive, after 4 months I've had enough, I've popped back in my mesh zyxel multi x and I'm back to bullet proof. I initially thought it was Apple devices but my PS5 right near a possible win on Apex legends WiFi dropped. Enough was enough.... all hardwired items are fine other than sporadic DNS issues no webpage for an instant then it refreshes...
very poor NETGEAR I'm going to create a ticket and try get these swapped but I guess it's firmware or poor development...
after reading 11 pages of people looking at logs telnetting etc honestly this thing should work, the Zyxels I have just work never fail I just wanted wifi6...
does anybody get this issue in access point mode? I've not tried that or is it purely as a modem it's doing it. And why NETGEAR did dns with some proxy thing out the box daft...if I wanted a proxy I'd have a business and zscaler
Users have reported the system works better when in AP mode.
What ISP modem/gateway/ONT do you have connected to the RBR?
NG has been using DNS Proxy for a LONG time. This is nothing new.
- energieLuminary
Just to make a clear statement: AP mode does not actually resolve the issue with the DNS server. In AP mode the DNS server (to be specific: DNS proxy - dnsmasq) of the Orbi is not used anymore, it is bypassed. This functionality then gets handled by a third party router, for example the router of your ISP or another router you need to place before the Orbi router.
I can understand you're going to return this product as you're still within the return window. I unfortunately don't have that option anymore. It is ammendable that you even tried using this product in AP mode with an additional router, as the Orbi should be functioning correctly in Router mode.
Let us know to which other wifi system you're switching to. We can then too list that as a viable workaround. Because why place another router in front of the Orbi when you can just swap the entire Orbi system for one that has a working DNS server / firmware. Seems also like the best environmental friendly solution.
FURRYe38 Considering you're statement that Netgear has been using DNS proxy for a long time. This product clearly shows the lack of experience the support team, the engineering team and QA has with the actual implementation. The Telnet workaround that is directly targeting the used DNS server/proxy - dnsmasq clearly shows that the engineering team did a bad job. So your statement holds no value.