New to Localist? Start with our Implementation Guide
Localist’s custom domain feature is an essential component in your overall white-labeling of the product as it changes the display of your Localist URL to a subdomain of your current website.Your calendar’s custom domain is set up by using a CNAME record. Note: a CNAME is different than a redirect, or domain-forward.
Setting Up a Custom Domain
Your custom domain will need to be a subdomain to your website, such as events.yourwebsite.com, and not set as a subdirectory, such as yourwebsite.com/events.
- If you do not currently own a website domain, you will need to purchase a domain from a registrar like Namecheap, pairNIC, Register, or iWantMyName. (This usually costs about $10-$40 per year.)
1. If you haven’t already told Localist Support the domain you will be using, please send a note to firstname.lastname@example.org so that we can configure the domain on our end.
2. Through your registrar, create a CNAME record to point your custom domain to your Localist placeholder URL, yourorganizationsname.enterprise.localist.com.
- Note: This is not a forward or a redirect, but an alias. If you are setting up a redirect for the non-www custom domain, the redirect should be unmasked.
- SetCNAME to events.yourdomain.com -> set in Calendar Settings
- Set unmasked redirect of events.yourdomain.com to events.yourdomain.com
3. If the domain has already been set up as a CNAME, we will add it to your Calendar Settings after configuration. If the domain has not been set up as a CNAME when the configuration is added on Localist’s end, you will need to add it to your Calendar Settings after completing that step.
- Note: It can take 24-72 hours for domain settings to propagate across the world. Confirm the domain has fully propagated before taking steps