Error - DNS A Record of example.com is not synced yet: ETRYAGAIN

[dsp76]

Error - DNS A Record of example.com is not synced yet: ETRYAGAIN

Will this resolve automatically after some time?
DNS is now pointing to Cloudron and the app is running fine. However, Cloudron still shows the error and blocks all menu options.

Restarting the app is not available in the main UI, only in the Terminal view. We restarted it from there, but the issue persists.

What triggers a re-check so that the error state is cleared?

[james]

Hello @dsp76

When using the base domain e.g.: example.com the DNS propagation takes longer compared to sub Domains.

Also check if your domain registrar or DNS management provider has set an alias for the base Domain.
This would block the DNS resolution.

[dsp76]

When checking with dnschecker.org I can see its already updated in all checked regions. The domain already resolves to our cloudron instance and its also responding as expected (Website). Also the certificate (LE) has been issued correctly. So why does the app still stay in error state?

[nebulon]

If this app was newly installed and hit immediately that error, it may end up in that state I think. The easiest here would be just uninstall and reinstall it on that domain. A simple app restart itself does not check the DNS nor setup the reverse proxy for it then.

Otherwise we may have to take a look at the server directly to see the state and why the relevant menu items to fix the situation are disabled.

[dsp76]

So how would I prepare an installation, when the DNS is about to be updated in some time later - maybe after timeout? Shouldn't the DNS setup be retried repeatedly for a while?

Can I uninstall and then reinstall from the backup? Can I update the backup of the App via some cli command, as the UI won't let me do it?

[joseph]

@dsp76 you can clone the app (to another location) from the latest backup. If that works, delete the original and move the clone to the original.

To answer your original question, the DNS is retried but it gives up after some time. Which DNS provider are you using?

[dsp76]

Hi,
I didn't have a chance to make a backup yet, after cloning from beta. I also don't have this DNS managed by Cloudron - "Manual Setup". Thus I decided to now uninstall and copy again from beta. Unfortunately this way I have some downtime. Yes I could have restored first to a different domain managed by Cloudron - and then move there.

[joseph]

@dsp76 ah ok, you are asking how to prepare for such things in the future?

Run host manual.example.com 127.0.0.150 on the server . If this returns the right value, then the DNS has propagated. So, the next time around, start installing an app after the above command returns the correct value. This is the internal mechanism used in Cloudron to check DNS propagation.