Location update task fails to complete if IPv6 support is enabled but DNS only includes IPv4.

[d19dotca]

I was changing the location of the Surfer app yesterday to a new domain for a client. It turns out their DNS provider doesn’t support AAAA IPv6 records so they only set the regular A IPv4 record for now. This prevented Cloudron from completing the location change task as it failed the DNS propagation test even though IPv4 was still present.

I worked around it by temporarily disabling IPv6 and then re-enabling it after the location app change was complete. But I’m worried this will come back again if I need to restore or make any other location domain additions to it.

How can we fix this behaviour? My suggestion is that as long as one of the methods is met, that it doesn’t fail to complete but perhaps just logs a warning or something to that effect.

[d19dotca]

Longer term of course I’ll suggest they use a different DNS provider that actually supports IPv6 so that it isn’t an issue, but it still brings forward that not every DNS provider supports AAAA records yet and this can be an issue in cases like this.

It’s Wix by the way which didn’t support IPv6 in case anyone was wondering.

I offered to host their DNS for them in OVH and they may take me up on that offer, but until then I’m hoping that we can find a different manner in which this can avoid failing location updates to the app.

[msbt]

I had a question about that a while ago: https://forum.cloudron.io/topic/12503/what-will-happen-when-i-enable-ipv6-on-cloudron-when-some-domains-don-t-support-it/2?_=1733313066534

@girish suggested this:

If you change the provider of the things you don't control to no-op, and make sure A/IPv4 is correct, then it won't crash and just ignore them. Certs should also be renewed (as long as there is no incorrect AAAA record).

[nebulon]

That is quite something if they dont support AAAA records in 2024! In that case though, I guess you can set the DNS backend for that domain to noop to skip all tests. Anyways you have to manually ensure the DNS records on such a provider.

[d19dotca]

@nebulon Fully agree, it's really odd that Wix doesn't allow AAAA records in this day and age.

I'll change that domain to noop for now then as recommended, but my preference is to have the logic of the location DNS propagation check change so that domains in manual status can still be successful even if only one IPv4 or one IPv6 address is set rather than both. The noop is for development after all, isn't it?

As long as one of the DNS records exists, that should be seen as successful IMO, since it will work in terms of getting traffic to the site still. There shouldn't be a reason to fail that.