DNS propagation

[llaume28]

Hello,

I'm encountering a DNS propagation issue for all new applications I install, Snappymail being one example. The error message I'm receiving is: 'DNS Error: DNS A Record is not synced yet: ETRYAGAIN.'

Here are the steps I've already taken:

Checked with OVH (my provider) and everything seems fine on their end.
Confirmed that DNS via Unbound is operational.
Rebooted Cloudron.
Uninstalled and reinstalled the application.
Notably, other applications like Papers and n8N, which were configured similarly, are still functioning correctly.

I'm out of ideas for troubleshooting this issue and would greatly appreciate any guidance or suggestions from the community.

Thank you in advance for your help.

[robi]

It's likely your browser.

[nebulon]

This may just have taken a long time to propagate through all nameservers from your DNS provider. Also reinstalling the app, will prolong the issue since the records will get rewritten and may take again time to propagate fully.

[girish]

You can use one of the many tools like https://www.whatsmydns.net/ and https://dnschecker.org/ if this is a real issue in DNS propagation. Thing is DNS is not propagating properly, Let's Encrypt might not see the correct DNS either and thus refuse certs (this is why we wait for DNS propagation)

[scooke]

Are you saying OVH is the domain registrar, or do you mean it's just strictly the provider (host, vps provider)? I know on all the domain registrars I use they all have a time length for full DNS prolongation. I learned about it when, once a long time ago, I was having a similar issue. I discovered that the registrar's DNS propagation length was like 12 hours? A pull down menu revealed that I could choose the amazingly speedy 5 minutes. The latest registrar I use, spaceship.com, even has 1 minute! So double check what the domain registrar uses. If it is longer than You want, edit something, fix it, change the DNS propagation time, and save it. Good luck!

[robi]

Changing an existing sub/domain takes the full TTL timeout, however adding new entries is quick as there is not record to timeout.

@girish Do the docs suggest lowering DNS TTL before one begins?

[llaume28]

Resolved, it was an incorrectly entered IP address on the OVH side, and they have corrected the error. Thank you all for your contributions.