NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
TeamT
Jan 17, 2017Star
R6220 stop to respond to DNS queries.
Hi, My R6220 router with firmware V1.1.0.34_1.0.1 stops to respond to DNS queries aproximately every 4th day. Restart of the router fix the problem temporarily. I have saved WireShark captures to...
- Nov 11, 2017
Hi,
My router has been OK for 27 days now. There are good reasons to assume that the bug has been fixed.
Kind regards,
TeamT
Tobro
May 02, 2017Initiate
I have the exact same issue and see this problem going back years? How is that possible? If you aren't using any parental controls why does the netgear router have to act as a passthrough DNS server. It should be assigning the manually assigned DNS entered on the WAN configuration, not it's own IP address. Seems like a really simple solution.
TeamT, hope they get an update to you.
- TeamTMay 03, 2017Star
Update:
Got a new firmware with some troubleshooting capabilities on the 28th of April. Installed it and the DNS bug showed up again at 1st of May.
I was instructed to start/restart the domain name relay daemon in the router by sending a command to the router via a web browser link. After restarting the daemon the router worked fine again. Issue is now back with engineering again.
My view is that this proved that the domain name relay daemon in the router fails (is killed or hangs) due to a bug. Very strange that the bug hasn't been solved as several users have reported problems during several years.
/ TeamT
- TeamTMay 29, 2017Star
Update:
Got a new firmware to log the domain name relay deamon. Were able to get a log when DNS hangs. Log is now with enginering.
Had a quick look at the log. Socket numbers seems to increase for some reason and after socket number 1023 DNS stops. Disconnect / conect the WAN cable restarts the domain name relay domain and it works fine again.
/ TeamT
- thekent90May 29, 2017Aspirant
I also have a R6220 with the exact same problems. Quite relieved that it's the Netgear router that's causing these issues. Hoping for a fast release of new firmware!