Set up Custom Domains for Salesforce Sites and HTTPS support for Branded Custom Domains
|Knowledge Article Number||000205653|
Implementing a custom domain for your site creates brand recognition and gives you additional control and functionality. We'll go through how you can get your custom domain implemented.
Important Consideration: ** Custom Web addresses are not supported for Sandbox or Developer Edition organizations
Using Branded Domains with Salesforce involves two way set up which consists of performing the steps as explained in Section 1 and 2, section 3 would explain how to have your branded domain set up with HTTPS support:
1. Click Setup.
2. Under "Administer," click Domain Management | click Domains.
3. Click Add A Domain.
4. Copy the 18 digit token. This token is case sensitive so copy it exactly as displayed.
5. In your DNS, create a CNAME. It should follow this format, www.example.com.00d200000005pikra.live.siteforce.com.
NOTE: Depending on your DNS provider, CNAME propagation can take up to 48 hours.
Add the Custom Domain information to Salesforce
This is a 2 step process, first you'll need to add the domain information to your org, and then you'll map the custom domain to your Salesforce Site.
Add the domain information to your Salesforce Org
NOTE: CNAME propagation needs to be complete before you can perform this next set of steps.
1. In your Salesforce Org, click Setup.
2. Under "Administer," Click Domain Management | click Domains.
3. Click Add A Domain.
4. Enter your custom domain in the Domain Name field.
If you get an error, it's likely because your CNAME propagation hasn't completed. You'll need to wait for propagation to complete before you can proceed.
Map the Custom Domain to your Salesforce Site
This step can be subdivided into setting up for a force.com site, includes communities exposed as force.com site, and Site.com site.
Set up for Force.com or community exposed as Force.com site
If you're only trying to set up a Site.com site, skip ahead to the next section labeled, "Set up custom domain for Site.com site."
1. In your Salesforce Org, click on Setup.
2. Under "Administration," click Domain Management | then click Domains.
3. Click on the domain that you added.
4. Click New Custom URL.
- You should be redirected to the Custom URL Edit screen.
6. For the field Site, click the look-up icon to select the Salesforce Site that you want to map to your custom domain.
7. For the field Path, enter the directory name if you want to have a subdomain with your custom domain.
- For example, if you have a Force.com site "abc.force.com" with label ABC, you'll see ABC in the lookup for "Site" field. If you want to have www.example.com/customers
mapped to abc.force.com, then put /customers in the “Path” field.
8. Click Save.
This will kick off reverse propagation from the Salesforce end. Once it's complete, you'll be able to navigate to the domain you've been working with and see content from abc.force.com. If the reverse propagation is still underway, you'll see a browser error.
Set up Custom Domain for Site.com Site
1. Click on Site Configuration | then click Domains.
2. Click Edit for the Site.com site that you want to mask.
3. Click the Site.com tab. This will list your Site.com sites.
4. Go to the App menu and select Site.com
5. In the “Domain Name” field, enter your custom domain. If you want to have something like "www.example.com/customers" mapped to your Site.com Site, then put /customers in the “Path” field and click Add.
6. Click Publish Changes.
Once the propagation is successful, you'll receive a confirmation email stating that the site was published successfully and is now live. At this point, you can navigate to the domain you've been working with and verify that it works both with and without the "/customers."
Add HTTPS support to custom domains
Before you start the process to enable HTTPS support for your custom domain, you'll need to have this feature enabled by submitting a case with Salesforce Customer Support.
After you've gotten the feature enabled by Salesforce Customer Support, you need to have created an CNAME record to reference. If you haven't created a CNAME record, you'll need to follow the steps outlined in this article for how to create a CNAME record in your DNS.