pfSense

I've had numerous occurrences where dynamic DNS entries either do not get updated at or have the wrong IP. Two factors that exacerbate the issue seem to be multiple up/down interface state changes in a short period of time dynamic DNS entries that monitor a gateway group. There are many log entries, which ultimately indicate that the DNS changes were made successfully. It seems several interface state change events occur in under 60 seconds cause the dynamic DNS update process to trip over itself. Starlink modems seem to be the worst for this.

I think reasonable workarounds for this issue include:

1. Allow for specifying custom update intervals other than the current hardcoded values of 6 or 25 days.
2. Allow specifying to forcefully update some or all dynamic DNS entries.
3. Allow a small random delay to avoid API rate limits when updating a large number of records, which can be an issue when using dynamic DNS on many firewalls. (Route53 has a hard limit of 5 API requests per second across the entire account.)

Examples of the desired behavior would be:

1. Forcefully update a specific dynamic DNS entry every 5 minutes.
2. Forcefully update all dynamic DNS entries every hour.

In any case, the current values of caching for 6 or 25 days seems very high and antiquated, so maybe just significantly reducing $maxCacheAgeSecs in services.inc and _dnsMaxCacheAgeDays in dyndns.class would be the simplest solution?