DDNS does not update automatically when router reboot

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
DDNS does not update automatically when router reboot
DDNS does not update automatically when router reboot
2013-02-14 02:41:21 - last edited 2021-08-21 03:12:10
Region : Others

Model : TL-R488T

Hardware Version : V3

Firmware Version : 3.7.1 Build 091203 Rel.53376s

ISP :


Dear All,
I have TP LINK 488T loadbalancer. The device information are as follows,

Firmware Version: 3.7.1 Build 091203 Rel.53376s
Hardware Version: R488T V2/V3 00000000

WAN1 port is set to PPPoE mode. The ADSL modem is set in bridge mode and both works fine. I created a DDNS account at no-ip.com and enable DDNS and set the DDNS information on the WAN1 port on Dynamic DNS page of the router WEB interface. These information are also saved for WAN1 port. I can update my public IP when I click on Connect button on the router interface. At that time it shows Connect status : succeeded! and my WAN IP is correctly reflected at no-ip.com.

when the WAN1 IP address is changed, perhaps the router reboots, the [COLOR="#FF0000"]
DDNS record is not updated automatically. At this time the Connect Status shows Not Launching! on Dynamic DNS page. Although when I click on the login button on Dynamic DNS page, it then connect to no-ip.com and update the DDNS record correctly there.

My question where is the problem , in the router configuration or in the firmware?

Your valuable suggestions are welcomed.
Thanking in anticipation.
  0      
  0      
#1
Options
2 Reply
Re:DDNS does not update automatically when router reboot
2013-02-14 14:52:53 - last edited 2021-08-21 03:12:10
Seems the problem causes by the firmware.
  0  
  0  
#2
Options
Re:DDNS does not update automatically when router reboot
2013-02-14 23:59:10 - last edited 2021-08-21 03:12:10
The firmware is the latest one for the product. Also the product is discontiuned by TP Link.

What to do next?
  0  
  0  
#3
Options