Bug 10606 - feature request: send an update unconditionally, but only in long intervals
Summary: feature request: send an update unconditionally, but only in long intervals
Alias: None
Product: DDNS Updater
Classification: Unclassified
Component: Core (show other bugs)
Version: unspecified
Hardware: unspecified Unspecified
: - Unknown - Minor Usability
Assignee: Stefan Schantl
QA Contact: Michael Tremer
Depends on:
Reported: 2014-08-28 16:04 UTC by Thomas Waldmann
Modified: 2014-08-28 20:53 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Waldmann 2014-08-28 16:04:00 UTC
as a free and unannoying dyndns provider, like nsupdate.info, you have one problem:

you never know whether a dynamic host entry is still used in case you do not receive updates for a while.

it could be unused, but also it could be a cable internet user whose ip rarely or never changes (or it could be even a static ip and the user just using your service to get an easy hostname although it's not really "dynamic").

so, basically, cleanup of your host database is impossible, because you do not know what's still alive and what not.

on the client side (IPFire side) you could help a bit by doing unconditional updates in long intervals.

like e.g. if your (well behaved) update client did not send an update since 1 week (because your IP did not change), send one! This will result in a nochg response, but as long as you do that in long intervals only, this is no problem.
Comment 1 Stefan Schantl 2014-08-28 20:25:03 UTC
IPFire offers this feature by using cron and performing a forced update once a week.