Porkbun automated DNS change

[ekevu123]

Not sure if this is expected or a bug, but I noticed this:

1. I registered a new domain with porkbun
2. I connected the domain to cloudron and gave API access
3. I tried to install a new app on that domain using Cloudron CLI

Expected Behaviour:
Cloudron manages the DNS records automatically.

Actual behavior:
box:dns Attempt 4 failed. Will retry: Porkbun DNS error 400 {"status":"ERROR","message":"Create error: We were unable to create the DNS record."}

The solution was to delete the default CNAME entries manually that were pointing to porkbun (they were created when I bought the domain).

Technically, this was a conflict, and I assume cloudron, as it acts usually conservatively, would not interfere with the current state, but show an error instead until this is resolved? Or can cloudron only add and edit, but not delete existing entries?

I just wanted to bring this up, I am not sure if cloudron would be supposed to resolve this on its own.

[james]

Hello @ekevu123
Thanks for reporting.
I can only assume that the default CNAME records after purchase have some sort of protection and or can't be changed by the API, thus blocking the process.
Can you share a screenshot of Porkbun where these CNAME records where set?

[girish]

Was the CNAME eventually pointing back to Cloudron server? If so, we have code to follow CNAME records. Cloudron doesn't ever delete external records, so if the CNAME is pointing to something else, it can only error.

[ekevu123]

Yeah, I don't have the original, because I repaired this manually already, but that is basically it - the CNAME was a standard of Porkbun pointing to their server.

Well, it's solved quickly, albeit manually.