As the title suggests, Hetzner is changing it's DNS infrastructure with API changes as well. This causes the DNS provider Hetzner not working as expected.

See for more details: https://www.hetzner.com/news/dns-beta/

·
·

Fixed! Please test :)

no votes yet
·

I also noticed this issue. With the latest release of the certbot-dns-hetzner plugin the issue is fixed to some extent: https://github.com/ctrlaltcoop/certbot-dns-hetzner/releases/tag/v3.0.0

Unfortunately generating certificates for sub-domains does not work anymore then, because the new API seems to expect the name fo the DNS zone to match the requested domain. With subdomain.domain.tld the name of the zone is domain.tld, so the current workaround would be to generate wildcard certificates for *.domain.tld. This works, but leads to renewal of existing certificates containing subdomains to fail.

It has to be noted that I had to install certbot and certbot-dns-hetzner manually and remove the pre-installed snap package, because the snap package caused major problems during certificate renewal on new Ubuntu servers.

no votes yet
· · Edited
·

I also created a ticket on the package: https://github.com/ctrlaltcoop/certbot-dns-hetzner/issues/41

no votes yet

Hetzner changes DNS infrastructure

1 total vote
  • Dennis moved item to board Live

    1 month ago
  • Stan moved item to project Bugs

    1 month ago
  • Stan created the item

    1 month ago
Quick Actions
Activity
View recent activity and updates
Use arrow keys to navigate