• Introduction
• Account Types
• Prerequisites
  • CDN DNS
• Workspace
• Architecture
• Extensions
• Nodes
• Layouts
  • Masters
  • Templates
  • CMS Form Tag
• Items
  • Child Items
• Draft Items
• Item Actions
• Caching
• Media Management
• Users & Groups
• Security
• Site Settings
  • Languages
  • Global Values
  • Properties
  • Data Definitions
  • User Profile
  • Membership User Profile
  • Membership Settings
  • Response Headers
  • Rewrite Directives
  • Page Redirects
  • Admin Timezone
  • Site Performance
  • Exceptions & Messages
  • MIME Types
• Tokens

Core Modules Documentation

DNS Records

The following DNS settings only pertain if the CMS instance is not using the CDN feature. If the CDN feature is enabled, please click here for DNS setup.

In order for your site to be publically available, a few DNS records will need to be created with your DNS provider.

• An A record for the primary base domain registered with Connected Apps point to the IP Address assigned to the domain.
  
  For instance, if the primary base domain is contoso.com, then an A record will need to be created without any sub domains specified in the record. The primary base domain is only used by administrators and contente editors to access the CMS workspace.
   
• An A record for each sub domain under each regisetered domain.
  
  For instance, the base domain contoso.com has content hosted at www.contoso.com, support.contoso.com and community.contoso.com. Therefore an A record for www, support and community will need to be created.
   
• An A record for each sub domain that hosts content should have a corresponding record prefixed with "dev."
  
  For instance, if content is hosted at www.contoso.com and support.contoso.com, then consider having A records for dev.www.contoso.com and dev.support.contoso.com.
  
  The CMS framework supports the "dev" prefix and when content is accessed using this prefixed domain, caching routines are bypassed, page cache headers are omitted and style & script links point to the un-minified versions. In addition, the built-in spider that indexes your pages will attempt to reach the page using the "dev" domain.

To find the registered domains/subdomains and associated IP address, click here.

SSL Certificate

Every CMS instance is created using a Self Signed Certificate. This type of SSL certificate provides the same security strength as certificates provided by well known certificate authorities such as Verisign and Thawte however will result in certificate exception error in browsers.

Accessing the CMS workspace requires a secure connection. It is recommened for customers to apply for certificates issued by well known certificate authorities but is not required. Sites planning to provide secure web pages to end users is strongly encouraged to upgrade the default certificate.

For more information on obtaining a  new certificate, please contact support.

IP Address

Each CMS instance is assigned a public IP Address. Becuase of the shortage of IPv4 addresses, CMS instances may share the same IP address with other instances. In order to support SSL access to the workspace over a shared public IP address, a TLS extension called Server Name Indication (SNI) is used. Support for SNI is supported to most modern browsers except for any browsers on Windows XP. If your CMS instance provides secure access to end users and you need to support a wide variety of operating systems then you can inquire about obtaining a dedicated IP address.