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"
Retired_Member
May be a silly question, but how are you seeing the dnsmasq logs on the router please?
Is it from settings done on the debug.htm page, or some log settings on another one like advanced > logs?
The recent logging issue in the firmware means I see very little entries in the advanced > logs screen now.
tantrum wrote:Retired_Member
May be a silly question, but how are you seeing the dnsmasq logs on the router please?
Is it from settings done on the debug.htm page, or some log settings on another one like advanced > logs?
The recent logging issue in the firmware means I see very little entries in the advanced > logs screen now.
Use telnet to get access to the router, then look for a process called dnsmasq
You can kill this running process and start again with logging ex.
dnsmasq -d -k -q -h -n -c 0 -N -i br* -r /tmp/resolv.conf -u root
Retired_Member Are you running a beta / early firmware for the router?
The telnet option doesn't display in the debug form for me, and even if I try and force it, either by using the browser dev tools and forcing the css to show the form block, or manually issuing the form post with the correct parameters using a curl request, the option doesn't stick on the debug page and the router doesn't respond when I try to telnet (port 23) to it.
tantrum wrote:Retired_Member Are you running a beta / early firmware for the router?
The telnet option doesn't display in the debug form for me, and even if I try and force it, either by using the browser dev tools and forcing the css to show the form block, or manually issuing the form post with the correct parameters using a curl request, the option doesn't stick on the debug page and the router doesn't respond when I try to telnet (port 23) to it.
I am on current firmware V3.2.15.25_1.3.15 and telnet has been enabled by default on my router and sats.
Maybe it has something to do with my account being enrolled for betatesting? Maybe some other betatesters can answere this?
Reg
Arild