RBR50 intermittent DNS lookup issues

NG is offering a beta if you choose to do so. 

In the real of networking devices, factory rest is a valid and sometimes necessary troubleshooting step. But it's up to you though. For some, it does work and does help. 

I have never seen this DNS issue on my RBK50 system. But I guess I can't post my opinion nor experiences. No, not a NG employee. But you can have your opinion. 

Good Luck though. 

Never said anything about appologizing. Just offering up suggestions. 

Its up to you to take the suggestions and try them, or not. 

If you aren't looking for solutions, then maybe the forums are not for you. What forums are for. Help and information. Maybe you should understand that. 

Why don't you offer up some help and information instead of complaining. If not then you'll need to contact NG support directly. 

BTW, any NG employee have a N next to there forum user name. You can definally contact them freely.

Good Luck. 

---

FURRYe38 wrote:

Never said anything about appologizing. Just offering up suggestions. 

Its up to you to take the suggestions and try them, or not. 

If you aren't looking for solutions, then maybe the forums are not for you. What forums are for. Help and information. Maybe you should understand that. 

 

Why don't you offer up some help and information instead of complaining. If not then you'll need to contact NG support directly. 

 

BTW, any NG employee have a N next to there forum user name. You can definally contact them freely.

 

Good Luck. 

---

You left out the part of your forum dominance (36k posts) and how you believe everything can be solved with the next firmware update and a factory reset 

---

archp wrote:
A factory reset isn't a solution for most users. Tell your grandma or parents, hey just factory reset and redo and reconfigure everything. Layman users or inexperienced ones likely used the free 90 support to get things setup to begin with.

The only reason people are looking at forums is because Netgear wants to charge for support after 90 days and their engineers are lazy as hell and do no testing on firmware releases.

Try putting yourself in the shoes of an average or inexperienced user. That's what companies are supposed to do.

---

Concur

we do have to occasionally fight off the FURRYe38 attack dogs 

---

archp wrote:
A factory reset isn't a solution for most users. Tell your grandma or parents, hey just factory reset and redo and reconfigure everything. Layman users or inexperienced ones likely used the free 90 support to get things setup to begin with.

---

To be honest, the ORBI mesh stuff is not for "basic" users. They should buy a plug-and-play system.
Even most of my friends do not know what a wifi-mesh is. And I'm still far away from being a grandpa.
The reason for most of the (ORBI) wifi-mesh buyers is to provide a great coverance and performance for themself and/or the family.
If not, then they buyed a over-provisioned gadget.

---

Ha_Ku_Na wrote:

---

archp wrote:
A factory reset isn't a solution for most users. Tell your grandma or parents, hey just factory reset and redo and reconfigure everything. Layman users or inexperienced ones likely used the free 90 support to get things setup to begin with.

---

To be honest, the ORBI mesh stuff is not for "basic" users. They should buy a plug-and-play system.
Even most of my friends do not know what a wifi-mesh is. And I'm still far away from being a grandpa.
The reason for most of the (ORBI) wifi-mesh buyers is to provide a great coverance and performance for themself and/or the family.
If not, then they buyed a over-provisioned gadget.

---

Nice opinion

However, I have found the Orbi to be a great plug and play system.  I've had my RBK50 for nearly 5 years and recently upgraded to the 753 and each time it was a simple setup and change the network name/password and it's done.  I don't tweak with the configurations nor do I use switches and multiple routers (ap mode, etc.)  From reading posts in here where folks have most of their problems is when they don't understand what mesh means and trying to run 2 routers, switches, etc.  Not saying it can't be done, but you really need to know what you're doing.  Never understood why someone would want to run 2 routers when most Orbi's can cover most homes with no problem.  I guess they're trying to provide wifi to the moon.  And then of course there's the whole issue of firmware where most think that life will stop if they don't grab the latest firmware.  Not true.  This grandpa is living proof.

To help with factory resets, users should and are advised and reminded to have a back up configuration saved to file. This helps save time should a reset be needed. Someting i try to mention in my responces. 

---

FURRYe38 wrote:

To help with factory resets, users should and are advised and reminded to have a back up configuration saved to file. This helps save time should a reset be needed. Someting i try to mention in my responces. 

---

factory resets (in most cases) should be viewed as a lat resort.  Did you or Netgear mess something up?

---

FURRYe38 wrote:

To help with factory resets, users should and are advised and reminded to have a back up configuration saved to file. This helps save time should a reset be needed. Someting i try to mention in my responces. 

---

Note: I think the reason the factory-reset approach has worked for others is exactly because they did NOT save configs to backup, and then (after restore) did not set both auto-adjust-DST and "Enable Traffic Meter".

Has anyone demonstrated that you can still use both settings active after a factory reset with firmware V2.7.2.104?

I did express that after all this started. Using v104 on mine and DST and TM enabled saw zero issues. Though some don't like it when I express my experiences or opinion about what works for me. :smileylol:

l8nc 

Ha_Ku_Na 

---

FURRYe38 wrote:

I did express that after all this started. Using v104 on mine and DST and TM enabled saw zero issues. Though some don't like it when I express my experiences or opinion about what works for me. :smileylol:

 

l8nc 

Ha_Ku_Na 

---

the questions was..."Has anyone demonstrated that you can still use both settings active after a factory reset with firmware V2.7.2.104?"

IMHO...it's not so much you stating such and such works for you, it's more of a case where you NEVER seem to (or admit) that you too had the same problem and now based on your fix, it now works. 

I won't admit to something falsely if it's not happening with mine. Sorry. If it's not happening to me and you don't belive that thats fine. Think what you will.  I'm not giving any false information based on what you believe. We are not here to prove anything to you.

Good Luck. 

---

FURRYe38 wrote:

I won't admit to something falsely if it's not happening with mine. Sorry. If it's not happening to me and you don't belive that thats fine. Think what you will.  I'm not giving any false information based on what you believe. We are not here to prove anything to you.

 

Good Luck. 

---

You're still missing the point.  No one is asking you or anyone to admit to anything falsely.  It has nothing to do with me believing anything about you or asking you to prove anything to anyone.

My position is if you are NOT or have NOT experienced the same problem that the original poster is going through and then to tell them that a certain firmware works for you with no problems certainly does NOT help your case.  Think about it, it's like saying...."I can do it why can't you?"   You're talking down to people.  Rather just offer your ideas for a fix.  Something you seem to have no shortage of.  

But as you've told me before you'll continue to post as you see fit.  

I'm chiming back in to say that I still have found a solution with my system yet, even after a week of back-and-forth with the netgear L2 support (who has not suggested any beta firmware or anything yet, just continuing to ask questions and for debug logs). 

My current workaround, which is stable, is that I've put my Orbi system into wireless access point mode and added an old router (Archer C7 with the wifi off) in-line between the cable modem and the Orbi to serve as the router. In that configuration, I've been stable for a couple days now. Obviously not ideal (why did I buy and expensive Orbi if all I can use it for is being a dumb wifi access point?), but it's letting my wife and I work in the meantime. 

If the Orbi support folks don't have many ideas, I think my next attempt will be to try some flavor of the Voxel firmware and see if that solves it. 

In the spoiler tag below I've added a summary of my past troubleshooting steps that haven't worked:

---

SidewinderX wrote:

I'm chiming back in to say that I still have found a solution with my system yet, even after a week of back-and-forth with the netgear L2 support (who has not suggested any beta firmware or anything yet, just continuing to ask questions and for debug logs). 

 

My current workaround, which is stable, is that I've put my Orbi system into wireless access point mode and added an old router (Archer C7 with the wifi off) in-line between the cable modem and the Orbi to serve as the router. In that configuration, I've been stable for a couple days now. Obviously not ideal (why did I buy and expensive Orbi if all I can use it for is being a dumb wifi access point?), but it's letting my wife and I work in the meantime. 

 

If the Orbi support folks don't have many ideas, I think my next attempt will be to try some flavor of the Voxel firmware and see if that solves it. 

 

In the spoiler tag below I've added a summary of my past troubleshooting steps that haven't worked:

Spoiler

Issue: Devices on the network repeatedly lose the internet connection for some period of time, which normally presents itself as a DNS issue. It's usually not all devices on the network (for example, my Roku and work laptop may work fine with no interruption, but my cell phones and wife's laptop might not be able to access).

Investigation notes:
* this started after upgrading to the .104 firmware (where I had the traffic meter on).

* I have tried the methods of disabling traffic meter, disabling daylight savings time, changing NTP, changing default DNS servers, etc.

*I've change the wire between the router and the cable modem to confirm the issue isn't on that end.

* I have factory reset the Orbi system (both router and satellite) several times, to no effect including:
- A factory reset while still on the .104 firmware (therefore disabling traffic meter); no improvement
- downgraded to 2.6 firmware, and then factory resetting on that firmware; no improvement
-upgraded back to the .104 firmware, and factory resetting on that firmware; no improvment

*during the investigation, seems more and more clear that it has something to do with the router and the internet routing (DNS/DHCP or something?).
- The router has always been able to run a speedtest from the router to the internet with no issues, even while some of my downstream devices have issues.
- Similiarly, I've never had wireless or wired connection dropouts, so the internal LAN seems to work just fine. For example, I'm able to endlessly ping my NAS device with not issues, even while the actualy internet connection from the device is inconsistent

*Finally, my last step, which seems to working for now, is that I've put the Orbi system (RBR50 and RBS50) into wireless access point mode, and added my old router (a TP Link Archer C7) in-line as the router (with its own wifi disabled). The configuration, with the Archer as the router, has had no issues managing the internet connection, so it seems pretty clear that the issue is in the Orbit LAN to WAN routing in some way.

 

---

You're not alone with Orbi DNS issue.  It's a long standing problem with Orbi across all version of firmwares.  It's more likely to happen with high traffic loads, which is taxing Orbi internal DNS server.  You've discovered the right solution by putting Orbi in AP mode.  I've done the same a while back and never look back.

Check out this thread: Orbi RBR50 Circle frequent DNS failures and solution 

An alternate solution: RBR50 DNS Issues/Solution 

Good luck!

Since NG obviously doesn't have coders with the skillset necessary to fix the issue, they should open telnet back up so others who are able to fix the issue can do so - at least for themselves (and anyone so inclined to follow instructions).

Perhaps an online petition will garner attention to the issue?