Router sets an old IP for DynDNS
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Have an issue with DynDNS with my router. Worked fine for months, but the other day my ISP must have done something, and I start getting quite different IP's form them. Used to be 31.x.x.x but now I get 100.x.x.x.
The router works fine with the new IP's, but my DynDNS service stopped. It do work in the sense that the router sends an IP to DynDNS, but it sends an old IP. The router log frankly says it does not send the current WAN IP but rather one I had a few days ago, and the logs at DynDNS confirms this. Tried the obvious stuff like reboot and renew WAN IP, but no change. Also tried the custom setting, and same behavior.
Any ideas?
you should note that the interval time you set for the update.
if it is 1 hour, you will have this 1 hour lag and you are required to manually log in to it and refresh it.
controller mode offers an extra option to set a custom time.
update:
and if you get 100.X IP, isn't that CGNAT?? you should contact your ISP. that's not a public IP address. not an issue with the router at all, bro.
you should note that the interval time you set for the update.
if it is 1 hour, you will have this 1 hour lag and you are required to manually log in to it and refresh it.
controller mode offers an extra option to set a custom time.
update:
and if you get 100.X IP, isn't that CGNAT?? you should contact your ISP. that's not a public IP address. not an issue with the router at all, bro.