Setting Up a CRM Custom Domain

This article provides instructions for setting up Custom Domain Hosting for Forth accounts who have signed up for the additional enhancement. If you have not signed up for this service but want more information, please contact sales@setforth.com.

Setup

You must add two CNAME records to enable your custom site to work within Forths’ Environment. Clients will need to do these two records for each site you have with us - e.g., if you have a CRM and a portal site, you will need to make four entries. 

1. A Domain Control Validation (DCV) CNAME - the purpose of this record is to generate a Let’s Encrypt certificate that will provide the SSL encryption used by the client and Forths’ web traffic.
   1. This entry must permanently stay in your DNS entries, or after 90 days, the SSL validation will expire. However, because of this process, clients will no longer need to provide a yearly SSL certificate for purchases. 
2. A pointing CNAME entry that points your subdomain to our hosting environment 

Examples

Here are examples of how you would set up the DCV CNAME and regular CNAME for crm.example.com. Screenshots are provided for AWS Route53. Each registrar will be slightly different in layout and process, and we cannot support each possible variation.

1. DCV CNAME
   1. CNAME: _acme-challenge.<subdomain>
      1. In our example domain, it would be: _acme-challenge.crm.example.com
   2. CNAME Value: <fulldomain>.b6ac64a870f2da4d.dcv.cloudflare.com
      1. In our example domain, it would be: crm.example.com.b6ac64a870f2da4d.dcv.cloudflare.com
2. Pointing CNAME
   1. CNAME: CRM
      1. In our example domain, it would be: crm.example.com
   2. CNAME Value:
      1. For Forth Customers: scweb.forthcrm.com (see example below)
      2. For CTX Customers: scweb.centrexsoftware.com

Article Version History: