RBR50 DNS Issues

There should be a ONT some place unless the ISP keeps this elsewhere. 

---

daverichard4 wrote:

Dont have any cable modem.  I have fiber right to the house.

---

Let us know what you find out. 

What is the Mfr and model# of the ISP modem the NG router is connected too?

Be sure not to enable any Circle or Armor features...

---

milenkojmb wrote:
Update... I changed the DNS from statically assigned on the Orbi to dynamic and rebooted. Within the next 24 hours, the issue still occurred 3 times. Each time just going to the web interface and clicking test resolves the issue. I just performed a factory reset on both the Orbi router and both satellites and set up again from scratch. I will report back with findings.

---

Yor modem seems to be a gateway modem, thus having a built in router and wifi. Is thie modem fully bridged? 

Glad it's working better. Hopefully this is just a Circle app issue causing this problem. 

---

milenkojmb wrote:
So far, so good. I have left the DNS at default dynamic for now after the factory reset. No issues so far.

Comcast modem is a Technicolor CGM4140COM.

---

Ok, just making sure. Let us know how it goes over the next few days. If you think this is a Circle or Armor related issue, please post about it in there perspective forums. 

---

milenkojmb wrote:
Yes, the modem is in bridge mode. I did not reenable circle or armor.

---

I would presume it temporarily interrupts services to acurrately test DNS services. 

Here is a copy of the grep with circle and armor not enabled.  I left both turned off after my factory default.

My Orbi has never had Disney Circle activated.  It shows a process

7225 root 2364 S aclhijackdns

Explanations of how Disney Circle works talk about ARP poisoning, not intercepting DNS.

I likewise have never activated Circle or Armor.  Here are my DNS processes, which includes aclhijackdns:

root@RBR50:/# ps -w | grep dns
1282 guest 2632 S /usr/sbin/dnsmasq --except-interface=lo -r /tmp/resolv.conf -P 4096 --log-facility /tmp/dnsmasq.log --log
7126 root 2364 S aclhijackdns
7877 root 2412 S /usr/sbin/ntgrddns -c /tmp/ntgrdns.conf
13776 root 1568 S grep dns

I can confirm all of the findings here.  Started after about 3-4 days of quarantine.  Been in use for over a year before and never had any problems.  Oddly enough, adding static DNS entries on the clients does not solve the problem (but I can do an nslookup from that same client specifying my DNS server).

I have changed my DNS servers on the router from the Comcast provided ones to 1.1.1.1 and 8.8.8.8 thinking it was upstream at first.  Same thing.  I also do have circle enabled, have my modem in bridge mode and am on the latest 2.5 firmware.

Disable Circle. This seems to be the cause of users problems with DNS. Users have mentioned DNS working again after Circle is disabled. 

---

agregory23 wrote:

I can confirm all of the findings here.  Started after about 3-4 days of quarantine.  Been in use for over a year before and never had any problems.  Oddly enough, adding static DNS entries on the clients does not solve the problem (but I can do an nslookup from that same client specifying my DNS server).

 

I have changed my DNS servers on the router from the Comcast provided ones to 1.1.1.1 and 8.8.8.8 thinking it was upstream at first.  Same thing.  I also do have circle enabled, have my modem in bridge mode and am on the latest 2.5 firmware.

 

 

---

I do have to say... I just recalled that the only setting that I have changed in a while was enabling the Traffic Meter.  Full disclosure I pay for Disney Circle because I find it great for metering and restricting my kids usage. 

I disabled Disney Circle and thought I would try re-enabling it and see if that helped.  At that point I came across the Traffic Meter setting and remembered I had enabled that a couple weeks back.  I have disabled that and will see if it makes a difference tomorrow.

Side note, I had setup a ping to www.google.com on my MacBookPro.  It stayed successfully pinging until I noticed my phone would not get out again.  I went back to my laptop and the ping was still resolving.  I stopped the ping and tried to start it again and it would not resolve.  Its like its a session based issue.  I am fairly certain if I was connected to my company VPN I would not have any problems as long as it was a full tunnel and did not fail.  That ping would also get intermittant failures every 20-30 pings.  Since disabling Traffic Metering its been constant with no loss.

Either way this is definetly a Netgear problem and they need to get on their firmware to fix this issue.  Its obviously happening to a decent amount of people.

---

agregory23 wrote:

Side note, I had setup a ping to www.google.com on my MacBookPro.  It stayed successfully pinging until I noticed my phone would not get out again.  I went back to my laptop and the ping was still resolving.  I stopped the ping and tried to start it again and it would not resolve.  Its like its a session based issue.

---

This observation is entirely correct.  Almost every device keeps a cache of resolved DNS entries.  When an application connects to a particular IP address, such as a web site, it tends to make 100's of connections to the same site.  So, the computer remembers that DNS address for a while.  Eventually, the cache "times out" and has to be reloaded.

Thank you for letting us know. Circle seems to be causing some problems. Keep it disabled if your not using it. 

---

Spiffywerks wrote:
I would like to thank all in this community for the help. I had Disney Circle enabled, but wasn’t using it. I turned it off and resolved the DNS failing issue I was experiencing for the past week after I began using VPN to connect to my office.

Manually setting DNS on each device to 8.8.8.8/8.8.4.4 would bypass the router’s DNS and internet would work, but was not an acceptable solution for 30+ devices connected. Was having to reboot the router 3-4 times a day.

Setup: Frontier Fios ONT > RBR50 > 2x Satellites with WiFi backhaul. (All on FW v2.5.1.8)

---

I don't think this issue is limited to Circle. 

We get DNS failures regurlarly, although unlike the failure modes experienced by other posters, this is temporary and resolves itself after a few seconds. But it's constant, it'll happen every 15-30 minutes. Generally with the message of DNS Probe Finished Bad Config. 

This has persisted across two different modems upstream of the Orbi, a SB6141 and a Netgear CM500. 

The issue is fully resolved when a static DNS address is set on the end device, either the ISP's DNS servers or Google or OpenDNS, all work flawlessly. 

However, the same DNS address set on the Orbi will generate this error regardless of which server I pick. This is across all devices on the network, and we have a mix of OSX, Windows, ChromeOS, Android, and iOS devices. Issue has persisted across DNS flushes. Issue goes away when tunneling through VPN. 

All Orbi routers/satellites are on latest firmware V2.5.1.8. All devices are getting ip addresses assigned by Orbi. Everything points to the DNS server on the Orbi being buggy. 

Try a factory reset on the RBR and setup from scratch. Be sure not to enable Circle. Others are reporting the reset also helps with DNS issues. I haven't seen this aswell. 

You can also try Voxels FW as well:

https://community.netgear.com/t5/Orbi/Voxels-FW-available-for-50-series-Orbi-only-available/m-p/1883615#M86604

---

gchk wrote:

I don't think this issue is limited to Circle. 

 

We get DNS failures regurlarly, although unlike the failure modes experienced by other posters, this is temporary and resolves itself after a few seconds. But it's constant, it'll happen every 15-30 minutes. Generally with the message of DNS Probe Finished Bad Config. 

 

This has persisted across two different modems upstream of the Orbi, a SB6141 and a Netgear CM500. 

 

The issue is fully resolved when a static DNS address is set on the end device, either the ISP's DNS servers or Google or OpenDNS, all work flawlessly. 

 

However, the same DNS address set on the Orbi will generate this error regardless of which server I pick. This is across all devices on the network, and we have a mix of OSX, Windows, ChromeOS, Android, and iOS devices. Issue has persisted across DNS flushes. Issue goes away when tunneling through VPN. 

 

All Orbi routers/satellites are on latest firmware V2.5.1.8. All devices are getting ip addresses assigned by Orbi. Everything points to the DNS server on the Orbi being buggy. 

 

---

You can enter in custom DNS on the RBRs web page under Basic/Internet. Select the
Domain Name Server (DNS) Address section and  select Use These DNS Servers. Enter in any known working DNS, Quad 1 or 8. Google DNS like quad 8s and 8.8.4.4. Save and apply. 

Has a factory reset and setup from scratch been performed since last update? https://www.youtube.com/watch?v=cMw4ePACgc4
https://www.howtogeek.com/434350/how-to-factory-reset-a-router/

Might try this and also power OFF the ONT for1 minute and back ON. Walk thru the setup wizard. 

---

Spiffywerks wrote:
6 days later after turning off traffic meter and Disney Circle, still having issues.

Setup:
Frontier ONT (Alcatel ONT I-211M-L) > Orbi RBR53 (v.2.5.1.8)

It was good for 3 days, but past three days having to reboot the router at least once a day. Rebooting the ONT doesn’t resolve the issue.

I cannot set a manual DNS in the router because it requires I also create a manual IP address which I cannot do. I’ve tried and there is no connection at all afterwards. Probably the way the ONT is setup?

All this trouble started after working from home and using a VPN client on my desktop to connect to work. Not sure why that would affect the entire network’s DNS.

---

• Manual DNS - Not able to. Explained in following paragraph
• Reboot ONT - Yes, have done this many times. Does not resolve the issue. Router is the issue.
• Factory Reset - No, have not attempted yet. Will try sometime when everyone is not needing it. between daughter, wife, and myself, we're using the internet from 7 am - 10 pm everyday for work and school activities.

I cannot set a manual DNS without first setting a Static IP address. Option for Manual DNS is greyed out on the interface unless I click the option for "Use Static IP Address" first. Disabling DHCP completely kills the connection with the ONT. If I turn off DHCP and leave the settings in the router, the router cannot communicate the with ONT anymore.  Everytime I reboot it gets a new WAN IP address.

What gets me is this setup was fine for the past 9+ months and suddenly this is happening after  we started working from home. -______-;