- Implementing Applications for AEM as a Cloud Service
- Using Cloud Manager
- Release Notes for Cloud Manager
- Understanding Programs and Program Types
- Production Programs
- Sandbox Programs
- Creating an AEM Application Project
- Managing Environments
- Managing your Code
- Cloud Manager CI-CD Pipelines
- Deploying your Code
- Understanding your Test Results
- Accessing and Managing Logs
- SLA Reporting
- User Access to New Relic
- Understanding Notifications
- Managing SSL Certificates
- Managing Custom Domain Names
- Introduction
- Getting a Custom Domain Name
- Adding a Custom Domain Name
- Adding a TXT Record
- Checking Custom Domain Name Status
- Configuring DNS Settings
- Checking DNS Record Status
- Viewing & Updating & Replacing a Custom Domain Name
- Updating a Custom Domain Name’s SSL Certificate
- Deleting a Custom Domain Name
- Managing IP Allow Lists
- Cloud Manager FAQs
- Developing for AEM as a Cloud Service
- AEM Project Structure
- AEM Project Repository Structure Package
- AEM as a Cloud Service SDK
- AEM as a Cloud Service Development Guidelines
- Logging
- Configurations and the Configuration Browser
- AEM Technical Foundations
- API Reference Materials
- Generating Access Tokens for Server Side APIs
- Customizing Site Templates and Themes
- Headful and Headless in AEM
- Full Stack AEM Development
- Getting Started Developing AEM Sites - WKND Tutorial
- Structure of the AEM UI
- Sling Cheatsheet
- Using Sling Adapters
- Using the Sling Resource Merger in AEM as a Cloud Service
- Overlays in AEM as a Cloud Service
- Using Client-Side Libraries
- Page Diff
- Editor Limitations
- Naming Conventions
- Components and Templates
- AEM Tagging Framework
- Building Tagging into AEM Applications
- Search
- Custom Error Pages
- AEM Node Types
- Headless Experience Management
- Headless and AEM
- Headless Documentation Journeys
- Getting Started Guides
- Content Fragments
- Headless Delivery with Content Fragments and GraphQL
- Working with Content Fragments
- Enable Content Fragment Functionality for your Instance
- Content Fragment Models
- Managing Content Fragments
- Variations - Authoring Fragment Content
- Markdown
- Using Associated Content
- Metadata - Fragment Properties
- Structure Tree
- Preview - JSON Representation
- Delivery API
- Hybrid and SPA AEM Development
- Hybrid and SPA with AEM
- Enabling JSON Export for a Component
- SPA Introduction and Walkthrough
- SPA WKND Tutorial
- Getting Started using React
- Getting Started using Angular
- SPA Deep Dives
- Developing SPAs for AEM
- SPA Editor Overview
- SPA Blueprint
- SPA Page Component
- Dynamic Model to Component Mapping
- Model Routing
- The RemotePage Component
- Editing an External SPA within AEM
- Composite Components in SPAs
- Server Side Rendering
- Enabling JSON Export for a Component
- Launch Integration
- SPA Reference Documents
- Developer Tools
- Personalization
- Configuring and Extending AEM as a Cloud Service
- Deploying to AEM as a Cloud Service
- Author Tier
- Content Delivery Overview
Configuring DNS Settings
After your custom domain name is successfully verified and deployed, you are ready to update the DNS records for your custom domain name with your DNS provider. Doing so enables your site to serve visitors. This activity is therefore typically done before Go-live.
You or the appropriate individual in your organization must be able to login or contact your DNS provider (the company whom you purchased the domain from) and make updates in your DNS settings.
To do this, you must determine if you must configure your DNS settings to a CNAME or Apex record pointing your custom domain name to the Cloud Manager domain name. A CNAME or A record, once provisioned will route all internet traffic for the domain to wherever it is pointing. If that location is not provisioned to serve the traffic, there will be an outage. If it has not been tested, there may be errors in the content. This is why this step is always done after testing is complete and the customer is ready for Go-live.
The following steps must be completed as indicated in the table below:
| Step | Responsibility | Learn More | |
|---|---|---|---|
| Add SLL Certificate | Add SLL Certificate | Customer | Adding an SSL Certificate |
| Domain Verification | Add TXT record | Customer | Adding a TXT Record |
| Review Domain Verification Status | Customer | ||
| Status: Domain Verification Failure | Customer | Checking Domain Name Status | |
| Status: Verified, Deployment Failed | Contact Adobe representative | Checking Domain Name Status | |
| Add DNS records that point to AEM as a Cloud Service by adding CNAME or APEX records | Configure DNS Settings | Customer | Configuring DNS Settings |
| Check DNS Record Status | Customer | Checking DNS Record Status | |
| Status: DNS status not detected | Customer | Checking DNS Record Status | |
| Status: DNS resolves incorrectly | Customer |
CNAME Record
The following sections will help you determine which type of record is appropriate for your DNS configuration.
A Canonical Name or CNAME record is a type of DNS record that maps an alias name to a true or canonical domain name. CNAME records are typically used to map a subdomain such as www.example.com to the domain hosting that subdomain’s content.
Login to your Domain Registrar and create a CNAME record to point your custom domain name to the target as shown below:
| CNAME | Custom Domain Name Point to Target |
|---|---|
| www.customdomain.com | cdn.adobeaemcloud.com |
APEX Record
An apex domain is a custom domain that does not contain a subdomain, such as example.com. An apex domain is configured with an A , ALIAS , or ANAME record through your DNS provider. The Apex domains must point to specific IP addresses.
Add all of the the following A records to your Domain’s DNS settings via your domain provider:
-
A RECORD -
A record for domain @ pointing to IP 151.101.3.10 -
A record for domain @ pointing to IP 151.101.67.10 -
A record for domain @ pointing to IP 151.101.131.10 -
A record for domain @ pointing to IP 151.101.195.10
Resources on adobe.com
Resources
Adobe Account
