Migrate to the new Hetzner DNS API

[jooola]

Dear maintainers,

This project holds a DNS provider for the old Hetzner DNS API.

A new Hetzner DNS API has been released.

We recommend any consumer of the old Hetzner DNS API to migrate to the new one.

The new Hetzner DNS API is currently in beta, which will likely end (reaching GA) on 10 November 2025. After the beta ended, it will no longer be possible to create new zones in the old DNS API (the old API will still be functional until May 2026). See the Hetzner DNS beta FAQ for more details.

If needed, an API client has already been implemented: https://github.com/hetznercloud/hcloud-go

Links:

• Hetzner DNS documentation: https://docs.hetzner.com/networking/dns
• Hetzner DNS API reference: https://docs.hetzner.cloud/reference/cloud#dns
• User migration guide to the new DNS system: https://docs.hetzner.com/networking/dns/migration-to-hetzner-console/process

If you have any additional questions, please let me know.

[cafferata]

Ping @das7pad, the maintainer of the Hetzner provider.

[das7pad]

Thank you for the heads up @jooola . I see that your release notes/library changes are fresh off the press (merged 11h ago).

When do you expect wider adoption for this new API? Did you run a private beta or any other kind of external testing?

Thank you for linking to your reference implementation. Are you interested in taking on a migration to this API client in dnscontrol? If not, I prefer delaying the adoption until after it reached GA and no further breaking changes are expected.

https://github.com/hetznercloud/hcloud-go/blob/7a591b7c57103f451f85e797f8818b38f0c3d1aa/hcloud/zone.go#L116
// Experimental: DNS API is in beta, breaking changes may occur within minor releases.

Notes from glancing over your documentation:

• It is great to see an endpoint for bulk deletion of records.
• https://docs.hetzner.com/networking/dns/migration-to-hetzner-console/process/ "The migration is a one-way process, it cannot be undone!" That sounds very risky to me! I think it is best to defer adoption in dnscontrol until after GA to avoid breaking DNS for users.
• The pagination limit for listing records seems quite low to me (50 per request). Are you planning on increasing it?

[jooola]

When do you expect wider adoption for this new API? Did you run a private beta or any other kind of external testing?

We did run an internal beta, the public beta should end (reaching GA) on 10 November 2025. The old API will still be functional until May 2026, we will just prevent adding new zones to the old system after the beta of the new system ends.

All our official integrations are tested against the API.

Are you interested in taking on a migration to this API client in dnscontrol? If not, I prefer delaying the adoption until after it reached GA and no further breaking changes are expected.

I do not have the time to do this, anyone is welcome to pick this up. I'll happily answer questions where I can.

The pagination limit for listing records seems quite low to me (50 per request). Are you planning on increasing it?

I'll check this and come back to you with an answer.

I think it is best to defer adoption in dnscontrol until after GA to avoid breaking DNS for users.

Fair enough :) Ideally the implementation and testing could already take place during the beta.

EDIT: Wrong button, need some ☕

[fkrauthan]

I assume because this project currently uses the old API and I've created an API key on the new console I get the Invalid authentication credentials error message? Or should I report that as a separate bug?

[LKaemmerling]

The pagination limit for listing records seems quite low to me (50 per request). Are you planning on increasing it?

@das7pad regarding the pagination limit of 50, we just deployed the change to increase this to 100 for this specific endpoint. (Should also be documented in the public API in a couple of minutes).

[sokai]

JFYI (= no solution): libdns/hetzner#11 (+ caddy-dns/hetzner#18)
KR

[Aartsie]

Maybe we can separate the Hetzner api's in 2 (old and new)? So you can let users use the "old" DNS console and for new domains you can use the new Hetzener console API?

Because now we are stuck, since 10-11-2025 we can't create new zones anymore on the old Hetzner DNS console platform.

[das7pad]

I've opened #3837 with a HETZNER_V2 provider for the new Hetzner DNS API.