Cloudron Forum

@scooke said in Why is netcups DNS so slow?:

Wildcard

I'm using the programmable DNS (CF and Bunny). Maybe that's why it's faster.

For namecheap, look at their docs - https://www.namecheap.com/support/knowledgebase/article.aspx/434/2237/how-do-i-set-up-host-records-for-a-domain/

@girish Thank you!

@Jan-Macenka The sync dns also syncs the mail related dns settings. There should also be an event in the eventlog indicating the dynamic dns updated your dns (or not). When things are going out of sync, can you check what it says in the event log?

@girish said in add deSEC as DNS Provider:

deSEC integration is implemented for next release.

That is the best message of the day. Thank you!

@j_vmess your domain works just fine for me here. Maybe it's a browser cache issue? Have you tried another browser or after clearing the browser cache? I removed your domain from the original post, since it was showing the setup screen.

@AartJansen for new apps, AAAA is automatically added. For existing apps, go to Domains -> Sync DNS.

@nichu42 said in DNS resolving problem:

I've tried to modify the forward-all.conf like this

forward-tls-upstream: yes forward-addr: 91.239.100.100@853#anycast.uncensoreddns.org forward-addr: 1.1.1.1@853#cloudflare-dns.com

but it didn't work (SERVFAIL).

Answer to myself (in case someone else ever needs this):

It is necessary to also add the following to the conf file:

server: tls-cert-bundle: /etc/ssl/certs/ca-certificates.crt

so the validity of the certificates can be verified.
After that, you can add TLS upstream servers as mentioned in my previous post. I've decided for anycast.uncensoreddns.org and dns.quad9.net now.

I figured out my issue. Turns out that even though I read the documentation I made one critical mistake right at the beginning. I had to create my email accounts and the addresses I wanted to work in Cloudron first. Then Install the Snappy mail client and set up the email accounts there second.

Once I deleted the Snappy mail client and reinstalled it everything worked. I'm not sure how but this topic can be marked as resolved.

I do have the same kind of shortages with uptime kuma. I did add Cloudron to see. Any idea of what is happening ?

I have a dedicated server with hetzner.

CleanShot 2024-04-29 at 19.55.51@2x.png

@girish thanks for the explanation! Yeah the change happened ~14 hours ago and the TTL was set to 24 hours I reckon. I'll just wait until tomorrow to continue 😉

My plan would have been to lower the TTL a few days prior to the A record, so the caches would invalidate sooner.

@jdaviescoates said in Installed at map.bridport.coop then deleted, then reinstalled on same location: server not found:

Is there a way to flush the NXDOMAIN cache on routers/ computers?

Not that I am aware of. These days browsers also do their own DNS caching complicating things even more.

@girish ok, sounds good to me.

@girish thanks, that worked 🙂

Hey y'all. Used another domain I had that was correctly propagated. It's perfect. Now I gotta wait for my DNS records to update before I do the switch!

@prusaman If the instance has no IPv4, how do you ssh in ? Via a jump host?

@redegelde said in server cloudron install ubuntu 22.04:

The fiddle was after installing Cloudron.

Cloudron tells you not to do so in the banner if you login over SSH after installation ^^ Everything you can do or change is documentated in the docs.

@redegelde said in server cloudron install ubuntu 22.04:

What is/are the good workaround to move from one to other vps

The easiest way for a fresh installation is setting up a new VPS with Cloudron and restore from a recent backup during setup.

For migrating Mastodons user management I can't give you any advice but there are various topics regarding this if you look through the Cloudron forum.

@Jonaz said in You are seeing this page because the DNS record of x.x.x.x is set to this server's IP but Cloudron has no app configured for this domain.:

I updated DNS, and my.cloudron works but not cloudron. which is fine with me. Thanx

As @subven said, wildcard DNS entry does not include the bare domain. So, you have to put cloudron separately in DNS and not just *.cloudron

@girish said in Incorrect error when removing an obsolete alias for a service:

Did you happen to set this up manually?

Hmm, I don't actually know. It's not impossible I guess...

Good to know though, I'll work on cleaning DNS up 🙂

@girish Thank you - now its working again.