Option to set interval of forced Dynamic DNS updates
I use dy.fi dynamic DNS service. It requires refreshing the IP every 7 days (even if it does not change) or it is released.
I have configured this via Custom 'Service Type' in the Dynamic DNS Clients. It works, but the update interval would seem to be hardcoded to 25 days based on the system log ("rc.dyndns.update: phpDynDNS (): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry. "). At least I did not find any practical way to configure this value.
Could it be possible to get this value configurable for the custom option?
I found at least the following: https://github.com/pfsense/pfsense/blob/6c4ccc9f76786f940a358698b6e2a7f0245b626d/src/etc/inc/services.inc. Around line 2643 there is "$maxCacheAgeSecs = 25 * 24 * 60 * 60;". I edited that via Diagnostics->Edit File to be 7 days. This did not change the log texts (not sure if it still actually works, has not been 7 days since). Log text would appear to come from https://github.com/pfsense/pfsense/blob/45ff6b8f1d574b3786d25286abc4978427675974/src/etc/inc/dyndns.class around line 2165.
(PFSense version 2.4.4-RELEASE (amd64))
P.S. I have previously used dd-wrt, which did have the option to select update interval in days. Also sorry in case making the issue was incorrect procedure.
Updated by Jaakko Kantojärvi over 2 years ago
Yes. My fix implements this specific provider. The generic solution, i.e. including the interval time as a form field, would require adding the value to the function arguments. I didn't want to touch that logic yet. I could look into that, once I the specific provider is done.
Updated by Jim Pingle about 2 years ago
- Status changed from Feedback to New
- Assignee changed from Renato Botelho to Jim Pingle
This appears to have introduced a bug. Any time the Dynamic DNS update process is triggered, it forces an update:
rc.dyndns.update: DynDns (<blah>): Dynamic Dns: More than 0 days. Updating. 1630066701 - 1630040466 > -3600
$this->_dnsMaxCacheAgeDays is ending up as
0. There is no configuration for
maxcacheage value in the GUI or config.xml