You can connect a domain name in the Content Delivery Network (CDN) console. For more information, see Adding Domain Names.
*.a.example.com. After you connect a wildcard domain name, its subdomain names or second-level wildcard domain names cannot be connected under another account. For example, if you connect the
*.example.com wildcard domain name, the access traffic to the
a.example.com domain name is accelerated based on the settings that are configured for the
*.example.com wildcard domain name, whereas the access traffic to the
example.com domain name is not accelerated.
a.path.example.com, at the same time under an account. In this case, the domain name settings are applied and traffic statistics are calculated based on the priorities of the domain names. A more accurate match between the accessed domain name and a connected domain name indicates a higher priority for the connected domain name. For example, the access traffic to
a.path.example.com is accelerated based on the settings of
a.path.example.com, the access traffic to
b.path.example.com is accelerated based on the settings of
*.path.example.com, and the access traffic to
c.example.com is accelerated based on the settings of
*.example.com. The same analogy applies to traffic statistics.
a.example.com subdomain name of the
*.example.com wildcard domain name is connected under Account A, you must delete the subdomain name under Account A before you can connect the
*.example.com wildcard domain name under Account B.
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.com is already connected to Tencent Cloud, then none of its sub-domain names can be connected to another account.
*.test.com wildcard domain name is connected under the current account, wildcard domain names in a format such as
*.path.test.com can be connected only under the current account.
a.path.test.com is accelerated based on the settings of
a.path.test.com, and the access traffic to
b.path.test.com is accelerated based on the settings of
It’s because your domain name has already been added to the VOD console. If you want to manage the domain name in the CDN console, it must be deleted from the VOD console and wait about 1 minute before adding it to the CDN console, or access other subdomain names.
Most CDN configurations take effect within 5 minutes. Some CDN configurations take effect within 5 to 15 minutes because a large number of tasks need to be run to complete the configurations. Please wait.
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.
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:
CDN nodes cache resources based on the cache validity configuration. If the resources that are cached on a CDN node are not expired, the CDN node does not synchronize the latest resources from the origin server.
After a resource on the origin server is updated, its cache on the CDN node must be updated immediately. You can use the cache purge feature to update unexpired caches on the CDN node, so as to ensure that resources cached on the CDN node and stored on the origin server are consistent.
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.
The origin domain is the website domain name that is accessed on the origin server during origin-pull on a CDN node. The IP or domain name that is configured on the origin server allows a CDN node to find the corresponding origin server during origin-pull. If multiple websites run on the origin server, the origin domain configuration specifies the domain name of the website to which requests are forwarded. If only one website runs on the origin server, you do not need to modify the origin domain, and the acceleration domain name is used as the origin domain by default.
If you use a Tencent Cloud Object Storage (COS) bucket or a bucket of a third-party object storage service as the origin server, you cannot modify the origin domain, and the origin-pull address is used as the origin domain by default.
dig command. In this example, the domain name is
nslookup -qt=cname www.test.com command. Check the CNAME resolution record in the output. If the CNAME resolution record is the same as the CNAME address that is provided by CDN, the CDN acceleration service has taken effect for the domain name.
dig www.test.com command. Check the CNAME resolution record in the output. If the CNAME resolution record is the same as the CNAME address that is provided by CDN, the CDN acceleration service has taken effect for the domain name.
If files cannot be downloaded from CDN, we recommend troubleshooting by the following methods:
When you configure CDN acceleration for WordPress, you must properly configure cache rules for resources that are related to dynamic requests, such as interface-related resources and login-related resources (resources in the /wp-admin backend login address). Otherwise, you may encounter a login failure. We recommend that you do not cache dynamic files.
Tencent Cloud CDN supports port customization when you configure the origin server. If you set the origin-pull protocol to HTTP, port 80 is used for origin-pull by default. If you set the origin-pull protocol to HTTPS, port 443 is used for origin-pull by default. If you configure a custom port, the custom port is used for origin-pull. Make sure that you properly configure the origin-pull protocol and port when you configure the origin server. Otherwise, origin-pull may fail. The following examples list the common configuration errors:
If the origin-pull protocol is valid and the default port is invalid, use a custom port. After you enter the information about the origin server, the system automatically checks whether the origin server supports access from the custom port and returns the check result. If the check fails, troubleshoot issues based on the returned check result.
Yes. CDN already supports domain names suffixed with .pw or .top.
CDN supports domain names that contain underscores (_) and Punycode-converted Chinese characters.
xn--fiq228c.xn--eqrt2g by using a thrid-party tool, and then connect
xn--fiq228c.xn--eqrt2g to CDN.
If you disable the CDN service of a connected domain name, CDN nodes will retain the connection configurations of the domain name, CDN traffic will no longer be generated, and the domain name will be inaccessible.
The error message appears when you use a sub-account to perform operations, such as adding domain names and querying data, and you have not used the root account to attach policies to the sub-account. To resolve the problem, use the root account to go to the Policies page in the CAM console, create CDN-related policies, and attach the policies to the sub-account. After the authorization is complete, you can go to the user list to view the policies that are attached to the sub-account.
To stop acceleration, log in to the CDN console, disable the domain name, and then delete the domain name. For more information, see Domain Name Operations. If you cannot delete the domain name after you disable it, check whether the domain name is in the Disabling state. If not, check whether you are logged in to the CDN console with a sub-account. If yes, use the root account to grant the required permissions to the sub-account.
After a domain name is disabled, resources that have been configured are retained, but the acceleration stops and the 404 error code is returned for incoming user requests. After the domain name is deleted, resources that have been configured are immediately deleted and cannot be recovered.
m.example.com domain names at the same time?
www.example.com, add an implicit or explicit URL at your DNS provider to point the domain names to a website by using the 301 redirect technology. For more information, see Implicit and Explicit URL Records.
We recommend that you enable dynamic and static content acceleration or dynamic content acceleration by using Enterprise Content Delivery Network (ECDN). You can configure the timeout period for the WebSocket connection. The timeout period can be up to 300 seconds. The WebSocket connection may be unstable or even fail when you use the following acceleration types: small webpage file downloads, large file downloads, and audio and video on demand.