This article guides you on how to implement IPv6 conversion services through global acceleration to meet the needs of IPv6 clients to access back-end IPv4 services.
Usage restrictions: Currently, only the following regions support IPv6 client access to the global acceleration service: North China 1 (Qingdao), North China 2 (Beijing), East China 1 (Hangzhou), East China 2 (Shanghai), South China 1 (Shenzhen), South China 2 (Heyuan), South China 3 (Guangzhou), Southwest 1 (Chengdu), China (Hong Kong), Singapore, USA (Virginia), Germany (Frankfurt). Please make sure that the acceleration region you add belongs to the above regions.
Note: After the following configuration of IPv6 is completed, you can use https://ipv6proxy.cn to test the content of pure IPv6 website in the case of IPv4.
Scenario example
1. The existing IT systems of some enterprises are deployed in the local IDC computer room. The IDC computer room is a pure IPv4 network. Due to business development needs, enterprises need to provide services for IPv6 clients. However, making an enterprise's existing IT system support IPv6 is a complex system engineering, the transformation is difficult and the cycle is long, which is usually a pain point for the enterprise. Now, the global acceleration product provides IPv6 conversion services, which can quickly realize IPv6 conversion without changing the existing IT system of the enterprise. The access request initiated by the enterprise IPv6 client is directly sent to the back-end IPv4 server after the global acceleration conversion, realizing fast service access. At the same time, for some enterprises whose IT systems are deployed on the cloud, IPv6 client access can also be quickly supported through global acceleration.
This document uses the following scenarios as examples to guide you how to deploy the Global Accelerated IPv6 Transition Service. The existing IT system of a company in Beijing is deployed in the local IDC room, which is a pure IPv4 network. Due to the needs of business expansion, the enterprise now plans to use global acceleration products to quickly implement IPv6 conversion to meet the needs of IPv6 clients to access back-end IPv4 Web services.
Configuration steps
Step 1: Combine Purchase Instances
You can fill in your acceleration business in the global acceleration console, and the system will recommend acceleration solutions based on the acceleration business intelligence. According to the acceleration scheme recommended by the system, you can purchase the acceleration instance and basic bandwidth package required for the acceleration business in combination.
Log in to the Global Accelerator Management Console .
On the Instance List page, click Purchase Wizard in the upper right corner.
Note If you are using the global acceleration service for the first time, please ignore this step.
In the intelligent recommendation product plan, select the following option areas related to your business, fill in the accelerated business according to the following information, and then click Generate plan.
configure | illustrate |
|---|---|
The region you need to accelerate | Select the region where access acceleration is required. This article selects Beijing. |
service area | Select the region where the target server is located. This article selects Beijing. |
Is there an ICP record | Select whether your acceleration service has a record. This article chooses to have a record. Note All websites that provide services to mainland China (mainland) must first go through ICP filing before they can open their services. For more information, see What is an ICP filing . |
The server is deployed in | Choose whether the backend service is deployed on Alibaba Cloud or a non-Alibaba Cloud. This article selects non-Alibaba cloud. |
Range of peak bandwidth | Enter the bandwidth usage during peak business hours, in Mbps. Enter 2 for this article. |
Maximum concurrent connections | Maximum concurrent connections defines the maximum number of connections that a Global Accelerator instance can carry. When the number of connections on the instance exceeds the maximum number of connections defined by the specification, the new connection request will be discarded. This article selects 5 thousand. |
In the Recommended Plan area, after confirming the plan content, click Go to Combine Purchase.
On the purchase page, purchase the instance required to accelerate the business according to the following information, and then click Buy Now and complete the payment.
configure | illustrate |
|---|---|
order time | Select the subscription time for the instance. |
Specification | Select the specification to purchase the Global Acceleration Instance. In this paper, small I (specification unit) is selected. |
Bandwidth Type | Select the bandwidth type to purchase the basic bandwidth package. This article chooses to enhance the acceleration bandwidth. |
Bandwidth Peak | Choose to purchase the bandwidth peak of the basic bandwidth package. This article chooses 2 Mbps. |
Step 2: Add Acceleration Area
After purchasing the instances needed to accelerate your business, you can add an acceleration zone, specify the region where users who can access backend services are located, and allocate acceleration bandwidth to them.
On the instance list page, find the created Global Accelerator instance, and click the instance ID.
Click the Acceleration Regions tab, and then click Add Access Region under the North China tab.
In the Add Acceleration Region dialog box, configure according to the following information and click OK.
configure | illustrate |
|---|---|
area | Select the region where the user accessing the acceleration service belongs. This article selects Beijing. |
bandwidth | Enter the geographic bandwidth of the acceleration service. Enter 2 Mbps for this article. |
IP address protocol | Select the IP address protocol for users to access the global acceleration service. This article chooses IPv6. |
After the addition is successful, Global Accelerator will allocate an IPv6 protocol acceleration IP in the access area to accelerate user access.
Step 3: Add listeners and endpoint groups
The listener is responsible for inspecting connection requests and handling inbound connections from clients based on the port and protocol you specify. Each listener is associated with an endpoint group, which is associated with the listener by specifying the region to distribute traffic to. Once associated, Global Accelerator will distribute traffic to the best endpoint within the endpoint group associated with the snoop.
On the instance details page, click the Listeners tab, and then click Add Listener.
On the Configure Snooping and Protocol Configuration Wizard page, configure snooping according to the following information, and then click Next.
configure | illustrate |
|---|---|
listen name | Enter a name for the monitor. The name is 2~128 characters long, starts with uppercase and lowercase letters or Chinese, and can contain numbers, underscores (_) and dashes (-). |
protocol | Select the protocol type to monitor. This article chooses TCP. |
port | Specifies the listening port for receiving requests and forwarding them to the terminal node. The value range of the port is 1~65499. Enter 80 for this article. |
Client Affinity | Choose whether to maintain client affinity. Client affinity is maintained, that is, when a client accesses a stateful application, all requests from the same client can be directed to the same endpoint. This article selects the source IP. |
On the Configure Endpoint Configuration Wizard page, configure the endpoint group according to the following information, and then click Next.
configure | illustrate |
|---|---|
Node group name | Enter a name for the endpoint group. The name is 2~128 characters long, starts with uppercase and lowercase letters or Chinese, and can contain numbers, underscores (_) and dashes (-). |
area | Select the region to which the endpoint group belongs, that is, the region of the target server to be accessed by the request. This article selects Beijing. |
The backend service is deployed in | Choose whether the backend service is deployed on Alibaba Cloud or a non-Alibaba Cloud. This article selects non-Alibaba cloud. |
Keep client source IP | Select on or off to keep client source IP. After enabling, the backend server can obtain the client source IP through this function. This article chooses to turn off keeping the client source IP. |
end node | An endpoint is the target host that a client requests access to. You can configure endpoints based on the following information: Backend Service Type: Select Custom IP. Backend Service: Enter the public IP address of the backend IPv4 web service. Weight: Enter the weight of the terminal node, the weight range: 0~255. Global Acceleration routes traffic to endpoints proportionally based on the weights you configure. Note If the weight of an endpoint is configured as 0, Global Accelerator will stop distributing traffic to that endpoint, please exercise caution. |
On the Configure Audit Configuration Wizard page, after confirming the listening and endpoint configuration information, click Submit.
Step 4: Configure DNS resolution
You need to configure DNS resolution to forward requests to access back-end IPv4 services to Global Accelerator to achieve acceleration. You can choose any of the following methods:
By adding an AAAA record, point the back-end IPv4 service domain name to an IPv6 address, that is, the acceleration IP of the IPv6 protocol allocated by the global acceleration instance.
By adding a CNAME record, point the backend IPv4 service domain name to another domain name, that is, the CNAME address assigned by the Global Accelerator instance.
Log in to the DNS console .
On the domain name resolution page, find the target domain name, and click Resolution Settings in the Action column.
Click Add Record, complete the following configuration, and then click OK.
Add AAAA record
configure | illustrate |
|---|---|
record type | Select AAAA. AAAA records are used to point a domain name to an IPv6 address. |
host record | Enter the prefix of the accelerated domain name. If your acceleration domain name is www.aliyun.com, the host record is www. If your acceleration domain name is aliyun.com, the host record is @. If your acceleration domain name is *.aliyun.com, the host record is *. If your acceleration domain name is mail.aliyun.com, the host record is mail. |
Parse the line | Choose Default. |
record value | Enter the acceleration IP of the IPv6 protocol assigned by the Global Accelerator instance. |
TTL | Choose 10 minutes. The time-to-live of DNS resolution records on the DNS server. |
Add CNAME record
configure | illustrate |
|---|---|
record type | Choose CNAME. CNAME records are used to point a domain name to another domain name. |
host record | Enter the prefix of the accelerated domain name. If your acceleration domain name is www.aliyun.com, the host record is www. If your acceleration domain name is aliyun.com, the host record is @. If your acceleration domain name is *.aliyun.com, the host record is *. If your acceleration domain name is mail.aliyun.com, the host record is mail. |
Parse the line | Choose Default. |
record value | Enter the CNAME assigned to the Global Acceleration instance. You can view the CNAME assigned to the Global Accelerator instance on the instance list page. |
TTL | Choose 10 minutes. The time-to-live of DNS resolution records on the DNS server. |
illustrate
The newly added CNAME record will take effect in real time, and the modified CNAME record will take effect within 72 hours.
If you encounter the problem of adding a conflict, you can change the speedup domain name or adjust the conflicting record, see Resolving Record Conflict .
After CNAME is configured, due to the delay of about 10 minutes in the status update, the domain name list page of the console may still prompt "CNAME not configured", please wait patiently.
Step 5: Access the test
In the access region (this article is Beijing), open the command line window of the IPv6 client.
Run the following command to test whether the IPv6 client can normally access the backend IPv4 web service.
curl -6 -g http://[<acceleration IP assigned by GA>]
Note This article uses the CentOS operating system as an example for testing. Different types of operating systems have different test commands. For specific test commands, see the operation guide of your operating system.
After testing, the IPv6 client can normally access the back-end IPv4 web service through the accelerated IP.
