firmware upgrade yields DNS_PROBE_FINISHED_NXDOMAIN V1.0.4.76_10.1.82

[drzwave2]

Upgraded to Rev V1.0.4.76 and now I can barely log into my work VPN due to the timeout of the DNS_PROBE.

HELLO NETGEAR - NEED A NEW RELEASE ASAP!!!

The "solution" is to downgrade to an earlier rev but this leave me open to old security threats. Really not an acceptable solution!

The real solution is for Netgear to make a hot patch and release a fix ASAP!!!

[plemans]

Thanks for posting!

The more posts about this, the more the mods and engineers can see. 

Just fyi, this is the community support forum where members of the public help out for free. We're not netgear and its rare to find a mod on here. 

[Lee-net]

After 2 weeks of extremely frustrated people, downgraded from 1.4.2.84_1.3.42 to V1.4.1.68_1.3.28 based on others comments. While on the newest version and running Armor, we would get 'This site can't be reached' on 2/3rds of domains including community.netgear.com. Multiple refreshes later would usually allow access to the site, but unfortuantely, the 1.4.2.84 version is causing denial of service. 

In my case, the windows (chrome) error is DNS_PROBE_FINISHED_BAD_CONFIG

Netgear... the other workaround that you could include as an option in your software is to allow us end users to configure the primary and secondary DNS servers in the DHCP configuration on your products. Even though most people are using your router for DHCP, providing the option to configure custom DNS servers would allow us to bypass the faulty DNS config in the 1.4.2.84 release or potentially future releases. 

Please provide updates to resolve the DNS service issues!

[Lee-net]

After 2 weeks of extremely frustrated people, downgraded from 1.4.2.84_1.3.42 to V1.4.1.68_1.3.28 based on others comments. While on the newest version and running Armor, we would get 'This site can't be reached' on 2/3rds of domains including community.netgear.com. Multiple refreshes later would usually allow access to the site, but unfortuantely, the 1.4.2.84 version is causing denial of service. 

In my case, the windows (chrome) error is DNS_PROBE_FINISHED_BAD_CONFIG

Netgear... the other workaround that you could include as an option in your software is to allow us end users to configure the primary and secondary DNS servers in the DHCP configuration on your products. Even though most people are using your router for DHCP, providing the option to configure custom DNS servers would allow us to bypass the faulty DNS config in the 1.4.2.84 release or potentially future releases. 

Please provide updates to resolve the DNS service issues!

[FURRYe38]

Thanks for letting us know though this thread is for a different FW and Model router.