<![CDATA[Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND]]>Hi, for some reason, configuring my domain doesn't work when restoring from a "box" backup.
I'm not sure what I should do.

As it's not the first time I tried to install it, and I kept the IP (188.245.41.19) around, the DNS A for domain my.cloudron.unly.org is already set. I don't have anything set for cloudron.unly.org, though.

3b672738-6087-45cc-a5ed-0df96b498007-image.png

256809bb-7f35-429a-83c7-a2fd09b06132-image.png

2024-06-10T17:13:49.643Z box:dns registerLocations: Will register [{"subdomain":"my","domain":"cloudron.unly.org","type":"dashboard","certificate":null,"fqdn":"my.cloudron.unly.org"}] with options {"overwriteDns":true}
2024-06-10T17:13:49.645Z box:network/generic getIPv4: querying ipv4.api.cloudron.io to get server IPv4
2024-06-10T17:13:50.442Z box:provision setProgress: restore - Registering location my.cloudron.unly.org
2024-06-10T17:13:50.450Z box:dns/digitalocean getInternal: getting dns records of cloudron.unly.org with my and type CNAME
2024-06-10T17:13:50.960Z box:dns/digitalocean getInternal: getting dns records of cloudron.unly.org with my and type A
2024-06-10T17:13:51.320Z box:dns upsertDNSRecord: location my on domain cloudron.unly.org of type A with values ["188.245.41.19"]
2024-06-10T17:13:51.326Z box:dns/digitalocean upsert: my for zone cloudron.unly.org of type A with values ["188.245.41.19"]
2024-06-10T17:13:51.326Z box:dns/digitalocean getInternal: getting dns records of cloudron.unly.org with my and type A
2024-06-10T17:13:51.915Z box:dns/digitalocean upsert: completed with recordIds:[null]
2024-06-10T17:13:51.919Z box:provision setProgress: setup - Waiting for propagation of my.cloudron.unly.org
2024-06-10T17:13:51.920Z box:dns/waitfordns waitForDns: waiting for my.cloudron.unly.org to be 188.245.41.19 in zone cloudron.unly.org
2024-06-10T17:13:52.006Z box:dns/waitfordns Attempt 1 failed. Will retry: queryNs ENOTFOUND cloudron.unly.org
2024-06-10T17:13:57.014Z box:dns/waitfordns Attempt 2 failed. Will retry: queryNs ENOTFOUND cloudron.unly.org
2024-06-10T17:14:02.020Z box:dns/waitfordns Attempt 3 failed. Will retry: queryNs ENOTFOUND cloudron.unly.org
2024-06-10T17:14:07.026Z box:dns/waitfordns Attempt 4 failed. Will retry: queryNs ENOTFOUND cloudron.unly.org

]]>https://forum.cloudron.io/topic/11887/error-when-restoring-whole-cloudron-box-dns-waitfordns-attempt-x-failed-will-retry-queryns-enotfoundRSS for NodeFri, 09 Oct 2026 23:14:44 GMTMon, 10 Jun 2024 17:26:03 GMT60<![CDATA[Reply to Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND on Wed, 12 Jun 2024 16:46:16 GMT]]>I should have changed DO DNS to AWS before deleting it then, but I didn't quite understand how to do that either.

I guess that'll be the worry of the next person who runs into a similar situation.

]]>https://forum.cloudron.io/post/89762https://forum.cloudron.io/post/89762Wed, 12 Jun 2024 16:46:16 GMT<![CDATA[Reply to Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND on Tue, 11 Jun 2024 19:39:10 GMT]]>

Regardless, this is solved, but was quite difficult to comprehend.

Looking at the logs it seems that previously you had a zone named cloudron.unly.org in DO. Maybe this changed? It's unable to do DO DNS transactions because there is no such zone.

]]>https://forum.cloudron.io/post/89723https://forum.cloudron.io/post/89723Tue, 11 Jun 2024 19:39:10 GMT<![CDATA[Reply to Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND on Mon, 10 Jun 2024 20:47:38 GMT]]>Yeah, I destroyed the old server and domain on DigitalOcean since then.
Regardless, this is solved, but was quite difficult to comprehend.

]]>https://forum.cloudron.io/post/89678https://forum.cloudron.io/post/89678Mon, 10 Jun 2024 20:47:38 GMT<![CDATA[Reply to Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND on Mon, 10 Jun 2024 20:28:37 GMT]]>@AmbroiseUnly
There is just an attempt to connect to DigitalOcean DNS, that's why the copy had saved settings from the previous server, where you had DNS from DigitalOcean. If you want a flawless transfer, switch DNS from DO to Amazon on the old server. Then make a backup and then restore on the new server.

]]>https://forum.cloudron.io/post/89676https://forum.cloudron.io/post/89676Mon, 10 Jun 2024 20:28:37 GMT<![CDATA[Reply to Error when restoring whole Cloudron - box:dns/waitfordns Attempt X failed. Will retry: queryNs ENOTFOUND on Mon, 10 Jun 2024 17:28:09 GMT]]>Re-reading the log, I see

2024-06-10T17:13:50.960Z box:dns/digitalocean getInternal: getting dns records of cloudron.unly.org with my and type A

It looks like it's fetching DigitalOcean, but I moved the domain to AWS, I was using a DO Droplet but I'm using Hetzner now.
So, maybe the issue is that those DNS are still set on DigitalOcean? 🤔

]]>https://forum.cloudron.io/post/89662https://forum.cloudron.io/post/89662Mon, 10 Jun 2024 17:28:09 GMT