Feature Request: Support for new DNS Console (via Hetzner Cloud API)

[bahuma20]

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/).

The old DNS console will be shut down in May 2026.

Impact

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

• Old tokens
• New tokens
• Token format has changed — new tokens are significantly longer and likely tied to Hetzner Cloud project scope.

2. API endpoints have also changed:

• Legacy DNS API
• New Cloud DNS API

As a result, tools relying on the legacy Hetzner DNS API (such as cert-manager-webook-hetzner) 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:

If so i would recommend the following procedure:

• Now: Add new API integration and configuration property for old or new dns console (default: old)
• May 2026: remove old API integration

I would love to help with the implementation but i am not fluent enough on Go 🙈

[josipnedic]

It seems that Hetzner implemented their own cert-manager-webhook-hetzner which works with the new Hetzner DNS API:

https://github.com/hetzner/cert-manager-webhook-hetzner

I'm just curious why they created a new GitHub organization (https://github.com/hetzner) and not using the existing one (https://github.com/hetznercloud).