Setting Up a Root Custom Domain
Point your root domain like www.yourdomain.com to your Exposure site.
Step One
Add a CNAME record for www and point it to domains.exposure.co.
You'll need to do this using the DNS control panel wherever you originally registered your domain name.
Type | Host | Points To |
CNAME |
|
|
Step Two (Optional — for non-www access)
If you want visitors to reach your site at yourdomain.com (without www), you'll need to set up a root-level DNS record. How you do this depends on your DNS provider:
If your DNS provider supports CNAME flattening, ALIAS, or ANAME records (e.g. Cloudflare, DNSimple, Route 53): Add an ALIAS, ANAME, or flattened CNAME for @ pointing to domains.exposure.co. This allows full HTTPS support on the root domain.
If your DNS provider only supports standard A records: You will need to set up a redirect from the root domain to
www.yourdomain.comthrough your DNS provider or registrar. Most registrars offer this as a forwarding option.
Type | Host | Points To |
ALIAS / ANAME / CNAME |
|
|
Step Three
Test your domain using our setup wizard. 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.
Important Notes
You must enter domains.exposure.co exactly. Any other value will not work with Exposure.
If you use CAA records, please add a CAA record that allows pki.goog so that your SSL certificate can be issued:
Type | Host | Value |
CAA |
|
|
If you use Cloudflare for your own DNS: Make sure the CNAME record is set to DNS only (grey cloud icon), not Proxied (orange cloud). If the record is proxied through your Cloudflare account, it will conflict with Exposure's SSL and your domain will not work correctly.
Troubleshooting
If you've set up DNS per our instructions, double-check for the following common issues:
Check that the CNAME is set to domains.exposure.co and NOT username.exposure.co
Check that the setup is fully complete at the setup wizard and test the URL from the wizard. This lets our platform know the domain is ready to use.
Make sure your DNS changes have had time to propagate. This can take up to 48 hours, though it's usually much faster.
If your browser shows a certificate warning, check whether your domain has CAA records that may be blocking certificate issuance. The CAA record must allow pki.goog.
Need Help?
If you have questions, reach out to us at [email protected]. We're happy to help!
