This article provides alternative solutions on how to handle APEX/Root domain configuration with the B2C Commerce platform's embedded Content Delivery Network (eCDN).
NOTE:
All Content Delivery Networks (CDNs) provide CNAME records as a part of DNS setup because CDNs can't have static IPs to point to multiple nodes in a distributed network.
For example, the following is NOT recommended as it will not work long term:
mysite.com A 104.28.26.118
Note: In the above scenario, 104.28.26.118 is the IP address of a Cloudflare node.
How will I handle my APEX/Root domains from now on?
Problem:
Due to limitations in DNS specification, Apex/Root domains (example.com) cannot carry a CNAME record to point to an alias hostname. A CNAME record is not allowed to coexist with any other data. For example, if suzy.example.com is an alias for sue.example.com, you cannot also have an MX record for suzy.example.edu, an A record or even a TXT record.
Workaround:
Use an external service to redirect from the Apex/Root domain to the sub-domain. This redirect should be set up for HTTP and HTTPS. For example:
Depending on your needs, you can also set up a HTTP to HTTPS redirection e.g. http://example.com redirects to https://www.example.com
The www.example.com will remain CNAME’d to eCDN.
External Redirect could be any of the following:
a. DNS provider handling the redirect.
b. Use a 3rd party Proxy Server, e.g. stacked CDN on top of eCDN.
c. Using IIS on a Microsoft Windows Server
d. If you’re using NGINX, you can rewrite rules via that channel.
e. Using Apache as a web server, you can do it via .htaccess.
What can I do if I don't want to redirect my APEX/Root domain to a subdomain?
Issue:
You intend to permanently serve traffic from the apex (example.com) instead of redirecting to subdomain (i.e. www.example.com).
Workaround:
Use a DNS-level solution to direct apex/root domains to eCDN CNAME alias. Known providers who support include UltraDNS, DynDNS, DNSMadeEasy, DNSimple, CSC Advanced DNS, NS1, etc..
What can I do if I want to migrate to a proxy zone?
Issue:
What steps need to be taken in order to move to a proxy zone as outlined in Migrate a Legacy Zone to a Proxy Zone?
Answer:
000391603

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.