AAAA dns error – how to solve?

[thoresson]

Hi!

I recently moved my Cloudron-installation to a new VPS at Netcup, and after the migration new apps can't be installed anymore.

I get this error for all apps I try:

But as far as I can tell, I've the AAAA record for the domain configured the right way at my registrar:

The IPv6 address is copied from the Network Settings in Cloudron.

What's causing this problem?

[nebulon]

Which DNS backend provider are you using for that domain? Also do you see more errors in the app logs?

Cloudron will retry until all nameservers are in sync. Do all of them have the expected AAAA record?

[thoresson]

It's a Swedish one, Oderland, configured using the Wildcard option. And yes, dns1/2/3.oderland.com all have the AAAA record.

[nebulon]

Hm, so all Cloudron will do here is to check all nameservers directly for the records. So are the records also resolving fine from the server itself via SSH?

You can check with:
host -t AAAA <app.yourdomain.com> <nameserver1/2/3>

[thoresson]

Hmm, your terminal command got me thinking: I'm trying to install apps under my Cloudron's primary domain. For primary.tld I've AAAA records configured at my registrar. I thought that Cloudron managed the AAAA records for any subdomains thanks to this setup? But should I add the AAAA record for linkwarden.primary.tld at my registrar as well?

I haven't done that for any of the already working apps, and they run as expected.

[nebulon]

Since Oderland is not a supported API by Cloudron, you have to setup all records manually. If you use the wildcard, then this works for all subdomains, but not the main domain. DNS wildcards for the primary.tld do not exist.

[thoresson]

Ah, I see! Thanks!

But I also noticed that it worked if I disabled IPv6 even for the primary domain. Why is that?

[nebulon]

Cloudron will then skip the check if it is disabled.

[thoresson]

So it's IPv6 entries that are handled by Oderland, but Cloudron takes care of the IPv4?

[nebulon]

Not really, Cloudron can't change records unless the provider has an API which is integrated with Cloudron and Oderland is not yet added. So in such cases you can either use wildcard or manual provider, which means you have to setup the records manually (or for subdomains the single wildcard DNS record works). A or/and AAAA are handled the same way.

[jdaviescoates]

Recently when I was installing a new Cloudron and using Wildcards it was stuck on waiting for dns propagation until I created both A and AAAA entries