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"
What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
What browser are you using?
Can you try a factor reset on the RBR and setup from scratch and this time, do not enable Armor...
Retired_Member wrote: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"