- Implementing Applications for AEM as a Cloud Service
- Using Cloud Manager
- Managing Environments
- Configuring your CI/CD Pipeline
- Deploying your Code
- Understanding your Test Results
- Accessing and Managing Logs
- 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
- Managing your Code
- 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
- AEM as a Cloud Service API
- Generating Access Tokens for Server Side APIs
- 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
- Java API Guidelines
- Hybrid 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
- Server Side Rendering
- Enabling JSON Export for a Component
- Launch Integration
- SPA Reference Documents
- Headless Experience Management
- Headless and AEM
- 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
- Developer Tools
- Personalization
- Configuring and Extending AEM as a Cloud Service
- Deploying to AEM as a Cloud Service
- Author Tier
- Content Delivery Overview
Adding a TXT Record
A DNS TXT record authorizes a Domain to be hosted in a CDN service. The customer must create a DNS TXT record in the zone that authorizes Cloud Manager to deploy the CDN Service with the custom domain and associate it with the backend service. This association is entirely under the control of the customer and strongly authorizes Cloud Manager to serve content from the service to a domain. That authorization may be granted as well as withdrawn.
You myst follow the steps below before you create a TXT record:
- Have the ability to modify the DNS records for your organization’s domain, or contact the appropriate person who can.
- Identify your domain host or registrar if you do not know it already.
When you initiate domain verification, Cloud Manager gives you the name and TXT value to use for verification. Add a TXT record to your domain’s DNS server using the specified Name and Value.
- Login to your Domain Host and visit the DNS records section.
- Add
_aemverification.[yourdomainname]as the Name, and add the TXT Value exactly as it appears.
Refer to the examples in the table below.
| Domain | Name | TXT Value |
|---|---|---|
example.com |
_aemverification.example.com |
Displayed in Cloud Manager UI and is specific to the domain and the Cloud Manager environment |
test.example.com |
_aemverification.test.example.com |
Displayed in Cloud Manager UI and is specific to the domain and the Cloud Manager environment |
When you are done you can verify the result by running: dig _aemverification.[yourdomainname] -t txt.
The expected result should display the TXT value provided in Cloud Manager UI.
For example, if your domain is example.com, then run: dig TXT _aemverification.example.com -t txt.
There are also various DNS lookup tools, Google DoH can be used to lookup TXT record entries and identify if the TXT record is missing or erroneous.