A CNAME (Canonical Name) record refers to the alias record in domain name resolution.
For example, a server named host.example.com
provides both WWW and MAIL services. To make it easier for users to access the services, two CNAME records can be added for this server (www.example.com
and mail.example.com
) at its DNS service provider, and all requests to access these two CNAMEs will be forwarded to host.example.com
.
.cdn.dnsv1.com
that is assigned by the system to the connected acceleration domain name configured in CDN Console. You need to configure a CNAME record at your domain name service provider. After the record takes effect, CDN will take care of domain name resolution, and all requests made to this domain name will be forwarded to the edge servers of CDN..cdn.dnsv1.com
that is assigned by the system to the connected acceleration domain name configured in the GCD Console. You need to configure a CNAME record at your domain name service provider. After the record takes effect, GCD will take care of domain name resolution, and all requests made to this domain name will be forwarded to the edge servers of GCD..ecdn.dnsv1.com
that is assigned by the system to the connected acceleration domain name configured in the ECDN Console. You need to configure a CNAME record at your domain name service provider. After the record takes effect, domain name resolution will be taken care of by ECDN, and all requests made to this domain name will be forwarded to ECDN nodes.This refers to when users make multiple requests for the same resource, the returned content varies, such as APIs and .jsp, .asp, .php, .perl, and .cgi files.
In CDN, an access log refers to the detailed log of user access requests to your domain name, including request time, client IP, access domain name, file path, number of bytes, district code, ISP code, HTTP status code, referer, Request-Time, UA, range, HTTP method, protocol identifier, and cache hits/misses.
In CDN, an origin-pull means that when a user sends a request from a browser, the server that responds to the request is the server of the source website rather than a cache server on a CDN node. Generally, if the content is not cached on the cache server or is modified on the origin server, it will be pulled from the origin server.
In CDN, an origin domain refers to a domain name of a website accessed on an origin server by a CDN node during origin-pull. For more information, please see Origin Domain Configuration.
This refers to when users make multiple requests for the same resource, the returned content stays the same, such as html, css and js files, images, videos, software installation packages, APK files, and compressed files.
In CDN, hit rate is the percentage of hit requests out of the total number of requests. When an end user uses the CDN service to access a resource, if the accessed resource has already been cached on a CDN node, it can be directly returned to the end user, which is called a "hit". Otherwise, it needs to be retrieved from the origin server, which is called a "miss".
This refers to the time it takes for data to travel from one end of the network to the other end.
A domain name is a set of server addresses that are easy for users to remember and use, which can be a website, email, FTP, etc. It is used to identify the electronic location (sometimes referred to as a geographic location) of a computer during data transfer.
This is an origin-pull server at the middle-layer between a business server (origin server) and an edge server. It can cache origin-pull requests of multiple edge servers. For requests that have the same content, the intermediate server only needs to perform one origin-pull to deliver the content to each edge server, reducing access pressure on the business server (origin server).
This refers to a server where your own web service is deployed. When connecting to an acceleration domain name, you can enter the server's public IP address as the origin server.
Was this page helpful?