DDNS forced updates working as intended

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

RMerlin

Asuswrt-Merlin dev
Some people expressed doubts that ddns updates were properly being enforced after a certain number of days (configured on the webui). Since for a rare occasion I actually broke a month of uptime on my primary router...

Code:
Sep 19 03:17:34 watchdog: Forced DDNS update (after 21 days)
Sep 19 03:17:34 rc_service: watchdog 1130:notify_rc restart_ddns
 

joegreat

Very Senior Member
I can confirm that forced update interval for DDNS works well - I have configured 3 days:
Code:
[email protected]:/tmp# grep restart\ ddns syslog.log*
syslog.log-1:Sep  7 08:18:09 START_service-event: started [restart ddns]
syslog.log-1:Sep  7 08:18:10 START_service-event-end: started [restart ddns]
syslog.log-1:Sep 10 08:18:09 START_service-event: started [restart ddns]
syslog.log-1:Sep 10 08:18:10 START_service-event-end: started [restart ddns]
syslog.log-1:Sep 13 08:18:09 START_service-event: started [restart ddns]
syslog.log-1:Sep 13 08:18:10 START_service-event-end: started [restart ddns]
syslog.log:  Sep 16 08:19:44 START_service-event: started [restart ddns]
syslog.log:  Sep 16 08:19:44 START_service-event-end: started [restart ddns]
syslog.log:  Sep 19 08:19:49 START_service-event: started [restart ddns]
syslog.log:  Sep 19 08:19:49 START_service-event-end: started [restart ddns]
The syslog entries are generated by my custom service-event script (triggered by the DDNS restart).
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top