When updating an app Location, we have multiple A records that need removing

[marcusquinn]

I admit this is an unusual scenario, probably exclusive to us - but it would save a lot of manual work.

When we are updating the Location, Cloudron does the DNS changes.

However, in our case, we are moving from K8S stacks, where we have multiple A records for the same domain/subdomain.

Currently, the fix is removing them manually, but then it takes a long time for Cloudron to recognise the updated DNS.

If you could account for the use-case of removing all matching A records when creating the single record for the Cloudron App, that would save us a lot of manual work please

[murgero]

@marcusquinn said in When updating an app Location, we have multiple A records that need removing:

but then it takes a long time for Cloudron to recognise the updated DNS.

Cloudron may update DNS - but DNS records can take up to 48 hours to be seen by the outside world (though RARELY ever this long). Most of the time, the records are processed automatically according to the DNS records TTL (Time To Live). If you changed or removed a record, the TTL is sometimes the minimum to which the record will be seen. Most of the time though, you should be able to see the changes within a few minutes BUT NOT ALWAYS. DNS is fun like that!

That said - when renaming or changing location, Cloudron should make the change for you already - is it not doing that?

[marcusquinn]

@murgero Yeah, know all that. Our use-case is unusual. It's just as I said above. I don't think the Cloudron DNS API scripts ever considered finding multiple A records for the same domain/subdomain because it's not a common setup to go from in that process.

[girish]

Right, it's entirely possible that our scripts don't handle multiple DNS records. Is this Route 53 ? These things tend to be provider specific.

I will mark this as a bug (instead of feature request).

[girish]

I opened https://git.cloudron.io/cloudron/box/-/issues/743 (assumed it's route53 unless you tell me otherwise).

[marcusquinn]

@girish thanks, it's apparent with Cloudflare but I expect the issue would be with any of them.

[robi]

Maybe one way around this would be to set up redirects for that app that match the existing records, then Cloudron would be 'aware' of them.

Still manual work.

[marcusquinn]

@robi Manual fix is just deleting the old triple records manually. Lots of domains though, and it's something that ought to be fixable with a checkpoint loop in the api call. Saving a few hours in a devs day is rather valuable.

[robi]

@marcusquinn can one do loops in postman or similar?

[marcusquinn]

@robi I can do it manually in Cloudflare. Not looking for workarounds.

It's just a nuisance factor in having to explain it to every developer working on migrations from K8S setups to Cloudron Apps.

K8S for high-availability is interesting but not as performant, cost-efficient or quick to replicate, hence moving our focus to single server apps and we'll then work on a new approach to HA.

[robi]

@marcusquinn said in When updating an app Location, we have multiple A records that need removing:

K8S for high-availability is interesting but not as performant, cost-efficient or quick to replicate, hence moving our focus to single server apps and we'll then work on a new approach to HA.

Sounds like a plan and a boost to getting HA Cloudron running.

[marcusquinn]

@robi yeah, with ecommerce being our primary business, we're invested in this. We have 12 very experienced devs on the team but just a few of them have had time to start looking at Cloudron this week. In this for the long-term though so I'm sure you'll start to see our work filtering through very soon.