What's new

DDNS forced updates working as intended

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

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
 
I can confirm that forced update interval for DDNS works well - I have configured 3 days:
Code:
admin@RT-AX88U:/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

Sign Up For SNBForums Daily Digest

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