You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you update a host to the IP which is already set, no actual changes will happen to the records, but it'll still cause the SOA-EDIT (if configured in PowerDNS) to trigger, and it updates the serial needlessly.
I suppose this is a minor gripe, but if you just send regular updates via cron jobs, 99% of them will be the IP that the host already has, and depending on the number of hosts being updated, this has the potential to increment your serial number a lot. If you set SOA-EDIT-API to the YYYYMMDD01 format, then it could easily cause so many updates that you use up that 'one hundred per day' on the end there and it'll start overflowing into the next day.
I wonder if we could have dyndns-pdns check to make sure it's actually making a change before trying to push an update to the record(s).
The text was updated successfully, but these errors were encountered:
If you update a host to the IP which is already set, no actual changes will happen to the records, but it'll still cause the SOA-EDIT (if configured in PowerDNS) to trigger, and it updates the serial needlessly.
I suppose this is a minor gripe, but if you just send regular updates via cron jobs, 99% of them will be the IP that the host already has, and depending on the number of hosts being updated, this has the potential to increment your serial number a lot. If you set SOA-EDIT-API to the YYYYMMDD01 format, then it could easily cause so many updates that you use up that 'one hundred per day' on the end there and it'll start overflowing into the next day.
I wonder if we could have dyndns-pdns check to make sure it's actually making a change before trying to push an update to the record(s).
The text was updated successfully, but these errors were encountered: