-

[JonesH]

Add Hetzner Cloud DNS provider (hetznerhcloud)

Summary

Implements DNS-01 challenge support for Hetzner Cloud DNS API (api.hetzner.cloud/v1/zones), distinct from the existing hetzner provider which targets the legacy DNS API (dns.hetzner.com).

Motivation

Hetzner Cloud customers managing DNS zones via the Cloud API require a unified token strategy. Current hetzner provider necessitates separate DNS-specific credentials, incompatible with Cloud
API tokens used for infrastructure-as-code workflows.

Implementation

Provider: 373 LOC total

• Core: 140 lines implementing challenge.Provider interface
• HTTP client: 108 lines (internal package)
• Tests: 101 lines (76% coverage)
• Metadata: 24 lines (TOML-driven documentation)

API Integration:

• GET /v1/zones → Zone resolution with caching
• POST /v1/zones/{id}/records → TXT record creation
• DELETE /v1/zones/{id}/records/{id} → Record cleanup
• Bearer token authentication
• Thread-safe concurrent operation support

Patterns Followed:

• Standard Lego provider interface (Present, CleanUp, Timeout)
• Environment-based configuration via platform/config/env
• Internal client package for HTTP abstraction
• Auto-generated documentation from TOML metadata
• Mutex-protected record ID caching for cleanup correlation

Testing

go test ./providers/dns/hetznerhcloud/...

PASS - 76% coverage, 3 test scenarios

Configuration

HCLOUD_TOKEN=xxx lego --dns hetznerhcloud -d example.com run

Optional: HCLOUD_TTL, HCLOUD_PROPAGATION_TIMEOUT, HCLOUD_POLLING_INTERVAL, HCLOUD_BASE_URL, HCLOUD_HTTP_TIMEOUT

Validation

• ✅ Builds without errors
• ✅ Tests pass with coverage
• ✅ Documentation auto-generated via make generate-dns
• ✅ Provider registered in zz_gen_dns_providers.go
• ✅ CLI help integrated via zz_gen_cmd_dnshelp.go
• ✅ Follows existing provider conventions

Related

• Existing provider: hetzner (legacy DNS API)
• API docs: https://docs.hetzner.cloud/reference/dns
• Addresses: Single-token workflow for Hetzner Cloud users

[ldez]

You should use your brain instead of AI.

Look for issues and PRs, and you will see that Hetzner Cloud DNS is already supported.

• hetzner: new API (Hetzner Cloud DNS) #2662
• hetzner: update to new API #2663

[ldez]

I ask you to sponsor the project for wasting my time -> https://donate.ldez.dev/

[JonesH]

I'm so sorry I really didn't want to make you angry... good morning to you, too