Hi @Steve Goldberg, I have a question regarding the communication about enforcing CDN caching on production. What happens with sites that have the root domain as their primary domain? I configured a new root domain in a test account and was able to enable the CDN and retrieve content from Akamai correctly. However, since it’s a root domain, the DNS status shows an error that i assumed that is because we use of CNAME flattening and not a real CNAME Record as we do for sub-domains. This causes the domain to be flagged as an invalid setup, which prevents manual cache clearing. Sorry to bring this up here, but I thought it might help others who encounter the same scenario. Thanks in advance!

The only way to set up a root domain is, as you say, using CNAME flattening. I can't verify whether your set up is correct. If you think it is then you might need to raise a case.

@Martin Hey bro! Typically I strongly push back on customers using root domain to run their SuiteCommerce. When I was in PS we created a rule and no customer was allowed to use root domain for their production site. There are ways of achieving it? yes. Is it advisable? Not in my opinion/experience. The only reason to have the root domain in NetSuite with the new setup, is so that it is secured and redirected automatically to the primary domain (IE: www). BTW: I can't confirm if this still the case but when I was still in NetSuite, root domains were not cached on CloudFront/Akamai so that was already a downgrade in performance. The infrastructure in general was not fully prepared to use root domain as the website domain.