CNAME Lookup
Look up CNAME (Canonical Name) records and trace alias chains. See where domain aliases point.
Frequently Asked Questions
What is a CNAME record?
A CNAME (Canonical Name) record creates an alias that points one domain name to another domain name — not directly to an IP address. For example, www.example.com CNAME example.com means www.example.com is an alias for example.com. The resolver then looks up example.com to get the final IP. CNAMEs are useful for pointing subdomains to a hosting provider's domain or a CDN.
Can I use a CNAME at my root domain (example.com)?
No — the DNS specification (RFC 1034) prohibits CNAME records at the zone apex (root domain) because CNAMEs cannot coexist with other record types, and the apex must have NS and SOA records. Many DNS providers offer a workaround called ALIAS, ANAME, or CNAME flattening that mimics CNAME behaviour at the apex by resolving the target and returning its A/AAAA records directly.
Can a CNAME point to another CNAME?
Technically yes, but it is strongly discouraged. A chain of CNAMEs (CNAME chains) requires multiple DNS lookups, adding latency and increasing the chance of resolution failure. The RFC recommends limiting CNAME chains to one level. Additionally, some DNS software has limits on CNAME chain depth. Always point a CNAME directly to the final canonical name.
What is the difference between a CNAME and an A record for subdomains?
An A record points a subdomain directly to an IP address — fast but inflexible (IP changes require updating every A record). A CNAME points a subdomain to another hostname — easier to manage since you only update the target's A record. Use CNAMEs for subdomains pointing to third-party services (e.g. shop.example.com CNAME stores.shopify.com) and A records when you control the IP directly.