Feature Request: Support for Hetzner DNS Migration to Hetzner Cloud Console #557

New Issue

saavagebueno · 2025-11-20T04:24:59-05:00

saavagebueno commented

2025-11-20 04:24:59 -05:00

Originally created by @rueckert-digital on GitHub (Oct 7, 2025).

Description

On October 7, 2025, Hetzner announced that DNS Management is being migrated to the Hetzner Cloud Console:
🔗 Hetzner News – DNS Beta

This change introduces a new management interface and authentication model for DNS zones. It appears that existing API tokens and zone identifiers from the legacy DNS Console (https://dns.hetzner.com) are not compatible with the new Cloud Console (https://console.hetzner.com).

Impact

API Tokens created in the old DNS Console are not migrated automatically.

Token format has changed — new tokens are significantly longer and likely tied to Hetzner Cloud project scope.
API endpoints have also changed:

As a result, tools relying on the legacy Hetzner DNS API (such as ddns-updater) may no longer function properly once users migrate their domains to the Cloud Console.

Request

Please add support for the new Hetzner Cloud DNS API, including:

Updated authentication using new Cloud API tokens.
Compatibility with zone identifiers under the Cloud Console structure.
Optional backward compatibility with the legacy DNS API (if feasible).

Remarks

Fantastic work on ddns-updater — it’s an excellent tool and has worked flawlessly with the old Hetzner DNS API.
This feature would ensure continued compatibility with Hetzner’s new Cloud DNS environment going forward.

Originally created by @rueckert-digital on GitHub (Oct 7, 2025). ### Description On October 7, 2025, Hetzner announced that DNS Management is being migrated to the Hetzner Cloud Console: 🔗 [Hetzner News – DNS Beta](https://www.hetzner.com/news/dns-beta/) This change introduces a new management interface and authentication model for DNS zones. It appears that existing API tokens and zone identifiers from the legacy DNS Console (https://dns.hetzner.com) are not compatible with the new Cloud Console (https://console.hetzner.com). ### Impact 1. API Tokens created in the old DNS Console are not migrated automatically. - [Old tokens](https://dns.hetzner.com/settings/api-token) - [New tokens](https://console.hetzner.com/projects/<project-id>/security/tokens) 2. Token format has changed — new tokens are significantly longer and likely tied to Hetzner Cloud project scope. 3. API endpoints have also changed: - [Legacy DNS API](https://dns.hetzner.com/api-docs/) - [New Cloud DNS API](https://docs.hetzner.cloud/reference/cloud#dns) As a result, tools relying on the legacy Hetzner DNS API (such as ddns-updater) may no longer function properly once users migrate their domains to the Cloud Console. ### Request Please add support for the new Hetzner Cloud DNS API, including: - [ ] Updated authentication using new Cloud API tokens. - [ ] Compatibility with zone identifiers under the Cloud Console structure. - [ ] Optional backward compatibility with the legacy DNS API (if feasible). ### Related Issues / References - #493 - #534 ### Remarks Fantastic work on ddns-updater — it’s an excellent tool and has worked flawlessly with the old Hetzner DNS API. This feature would ensure continued compatibility with Hetzner’s new Cloud DNS environment going forward.

saavagebueno commented

2025-11-20 04:25:00 -05:00

@Julian-Bastelstube commented on GitHub (Nov 15, 2025):

Update from sombody who just got a Domain with Hetzner: It is not possible anymore to create new DNS zones in the old DNS console (https://dns.hetzner.com/). Therefore, it is no longer possible to use this tool for newly created/registerd domains.

@Julian-Bastelstube commented on GitHub (Nov 15, 2025): Update from sombody who just got a Domain with Hetzner: It is not possible anymore to create new DNS zones in the old DNS console (https://dns.hetzner.com/). Therefore, it is no longer possible to use this tool for newly created/registerd domains.

saavagebueno commented

2025-11-20 04:25:00 -05:00

@janolehuebner commented on GitHub (Nov 15, 2025):

Update from sombody who just got a Domain with Hetzner: It is not possible anymore to create new DNS zones in the old DNS console (https://dns.hetzner.com/). Therefore, it is no longer possible to use this tool for newly created/registerd domains.

you could fork the repo and merge this PR yourself. i did that, built my own image and everything works.

@janolehuebner commented on GitHub (Nov 15, 2025): > Update from sombody who just got a Domain with Hetzner: It is not possible anymore to create new DNS zones in the old DNS console (https://dns.hetzner.com/). Therefore, it is no longer possible to use this tool for newly created/registerd domains. you could fork the repo and merge [this PR](https://github.com/qdm12/ddns-updater/pull/1046) yourself. i did that, built my own image and everything works.

saavagebueno commented

2025-11-20 04:25:00 -05:00

@rueckert-digital commented on GitHub (Nov 15, 2025):

Great work, @janolehuebner ...
Looking forward for merge and new docker image, @qdm12 😉

@rueckert-digital commented on GitHub (Nov 15, 2025): Great work, @janolehuebner ... Looking forward for merge and new docker image, @qdm12 😉

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ddns-updater#557