When setting up a custom domain, it's important to follow the steps in the correct order to avoid running into any errors along the way.

Choose a subdomain

Only subdomains can be used to serve your documentation. It's not possible to use an apex domain.

Here are some examples of what you could and could not choose — just replace example.com with your own domain:

www subdomain | www.example.com | - supported

Custom subdomain | jobs.example.com | - supported

Configure DNS

Configuring DNS happens at the DNS provider you are using for your domain

This step is important because the correct DNS configurations are what allow us to connect the subdomain to your careers hub in the next step.

Configure a CNAME record

The names of the fields and what to actually enter to configure the record may differ between DNS control panels, but we've covered the most common options here. If you're in any doubt, check with your DNS provider.

The type is the kind of DNS record that you want to create. Here, you need to choose CNAME.

The name or DNS entry is where you enter your subdomain. You might need to enter it in full (e.g. jobs.example.com) or you might just need to enter the part before your apex domain (e.g. jobs). If you're not sure which to use, check with your DNS provider.

The target or value or destination is where the subdomain should be pointed. In this case, that's hosting.inploi.com.

You might also see a field named TTL, which stands for Time To Live. It's the number of seconds that the DNS record can be cached for. If you're not sure what to set, look at the TTL for your existing DNS records. You could set the same number. If you're still not sure, we suggest setting 43200 seconds (12 hours) or 86400 seconds (24 hours).

Here's an example of how a correct configuration looks in Cloudflare's control panel:

Are you using Cloudflare?

If you are configuring DNS in Cloudflare's control panel, you may be tempted to activate Cloudflare's proxying (the orange cloud, also called "Proxy status" in your domain settings).

While this configuration might work in most cases, we strongly recommend against activating it. Firstly, because your custom domain will already benefit from Cloudflare's CDN and a DigiCert SSL certificate. Secondly, this option obfuscates the DNS target for your domain to the public, preventing inploi to properly run routine checks on your custom domain.

Whenever possible, please turn off Cloudflare proxying to ensure that your documentation is served without issues and can be monitored by inploi.

Contact your inploi Account Manager

Once you have completed the first two steps, you should contact your inploi account manager detailing the custom domain(s) you have configured. We will complete the configuration and respond to you once everything has been deployed.