NetSuite Changelog
AuthenticationRelease NotesNew FeatureSecurity

Domain Settings Transition to DNS Challenges in NetSuite 2024.1

Starting in NetSuite 2024.1, domain verification shifts from HTTP to DNS challenges, enhancing security and streamlining configurations.

·2 min read·5 views·NetSuite 2024.1·From NetSuite Release Notes PDF

TL;DR Opening

Starting in NetSuite 2024.1, domain owner verification has transitioned from HTTP-based challenges to DNS-based challenges utilizing the Automatic Certificate Management Environment (ACME) protocol. This update enhances the security and management of new domain setups while maintaining existing configurations.

What's New in 2024.1

The transition to DNS challenges signifies a substantial change in how domain configurations are managed within NetSuite. Specifically, this affects each new domain established in the system:

  • DNS-Based Challenges: Existing domains will continue using HTTP challenges, ensuring no immediate changes are required for current DNS setups.
  • UI Improvements: Significant updates have been made to the Domain record page:
    • The Certificate area: The option to switch to automatic certificates when a manual certificate expires has been removed since it is no longer applicable with DNS challenges.
    • The Domain area is now split into two distinct sections:
      • Domain: Displays crucial fields, including Domain Name, Website, and Hosting Root.
      • DNS: Where you can find information regarding the CNAME records needed for hosting and DNS challenge configurations.

Implementation Note

When setting up a new domain, administrators must ensure they copy the necessary CNAME records from the DNS area in NetSuite and add them to their domain provider's website to complete the setup successfully.

For further details on DNS challenges and domain configurations, consult the help topic titled Set Up a Domain.

Who This Affects

This update impacts several key roles within organizations:

  • Administrators: Responsible for domain setup and configuration.
  • Security Personnel: Monitoring domain security compliance.
  • Developers: Integrating and managing domain-related functionalities within applications.

Key Takeaways

  • NetSuite 2024.1 introduces DNS challenges for new domain setups.
  • Existing domains retain their current configurations using HTTP challenges.
  • Domain record UI has been updated for a clearer segregation of domain and DNS settings.
  • Administrators must update CNAME records when establishing new domains to ensure proper DNS challenge implementation.

Frequently Asked Questions (4)

Do existing domains need to be reconfigured to comply with the new DNS challenges?
No, existing domains will continue to use HTTP challenges, so there are no immediate changes required for current DNS setups.
What steps must administrators take when setting up a new domain under the DNS challenge system?
Administrators must copy the necessary CNAME records from the DNS area in NetSuite and add them to their domain provider's website to complete the domain setup successfully.
Does the transition to DNS challenges affect the Certificate area in the Domain record page?
Yes, the option to switch to automatic certificates when a manual certificate expires has been removed from the Certificate area, as it is no longer applicable with DNS challenges.
How does the DNS area in the Domain record page differ from the previous setup?
The DNS area now provides information regarding the CNAME records needed for hosting and DNS challenge configurations, while the Domain area displays crucial fields like Domain Name and Hosting Root.
Source: Domain Settings Transition to DNS Challenges — NetSuite Release Notes PDF. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

Also from NetSuite 2024.1

View all NetSuite 2024.1 changes →