Domain names
When creating an application, you have two (non exclusive) choices for domain names:
- Using a personal domain name
- Using a *.cleverapps.io free domain for dev purposes, with built-in SSL
You can link one or several domain names in the console.
Add it in the application configuration: in the console, click on your application name in the first panel, then choose domain names. You’ll have to choose to add a custom domain name or use a sub-domain under *.cleverapps.io
.
Using a *.cleverapps.io free domain, with built-in SSL
cleverapps.io domains are for developement only!
*.cleverapps.io
domains are given for development and tests purpose. They point to
specific reverse proxies and have the following weaknesses:
- .io TLD is not a stable one
- since we offer the domain, the probability that people will abuse it is high. Thus, we do not garantee the same QoS on the cleverapps reverse proxies.
In the console, in the domain name sub menu of your application, there is a default entry configured by default for every new app: yourAppID.cleverapps.io
, which can be removed.
In your application’s domain section, just enter example.cleverapps.io
. You have to choose a unique one. Trusted SSL is available on every sub-domain.
TLS on sub-domain level
*.cleverapps.io
certificate is only valid for the first sub-domain level, it won’t work with a domain like blog.mycompany.cleverapps.io
.Using Personal Domain Names
You can point your domain name to Clever Cloud either with a CNAME record or with A records.
The use of a CNAME record is highly recommended.
With a CNAME record, your DNS configuration is always up-to-date. Using A records will require you to keep the DNS configuration up-to-date manually.
Domain names linked to Clever Cloud applications are monitored, so we will send you an email if your DNS configuration is obsolete or incorrect.
We also support wildcard personal domain names, to do so use the standard pattern to describe it: *.example.com
Your Application Runs in the Europe/Paris (‘PAR’) Zone
Provide the following to your registrar:
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.par.clever-cloud.com. |
A Only if CNAME is not available | Four records:@ 10800 IN A 185.42.117.108 @ 10800 IN A 185.42.117.109 @ 10800 IN A 46.252.181.103 @ 10800 IN A 46.252.181.104 |
Your Application Runs in the Europe/Roubaix (‘RBX’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.rbx.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 87.98.180.173 @ 10800 IN A 87.98.182.136 |
Your Application Runs in the Europe/Roubaix HDS (‘RBXHDS’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.rbxhds.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 135.125.16.47 @ 10800 IN A 135.125.16.49 |
Your Application Runs in the Europe/Warsaw (‘WSW’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.wsw.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 145.239.17.127 @ 10800 IN A 145.239.17.192 |
Your Application Runs in the North-America/Montreal (‘MTL’) Zone
Provide the following to your registrar:
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.mtl.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 149.56.147.232 @ 10800 IN A 149.56.126.234 |
Your Application Runs in the Asia/Singapore (‘SGP’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.sgp.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 51.79.197.159 @ 10800 IN A 51.79.197.160 |
Your Application Runs in the Oceania/Sydney (‘SYD’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.syd.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 139.99.253.215 @ 10800 IN A 139.99.253.237 |
Your Application Runs in the Jeddah (‘JED’) Zone
CNAME Recommended | {yoursubdomain} 10800 IN CNAME domain.jed.clever-cloud.com. |
A Only if CNAME is not available | Two records:@ 10800 IN A 158.101.226.110 @ 10800 IN A 150.230.50.217 |
Warning on CNAME Availability
You cannot use a CNAME on a top-level domain, or on a subdomain which already has DNS records.If you want to make your application available from a domain name which does not support CNAME records (eg example.com
in addition to www.example.com
), check if your registrar provides a web redirection service. This way, you only have to make www.example.com
point to Clever Cloud. Please note that web redirection provided by registrars only work over HTTP.
Remember that DNS changes may take time to propagate (usually a few hours, sometimes up to a day or more). It depends on the TTL setting of your DNS configuration. For faster changes, you can lower the TTL value in advance, and rise it again afterwards.
Note on using a domain wildcard
*.example.com
will match e.g. blog.example.com
or www.example.com
.example.com
, you will have to add both *.example.com
and example.com
to your application.Contextual Example
Domain Name Use Case | CNAME config | record A config | Web redirections |
---|---|---|---|
www.example.com example.com | point www.example.com to domain.par/mtl.clever-cloud.com. | No A record needed | Redirect example.com to www.example.com |
www.example.com | point www.example.com to domain.par/mtl.clever-cloud.com. | No A record needed | No redirect needed |
example.com | No CNAME record needed | point example.com to the two IP addresses of the selected region | No redirect needed |
Prefix routing
Requests are routed to applications based on the domain name, but you can also route based on a path prefix.
For instance, you can bind example.com/api
to an app, and example.com
to another one.
All the HTTP requests on example.com
where the path starts with /api
will be routed to
the first app. The other requests will be routed to the second app. You can add a path after every domain name you bind in the console (or with clever tools).
Gandi CNAME configuration
Here is an article that demonstrates a simple setup for Gandi CNAMEs.