hetzner dns api outdated

[hasufell]

Describe the bug

Hetzner DNS Console API is deprecated and it appears AMCE challenges are failing (at least I suspect that might be the cause for #806)

libdns/hetzner has implemented support for the new Hetzner DNS Cloud API: libdns/hetzner@43c0630

maddy needs to use "github.com/libdns/hetzner/v2" now instead. But it appears that causes a terrible dependency update chain. I have not had success building maddy after such an update.

Steps to reproduce

See #806

Log files

Use a service like hastebin.com or attach a file if it is big

Configuration file

See #806

Environment information

• maddy version: 0.8.1

[hasufell]

Also see acmesh-official/acme.sh#6554

[foxcpp]

maddy needs to use "github.com/libdns/hetzner/v2" now instead. But it appears that causes a terrible dependency update chain. I have not had success building maddy after such an update.

New library requires Go 1.24. I guess it's time to upgrade.

[foxcpp]

libdns/hetzner/v2 is based on libdns 1.1, while maddy uses pre-1.0 libdns. libdns/vultr is also apparently stuck on pre-1.0 libdns. So currently it is either hetzner or vultr libdns.
Judging by the fact this issue is almost a year old: libdns/vultr#4, it is unlikely to be updated by the original maintainer.

[foxcpp]

libdns providers incompatible with libdns 1.x:

• vultr
• namedotcom
• leaseweb
• libdns-gandi (will lose API key support moving to upstream libdns/gandi)

[foxcpp]

So, here is the plan. I will tag 0.9.1 with old hetzner and pre-1.0 libdns then will build oddly named 0.9.1-libdns1 release that updates to libdns 1.0, dropping providers mentioned above and adding hetzner/v2. 0.10.0 will use libdns 1.x and will therefore also drop them - 0.9.1 will be the last release to support old hetzner API along with providers mentioned above (unless they all update to libdns 1.x).