Custom 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, with built-in SSL

Linking your Domain Name to your Application

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.

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.

If you need to configure a custom domain name, follow the steps below.

Personal Domain Names

Your Application Runs in the Europe/Paris ('PAR') Zone

Record Type
Value
CNAME
Recommended
domain.par.clever-cloud.com.
A
Only if CNAME is not available
Four records on 163.172.235.152, 163.172.235.153, 163.172.233.43 and 163.172.233.44

Your Application Runs in the North-America/Montreal ('MTL') Zone

Record Type
Value
CNAME
Recommended
domain.mtl.clever-cloud.com.
A
Only if CNAME is not available
Two records on 149.56.147.232 and 149.56.126.234


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.

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.
But for the raw domain 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 adresses 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).

Edit me on GitHub