After configuring a CNAME record for your domain name, verify that CNAME resolution is working. This ensures traffic is properly routed to CDN points of presence (POPs).
Verification methods
Use a query tool such as nslookup or dig to verify a CNAME record. Do not use the ping command, because the resolution information it returns may be inaccurate.
Windows
Run the following command in Command Prompt (CMD) or PowerShell to query the CNAME record:
nslookup -type=CNAME <accelerated domain name>If the output matches the CNAME value provided by your CDN, the CNAME resolution is successful.

Linux/Mac OS
Use the
digcommand in the terminal to verify the record:(Recommended) Query only the CNAME target address:
dig +short <accelerated domain name> CNAMEIf the output matches the CNAME value provided by your CDN, the CNAME resolution is successful. An example result is shown below:
dig +short cdn.example.com CNAME cdn.example.com.w.alikunlun.com.Query detailed domain name information:
dig <accelerated domain name> CNAMEIf the CNAME value in the
ANSWER SECTIONof the output matches the CNAME value provided by CDN, the CNAME record is working properly.
FAQ
Why does my query returnNXDOMAIN or record not found?
Follow these steps to troubleshoot the issue:
Check the domain spelling: Ensure the domain name in the command is spelled correctly.
Check your DNS configuration: In your DNS provider's console, verify that the CNAME record exists and the host record is correct.
Wait for DNS propagation: DNS record changes take time to propagate globally. Wait a few minutes and try the query again.
The time it takes for a DNS record to propagate globally depends on its Time to Live (TTL). For example, if an old record has a TTL of 10 minutes, the new record will take at least 10 minutes to take effect. Before you modify a CNAME record, we recommend setting the TTL of the original record to a small value, such as 60 seconds, to speed up the change.
Why do I see an A record but no CNAME record?
This issue occurs when a host record has both an A record and a CNAME record, which is an invalid configuration. To resolve this, delete the conflicting A record, leaving only the CNAME record for that host.