- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- CLB Listener Overview
- Configuring TCP Listener
- Configuring UDP Listener
- Configuring TCP SSL Listener
- Configuring QUIC Listener
- Configuring HTTP Listener
- Configuring HTTPS Listener
- Load Balancing Methods
- Session Persistence
- Layer-7 Redirection Configuration
- Layer-7 Custom Configuration
- Layer-7 Domain Name Forwarding and URL Rules
- Using QUIC Protocol on CLB
- SNI Support for Binding Multiple Certificates to a CLB Instance
- Real Server
- Health Check
- Certificate Management
- Monitoring and Alarm
- Log Management
- Cloud Access Management
- Classic CLB
- Best Practices
- Enabling Gzip Configuration & Testing
- HTTPS Forwarding Configurations
- Obtaining Real Client IPs
- Notes on SNAT and Non-SNAT Types for Private Network CLB
- Implementing HA Across Multiple AZs
- Load Balancing Algorithm Selection and Weight Configuration Examples
- Configuring WAF protection for CLB listening domain names
- Troubleshooting
- OPS Guidelines
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Instance APIs
- Listener APIs
- Real Server APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Cloud Load Balancer APIs
- Classic CLB APIs
- Data Types
- Error Codes
- CLB API 2017
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
Note：
- IPv6 NAT64 CLB can only be created in three regions: Beijing, Shanghai, and Guangzhou.
- IPv6 NAT64 CLB does not support classic CLB.
- IPv6 implementations are still at the preliminary stage across the internet, and SLA is not guaranteed. In case of access failure, please submit a ticket for assistance.
CLB supports creating IPv6 NAT64 CLB instances. Tencent Cloud will assign an IPv6 public IP address, i.e., VIP of the IPv6 edition, to an instance, and the VIP will forward requests from IPv6 clients to the real IPv4 CVM instance.
IPv6 NAT64 CLB Instance Overview
An IPv6 NAT64 CLB instance is a load balancer implemented based on the IPv6 NAT64 bridge technology. Through an IPv6 NAT64 CLB instance, real servers can be quickly accessed by IPv6 users without any IPv6 modification required.
IPv6 NAT64 CLB Architecture
The IPv6 NAT64 CLB architecture is as shown below.
When IPv6 NAT64 CLB is accessed from an IPv6 network, CLB can smoothly convert IPv6 addresses to IPv4 addresses to adapt to existing services and quickly implement IPv6 transformation.
IPv6 NAT64 CLB Advantages
Tencent Cloud IPv6 NAT64 CLB has the following advantages when helping your business quickly connect to IPv6:
- Quick connection: CLB enables connection to IPv6 in a matter of seconds and is available upon purchase.
- Smooth business transition: in order to smoothly transit your business to IPv6, you only need to transform the client with no modifications required for real servers. IPv6 NAT64 CLB supports access from IPv6 clients and converts IPv6 messages into IPv4 messages. IPv6 transition is imperceptible to applications on real servers, which still work in their original way.
- Ease of use: IPv6 NAT64 CLB is compatible with IPv4 CLB operation process and easy to use with no additional learning costs incurred.
Operation Guide
Creating IPv6 NAT64 CLB instance
- Log in at Tencent Cloud's official website and go to the CLB purchase page.
- Select options for the following parameters correctly:
- Region: only Beijing, Shanghai, and Guangzhou are supported.
- Instance Type: CLB.
- Network Type: public network.
- IP version: IPv6 NAT64.
- Network: VPC.
- Other configurations are the same as general instance configurations.
- After setting the configuration items on the purchase page, click Buy Now to return to the CLB instance list page, where you can view the IPv6 NAT64 CLB instance you just purchased.
Using IPv6 NAT64 CLB
Log in to the CLB Console and click an instance ID to enter the details page. On the "Listener Management" tab, you can configure listeners and forwarding rules and bind CVM instances. For more information, please see Getting Started with CLB.
Relevant Documentation
Obtaining Real Client IPs via TOA in Hybrid Cloud Deployment
Yes
No
Was this page helpful?