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

Forum Discussion

joetechbob's avatar
Dec 29, 2021

R8000P DNS Issues After Updating Firmware to 1.4.2.84

Hi!

 

I noticed that my R8000P started having significant DNS issues after updating the firmware to version 1.4.2.84 (across multiple devices, but most noticeably on our Xbox Series X and Windows 10 machines on both wired and wireless connections). In some cases it would take 5 - 10 attempts to successfully perform DNS resolution, even after performing router restarts, device restarts, setting the router to use google's dns servers, restarting the modem itself, etc. Ultimately, rolling back to the prior firmware version has fixed the issue (so far), however, there are fixed security vulnerabilities in the latest version.

 

Has anyone else experienced this and/or have an active ticket with Netgear? I had hoped to report a bug with the Netgear folks directly, but I didn't see a great way to do this.

 

Thanks in advance.

9 Replies

  • plemans's avatar
    plemans
    Guru - Experienced User

    Its been an ongoing issue and there's been quite a few posts about it. 

    One fix that has worked for some is to enable IPv6 support in the router. 

    If that doesn't help, its the downgrade firmware option .

    • Pernix's avatar
      Pernix
      Aspirant

      I am having DNS issues since the last firmware update, three months ago.

      I see Netgear knows about the issue but it is not fixing it, so I'll ban forever Netgear from my home, that's it.
      I spent money for a piece of technology that two years after only, turns into a piece of crap, and that's intolerable.

        
         Best Regards

             Tom

    • agibson684's avatar
      agibson684
      Tutor

      The enablement of IPv6 in the router seems to have squelched the DNS Probe issues.  I was seeing trouble with an iPhone 8 and an AppleTV 4K device losing access to the internet when connected to my home Wi-Fi network as well so we shall see if this change puts that issue to rest as well.