Single domain, multiple cloudrons?
-
Is it possible to use a single domain, let's say example.com, with 2 (or more) cloudrons?
The use case would be to host multiple applications for the same company each on their own server, e.g. websites on one server and forum and mail on another server.
Note: I'm new to Cloudron and I really like it so far, but I'm having some specific use cases and it's not clear to me whether Cloudron is a good fit for them.
-
Hi @guyds,
I think that should work, there is one downside however. The cloudron dashboard is always available at
my.domain.tld
so when setting up your various cloudrons you cannot specifydomain.tld
as the domain for each of them, but would need to doserver1.domain.tld
(so that the cloudron dashboard would then be atmy.server1.domain.tld
).After the initial setup you can then add
domain.tld
to the domains so you can haveforum.domain.tld
etc. -
Great!
I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC?This brings me to another question however:
what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them? -
@guyds said in Single domain, multiple cloudrons?:
I suppose each Cloudron needs a unique domain name because of the DNS records that are being created when installing a Cloudron: DKIM, SPF, DMARC?
Yes, and also because we need a unique location to access the dashboard.
what if the domain that's being used for a Cloudron already has e-mail related DNS records, for example when it's already configured for use with G Suite or Office 365? Will Cloudron modify those records, override them or just ignore them?
If you have an existing DMARC, it don't touch it. Otherwise, it will put the default strict DMARC policy. DKIM uses a unique selector domain, so it won't affect other DKIM entries. The SPF is modified with "a: my.<domain.com" into the existing SPF.