Edge Acceleration
  • Site Acceleration
    • Overview
    • Quickly Import and Export Site Configuration
    • Access Control
      • Token Authentication
      • Authentication Method A
      • Authentication Method B
      • Authentication Method C
      • Authentication Method D
      • Authentication Method V
    • 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
      • HTTP Response
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
      • HTTP Restrictions
    • 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
    • Overview
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Batch Importing DNS Records
      • Advanced DNS Configuration
      • Enumeration of Resolution Lines and Corresponding Codes
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
      • Verify Business Access
    • 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
        • Origin-Pull Timeout
        • 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/
Overview/

Overview

Traffic scheduling management is a multi-CDN smart resolution and scheduling tool provided by Tencent Cloud EdgeOne. It supports custom traffic scheduling policies between the origin server and multiple service providers to implement smooth canary migration of traffic and flexible allocation of services, thereby ensuring a high service availability. Once your site is connected to EdgeOne, you can manage your connected domain name through the domain name service module. When your site is connected, EdgeOne provides you with three different connection modes, including connection via NS, connection via CNAME, and connection via DNSPod. Depending on the mode of site connection, different capabilities will be offered within the domain name service module.

Description of Connection Modes

To allow users to flexibly connect to EdgeOne based on actual business needs, EdgeOne currently supports three connection modes: connection via NS, connection via CNAME, and connection via DNSPod. Below is a comparison of the three modes:
Mode
Connection via NS (Recommended)
Connection via CNAME
Connection via DNSPod
Use case
You can modify the DNS resolution service provider of your domain name and switch the domain name resolution service to EdgeOne.
If your current domain name is already managed by another DNS resolution service provider and you do not want to change the existing service provider, you can use the mode of connection via CNAME.
When the domain name is managed on Tencent Cloud DNSPod, it is recommended to use this connection mode.
DNS record management
After connection, DNS records of the current domain name are managed solely in EdgeOne.
After connection, DNS records are still managed by the existing DNS resolution service provider.
After connection, DNS records are still managed in the Tencent Cloud DNSPod console.
Advantage
You can manage DNS records of your domain name in EdgeOne in a one-stop manner. After domain name acceleration takes effect, it can support directly resolving A records by default to point to the nearest EdgeOne edge node, reducing the time taken for domain name resolution.
You can connect without changing the DNS resolution service provider for the domain name, making the usage more flexible and allowing quick switching between multi-cloud vendors.
Through connection via DNSPod, you can skip domain name ownership verification. It also supports one-click addition of domain name CNAME records for quick acceleration.

Supported Capabilities

Depending on the connection mode, different capabilities will be provided for you in the domain name service menu:
Feature
Description
Applicable Connection Mode
This feature is used to manage DNS resolution records of the domain name. The capabilities differ, depending on the connection mode:
Connection via NS: After changing the DNS server to point to EdgeOne, you can manage all resolution records of the domain name in the DNS records. The addition, modification, and deletion of resolution records are supported.
Connection via DNSPod: Your current domain name's A/AAA/CNAME records configured in DNSPod will be automatically synchronized, and only viewing is allowed. To add, modify, or delete resolution records, you can go to the DNSPod console for management.
Connection via NS
Connection via DNSPod
This feature is used to configure advanced DNS capabilities, including DNSSEC and custom NS server names.
Connection via NS
This feature is used to perform centralized management of information on acceleration domain names connected to EdgeOne. On this page, you can configure the origin server and HTTPS Certificate for these acceleration domain names.
All connection modes
Traffic Scheduling Management is a smart resolution and scheduling tool provided by EdgeOne. It supports custom traffic scheduling policies between the origin server and multiple service providers to implement smooth canary migration of traffic and flexible allocation of services, thereby ensuring a high service availability.
Connection via CNAME
Connection via DNSPod