hetzner: new API (Hetzner Cloud DNS)

[jooola]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, the DNS provider exposes a public API.
• Yes, I know that the lego maintainers don't have an account in all DNS providers in the world.
• Yes, I'm able to create a pull request and be able to maintain the implementation.
• Yes, I'm able to test an implementation if someone creates a pull request to add the support of this DNS provider.

How do you use lego?

I don't know

Link to the DNS provider

https://www.hetzner.com/

Link to the API documentation

https://docs.hetzner.cloud/reference/cloud#dns

Additional Notes

Dear maintainers,

This project hold 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.

[ldez]

Hello,

I feel like 1 month to migrate to a new API is a short time.

---

I would prefer not to use your API client because:

The dependencies

• github.com/jmattheis/goverter
• github.com/vburenin/ifacemaker
• github.com/prometheus/client_golang

The generators are dev dependencies, but they will increase the size of the module cache.

The Prometheus dependency is not useful for lego, and this is the type of dependency that has recurring compatibility issues.

The client depends on all structures

• https://github.com/hetznercloud/hcloud-go/blob/7a591b7c57103f451f85e797f8818b38f0c3d1aa/hcloud/client.go#L100-L119

As the client, per design, has a dependency on all structures, it will increase the size of the lego binary.

---

If you want to understand why I'm attentive to those things: #2590

---

If you want to implement an internal lightweight client inside lego, it will be welcome.

[jooola]

I feel like 1 month to migrate to a new API is a short time.

Note that the old API will still be working after the beta ended, only the creation of new Zones will not be available.

I would prefer not to use your API client

I understand :)

If you want to implement an internal lightweight client inside lego, it will be welcome.

I do not have the time to implement this, but some other can pick this task.

[jooola]

I feel like 1 month to migrate to a new API is a short time.

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.

[wimwenigerkind]

Hello,
I would like to implement the new Hetzner DNS API if the task is still available.
My question: Should I update the existing Hetzner provider or create a new separate provider?

[ldez]

I am already working on it, but I will need Hetzner user to test the PR.

[jojugaad]

Hey there, we're also affected by this and do very much appreciate that you're working on this already @ldez. Happy to support with testing.

[ski7777]

If you need somebody to test it, just hit me up here

[ldez]

The PR is ready to be tested: #2663

---

I hope you enjoyed my work. Please consider supporting me.

My only source of income is from donations.

This will be appreciated, thank you ❤️

https://donate.ldez.dev/