Skip to main content
Setting Up a Custom Sub-domain

Step by step instructions to set up a sub-domain with Exposure

Luke Beard avatar
Written by Luke Beard
Updated over a year ago

Follow the steps below to set up and test your domain name. You'll need to do this using the DNS control panel where-ever you originally registered your domain name.

Step One

Add a CNAME for your desired subdomain (e.g. blog.yourdomain.com, stories.yourdomain.com etc) and point it to domains.exposure.co.

Step Two

Test your domain below , you will need to be signed in. Once it's configured correctly you will be asked to complete your custom domain setup and your domain will be active.

Please note: You will need to enter domains.exposure.co exactly. Any other value will not work with Exposure. Also, redirects or masking setups, like CloudFlare, are not supported.If you use CAA records please add a CAA record for your subdomain that is set to letsencrypt.org to make sure we can issue your free SSL certificate.
โ€‹

I can't get my domain working, can you help?

If you've set up DNS per our instructions, double-check for the following common issues:

  1. Check that the CNAME is set to domains.exposure.co and NOT username.exposure.co

  2. Check that the setup is fully complete at https://exposure.co/custom-domains/wizard/have-domain and test the URL from the wizard. (This lets our platform know the domain is ready to use.)

  3. Ensure your domain name allows SSL certs from letsencrypt.org. In most cases, there is nothing you need do here; but, for larger web properties (often where there are dedicated technology teams), this can pose a problem. If, when completing the wizard, Exposure says that the domain has been set up successful but your browser provides a warning that certificate is invalid, you may need to add a CAA record to your DNS record. The details for how to do this vary by DNS provider, but looking up the raw record should respond with this:

example.com. 3600 IN CAA 0 issue "letsencrypt.org"

or

subdomain.example.com. 3600 IN CAA 0 issue "letsencrypt.org"

While domain records generally update quickly, sometimes they can take up to 24-48 hours to fully resolve.

If you are still experiencing issues and have already contacted your registrar, email us at [email protected] and we will get back to you ASAP.

Did this answer your question?