Loading

Update your naked domain configuration to avoid service disruption

Date de publication: Oct 13, 2022
Description
This is a follow up to a recent TCR sent in early May 2022 to customers that do not use ANAME/ALIAS/CNAME-flattening, or use an external host that does not route traffic to a Salesforce CNAME, also called naked domains.

As part of enhancing performance for global users and service availability, Salesforce is updating our internal infrastructure to the Salesforce Edge Network for Communities who supply their own certificate. 

This help article defines a naked domain and describes how you can use naked domains for your Salesforce org.

To ensure this migration can complete without disruption, take the action below before the specified deadline in your Outreach case. 
Résolution

Option 1 (Recommended Option): Add ANAME/ALIAS/CNAME-flattening for your domain

Work with your DNS vendor to update this domain to use ANAME/ALIAS/CNAME instead of ‘A record,’, to resolve the fully qualified domain name (FQDN).

To find your corresponding domain name:

  1. Log on to your org on salesforce.com.
  2. Click Setup on the upper right side of the dashboard.
  3. On the left pane, either search for Domain Management or go to Domain Management directly.
  4. Under Domain Management, go to Domains and click Add Domain for the domain you want to migrate to EDGE.
  5. Locate the domain name that you will use to set up the CNAME target with your DNS vendor. Use the URL format as specified in the Naked Domains help article:

    <domain_name>.<18_char_org_id>.live.salesforce.com
Option 2: Change to a DNS vendor that supports Option 1
If your current DNS vendor can only support ‘A records’ for naked domains, consider changing to a different DNS vendor that can support Option 1 above.

Option 3 (Not Recommended): Update IP addresses in the domain 'A Record'
Update the domain ‘A record’ to remove the existing IP addresses and contact Support for new IP addresses. 

Once you’ve obtained and updated the IP addresses, validate the update using the following step:
> From your browser, enter <YourFQDN>/smth.jsp (for example,  https://example.com/smth.jsp). 

If you see X-Salesforce-VIP : EDGE in the HTTP header, your domain is good to go.

Note: Option 3 is not recommended for the following reasons:
  • The IP addresses above can change as frequently as every 6 months.
  • Your custom domain’s performance will be subpar compared to using the entire Salesforce Edge Network with FQDN in the DNS record.

 

Numéro d’article de la base de connaissances

000389365

 
Chargement
Salesforce Help | Article