Hetzner: DNS Transfer to new Console

[jayonrails]

https://forum.cloudron.io/post/113774

I think this better fits here, sorry for not searching properly before posting.

[nebulon]

The other thread is really about the old Hetzner DNS api, so fine to keep this thread.

As mentioned in the other, work is tracked at https://git.cloudron.io/platform/box/-/issues/860

The implementation is just finished, pending some more testing. But the API fairly easy so I don't expect much hiccups.

[jayonrails]

Amazing work. Do you need some testers? Did you try migrating from the old version to the new one.

[nebulon]

I will add it to our e2e testing today so will be part of some 9 release. Otherwise it is a bit hard to test this on other Cloudrons.

The domain I have used was migrated from the old to the new hetzner DNS so that path seems to work fine.

[nebulon]

We merged the change now for 9.0.4 so this is supported from next patch release on.

[Kubernetes]

This post is deleted!

[Berendef]

I moved my domains to the new dns console at Hetzner.
In the logs I got this:

Dec 02 03:10:18 box:reverseproxy ensureCertificate: error: Hetzner DNS error 404 {"zones":[],"meta":{"pagination":{"page":0,"per_page":0,"previous_page":0,"next_page":0,"last_page":0,"total_entries":0}},"error":{"message":"zone not found","code":404}}

Is there anything can do to corrct this?

regards Berendef

[james]

Hello @berendef and welcome to the Cloudron forum

Can you share the domain so I can run some dig commands to verify NS records and such?

[joseph]

@Berendef In Domains view, edit the domain. There are two providers - Hetzner and 'Hetzner Cloud' . 'Hetzner Cloud' is the new one.

[Berendef]

@james @joseph thanks for your fast replies. I managed it with the hint from joseph and also created a new api token. Works well now.

thnx!