You can connect a domain name on the CDN console. For more information, please see Adding Domain Names.
Yes. The following are the requirements for connecting a domain name to CDN:
a.b.test.comor a wildcard domain name in the format of
Yes, CDN supports connecting wildcard domain names, for which domain name ownership verification is required. Once verified, domain names can be connected or retrieved.
*.test.comis already connected to Tencent Cloud, then none of its sub-domain names can be connected to another account.
*.test.comis already connected to your account, then wildcard domain names in formats such as
*.path.test.comcannot be connected to your account.
Generally, it takes less than 30 minutes for the CDN configuration to take effect. If the configuration does not take effect within 30 minutes, you can submit a ticket for assistance.
Yes. After you configure multiple IPs, CDN will randomly access one of the IPs when forwarding a request to the origin server. If the number of origin-pull failures with this IP exceeds the threshold, the IP will be isolated for 300 seconds by default, during which no origin-pull requests will be forwarded to the IP.
See CNAME Configuration for how to bind CNAME with your DNS service provider.
Please check whether the user is a collaborator. The collaborator's permission is configured by the creator of the CDN service. If the creator does not assign the relevant permission to the collaborator, the collaborator cannot perform the operation. If you are sure that the collaborator has been granted the permission but still cannot perform the operation, submit a ticket for assistance.
Yes. After the acceleration service is disabled, the domain name configuration will be retained, but the acceleration service will no longer be available. In this case, a 404 status code will be returned for user requests.
No. After a domain name is deleted, its configuration will not be retained.
You can disable the acceleration service on the CDN console. For detailed directions, please see "Disabling the acceleration service" in Domain Name Operations.
You can delete an acceleration domain name on the CDN console. For detailed directions, please see "Deleting acceleration domain names" in Domain Name Operations.
Please submit a ticket for assistance.
The selected service type determines which resource platform is used by the domain name. Acceleration configurations vary by resource platforms. Please choose the service type that matches your business:
Log in to the CDN console, select Domain Management on the left sidebar, click Manage on the right of a domain name, open the Basic Configuration tab, and then modify the domain name project. To modify the projects of multiple domain names in batches, please tick target domain names on the Domain Management page, click More Actions drop-down list, and select Edit Project. Up to 50 domain names can be operated at a time.
Users on the CDN permission system should proceed with caution, since this operation may cause changes to the permissions of sub-users.
After you obtain your ICP filing, it takes some time to sync the information from the MIIT to Tencent Cloud CDN. Please wait 24 hours and try again.
Origin domain is the website domain name accessed on the origin server during origin-pull on a CDN node. Origin server and origin domain: The IP or domain name configured at the origin server allows a CDN node to find the corresponding origin server during origin-pull. There can be multiple websites on the server, and the origin domain indicates on which website a resource resides.
You can run the
nslookup command to query the DNS resolution of your CDN acceleration domain name. If the resolution result domain name is suffixed with
dnsv1.com (the CNAME record) as shown in the image, it indicates that the CDN acceleration service for your domain name has taken effect.
If files cannot be downloaded from CDN, we recommend troubleshooting by the following methods:
WordPress involves dynamic requests. If the cache configuration is inappropriate, login exceptions may occur. We recommend setting the cache validity of the corresponding dynamic file type to 0, so that files of this type will not be automatically cached. Common dynamic file types include .asp, .jsp, .php, .perl, and .cgi. For detailed directions, please see Node Cache Validity Configuration (Legacy).