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 InstanceDirections for Upgrading to Domain Name-Based CLB

Directions for Upgrading to Domain Name-Based CLB

PDF
Focus Mode
Font Size
Last updated: 2024-10-17 18:05:02
You can upgrade your existing public network Cloud Load Balancer (CLB) instances to domain name-based CLB instances. After the upgrade, the CLB service will be delivered through domain names, and VIPs may change dynamically with business requests and will no longer be displayed in the console.

CLB Service Comparison Before and After the Upgrade

Item
After Upgrade
Before Upgrade
SLA
99.99%
99.95%
Domain names supported
Yes
No
Automatic VIP scaling supported
Yes
No
VIP changes
VIPs may change dynamically with business requests and will no longer be displayed in the console.
VIPs are fixed.
Health check source IP
100.64.0.0/10 IP range by default, helping prevent IP conflicts
CLB instance VIP by default, which can be switched to the 100.64.0.0/10 IP range

Restrictions

Classic networks do not support the upgrade of CLB instances. If your CLB instance is in a classic network, migrate the instance first. For more information, see Ending Support for Classic Network.
Classic CLB does not support upgrade. Upgrade classic CLB instances to CLB instances as instructed in Classic CLB Upgrade Prompt.
CLB instances created by containers currently do not support direct upgrade through the console. If upgrade is needed, please submit a ticket for assistance.
Anti-DDoS Pro currently does not support protection for domain name-based CLB. After upgrading to domain name-based CLB, Anti-DDoS Pro will fail and seriously affect business security. For users with public network CLB instances already bound to Anti-DDoS Pro, or users with Anti-DDoS needs for public network CLB instances, upgrading to domain name-based CLB instances is not recommended. For other issues, please submit a ticket for assistance.

Prerequisites

1. Your business service is accessible through CNAME resolution.
2. The health check source IP has been changed to the 100.64.0.0/10 IP range. For more information, see Changing Health Check Source IP.

Directions

Method 1: Upgrading a specific CLB instance

1. Log in to the CLB Console.
2. Select a region in the top-left corner of the Instance management page. In the instance list, locate the target instance, click More in the Operation column of the instance, and select Upgrade to domain name-based instance.
3. In the Upgrade to domain name-based instance pop-up window, click OK.



Method 2: Upgrading instances in batches

1. Log in to the CLB Console.
2. Select a region in the top-left corner of the Instance management page and select the instances to upgrade in the instance list.
3. Click More above the instance list, and select Upgrade to domain name-based instance.


4. In the Upgrade to domain name-based instance pop-up window, click OK.


Previous Topic: Deploying Java Web on CentOSNext Topic: Creating CLB Instances

Help and Support

Was this page helpful?

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

Feedback