@girish definitely need for the mail server.

@atrilahiji I use Namecheap too, decent service but equally the Cloudflare free DNS services is pretty solid and not had any trouble with that & Cloudon. Just mentioning in case you got stuck or hadn't compared that option.

Thanks @marcusquinn ! There is a bug in the Cloudron code where we were using the wrong API call to list zones when validating the config. https://git.cloudron.io/cloudron/box/-/commit/45c49c975712ee4b3bbf306ca7492c60a41c4c57 was the fix.

@alejandrolengua This documentation page is mostly geared towards setting up with different DNS providers, but this is a good place to start too as you'll need this to add new domains to your Cloudron server: https://cloudron.io/documentation/domains/

@girish This is intentional because the root domain record can be in use on another server/app/website. Right, that makes sense. I added a redirect from the root domain and it solved all my problems. Thanks for the quick help.

@girish yes, that’s a much better idea. Essentially the ability to “swap” app instances, or in other words the ability to easily promote from staging app instance to production app instance on the same server. That’d be ideal.

Thanks for the reply, @girish. Doing a host -t NS lead me to find that the NS records were not added in DigitalOcean. Adding them in fixed the problem.

@davisdre The feature is available. Linode DNS is only not available in the initial Cloudron setup screen. This is only because user's were complaining nothing is happening for 15 minutes when they use Linode DNS. You can later go to Domains view and change it from wildcard to Linode DNS. I will put a note in the docs.

@necrevistonnezr said in Best domain provider for Cloudron for a server with non-static IP?: Namecheap offers dynamic DNS update but requires an API key For the DynDNS, Namecheap provide a password by domain But yes Cloudron use the API maybe you could run https://github.com/linuxserver/docker-ddclient

@girish said in Multi Domain for the same app such as Nextcloud: Indeed, I replied there - https://forum.cloudron.io/topic/2202/multi-domain-for-the-same-app-such-as-nextcloud You mean here: https://forum.cloudron.io/post/6315

@will said in domain alias (not redirect): @zedomingues Have you considered other ways to achieve this goal? How would you do this ? Personally I would try to add a new nginx config in /etc/nginx/applications/ which contain server_name other.domain.tld proxy_pass http://127.0.0.1:35611; but the proxy_pass port seams to be non static. Another way, I would two time the apps and pointing them to the same data directory

Thanks for the thorough reply @girish , I've updated my DNS accordingly and the certificates renewed! I'll figure something out with the Github Pages (or self host on Cloudron!)

@JOduMonT Currently, Cloudron does not support IPv6 and requires an IPv4. You can, of course, configure your server to have IPv6 address additionally and configure DNS AAAA records manually and that should work. Goes without saying, we want to add IPv6 support at some point (I know it's 2020!! )

@girish WOrked like a charm, thanks!

@girish As far as I know, it's correct - unless DKIM has the IP included, since that did change during the migration. Unfortunately, the Email section of Cloudron wasn't properly giving the needed information - previously it was saying DKIM was incorrect, but the display just said something like "expected null to equal null". DKIM isn't showing in the Email status page at all with the workaround I added here. I'll put that in as a separate issue, though, once the update comes out and I see the proper message.

Also, note that changing the nameserver sometimes takes a bit of time. So, you might have to wait a bit between step 2 and step 3.

@PRajShar To clarify what this error is trying to say: Let's assume that you have an existing website app (i.e external to Cloudron) on app.domain.com. Now, you go to Cloudron and try to install an app in the domain app.domain.com. Cloudron will detect that the DNS already has an entry for this and fail with the above error. To fix this, go to your DNS provider and remove the app.domain.com entry. Then in Cloudron, click the Repair (wrench icon) and it should work. Alternately, just use another subdomain app2.domain.com or something.

Done, added notification for the next release.

@murgero Thanks for reporting, this was indeed a regression. Fixed now for the next release.

Indeed, missed that. Just making a blog post for 4.1 release which will include it.