This article explains how to update your naked domain DNS configuration to avoid service disruption when Salesforce migrates your Communities site to the Salesforce Edge Network.
A naked domain (also called an apex domain or root domain) is a domain name without a subdomain prefix — for example, example.com instead of www.example.com. Standard DNS does not allow a naked domain to use a CNAME record, so some customers configure their naked domain using an A record (a direct IP address mapping instead of a hostname mapping).
Salesforce is updating its internal infrastructure to the Salesforce Edge Network for Communities sites that supply their own SSL certificate. Customers who currently use an A record (direct IP address) for their naked domain — instead of ANAME, ALIAS, or CNAME-flattening — must update their DNS configuration before the deadline specified in your outreach case to avoid service disruption.
CNAME-flattening (also called ANAME or ALIAS) is a DNS feature supported by many modern DNS vendors that allows a naked (root) domain to point to a hostname (CNAME target) rather than a direct IP address. This is the recommended approach for Salesforce naked domain configurations because it allows Salesforce to update the underlying IP addresses of the Edge Network without requiring you to update your DNS records each time.
You are affected if all of the following are true:
To avoid service disruption during the Salesforce Edge Network migration, choose one of the following three options. Option 1 is strongly recommended. Update your configuration before the deadline specified in your outreach case.
Work with your DNS vendor to update your naked domain to use ANAME, ALIAS, or CNAME-flattening instead of a direct IP address (A record). This resolves your domain to a Fully Qualified Domain Name (FQDN) — a complete hostname that identifies your Salesforce org's Edge Network endpoint — rather than a fixed IP address that can change.
To find your CNAME target hostname:
.live.salesforce.com. For example, if your domain is example.com and your org ID is 00D000000000001AAA, your CNAME target is example.com.00D000000000001AAA.live.salesforce.com.If your current DNS vendor only supports A records for naked domains and cannot configure ANAME, ALIAS, or CNAME-flattening, consider migrating to a DNS vendor that supports these record types. Once you have switched DNS vendors, follow the steps in Option 1 to configure the CNAME target.
If you are unable to implement Option 1 or Option 2 before the deadline, you can temporarily update the IP addresses in your A record to the new Salesforce Edge Network IP addresses. Contact Salesforce Support to obtain the new IP addresses.
Steps to update and validate:
/smth.jsp (for example, `<REDACTED>).X-Salesforce-VIP has the value EDGE, your domain is successfully routing through the Salesforce Edge Network.Why Option 3 is not recommended:
000389365

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.