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

Forum Discussion

DirtyWilly's avatar
DirtyWilly
Star
Aug 20, 2021

R8500 Latest Firmware Version V1.0.2.154 Broke DNS!

Hello, the latest firmware version V1.0.2.154 for the R8500 router appears to have broken DNS!  I have to refresh pages multiple times to get them to load.  Attached is the most common error.  DNS_PR...
CaledonKen's avatar
CaledonKen
Star
Dec 13, 2021

Are any of the posters on this thread having success with version 156 with respect to this error? That is, does v156 fix this DNS issue?

 

 

 

 

JFII's avatar
JFII
Guide
Mar 27, 2022

Allowing the router to dynamically retrieve the IP and DSN seems not to have the issue. When I was having the issue I was manually entering the IP and DNS it wasn't until I limited the DNS to 1 entry did the issue go away (and of course allowing them to be retrieved by the ISP)

I also reboot the device every week or so. Which bring up my the issue of using the device as a media server. When rebooting the R8500 does not remount the USB chip I have plugged into it. I have to physically remove the chip and plug it back it for it to work.

  • CogX's avatar
    CogX
    Aspirant
    Mar 27, 2022

    So, count me as one who starting having the DNS "probe" errors as soon as I had installed firmware R8500-V1.0.2.154 last summer now.  After a few days, once I realized it wasn't just me, I downgraded back to R8500-V1.0.2.144 and been there since.

    However, it turns out, I do actually get those DNS errors sometimes even with .144, but it's temporary, it shows that error in Chrome for a second or two and then the page I'm trying to get to then does load.  With .154, it wasn't re-loading and it was also happening in Firefox, not just Chrome.

    Now, I do use a different DNS server than my ISP, and I did have both a primary and secondary set, but I just went in and took out the secondary.  We'll see if get that DNS probe error again at some point with .144.

    I guess the question for everyone fighting this Netgear bug, does everyone have manual DNS settings?