dns/ddclient Hetzner [hetzner.cloud] API not updating existing record

[jnikodemus]

Is it intended to not update the pre-existing record after reboot? I've noticed that it creates a new record just fine but after a reboot the record is not updated. Here are my steps to reproduce:

1. Setup the provider (with token read+write access, no Record protection enabled)
2. Enable it and see it first time creating the A record
3. Reboot Opensense to get a new DHCP lease on WAN
4. Record is not updated contrary to what the log states

Logs:
Initial successful creation:

2026-01-31T15:10:28 Notice ddclient Flush dyndns status to disk
2026-01-31T15:10:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] updated
2026-01-31T15:10:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] set new IP 80.132.66.180 for dummyhostname
2026-01-31T15:10:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] created dummyhostname A with 80.132.66.180
2026-01-31T15:10:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] updating dummyhostname (record: dummyhostname, type: A) to 80.132.66.180
2026-01-31T15:10:27 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] found zone ID 25717 for dummydomain.tld
2026-01-31T15:10:27 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] executing
2026-01-31T15:10:27 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] uses Hetzner for service
2026-01-31T15:09:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] not modified
2026-01-31T15:09:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] executing
2026-01-31T15:09:28 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] uses Hetzner for service

After reboot:

2026-01-31T15:14:19 Notice ddclient Flush dyndns status to disk
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] updated
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] set new IP 80.132.79.213 for dummyhostname
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] updated dummyhostname A to 80.132.79.213
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] updating dummyhostname (record: dummyhostname, type: A) to 80.132.79.213
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] found zone ID 25717 for dummydomain.tld
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] executing
2026-01-31T15:14:19 Notice ddclient Account REMOVED [hetzner - Home DynDNS IP] uses Hetzner for service

I have also checked the Hetzner account logs that shows a single successful " zone.rrset.update " activity after reboot but the RRSET is not updated at all and suck with the old IP. The log sadly does only state where the requests came from and not what has been tried to set.

Originally posted by @dporki in #5082 (comment)

[OPNsense-bot]

Thank you for creating an issue.
Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository,
please read https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.