NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kyk
Sep 05, 2021Tutor
R6700v3 — Nighthawk AC1750 Smart WiFi Dual Band Gigabit Router DNS problem with Spectrum
DNS Problem I have an R6700v3 — Nighthawk AC1750 Smart WiFi Dual Band Gigabit Router I have an ongoing internet problem. This is randomly occurring. It’s not site specific but happens on some sig...
plemans
Sep 05, 2021Guru - Experienced User
How longs it been going on?
The last firmware pushed out seemed to cause a lot of dns issues.
Most fixed it by downgrading a version and are now waiting on netgear to update.
have you tried this?
- kykSep 05, 2021Tutor
Thank you. I'll try downgrading my router.
Another observation...
I don't seem to have the problem when connect through a VPN.
- Jambo11230Nov 09, 2021Aspirant
Did downgrading your firmware resolve your issue? I've just moved to Spectrum, and I am using the R8000P. I am receiving intermittent DNS_PROBE_FINISHED_NXDOMAIN errors, with very similar behavior to that which you describe. Roku works fine, Phones work fine, Windows PCs all exhibit errors.
- kykNov 09, 2021Tutor
I started using a vpn. That took care of the problem for me.
I'm curious though, did you have the problem with your last provider?
I'm thinking it's a spectrum problem.
Maybe Windows 11 will help.
- jinxtMar 03, 2022Aspirant
I am also a Spectrum customer with very similar DNS issues. However, VPN is not a solution for me.
My question is fundamentally if it has been established (within this forum or otherwise) that this type of issue is entirely within Spectrum's realm, or is the consensus currently that this is squarely a Netgear Router problem??
Acting on other relevant posts in this forum, I downgraded 2 days ago to V 1.0.4.102_10.0.75 from the currently available V 1.0.4.126_10.0.102 which had no positive effect on this issue.
I have 3 windows 10 PC's, 2 Roku's, 2 LG TV's with WEB OS, 2 Android smart phones, all of which singularly only get online with their adapter settings using fixed Google DNS settings. I had this problem now for over a year and am about to dump this router.
While I was getting by with this arrangement until now, my brand new Tesla’s wireless network adapter is unable to connect to my network/internet. “unable to get IP address”.
No interface exists to its network adapter to make any DNS changes. It is using “automatic DNS mode”. Strong wifi signal at car. My laptop connects properly at same physical location (albeit with Google DNS).
Doing more investigation, I noticed that router internal time is Sep 22, 2020 and is stuck there. Also had eastern time zone selected.
Was able to correct time Zone, but no effect on date/time.
Automatic adjustment is selected.
Default Netgear NTP is selected.
Could incorrect time stamp be behind this DNS issue?
Tried using “time.cloudflare.com” to no effect, router apparently never connects to any such site.
Multiple Modem/router factory resets had no effect either.
Router user interface after login shows RED “no Internet” on Basic Home Tab. However, when selecting the “Advanved” tab, it shows the internet port with a green check mark and I can get online without any issues as long as I use google DNS on the adapters.
It appears that some router internal portion thinks it has no internet and (perhaps) this is why it never updates its date/time?? A case of “split” personality?
Welcome any useful input. Thanks.
- KitsapMar 04, 2022Master
Yes, the ntp time issue could impact your DNS response. The Netgear time server always seemed inconsistent in its response to my location. Sometimes it responded quickly and sometimes not.
Do a search for ntp servers. Several options will come up if you are in the US. One is pool.ntp.org. I use this one in Washington state and it works fine with OpenDNS.
Here is a link: https://timetoolsltd.com/information/public-ntp-server/
From the government, try time.nist.gov.
- kykMar 04, 2022Tutor
Problem solved. Moved to a new house. Still have Spectrum but everything works here. Looks to me like there was a connection issue at the old house.
Note, I was moving anyway, I didn't buy a new house to fix the issue.