Feature request: force an update periodically even if the ip is unchanged #538

New Issue

saavagebueno · 2025-11-20T04:24:47-05:00

saavagebueno commented

2025-11-20 04:24:47 -05:00

Originally created by @h7io on GitHub (Jun 23, 2025).

What's the feature?

A setting for a forced update interval.

Extra information?

Some providers (like freemyip) require a periodic update, regardless if the ip changed, or the subdomain gets removed.

Originally created by @h7io on GitHub (Jun 23, 2025). 1. What's the feature? A setting for a forced update interval. 2. Extra information? Some providers (like freemyip) require a periodic update, regardless if the ip changed, or the subdomain gets removed.

saavagebueno commented

2025-11-20 04:24:48 -05:00

@MikeV7896 commented on GitHub (Jul 20, 2025):

I've seen multiple providers that do this, to clean up hostnames that may no longer be active, rather than relying on the user to delete it. Most of the services I've seen usually do this after 30 days.

Maybe create a parameter (--force-update) and set a number of days after which to force an update to all DDNS entries. That lets the user turn it on if needed, and set the number of days in case their provider might have a shorter or longer limit.

@MikeV7896 commented on GitHub (Jul 20, 2025): I've seen multiple providers that do this, to clean up hostnames that may no longer be active, rather than relying on the user to delete it. Most of the services I've seen usually do this after 30 days. Maybe create a parameter (--force-update) and set a number of days after which to force an update to all DDNS entries. That lets the user turn it on if needed, and set the number of days in case their provider might have a shorter or longer limit.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#538