mirror of
https://github.com/qdm12/ddns-updater.git
synced 2026-08-02 10:38:41 -04:00
Feature request: Force a change of the DNS record #261
Assignees
saavagebueno
Clear assignees
saavagebueno
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: starred/ddns-updater#261
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Jeppedy on GitHub (Mar 1, 2023).
Originally assigned to: @qdm12 on GitHub.
I changed my GoDaddy DNS address manually to confirm this great solution was working. Because TTL is one hour for my record, and because the updater does a DNS resolution to see if the configured IP matches the current IP, the utility doesn't recognize my manual IP update yet.
While I understand what's happening, and I understand that when the TTL expires, the utility will recognize my tweaked IP and update it, I'd think it would be good to have a Force parameter, or a "IF No updates.json, force update", etc to help override and perform the update, even if DNS is resolving to match the current IP.
@qdm12 commented on GitHub (Jan 19, 2024):
That's a good idea, I'll add something in the UI (and future API) to force an update without comparing against the resolved ip. Thanks for proposing this!