CISA and the CERT Coordination Center (CERT/CC) are aware of multiple vulnerabilities affecting Dnsmasq version 2.82 and prior. Dnsmasq is a widely-used, open-source software that provides Domain Name Service forwarding and caching and is common in Internet-of-Things (IoT) and other embedded devices. A remote attacker could exploit some of these vulnerabilities to take control of an affected system.
CISA and the CERT Coordination Center (CERT/CC) are aware of multiple vulnerabilities affecting Dnsmasq version 2.82 and prior. Dnsmasq is a widely-used, open-source software that provides Domain Name Service forwarding and caching and is common in Internet-of-Things (IoT) and other embedded devices. A remote attacker could exploit some of these vulnerabilities to take control of an affected system.
Did @DNS_PROBE_FAIL and @Mikey94025 use the beta FW build that @Ace321 is utilizing or just the most recent one you can officially get off of Netgear? I just want to make sure we are clear on what is working and what is not. Thanks!
Did @DNS_PROBE_FAIL and @Mikey94025 use the beta FW build that @Ace321 is utilizing or just the most recent one you can officially get off of Netgear?
I did not use a Beta build nor am I working with Netgear for my issues (I have easy workarounds or not serious enough to spend my time on it). I'm using the latest available for public download: V3.2.17.12_1.4.14.
What I did was boxed up my $1000 Orbi system and returned it, then reinstalled my older RBR50 / AC3000 system with the same configuration on our network and boom! No DNS issues, errors or device timeouts and I don't even have to enable IPv6 for it to work!
This is an epic fail from Netgear. Total lack of ownership of their issues at the expense of the consumer. I wish you all luck but I'm setting sail for smoother waters elsewhere.
I'm going to buy the Asus WiFi6 mesh solution and never look back.
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.
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.
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.
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.
Yes, I've currently got the Hub in modem-only mode (your scenario 1). This means the Orbi is acting as the router but because it's not handling the DNS requests correctly, I am having my current issues.
I was considering changing to your option 3 (using the Virgin hub as the router, turning off the router's wifi and using the Orbi as an access point). This would mean the Virgin router handles the DNS requests and should resolve the current issue. I don't think this would cause a double NAT?
Or would the Orbi still cause DNS errors even when used in AP mode?
(Thanks for all your help by the way - I really appreciate it)
But if you go AP mode you lose guest networking and any ability to further segment your network with the ROUTER you bought. This is just STUPID. All that Netgear needs do is add DHCP OPTION DNS to the DHCP config screen and let us use a working. DNS server instead of their broken one.
Also wonder for those of you who have these gateway modems are also a problem. Even though in bridge or modem only mode, makes me wonder if these modems units are also causing problems. I dont use a gateway modem and have a modem only unit, I have never seen this issue to date with my Orbi AX.
At any rate, users will need to keep in contact with NG support about this.
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).
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.
I reported this problem as early as April 2020: https://community.netgear.com/t5/Orbi-AX/Very-Brief-Internet-Connection-Issues/m-p/1898077#M3063. This was right after I got my Orbi AX system. Since not everyone sees this particular bug, including yourself (who keeps telling us that you don't have the problem), there is insufficient data to know when it really started or if it truly did not exist when the Orbi AX system was initially launched.
There really is no need to further defend or debate this bug. Merely admit it exists.
Not denying it, just seems that for some and for some one certain ISPs or with certain ISP hardware, seems to be a problem. Others don't seem to have this problem, never the less, Again, something NG will need to address and resolve.
I bought an open box RBR853 (3 piece system) from Amazon and it had the issues, regardless of firmware version. Changes to AX settings did nothing to help it either. I returned that system and bought a new, never opened RBR853 system and it also has the same DNS issues with the 3.2.16 firmware it auto updated to, as well as the V3.2.17.12_1.4.14 firmware that netgear support asked me to update.
My internet modem is a Netgear CM1000 and has no issues with other wifi systems, including an older Orbi RBR50.
Only enabling IPv6 resolves DNS issues, which is not a fix, because it only helps IPv6 capable devices.
Even with IPv6 enabled, I have had frequent app and internet timeouts with mobile devices on guest wifi, even if they support IPv6.
Could everyone with this issue (me included) provide details in regards to:
1) Have you ever used and actived the NetGear Armor option under the Orbi App?
I already have Kaspersky Internet Security which does all the protection and didn't require NetGear Armor, so didn't bother with it for ages. Kaspersky has it's own plugin for web-browsers to check URL phishing and the works, so it's also doing a lookup itself. I then struggled with a slightly slow/delayed DNS lookup and random "DNS_PROBE_FINISHED_NXDOMAIN" messages, till I download and installed the Orbi App and logged into the router from that to enable the trial version of NetGear Armor. I strongly believe there's a linkage between the DNS lookups going via that, if missing it waits and delays more. So far that has resolved the issue.
2) Are you using a certain Optical Network Terminal (ONT) model / brand?
This could be another reason. My ONT is Chorus Model Type 200, which has no Wifi features. However, if your ONT or Router has another Wifi signal, that needs to be disabled/bypassed or the Orbi Mesh should be set to AP Mode to use the same Wifi group.
3) Are you using certain DNS Servers?
I was originally using the CloudFlare DNS, assuming it was the fastest for my Internet. It was not due to my location in the world.
Provide it with the Domain Name Servers from your ISP (Internet Sevice Provider) and whatever others you might like to consider using, then test all their performance. It will work out the fastest ones for you. Some are seriously better than others. The slow/delayed DNS lookup and random "DNS_PROBE_FINISHED_NXDOMAIN" messages reduces greatly when you set the DNS under your Router to the fastest option available. You will barely ever notice the problem at all or it will go away completely with a fast DNS. The slower the DNS responses, the more you will see this problem. We are talking a milliseconds difference between it occuring or not.
Could everyone with this issue (me included) provide details in regards to:
1) Have you ever used and actived the NetGear Armor option under the Orbi App?
2) Are you using a certain Optical Network Terminal (ONT) model / brand?
3) Are you using certain DNS Servers?
1. Never run Armor
2. Using Xfinity/Comcast gateway TG3482G, currently configured with Double NAT to my Orbi RBR850 (works fine for my needs)
3. I have previously tried configuring my Orbi RBR DNS to Google DNS but it did not help with this bug. I have been running with Comcast default DNS. Per your recommendation I configured it back to 8.8.8.8/8.8.4.4 so I can see if Google DNS reduces the bug frequency.
