NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR850 frequently issuing DNS REFUSED responses
Had the RBK852 now for just over a month, and have an issue I'll open a support ticket for. Wondered though if others have been experiencing anything similar. Basically and since day 1 after put...
Good Luck. This issue is resolved by the beta thats available.
I see the same things here. I have Armor activated but the problem has been there before activation.
Logs from dnsmasq on the rbr850 when I try to access http://bugs.debian.org (when not in DNS cache)
--
dnsmasq: query[A] bugs.debian.org from 192.168.1.32
dnsmasq: forwarded bugs.debian.org to 92.220.228.70
dnsmasq: forwarded bugs.debian.org to 109.247.114.4
dnsmasq: query[A] bugs.debian.org from 192.168.1.32
dnsmasq: query[A] nav.smartscreen.microsoft.com from 192.168.1.32
dnsmasq: forwarded nav.smartscreen.microsoft.com to 109.247.114.4
dnsmasq: forwarded nav.smartscreen.microsoft.com to 92.220.228.70
dnsmasq: reply nav.smartscreen.microsoft.com is <CNAME>
dnsmasq: reply wd-prod-ss.trafficmanager.net is <CNAME>
dnsmasq: reply wd-prod-ss-eu-north-1-fe.northeurope.cloudapp.azure.com is 23.102.47.40
dnsmasq: query[A] google.com from 192.168.1.32
dnsmasq: forwarded google.com to 109.247.114.4
dnsmasq: forwarded google.com to 92.220.228.70
dnsmasq: reply google.com is 216.58.207.238
dnsmasq: query[A] bugs.debian.org from 192.168.1.32
dnsmasq: forwarded bugs.debian.org to 92.220.228.70
dnsmasq: forwarded bugs.debian.org to 109.247.114.4
dnsmasq: reply bugs.debian.org is 140.211.166.212
dnsmasq: reply bugs.debian.org is 140.211.166.201
dnsmasq: reply bugs.debian.org is 209.87.16.39
--
As you can see it need to forward the request 3 times before we get a dns replay, and this makes the browser show "page not found"
To narrow and workaround this DNS issue, can I change my Windows connection's TCP/IP properties for DNS and choose directly Google DNS (8.8.8.8 and 8.8.4.4)? By doing that and not using the default DNS server address (i.e., my Orbi router's IP address) then should we expect my intermittent browser DNS episodes to stop? I'm trying it now to see if I notice a difference today.
Yes that's right.
Setting them on the router wouldn't help workaround it (but does help confirm it's not an ISP DNS service issue but a dnsmasq one).
Setting them directly on your host (e.g. windows) machine IP properties instead of relying on DHCP picking up the router's address for DNS should instantly** prevent further occurences.
** At least in something modern, i.e. Windows 10, which doesn't require you to restart from DNS IP changes.
And to exacerbate / test harder on purpose, issue frequent "ipconfig /flushdns" calls inbetween attempts to resolve a hostname, either with the router/DHCP address for DNS, or whether the directly entered google ones into your connection's IP properties, and you should see the frequency of the issue increase with the router/DHCP address, and still no problems with the directly entered google ones to the machine.