NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR50 DNS Issues
Have the Orbi RBR50 all on the latest firmware. Have reset the entire router and satellite units. DNS keeps locking up. All devices connect to the Orbi fine yet when accessing the internet it locks u...
I want to echo tcomp post as I too am an IT professional and have done extensive testing. The problem IS in DNS resolution. Obviously, a reboot does fix the issue, but then it takes time for the satellites to re-sync. The solution 100% of the time is to run test internet on the orbi web page.
Here are some notes i have found:
- ping works from every device to an ip adress
- ping DOES NOT work to DNS name as DNS cannot be resolved, i am using nslookup.
- I can telnet into the orbi, run nslookup and it DOES work
- I do use Circle
- this strated happending in the past 2 months, more now that i am on 2.5.1.8.
- I correct the issue by running test on the internet setup page.
- If i have a device with manual DNS, no issues.
- I've been watching the debug page and have not been able to attribute high cpu to issue.
- I am logged into router via telnet, looked at many log messages and have not found any errors, where should I look.
Here is what is running on router regarding dnsmasq:
ps |grep dns
9137 root 2364 S aclhijackdns
9787 root 2412 S /usr/sbin/ntgrddns -c /tmp/ntgrdns.conf
22492 root 2616 S dnsmasq -h -n -c 0 -N -i br0 -r /tmp/resolv.conf -u
22768 root 1216 S /mnt/circle/shares/usr/bin/mdnsd 172.16.5.1 FE80::C0
22794 root 888 S runsv dnsmasq
22800 root 2972 S /mnt/circle/shares/usr/bin/dnsmasq -k --max-ttl=1 --
26368 root 1568 S grep dns
26369 root 1572 S /bin/sh -c /usr/sbin/dns-hijack
26370 root 1572 S {dns-hijack} /bin/sh /usr/sbin/dns-hijack
26372 root 1564 R killall -SIGUSR2 dnsmasq
netgear Please help!
What is the Mfr and model# of the ISP modem the NG router is connected too?
Does using default DNS or letting the RBR auto detect and use DNS keep the DNS running for your devices. Try quad 9?
Has a factory reset and setup from scratch been performed since last FW update and use auto DNS?
Circle has been know to cause problems as well. Try a reset and setup from scratch with out any Armor or Circle.
If any of these fail to resolve anything, please file a support ticket here:
https://www.netgear.com/support/#
iamkeyman3 wrote:I want to echo tcomp post as I too am an IT professional and have done extensive testing. The problem IS in DNS resolution. Obviously, a reboot does fix the issue, but then it takes time for the satellites to re-sync. The solution 100% of the time is to run test internet on the orbi web page.
Here are some notes i have found:
- ping works from every device to an ip adress
- ping DOES NOT work to DNS name as DNS cannot be resolved, i am using nslookup.
- I can telnet into the orbi, run nslookup and it DOES work
- I do use Circle
- this strated happending in the past 2 months, more now that i am on 2.5.1.8.
- I correct the issue by running test on the internet setup page.
- If i have a device with manual DNS, no issues.
- I've been watching the debug page and have not been able to attribute high cpu to issue.
- I am logged into router via telnet, looked at many log messages and have not found any errors, where should I look.
Here is what is running on router regarding dnsmasq:
ps |grep dns
9137 root 2364 S aclhijackdns
9787 root 2412 S /usr/sbin/ntgrddns -c /tmp/ntgrdns.conf
22492 root 2616 S dnsmasq -h -n -c 0 -N -i br0 -r /tmp/resolv.conf -u
22768 root 1216 S /mnt/circle/shares/usr/bin/mdnsd 172.16.5.1 FE80::C0
22794 root 888 S runsv dnsmasq
22800 root 2972 S /mnt/circle/shares/usr/bin/dnsmasq -k --max-ttl=1 --
26368 root 1568 S grep dns
26369 root 1572 S /bin/sh -c /usr/sbin/dns-hijack
26370 root 1572 S {dns-hijack} /bin/sh /usr/sbin/dns-hijack
26372 root 1564 R killall -SIGUSR2 dnsmasq
netgear Please help!
- I can confirm this issue as well. Same symptoms, same firmware. Also IT engineer by trade. All lan devices that look to the orbis for DNS fail to resolve an nslookup. If I manually set the DNS on the Orbi to 1.1.1.1, laptop1 to my Orbi for DNS and laptop2 to 1.1.1.1. I then wait for the issue to occur... Sometimes multiple times per day. Laptop1 stops resolving IPs, laptop2 continues working without issue. The Orbi says it's connected and never shows sign of any issue in the web interface. This has become increasingly frustrating. Testing the connection from the web interface fixes it.
Has a factory reset and setup from scratch been performed since last FW update and use auto DNS?
milenkojmb wrote:
I can confirm this issue as well. Same symptoms, same firmware. Also IT engineer by trade. All lan devices that look to the orbis for DNS fail to resolve an nslookup. If I manually set the DNS on the Orbi to 1.1.1.1, laptop1 to my Orbi for DNS and laptop2 to 1.1.1.1. I then wait for the issue to occur... Sometimes multiple times per day. Laptop1 stops resolving IPs, laptop2 continues working without issue. The Orbi says it's connected and never shows sign of any issue in the web interface. This has become increasingly frustrating. Testing the connection from the web interface fixes it.According to SymonB's post on 2019-09-16 07:58 AM, a full factory reset does not resolve the problem with DNS. I like several others have troubleshot and come to the same conclusion that there is a problem with DNS on the router. Can someone from Netgear development acknowledge the issue and get it fixed, please. With lots of us working from home due to the Coronavirus, our home internet systems are of utmost importance. I will be logging an actual support ticket with Netgeat if I even can. Not sure if they will allow that since I am out of warranty though.