I recently encountered some issues after I switched from wildcard DNS configuration to provider-based automatic DNS configuration.
When you create an app with provider-DNS configured, cloudron will use your provider's API to automatically create the DNS subdomain record to point to your server so cloudron can serve the app. But if you create the app while you have wildcard DNS configured, no specific subdomain will be created. This is expected.
However, if you create the app under wildcard-DNS, then switch to provider-DNS, then the subdomains that would normally have been created when running under provider-DNS are not created automatically when switching between DNS configurations. This can cause a problem when the user deletes their wildcard DNS record because they assume that Cloudron will use provider-DNS to provision DNS entries for all apps.
I propose that Cloudron add a feature to check the DNS entries and reprovision DNS records as required when the user switches DNS configurations. I could imagine this could be implemented by triggering automatically as soon as the user switches DNS configurations, or as a button on the dashboard to recheck that dns entries for all apps are correctly assigned (including
I have implemented this for 6.2 (next release).
This was required as part of another feature - making it possible to restore Cloudron without updating DNS (https://git.cloudron.io/cloudron/box/-/issues/737). Currently, it is not at a domain level but at a global level (can always add it later).