tencent cloud

Cloud Load Balancer

Release Notes and Announcements
CLB Release Notes
Product Announcements
Product Introduction
Overview
Strengths
Use Cases
Principles
Product Comparison
Use Limits
Service Regions and Service Providers
Purchase Guide
Billing Overview
Billing
CLB Resource Package
Purchase Methods
Payment Overdue
Product Attribute Selection
Getting Started
Getting Started with Domain Name-Based CLB
Getting Started with CLB
Getting Started with IPv6 CLB
Deploying Nginx on CentOS
Deploying Java Web on CentOS
Operation Guide
CLB Instance
CLB Listener
Real Server
Health Check
Certificate Management
Log Management
Monitoring and Alarm
Cloud Access Management
Classic CLB
Practical Tutorial
Deploy certificate to CLB (mutual authentication)
Enabling Gzip Compression & Testing
HTTPS Forwarding Configurations
Obtaining Real Client IPs
Best Practices for Configuring Load Balancing Monitoring Alerts
Implementing HA Across Multiple AZs
Load Balancing Algorithm Selection and Weight Configuration Examples
Configuring WAF protection for CLB listening domain names
Configure IAP to authenticate web access to the CLB domain and path
Configure IAP to authenticate programmatic access to CLB's domain and path
Ops Guide
Solution to Excessive Clients in TIME_WAIT Status
Load Balancer HTTPS Service Performance Test
Stress Testing FAQ
CLB Certificate Operation Permissions
Troubleshooting
UDP Health Check Exception
API Documentation
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
FAQs
Billing
CLB Configuration
Troubleshooting Health Check Issues
HTTPS
WS/WSS Protocol Support
HTTP/2 Protocol Support
Default Domain Name Blocking Prompt
Service Level Agreement
Contact Us
Glossary
DocumentationCloud Load BalancerOperation GuideCLB InstanceConfiguring a CLB Forwarding Domain Name

Configuring a CLB Forwarding Domain Name

PDF
Focus Mode
Font Size
Last updated: 2025-06-04 10:29:20
When a client initiates a request, the Cloud Load Balancer forwards the request to the backend server according to the configured listener forwarding rules. The domain name in the listener forwarding rules is the domain name used by your backend service. This document explains how to configure a domain name.

Directions

Step 1: Register a Domain Name

Domain registration is the foundation of establishing services on the Internet.
If you already have your own domain name with another registrar, you can transfer the domain name to Tencent Cloud Domain Services. For details, please see Domain Transfer In.
If you do not have a domain name yet, you need to register a domain name. For details, please see Domain Registration.

Step 2: Add Domain Name Resolution

1. Log in to the DNSPod Console.
2. In My Domains, click the domain name that requires CNAME record forwarding to enter its Record Management page. As shown below:

3. Click Add Records and fill in the following record information. As shown below:

Host: fill in a subdomain. For example, when adding a record for www.dnspod.com, you can simply select www in the Host field. If you only want to add a record for dnspod.com, select @ in the Host field. The @ CNAME record will affect the normal resolution of MX records, please add it with caution.
Type: select CNAME.
Split Zone: select Default, otherwise some users may not be able to resolve it. For example, if you want to point China Unicom users to 2.com and all other users to 1.com. You can implement this by adding two CNAME records, one with the split zone Default and record value 1.com, and the other with the split zone China Unicom and record value 2.com.
Value: you can only fill in a domain name pointed to by the CNAME.
Weight: a split zone with identical hosts. It can be set for different record values, and the resolved content will be returned according to the set weight ratio during DNS resolution. Enter an integer between 0 and 100.
MX: leave it empty.
TTL: cache time. The smaller the value, the faster the modification record will take effect in various regions. Default: 600s.
4. Click Confirm.

Step 3: Verify the Resolution Result

Note:
Resolution will take effect in about 10 minutes.
After completing the above steps, you can enter the CNAME domain (such as www.example.com) in the browser to test if the domain resolves correctly.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback