CNAME Configuration Issues with CDN in NetSuite
Resolve CDN issues by ensuring CNAME records are set correctly in NetSuite for optimal site performance.
TL;DR Opening
This article addresses common issues when the CNAME is configured correctly, yet the CDN is not enabled in NetSuite. Proper configuration is essential for ensuring your website leverages NetSuite’s Content Delivery Network (CDN) effectively.
Understanding CNAME Configuration and CDN
A Canonical Name (CNAME) record serves as a redirect to another domain, allowing your website to be associated with a different address. Specifically, in the context of NetSuite, a CNAME directs traffic to the appropriate hosting servers, which should be the CDN to maximize site performance.
Diagnosing CNAME Configuration Issues
If you notice your site is translating to NetSuite's standard shopping servers instead of the Akamai CDN, this indicates an issue with CDN settings. The results from a dig command can often reveal this:
;; ANSWER SECTION:www.scaexample.com. 14099 IN CNAME www.scaexample.com.hosting.netsuite.com.www.scaexample.com.hosting.netsuite.com. 299 IN CNAME shopping.na1.netsuite.com.shopping.na1.netsuite.com. 2962 IN A 64.89.45.13The above shows that your CNAME setup might not be correctly enabling the CDN. To resolve this, ensure that you check the Use CDN Cache option when updating your configuration.
Steps to Update Your CNAME Records
- In NetSuite, navigate to Commerce > Hosting > Domains.
- Click View next to your domain name.
- In the Domain section, locate the CNAME in the CNAME (Alias) field; store this information for the next steps.
- Access your DNS provider's control panel to edit DNS settings for your site domain related to SCA.
- Replace any existing A records with a new CNAME record using the alias from Step 3. Ensure to include the 'www.' prefix if applicable.
- Important: Keep existing MX records untouched to maintain email functionality.
- Return to NetSuite, access Commerce > Hosting > Domains, and click View next to your domain name again.
- Navigate to the Advanced section and check the Use CDN Cache box.
- Click Save.
Timing for Configuration Changes
After you have made changes, note that DNS updates can take from a few hours to potentially a full day to propagate. If the CDN does not function correctly after this period, you may need to troubleshoot further.
Conclusion
Properly configuring your CNAME records and ensuring that the Use CDN Cache option is enabled are crucial for leveraging NetSuite's CDN effectively, thus enhancing your site’s performance and reliability.
Source: This article is based on Oracle's official NetSuite documentation.
Key Takeaways
- The CNAME record must be configured to point to the CDN.
- Check the Use CDN Cache setting in NetSuite for effective operation.
- DNS changes may take time to propagate and reflect.
- Keep an eye on MX records to ensure email services remain functional.
Frequently Asked Questions (4)
Do I need to enable a specific setting in NetSuite to use the CDN effectively?
What should I do if my site is translating to NetSuite's standard shopping servers instead of the CDN?
What are the implications of incorrectly configured CNAME records for my eCommerce site?
How should I handle MX records when updating CNAME records for CDN configuration?
Was this article helpful?
More in Commerce
- Available Items Only Feature in NetSuite 2026.1
Available items only filtering boosts sales efficiency in NetSuite 2026.1 with Intelligent Item Recommendations.
- Commerce Extensions in NetSuite 2026.1
Commerce Extensions in NetSuite 2026.1 enhance performance and user experience in eCommerce.
- Convert Multiple Transaction Line Items into Configured Items in
Enhance transaction processing in NetSuite by converting multiple line items into configured items with improved session handling.
- New SuiteCommerce Features in NetSuite 2026.1
New SuiteCommerce features in NetSuite 2026.1 enhance user experience and improve eCommerce efficiency.
