What's the frequency of ddns-start runs?

[XIII]

For quite some time I have successfully been using a custom ddns-start script and Inadyn to set up DNS records at Cloudflare.

This week I discovered healthchecks.io. I have configured checks for several cron (cru) jobs on the router (and my Raspberry Pi), but would like to monitor ddns-start runs as well, if possible.

What triggers ddns-start runs?

Is there a guaranteed frequency (interval between runs), even if there's no other trigger (such as a reboot)? (like "every 21 days")

 

[XIII]

PS: If there’s no fixed frequency, would it “hurt” if I schedule a cron job to run ddns-start once a day?

 

[Crimliar]

Wouldn't this be tied to the "wan-event" script, so it only runs when it needs to on a change of the WAN connection?

 

[XIII]

Probably.

 

[ColinTaylor]

Is there a guaranteed frequency (interval between runs), even if there's no other trigger (such as a reboot)? (like "every 21 days")

What, other than the "Forced update interval (in days)" option?

 

[XIII]

What, other than the "Forced update interval (in days)" option?

That's the other thing I had in mind and need to check now... Thanks!

 

[bluepoint]

For quite some time I have successfully been using a custom ddns-start script and Inadyn to set up DNS records at Cloudflare.

This week I discovered healthchecks.io. I have configured checks for several cron (cru) jobs on the router (and my Raspberry Pi), but would like to monitor ddns-start runs as well, if possible.

What triggers ddns-start runs?

Is there a guaranteed frequency (interval between runs), even if there's no other trigger (such as a reboot)? (like "every 21 days")

I don't know if this is the intended purpose but since I enabled native IPv6 in dual stack, ddns triggers every hour.

Dec 11 09:59:29 rc_service: dhcp6c 24818:notify_rc restart_ddns
Dec 11 09:59:29 custom_script: Running /jffs/scripts/service-event (args: restart ddns)
Dec 11 09:59:29 ddns: update WWW.ASUS.COM update@asus.com, wan_unit 0
Dec 11 09:59:29 ddns: Clear ddns cache.
Dec 11 09:59:29 ddns: Start Inadyn(10).
Dec 11 09:59:29 inadyn[24828]: In-a-dyn version 2.9.1 -- Dynamic DNS update client.
Dec 11 09:59:29 inadyn[24828]: Update forced for alias xxxxxxxxx.asuscomm.com, new IP# 108.30.xxx.xxx
Dec 11 09:59:29 inadyn[24828]: alias address=<108.30.xxx.xxx>
Dec 11 09:59:29 inadyn[24828]: request<GET /ddns/update.jsp?hostname=xxxxxxxxx.asuscomm.com&myip=108.30.xxx.xxx&model=RT-AX88U&fw_ver=3.0.0.4.388.1_0 HTTP/1.0^M Authorization: Basic MDRENEM0NEZGRUUwOjkxMzUxRTI5OTJCRjI3RkNCMjZFNDg5RDZFRjhBMyyyyy Host: ns1.asuscomm.com^M User-Agent: inadyn/2.9.1 https://github.com/troglobit/inadyn/issues^M ^M >
Dec 11 09:59:29 inadyn[24828]: [response_update]HTTP/1.1 200 OK^M Date: Sun, 11 Dec 2022 14:59:29 GMT^M Server: Apache^M Content-Length: 0^M Connection: close^M Content-Type: text/html; charset=UTF-8^M ^M
Dec 11 09:59:29 inadyn[24828]: Updating cache for xxxxxxxxxx.asuscomm.com

 

[archiel]

AFAIK DDNS on IPv6 will trigger based on the lease length provided by your ISP. So as mine has 1 Hour, DDNS is every 30 mins (checks 30 minutes before expiry and on expiry). It may will be that DDNS on IPv4 does the same, simply that it does not report to Syslog unless there is an actual change. I would assume that the Forced update interval (in days) is there as a longstop.

 

[XIII]

My provider does not offer IPv6, so it’s IPv4 only for me.