After activating CDN, you can log in to the CDN Console and select Domain Management on the left sidebar. Click Create a Distribution to add an acceleration domain name. After the domain name is added, its configuration will be distributed to the CDN cache nodes across the entire network without directly affecting your business in the production environment. To activate acceleration, you need to configure a CNAME record. For specific directions, please see CNAME Configuration.
Access the domain name management page and click Create a Distribution.
The distribution creation page consists of three parts:
Based on your selected domain and origin configurations, CDN will recommend service configuration, which can be submitted without modification.
Enter your business domain name in the domain name field and select the project, region, and service type:
|Domain||1. The domain name can contain up to 50 characters.
2. ICP filing for services in Mainland China has been obtained from the MIIT for the domain name.
3. Subdomain names in the format of
4. If the domain name is a wildcard domain or has been configured by another user, you need to complete ownership verification to access or retrieve it.
1. After a wildcard domain name is configured, its subdomain names and second-level wildcard domain names cannot be configured under another account.
2. Domain names in the format of
|Project||Project is a set of resources shared by all Tencent Cloud products. You can manage it on the project management page.|
|Region||Mainland China: access requests of global users will be scheduled to cache nodes in mainland China for acceleration.
Overseas: access requests of global users will be scheduled to cache nodes outside mainland China for acceleration.
Global: access requests of global users will be scheduled to the nearest optimal node for acceleration.
Acceleration service in and outside mainland China are billed separately. For more information on billing policies, please see here.
|Service type||CDN optimizes acceleration performance based on service type.
For the best acceleration result, we recommend you select the service type similar to that of your actual business.
Static acceleration: suitable for small-scale resource acceleration scenarios such as ecommerce, websites, and game images.
Download acceleration: suitable for download scenarios such as game installation, source audio/video file download, and mobile phone firmware distribution.
Streaming VOD acceleration: suitable for scenarios such as online education and VOD.
|Internet protocol||IPv4: nodes can be accessed only through IPv4 addresses.
IPv4+IPv6: nodes can be accessed through both IPv4 and IPv6 addresses. Only when this option is selected can an IPv6 origin server be configured.
IPv6 is only supported in mainland China.
Configure business origin server information. If the CDN node has no resource cache, the node will pull the resource from the origin server and cache it.
|Origin type||External: select this if you already have your own stable business server (i.e., origin server).
COS origin: if resources have already been stored in COS, the bucket can be directly selected as the origin server.
|Origin address||External origin server:
1. Multiple IPs can be configured as the origin server, which will be polled during origin-pull.
2. If multiple IPs are used, you can configure weighted origin-pull in the format of
3. You can configure one domain name as the origin server, which should be different from the business acceleration domain name.
1. Select from the drop-down list the bucket to be configured as the origin server.
2. If the bucket is private read/write, first grant CDN access to the bucket. Otherwise, origin-pull will fail.
|Origin-pull protocol||This can be selected based on the protocols supported by the origin server:
HTTP: HTTP/HTTPS access requests use HTTP origin-pull.
HTTPS: HTTP/HTTPS access requests use HTTPS origin-pull (the origin server must support HTTPS access).
Follow protocol: HTTP access requests use HTTP origin-pull, while HTTPS access requests use HTTPS origin-pull (the origin server must support HTTPS access).
|Origin domain||This refers to the site domain name accessed on the origin server by a CDN node during origin-pull.
If a subdomain name is configured, it will be the same as the acceleration domain name by default and can be customized.
If a wildcard domain name is configured, it will be the actual access subdomain name by default and can be customized.
Configure the node acceleration service:
|Basic configuration||A node caches resources by following the
If "Ignore Query String" is enabled, parameters after "?" in the URL will be ignored before mapping.
By default, this feature is enabled for download and streaming VOD acceleration, but not for static acceleration.
|Enable Range GETs||This specifies whether to process partial requests during origin-pull. It can be enabled only if the origin server supports Range GETs.
This feature is enabled for COS origin server by default.
|Cache configuration||This specifies the expiration period of the node cache, which is 30 days for all files by default.
The configured expiration period is an estimate. The actual expiration period may be shorter depending on the available storage capacity of the node.
Click Submit to add the domain name and wait for the domain name configuration to be distributed across the entire network. This will take about 5–10 minutes.
When the distribution is completed, CDN will allocate a corresponding CNAME address to you, which needs to be configured before taking effect. For detailed directions, please see CNAME Configuration.
If the domain name is a wildcard one or has been connected to by another user, you need to verify ownership before accessing or retrieving it. DNS verification is used. The verification steps are as follows:
_cdnauthas its host record and the record value randomly generated on the "Verification Method" page as its record value.