CNAME Record Lookup
Check CNAME aliases and verify subdomain configuration from multiple global locations.
About DNS Lookup
Complete DNS lookup tool that queries A, AAAA, MX, TXT, NS, CNAME, and other DNS record types from multiple global DNS servers.
Key Features
Multiple record types (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA)
Multi-region DNS resolution
Propagation checking
TTL information
Reverse DNS lookup
CNAME (Canonical Name) records create aliases that point one domain name to another, making them essential for CDN configurations, SaaS integrations, and subdomain management. Instead of maintaining IP addresses that might change, CNAMEs let you point to a target domain that handles its own IP resolution.
Our multi-region CNAME lookup tool traces the full resolution chain, showing you exactly where your aliases point and verifying consistency across global DNS servers. This is particularly valuable when setting up CDNs, configuring third-party services, or troubleshooting why a subdomain isn't resolving correctly.
When using CNAMEs for CDN or SSL purposes, verify your SSL certificate covers all hostnames including www and apex domains. For CDN setups, also check CAA records to ensure your certificate authority is authorized.
**Methodology:** CNAME chain resolution from 6 regions showing alias targets and final resolved IP addresses.
Common DNS Errors & How to Fix Them
4 relevant issuesThe domain name does not exist in DNS. This means no DNS records of any type were found for this domain.
1) Verify spelling: dig example.com ANY. 2) Check registration: whois example.com (look for "Status: active"). 3) Verify NS at registrar matches your DNS provider. 4) If recently registered, wait 24-48 hours and test with: dig @8.8.8.8 example.com
The CNAME record points to another CNAME, creating a chain that's too long or creates a circular reference. Most resolvers limit CNAME chains to 8-16 hops.
1) Trace the CNAME chain: dig +trace example.com CNAME. 2) Check each hop: dig alias1.example.com CNAME, then dig alias2.example.com CNAME. 3) Ensure chain ends at A/AAAA: the final target must have an A or AAAA record. 4) Simplify by pointing directly to final target or using A record instead.
The domain exists but has no records of the requested type. For example, querying MX records for a domain that only has A records.
1) Confirm record type exists: dig example.com MX +short. 2) Check all records: dig example.com ANY. 3) Query authoritative NS: dig @ns1.yourprovider.com example.com MX. 4) For MX, verify mail is configured in your DNS panel. For AAAA, IPv6 may not be configured (this is often intentional).
The DNS server did not respond within the expected time. This can indicate network issues, overloaded nameservers, or firewall blocking.
1) Test NS connectivity: dig @ns1.example.com example.com +time=10. 2) Check if NS responds: nslookup example.com ns1.yourprovider.com. 3) Verify UDP port 53: nc -vzu ns1.example.com 53. 4) Test from different resolver: dig @1.1.1.1 example.com. If public resolvers work, your NS may be overloaded or blocking.
Frequently Asked Questions
4 relevant questionsA CNAME (Canonical Name) record creates an alias from one domain to another. Instead of an IP address, it points to another domain name. For example, "www.example.com" might CNAME to "example.com" or to a CDN like "example.cloudfront.net". CNAMEs are useful for subdomains and CDN setups, but you cannot use a CNAME at the root domain (apex) alongside other records.
Use A records when pointing directly to an IP address you control. Use CNAME when pointing to another domain, especially third-party services (CDNs, SaaS platforms, load balancers). CNAMEs automatically follow IP changes on the target domain, reducing maintenance. However, CNAMEs add a DNS lookup step, slightly increasing latency. For the root domain, you must use A/AAAA records or provider-specific solutions like ALIAS/ANAME records.
DNS propagation is the time it takes for DNS changes to spread across all DNS servers worldwide. When you update a DNS record, the change must propagate from your authoritative nameserver to DNS resolvers globally. Propagation typically takes 1-24 hours, though it can take up to 48 hours in rare cases. The actual time depends on the TTL (Time To Live) value of your records—lower TTLs mean faster propagation but more DNS queries to your servers.
TTL (Time To Live) tells DNS resolvers how long to cache a record before checking for updates. A TTL of 3600 means resolvers cache the record for 1 hour. For stable records, use higher TTLs (3600-86400 seconds) to reduce DNS queries and improve performance. Before making changes, lower your TTL to 300-600 seconds a day in advance, make your changes, then restore the higher TTL. This minimizes downtime during DNS changes.
Related Tools
View All Tools →Related Tools
Global Infrastructure Verification
Verify SSL certificates, DNS records, and connectivity from 6+ regions worldwide. Get automated monitoring, expiry alerts, and full API access.