NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

rax120_rax80's avatar
rax120_rax80
Apprentice
Mar 09, 2020

RAX120 Router Random Disconnects

Hey everyone, I know that I'm not the only one with problems on the Nighthawk WiFi 6 devices, but thought I'd post my most recent headache. My hardware consists of a Motorola MB8600 DOCS 3.1 modem w/...
bamcgregor89's avatar
bamcgregor89
Aspirant
Mar 30, 2020

I wanted to throw out that my RAX120 has started having issues proxying DNS as well. Started last night when it stopped sending traffic to my Pi-Hole for resolution. Nslookup queries to router would return no response, while queries directly to the Pi-Hole would return expected results. Reboots get it going again for a bit, but it eventually drops out after a while.

 

Router DNS was changed to public servers (Quad 9, Cloudflare, and Google) and was updated to latest public firmware (v1.0.1.118) with no improvements - DNS resolution stopped sometime this morning again.

 

I currently have a workaround (Pi-Hole is now running DHCP for my network so devices can pick up functioning DNS settings automatically), so I'm not looking for a fix, but I want to make it known to Netgear that this is indeed an issue. FFS, if I wasn't tech savvy I'd be dead in the water having to reboot the router every few hours.

 

If nothing else, allow users to bypass the stupid DNS proxy and push the actual DNS servers to devices over DHCP. At least the option would allow everyone here to get back to working order.

  • a3gill's avatar
    a3gill
    Aspirant
    Mar 31, 2020

    Same issue on and off for me, too.

    To be clear, the problem is that DNS Relay is failing, right? I can manually assign ISP DNS to clients and all is well (or, as mentioned, configure an alternate DHCP Server/DNS Relay Server).

     

    My experience...:

    - First noticed it with 1.0.1.114.

    - Applied 1.0.1.118 hotfix and neither better nor worse.

    - Rolled back to 1.0.1.108 and all was well.

    - Applied public release of 1.0.1.118 and no issues for days, perhaps weeks.

    - Configured and applied an Upstream QOS policy and rebooted. Now, this evening, I've lost DNS resolution via RAX120 DHCP twice.

    - Currently: I removed the QOS and it ran fine for a few hours, no issues and just now re-applied the QOS.

     

    So far so good. We'll see. If it craps out again I have my config backup and FW 1.0.1.108 ready to go if need be. Fingers-crossed :)

     

    Thanks!

    • a3gill's avatar
      a3gill
      Aspirant
      Mar 31, 2020
      a3gill wrote:

      - Configured and applied an Upstream QOS policy and rebooted. Now, this evening, I've lost DNS resolution via RAX120 DHCP twice.

      I wasn't very clear... Within an hour of enabling QOS, the issue re-appeared, and then again shortly after.

       

      Thanks!