This notice is intended for customers where one or more of your NetSuite-hosted websites is incorrectly configured, including:
A site or sites is using a third-level domain that has an incorrect DNS configuration.
A site or sites is using a second-level domain that does not include a subdomain (for example, when the domain does not include a subdomain such as “www” or “shop”).
The solution to both situations is similar: the CNAME on your DNS records must resolve to the CNAME shown on the Domain records in NetSuite. Your chosen domain must include a subdomain, unless your DNS provider supports CNAME flattening.
Your account will soon be moved to a new data center built on the Oracle Cloud Infrastructure (OCI). Account moves are targeted to begin in May 2021. To avoid performance issues related to the account move, you need to perform the actions detailed in Fixing Your DNS Records.
What is Changing?
The IP addresses of NetSuite services have always been subject to change at any time. Oracle NetSuite is moving your account to a new data center. The IP addresses will change with your account move, and they may change more often in the future. Therefore, your DNS records must not rely on static IP addresses. You should fix your DNS records as soon as possible before your account is moved.
The DNS setup for a second-level domain is often dependent on a static IP address, and therefore this DNS setup is not recommended.
Fixing Your DNS Records
To fix your DNS records, you must use the Domain Name and CNAME (Alias) shown on your Domain record in NetSuite. For more information, see the NetSuite help topic Point your Domain Name at your Domain (DNS Settings), SuiteAnswers ID 27482.
Note: Wherever you are using a second-level domain, you must include a subdomain, unless your DNS provider supports CNAME Flattening. Support of the CNAME flattening feature varies by DNS provider. Contact your DNS provider to confirm whether they support CNAME flattening. In addition to following the CNAME Flattening instructions provided by your DNS provider, see also the NetSuite help topic Website Domains and Email Hosting, SuiteAnswers ID 42736.
To fix your DNS records:
- For each website, locate the Domain Name and CNAME (Alias) fields on the Domain record in your NetSuite account.
- Wherever you are using second-level domains, if CNAME Flattening is not supported by your DNS provider, you must update the Domain Name field on your Domain record in NetSuite so that your domain includes a subdomain such as “shop” or “www”. Take note of the resultant change to the CNAME (Alias) field.
- Log in to your DNS provider’s site. Verify the DNS record for each site, and edit the DNS record as necessary to comply with the following format:
- Domain Name IN CNAME CNAME (Alias):
www.example.com IN CNAME www.example.com.hosting.netsuite.com
For example, if the Domain Name field on the Domain record in NetSuite is shop.wolfeelectronics.com, the CNAME (Alias) field displays shop.wolfeelectronics.com.hosting.netsuite.com. The format of the entry on your DNS record would be:
shop.wolfeelectronics.com IN CNAME shop.wolfeelectronics.com.hosting.netsuite.com
You can update your DNS records at any time before your account is moved. However, to avoid downtime for your websites, you must make these changes before your account is moved. Your websites will stop working if you have not made the required changes to your DNS records.
To avoid future problems with your DNS setup, you should only use a second-level domain for a redirect to a third-level domain.
After making changes to your DNS setup, review your Domain Health Status on the Set Up Domains page in NetSuite to ensure that your domain is setup correctly. For more information, see the NetSuite help topic Troubleshoot Domain Setup Errors, SuiteAnswers ID 78125.
Required Actions and Timeline
Before Your Account is Moved
- See Fixing Your DNS Records above. You must make the required changes to your DNS records. Verify that all DNS entries for your websites point to domain names rather than static IP addresses.
- Ensure that hardcoded IP addresses are not used in your account:
- Verify that any custom scripts and services point to domain names rather than IP addresses.
- Verify that there are no firewall configurations using a fixed IP address to restrict traffic into or out of NetSuite servers. This configuration is rare and against our policies, but it could be something your IT or Security team set up in your company’s infrastructure.
- Schedule your move-related maintenance. At least 30 days before the move of your account you will receive the first of several notifications. To minimize the disruption to your websites and services, the notifications provide instructions for selecting your preferred time slot for the move-related maintenance.
- Set up a custom Site Maintenance page that your website customers will see while your site is unavailable. If you do not customize a site maintenance page, a default "temporarily offline" message will be displayed. For more information, see the NetSuite help topic Custom Site Maintenance Page, SuiteAnswers ID 39555.
During the Account Move
We understand that the availability of your websites is critical to your business and we try to minimize downtime wherever possible.
- During the move:
- Your account and websites will be offline during the move. Most moves complete in 30 minutes. Some accounts are offline for approximately 60 minutes while the data is securely synchronized.
- Your shoppers will automatically see a default "temporarily offline" message, or, if you have one, your customized Site Maintenance page.
After the Move
After the move-related maintenance is complete, your account and websites will automatically be brought back online.
If you have additional questions, contact NetSuite Customer Support.