Hetzner DNS
Hetzner DNS is reached through the Hetzner Cloud API (api.hetzner.cloud) with a single project API token. Fast propagation and unlimited DNS-01 volumes make this a great option for labs and small-scale prod.
CertAutoPilot talks to the Hetzner Cloud API only. A token created in the old DNS Console (dns.hetzner.com) is a different key type and is refused. Create the token in the Hetzner Console project that holds the zone, as below.
Prerequisites
- A Hetzner Console project.
- The zone managed in that project's DNS. A zone still on the legacy DNS Console or on Konsoleh is not visible to the Cloud API; move it into the project first.
- Outbound HTTPS from CertAutoPilot to
api.hetzner.cloud— see Outbound network access.
Create the API token
- Sign in to the Hetzner Console and open the project that holds the zone.
- Security → API tokens → Generate API token.
- Name:
certautopilot-dns. Permission: Read & Write. Copy the token — shown once.
A token is scoped to its project, not to a single zone: it can change every zone and resource in that project. Keep DNS zones in a dedicated project if that matters, and rotate the token on a schedule.
Add the credential
- Settings → DNS Credentials → New → Hetzner.
- Name:
hetzner-example-prod. - API token: paste.
- Test connectivity → Save.
Config fields
| Field | Required | Purpose |
|---|---|---|
api_token | yes | Hetzner Cloud project API token (Read & Write). |
Propagation
Hetzner propagates in under 30 seconds typically. Default settings work.
Troubleshooting
"Unauthorized"
The token is wrong, revoked, or a legacy DNS Console token. Create a Read & Write token in the Hetzner Console project that holds the zone.
"Forbidden"
The token is read-only: it can list the zone but not write the challenge record. Create a Read & Write token in the same project.
"Zone not found"
The zone is not in the token's project — it is in another project, or still on the legacy DNS Console or Konsoleh. Move it into the project the token belongs to.