Showing posts with label Sites. Show all posts
Showing posts with label Sites. Show all posts

Monday, June 2, 2014

How to register a custom domain for Sites

Just noticed (thanks to Jason and Kara!) that since Winter '14 the setup needed to register a custom domain to use with Force.com Sites has changed.  Here's the instructions on the setup page (will show the actual org Id):

A new or renamed domain will be permitted if any of the following criteria is true. Note that 00d7************** is your organization's unique API identifier in lower-case characters.

  • Your domain name is a CNAME record that points to [domain].00d7**************.live.siteforce.com.
    • As an example, if you are adding www.example.com, it must be a CNAME record that points to www.example.com.00d7**************.live.siteforce.com.Note that your domain will need to be a CNAME record for Salesforce to serve your domain.
  • Your domain name has a TXT record that equals 00d7************** with no punctuation.
  • Your domain name is a subdomain of an another domain in your organization.


There's a recipe in the Force.com Cookbook that really needs to be updated, but I couldn't even add a comment to suggest that (errored out each time I tried)...

Thursday, February 13, 2014

Salesforce domain name management: you can only have three wishes

You can really have a bunch of stuff under the Domains section, and sometimes wonder how they ended up there.  Some you probably know well, because you actually asked your domain/DNS administrator to create the redirect/alias once you assign the names to your Sites.  But there are some in there you can neither edit nor delete from the list.  They are the genie wishes with your Salesforce domains.  Let's look at an example and see what they really are.


  1. That's My Domain name.  When you enable that feature, you'll need to pick the name, and it will appear in all the URLs of your Salesforce org pages.
  2. That comes from Sites.  This subdomain name is the real URL start of all Sites pages.  You may have your own domain URLs over those, but eventually your DNS servers need to know where to redirect the visitors to the real URLs.
  3. That's for your Communities.  Once picked when you enable the feature, that becomes the real URL start for all Community sites, which are essentially special Sites.
These 3 are truly genie wishes in the sense that once you asked Salesforce to grant them, and were indeed granted (at the time of feature activation), you can neither change them nor take back.  They're stuck with you for eternity (of the org).  So choose wisely!  You are certainly constrained by your organization's name or traditional marketing tags, but if you do have some options, try to pick nice, short, and generic names.  It's easy to understand why being nice and short matters, but being generic is often overlooked.  When you start to use Sites or Communities it's often a specific need, but the name will be applied to all subsequent uses, which may have nothing in common with the initial project.  So being generic is also important.