Forum Discussion

Guru - Experienced User

Apr 23, 2022

New - RAX200 Firmware Version 1.0.6.138 Released

New Features and Enhancements: Adds support to EU SKU for Router Analytic (RA) opt-in, opt-out feature Removes support from China SKU for gaming VPN Funjsq Security Fixes: Fixes sec...

adm1r4lj

Star

Apr 27, 2022

I can confirm that 1.0.6.138 DOES INDEED contain a DNS breaking bug for DHCP clients and any device using the RAX200 for DNS.

I spent the entire day debugging this, performing factory resets, up/downgrading firmware, etc. to see where it starts to come apart. From my testing starting with a factory-reset RAX200, everything seems to hold up well for my environment on 1.0.6.138 until I start to create DHCP reservations. The second I create one entry, any device using the RAX200 for DNS (both DHCP clients and devices manually pointing to the RAX200) are unable to receive DNS replies. The RAX200 receives the queries, but does not forward them out to the WAN interface. Deleting the DHCP reservations also does not fix the issue. When I downgrade back to 1.0.5.132, the bug is eliminated and everything works as expected. Switching between 1.0.5.132 and 1.0.6.138 with a fully populated DHCP reservation table confirms the bug exists in 1.0.6.138.

Until Netgear support can release a bugfix, these are the available options:

1. Run 1.0.5.132 until the bug is fixed, or

2. Run 1.0.6.138 and manually configure all client devices to use external DNS servers on the client itself. I have confirmed this works and was using this as a workaround during my debugging, though it is not a practical solution as many devices don't allow you the option to manually configure the device (IoT devices specifically).

nicoimages

Tutor

Apr 27, 2022

In response to the question from crjohnson I did indeed spend a considerable time doing a factory reset and setting everything up again and still had exactly the same issue.

Adding the DNS settings manually into clients is not practical given the amount of devices I have on the network. Rolling back was the only thing that worked

Thanks

Nicholas

EdCzar
Star
Apr 27, 2022
In the release notes, they also make no reference to addressing the problem where the router disconnects from the Internet when a Time Syncronization is taking place (https://community.netgear.com/t5/Nighthawk-Routers-with-WiFi-6-AX/Time-synchronized-with-NTP-server-RAX80-Router-disconnects-me/m-p/2217049#M25885)

With the addition of the DCHP bug it seems like this upgrade breaks more than it fixes.
- crjohnson
  Guide
  Apr 27, 2022
  I want to extend my appreciation to both adm1r4lj and nicoimages for their extensive testing performed and sharing of results. The time and hard work spent dissecting the DNS issue has not gone unnoticed.
  
  I as well use IP address reservations and feel it's impractical to manually configure devices as a work around.
  
  I'll wait for the next firmware release proven to have corrected the situation.
  
  Thank you both again!!
  
  Cliff