The Salesforce documentation (linked below) indicates that you can use an FQDN, like mydomainname.com, to point to your Salesforce production org. After having a little trouble setting this up, I contacted Salesforce Support and was told that this is only possible for Experience Cloud Sites. I always thought that was true as well, but the documentation only mentions Experience Cloud in saying that the CDN can only be used for Sites.

Has anyone set up a custom domain name for accessing a Salesforce production org, and, if so, can you explain how you've done it?

Referenced documentation:

Adding a Domain

Options for Serving a Custom Domain


  • On the "options for serving" page, step 4 for each of the options does say, "content that Salesforce is hosting for you in Salesforce sites or Experience Cloud sites," so I have a feeling the answer is "no" to this one. Jul 1, 2022 at 21:22
  • 2
    AFAIK custom domain for "baseline" org was never an option. When custom domains were introduced in 2012 or so, it required a site (at the time - a Force.com site).
    – identigral
    Jul 2, 2022 at 2:09
  • Thanks, @identigral -- that's what I thought as well, but seeing this page of the documentation not explicitly related to Experience Cloud had me questioning that. It's quite vague. help.salesforce.com/s/… Jul 2, 2022 at 4:35
  • ...though it referencing a siteforce domain should have been a give-away. Hmm. Jul 2, 2022 at 4:36

1 Answer 1


Custom domain for base orgs (and its sandboxes) is not possible in Salesforce platform (at the least there is no documentation around this or OOB approach). You can only configure subdomains via My Domain (ref)

Consider the following (just my thoughts on why this isn't facilitated yet):

  1. As opposed to the base orgs, experience sites are lightweight, support heavy UX customization and actually meant for exposing web content to external users. Since, this perfectly falls under the use case of Salesforce customers wanting to serve their content via experience sites from their existing domains (or new custom domain), Salesforce has an implementation approach and necessary infrastructure in place to support the same.
  2. As mentioned here, there are many domains involved in base org (as opposed to experience cloud site)

In each Salesforce org, multiple domains serve content to users. In addition to your My Domain login URL, your org has application URLs on different domains. Here are a few examples.

Lightning pages, Visualforce pages, Experience Cloud sites, Experience Builder for Digital Experiences, Salesforce Sites User-stored content served by Salesforce, such as images and files

When you rename your My Domain or change your My Domain suffix, all those domains are updated.

  1. Salesforce is hosted in a multi-tenant infrastructure whose base domain, FQDN, CNAME and related DNS mappings have to follow a certain standard practice and security measures in place.

so, if the base org has to be exposed via custom domain, it would take a lot more than a simple CNAME change or DNS mapping. While this is technically possible, it would be a highly complex soluion and I don't think Salesforce (has planned or) has the strategy, infrastructure and necessary solutions in place yet.

  • Yep, looking again at step 4 in each of these examples, it does say, "Content that Salesforce is hosting for you in Salesforce sites or Experience Cloud sites." Salesforce support confirmed. Thanks, @Arut! help.salesforce.com/s/… Jul 2, 2022 at 4:32
  • @ShaneSteinfeld Updated my answer with few more supporting points.
    – arut
    Jul 2, 2022 at 5:04
  • Thanks, @arut! Appreciate the extra detail. Jul 5, 2022 at 23:47

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .