NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Routers not recognizing DNS changes
I am a web developer with matching R6260 routers at both my home and office. Both connected to the same ISP.
In the past week I have made 3 changes to my client websites - 2 nameservers changes, and one A record change - and the changes have been very slow to be recognized.
One nameservers change that I applied on Friday is still not being recognized by either of my routers on Monday morning. I can confirm that the change has propagated virtually everywhere, including my local ISP via NSLOOKUP. I get the new site on my cellphone using mobile data. But when connected to my Netgear routers, in both locations, I still see the old site.
The change that I made to a different site on Thursday was not available to my home computer until Sunday, and started resolving at my office sometime over the weekend (it was finally OK on Monday morning.)
I understand that TTL values come into play. But when my local ISP has had the proper updated information for 24+ hours, how long should I expect my 192.168.1.1 to continue to route to the old value?
What is most concerning is that this is happening with both routers. I've tried rebooting and applied a firmware upgrade, but the problem persists. ipconfig /flushdns does not make any difference.
I've had these routers for some time and have never noticed an issue like this until this past week.
Will it clear it up? Unknown but its worth a shot.
Its pretty easy to switch it back if it doesn't.
Again, if you have ipv6 enabled, check that as well.
What modem/gateway is it connected to?
You can also make a backup if you think it might corrupt something.
8 Replies
The router doesn't save the dns info. Each request it gets, it uses whatever you've set for your DNS server to get the proper ip address info.
You could try changing the router's dns server as maybe your ISP doesn't have it fully done.
Try a different DNS Server. Here's a few for ipv4. Also remember to change the ipv6 dns server if ipv6 is enabled
CloudFlare 1.1.1.1 and 1.0.0.1
GoogleDNS 8.8.8.8 and 8.8.4.4Thank you for the reply.
I'm reaching out to a friend who is on the same ISP, but obviously not using my routers, to see what result he gets.
Here is what I get on an NSLOOKUP, querying for the domain by itself (192.168.1.1), my ISP's DNS, and 8.8.8.8. The old IP of the website begins with 216, and the new/correct IP begins with 199.
C:\Users\matt>nslookup
Default Server: www.routerlogin.com
Address: 192.168.1.1> websiteinquestion.com
Server: www.routerlogin.com
Address: 192.168.1.1Non-authoritative answer:
Name: websiteinquestion.com
Address: 216.xxx.xxx.xxx> websiteinquestion.com myispdns.net
Server: myispdns.net
Address: xxx.xxx.xxx.xxxNon-authoritative answer:
Name: websiteinquestion.com
Address: 199.xxx.xxx.xxx> websiteinquestion.com 8.8.8.8
Server: [8.8.8.8]
Address: 8.8.8.8Non-authoritative answer:
Name: websiteinquestion.com
Address: 199.xxx.xxx.xxx>
Is it possible that while my ISP is receiving the correct IP, it isn't providing it to me?
Just heard back from my friend who has the same IP. He got the new website. So it appears as though the ISP is properly sending incoming traffic to the right place.
How might I get my local router(s) at 192.168.1.1 to send me to the right place?
I guess I can just wait another day or two, but especially since I'm the one administering the DNS changes it would be nice to be able to verify propagation locally.