- Updates and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Configuration Guide
- Permission Management
- Use Cases
- Best Practice
- API Documentation
- FAQ
- Troubleshooting Methods
- CDN Service Level Agreement
- Glossary
- Updates and Announcements
- User Tutorial
- Product Introduction
- Purchase Guide
- Getting Started
- Configuration Guide
- Permission Management
- Use Cases
- Best Practice
- API Documentation
- FAQ
- Troubleshooting Methods
- CDN Service Level Agreement
- Glossary
Preparations
Activating CDN
Before configuring CDN, you need to activate it first. If you have already activated it, proceed directly.
Confusing concepts
| Configuration Item | Description | Use Position |
|---|---|---|
| Acceleration domain name | Domain name to be connected to CDN, which is the actual domain name accessed by end users | Create a Domain Name > Domain Configuration |
| Origin address (IP/domain name) | IP address (domain name) of the origin server. If the requested content is not on the CDN node, this address (domain name) will be accessed to get the requested content. Origin server: server that provides a service, which can process and respond to user requests. End users access your business at the origin address. An origin address can be a domain name or IP address. |
Create a Domain Name > Origin Configuration |
| Origin domain | Server content actually requested during origin-pull of the CDN node. This is generally consistent with the acceleration domain name. You can enter the actually requested content in the origin-pull request based on your business needs. | Create a Domain Name > Origin Configuration |
| CNAME domain name | After your acceleration domain name is connected, the system will automatically assign a CNAME domain name suffixed with .cdn.dnsv1.com or .dsa.dnsv1.com.After your acceleration domain names are mapped to the CNAME domain name, Tencent Cloud will dynamically change the IP address pointed to by the CNAME record and update all your acceleration domain names, eliminating your need to manually change the IP addresses pointed to them. |
Configure CNAME |
- Acceleration domain name: if end users access your business through
cdntest.com, thencdntest.comis the acceleration domain name. - CNAME domain name: after an acceleration domain name is connected, the system will automatically assign a CNAME domain name suffixed with
.cdn.dnsv1.comor.dsa.dnsv1.com, such ascdntest.com.cdn.dnsv1.comandcdntest.com.dsa.dnsv1.com. - Origin address: if the CDN node does not cache the content requested by the user, the node will request such content at
1.1.1.1, which is the origin address. - Origin domain: when the CDN node is requesting
1.1.1.1, if you expect that the actually requested address isoriginhost.com, which is different fromcdntest.comin the end user's request, then set the origin domain tooriginhost.com, and the end user will access the content atoriginhost.comafter origin-pull throughcdntest.com. Generally, the acceleration domain name and the origin domain should be the same, which can be adjusted based on your business needs.
Directions
Go to the CDN console, select Domain Management on the left sidebar, and click Create a Domain Name.
You need to configure the following three parts to connect a domain name:
Configuring the domain name
- Select an acceleration region.
- Enter an acceleration domain name.
If your connected domain name meets one of the following conditions, you need to verify your ownership as instructed in Domain Name Ownership Verification.- The domain name is being connected for the first time.
- The domain name has been connected by another user.
- The domain name is a wildcard domain name.
- Select an acceleration type.
- Set other optional items (which can be modified in Domain Management subsequently).
Configuration item description
| Configuration | Description |
|---|---|
| Region | Chinese mainland: all requests are scheduled to cache nodes in the Chinese mainland. Outside the Chinese mainland (including Hong Kong/Macao/Taiwan (China)): all requests are scheduled to cache nodes outside the Chinese mainland. Global: requests are scheduled to the nearest optimal node. Notes: acceleration services in and outside the Chinese mainland are billed separately. For more information, see Billing Overview. |
| Acceleration Domain Name | 1. The domain name can contain up to 81 characters. 2. ICP filing is required for domain names running in the Chinese mainland. 3. Sub-domains ( a.test.com or a.b.test.com) and wildcard domain names (*.test.com or *.a.test.com) are supported.4. You need to verify the domain name ownership when connecting a domain name for the first time, a wildcard domain name, or a connected domain name. Notes: 1. If a wildcard domain name is connected here, its sub-domains and second-level wildcard domain names cannot be connected by any other accounts. 2. Domain names in the format of *.test.com and *.a.test.com cannot be configured at the same time.3. Malicious or high-risk domain names cannot be connected to. For more information, see Use Limits. |
| Acceleration type | CDN optimizes acceleration performance based on service type. For better acceleration effect, we recommend selecting the acceleration type similar to that of your actual business. CDN Static acceleration: applicable to small-scale resource acceleration scenarios such as e-commerce, website, and game photos. Download acceleration: applicable to downloading scenarios such as game installation packages, audio and video source file downloads, and mobile phone firmware distribution. On-demand video streaming acceleration: applicable to online education and on-demand video streaming. ECDN Dynamic/Static acceleration: applicable to business scenarios where static and dynamic data is integrated, such as various website homepages. Dynamic acceleration: applicable to scenarios such as account login, order transaction, API call, and real-time query. Note: The billing standards vary by acceleration type. For more information, see Billing Overview of CDN and Billing Overview of ECDN respectively. |
| IPv6 Access | IPv6 access is disabled by default. If it is enabled, CDN nodes can be accessed over the IPv6 protocol. Notes: • IPv6 access is currently not supported due to platform upgrade. Please stay tuned for the official launch. • IPv6 access is only available in the Chinese mainland. •For global acceleration domain names, if IPv6 access is enabled, it will take effect only in the Chinese mainland. |
| Project | Project is a set of resources shared by all Tencent Cloud products. You can manage it on the Project Management page. |
| Tag | The tag key and value are required. If you have not created a tag, create one in Tag Management. |
Origin server configuration
- Select the origin server type.
- Select the origin-pull protocol.
- Enter the origin address.
- Configure the origin domain.
Configuration item description
| Configuration Item | Description |
|---|---|
| Origin Type | Customer Origin: Select this if you already have your own business server (i.e., origin server). Tencent Cloud COS: If COS is used, you can directly select the corresponding bucket. Third-Party Object Storage: a third-party object storage platform other than Tencent Cloud. Currently, AWS S3 and Alibaba Cloud OSS are supported. Note: This option is unavailable for some platforms at the moment. Please stay tuned for the official launch. |
| Origin Server Address | Customer Origin: 1. Multiple IPs can be configured as the origin server, which will be polled during origin-pull. 2. You can configure port (0 - 65535) and weight (1 - 100) in the format of origin server:port:weight. The port can be omitted and the format becomes origin server::weight. Note: HTTPS protocol currently only supports port 443. 3. You can configure a domain name as the origin server, which should be different from the CDN acceleration domain name. Note: using a connected CDN acceleration domain name as the origin server will cause resolution loop and origin-pull failure. Tencent Cloud COS: 1. You can select a bucket of Tencent COS as the origin server. 2. Set the origin server type to default domain name or static website according to the bucket configuration and your actual use case. 3. For a private bucket, grant CDN access to the bucket. Third-party Object Storage: 1. If the resource is stored in a third-party object storage platform, please enter a valid bucket access address as the origin server. For now, AWS S3 and Alibaba Cloud OSS are supported. Note: http:// and http:// cannot be included. my-bucket.oss-cn-beijing.aliyuncs.com and my-bucket.s3.ap-east-1.amazonaws.com are supported.2. For a third-party private bucket, enter the valid key and enable forwarding authentication to access the bucket. |
| 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 domain name accessed on the origin server by a CDN node during origin-pull. Customer Origin: it defaults to the acceleration domain name. If a wildcard domain name is connected, it will be the actual access subdomain name by default and can be customized. Tencent Cloud COS: it defaults to the bucket access address, which is the same as the origin address and cannot be modified. Third-party Object Storage: it defaults to the bucket access address, which is the same as the origin address and cannot be modified. |
Service configuration (optional)
CDN provides common service configuration items for you to configure as needed. If you don't want to configure the service right now, you can do so after connecting the domain name.
Configuration item description
| Configuration | Description |
|---|---|
| Ignore Query String | A node caches resources by following the Key-Value mapping, where Key is the resource URL. If Ignore Query String is enabled, parameters after "?" in the URL will be ignored. Otherwise, Key will be a complete resource URL. 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. By default, this feature is enabled for COS origin server or download and streaming VOD acceleration. |
| Cache Configuration | Validity of node cache. For static acceleration, the general dynamic files (such as PHP, JSP, ASP, and ASPX files) will not be cached, and other files will be cached for 30 days by default. For download and streaming VOD acceleration, the cache validity of all files is 30 days. The configured cache validity is the longest possible time, the actual cache validity is related to the resources on nodes. |
Completing the Configuration
After adding the domain name, wait for the domain name configuration to be distributed to the entire network, which usually takes 5 to 10 minutes.
Subsequent Steps
When the distribution is completed, CDN will allocate a corresponding CNAME address to you. You need to configure the CNAME to use the CDN service. For detailed directions, see CNAME Configuration.
Yes
No
Was this page helpful?