Edge Acceleration
  • Site Acceleration
    • Overview
    • Quickly Import and Export Site Configuration
    • Access Control
      • Token Authentication
    • Smart Acceleration
    • File Optimization
      • Smart Compression
    • Network Optimization
      • HTTP/2
      • HTTP/3(QUIC)
        • Overview
        • Enable HTTP/3
        • QUIC SDK
          • SDK Overview
          • SDK Download and Integration
          • Sample Code
            • Android
            • iOS
          • API Documentation
            • Android
            • iOS
      • IPv6 Access
      • Maximum Upload Size
      • WebSocket
      • Client IP Geolocation Header
      • Client IP Geographical Location
      • gRPC
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Custom Error Page
    • Request and Response Actions
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
    • Media Services
      • Audio and Video Pre-pulling
      • Just-in-Time Image Processing
      • Just-in-Time Media Processing
      • VOD Media Origin
  • L4 Proxy
    • Overview
    • Creating an L4 Proxy Instance
    • Modifying an L4 Proxy Instance
    • Disabling or Deleting an L4 Proxy Instance
    • Batch Configuring Forwarding Rules
    • Obtaining Real Client IPs
      • Obtaining Real TCP Client IPs via TOA
      • Obtaining Real Client IPs Through Protocol V1/V2
        • Overview
        • Method 1: Obtaining Real Client IPs Through Nginx
        • Method 2: Parsing Real Client IPs on Application Server
        • Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
      • Transmitting Client Real IP via SPP Protocol
  • Edge DNS
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Advanced DNS Configuration
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
    • Domain alias
      • Overview
      • Configuration Guide
      • Batch Connecting SaaS Domain Names
      • Configuring Alias Domain Names for Disaster Recovery
    • Traffic Scheduling
      • Traffic Scheduling Management
    • Origin Configuration
      • Origin-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Load Balancing
        • Overview
        • Quickly Create Load Balancers
        • Health Check Policies
        • Viewing the Health Status of Origin Server
        • Related References
          • Load Balancing-Related Concepts
          • Introduction to Request Retry Strategy
      • Origin Group Configuration
      • Related References
        • ld Version Origin Group Compatible Related Issues
      • Collect EdgeOne origin-pull node IP
  • Edge Cache
    • Overview
    • EdgeOne Cache Rules
      • Content Cache Rules
      • Cache Key Introduction
      • Vary Feature
    • Cache Configuration
      • Custom Cache Key
      • Node Cache TTL
      • Status Code Cache TTL
      • Browser Cache TTL
      • Offline Caching
      • Cache Prefresh
    • Clear and Preheat Cach
      • Cache Purge
      • URL Pre-Warming
    • How to improve the Cache Hit Rate of EdgeOne
  • Rules Engine
    • Overview
    • Supported Matching Types and Actions
    • Rule Management
    • variables
Docs Overview/
Edge Acceleration/
Edge DNS/
Domain alias/
Configuring Alias Domain Names for Disaster Recovery/

Configuring Alias Domain Names for Disaster Recovery

This document describes how to achieve business disaster recovery by using EdgeOne alias domain names. If a domain name becomes unavailable due to, for example, DNS exceptions, the alias domain name can provide the service instead.



Note:
This feature is supported only by the Enterprise plan and is currently in beta test. If you need to use it, please contact the business personnel to enable the allowlist for use.

Purpose

Reading this document may take 10 minutes, which helps you learn:
1. How to use alias domain names to relieve the workload of maintaining multiple domain names for the same business.
2. How to verify that an alias domain name is working as expected.
3. How to improve business disaster recovery by using alias domain names.
4. How to apply for and maintain free certificates for alias domain names.

Background

When promoting your business with many top-level domain names or with many alternate domain names in expectation for keeping your business uninterrupted, normally you need to configure these domain names one by one while ensuring each of them is configured identically in EdgeOne. This can result in a huge maintenance workload when it comes to adding/modifying configuration and applying for/renewing HTTPS certificates.

EdgeOne synchronizes the security and acceleration capabilities of one domain name to others by pointing multiple alias domain names to a target domain name. The configuration of the target domain name will then be synced among these alias domain names. Free HTTPS certificates can also be applied for and auto-renewed.

Prerequisites

1. You have purchased the EdgeOne Enterprise plan.
2. You have connected a site to EdgeOne. For more information, see Adding Sites.
3. You have added the target domain name in EdgeOne.

Sample Scenario

In this scenario, you have connected target.example.com to EdgeOne and want these domain names to serve as alternatives:
1. alias1.site.com
2. www.shop.com
3. backup.website.com
To do so, add these domain names as alias domain names to target.example.com, and make sure that they have the same accessibility as target.example.com via browser:



Directions

Step 1. Create an alias domain name

1. Log in to the EdgeOne console. Navigate to Site List and select a site for management.
2. In the left sidebar, click Alias Domain Names. On the page that appears, click Create.
3. Enter alias1.site.com as your alias domain name, select target.example.com as your target domain name, and set Off for certificate configuration. Click OK.




Step 2. Add a CNAME record that points to the target domain name

You must add a CNAME record that points to the target domain name to the alias domain name. Only activated alias domain names support applications for free certificates.
1. When your alias domain name is added, the status is default to Not activated, as shown in the figure below:



2. Go to the DNS provider where the alias domain name is located and add a CNAME record pointing to the target domain name. For details about modifying CNAME, see Modifying CNAME Records.

3. When the CNAME record is added, EdgeOne automatically checks for updates and changes the status of the domain alias to Activated.

4. Perform the same steps to add and activate www.shop.com and backup.website.com, as shown below:




Step 3. Verify the configuration

Access the alias domain names alias1.site.com, www.shop.com and backup.website.com via your browser to verify whether the configuration has taken effect.



As shown above, the same response is obtained for the access requests to the alias domain names and target domain name. This indicates that the alias domain names have taken effect as expected.

If alias1.example.com becomes Not activated due to DNS resolution failures, alias1.site.com, www.shop.com and backup.website.comcan keep providing services.

Step 4. Apply for a free certificate (optional)

After you configure the CNAME record for your alias domain name by following Step 2, apply for a free HTTPS certificate as follows:
1. On the alias domain name list page, find alias1.site.com and click Configure in the HTTPS column. In the pop-up window, select Free certificate and click OK.



2. On the alias domain name list page, move the pointer over

to view the information about the certificate: