A CNAME Record Lookup helps you find the Canonical Name (CNAME) record associated with a domain or hostname. A CNAME record points one DNS name to another, making it useful for configuring website subdomains, connecting third-party services, and troubleshooting DNS settings.
Enter a public hostname, such as www.example.com, to check whether it has a CNAME record and identify its configured alias target.
Results reflect the DNS resolver used by this website server. Cached answers and resolver differences may affect what you see.
How to Check a CNAME Record
Once the lookup tool is available, follow these steps:
- Enter a hostname. Type the domain or subdomain you want to check, such as
www.example.com. - Run the lookup. Select the lookup button to request its DNS CNAME information.
- Review the result. If a CNAME exists, the result will identify the hostname it points to.
- Check the configuration. Compare the returned target with the DNS settings required by your hosting provider or connected service.
You can also repeat the lookup after making DNS changes to check whether the expected record is being returned.
What Is a CNAME Record?
A CNAME (Canonical Name) record is a type of Domain Name System (DNS) record that creates an alias from one hostname to another.
Instead of assigning an IP address directly to a hostname, a CNAME record refers to another DNS name. That target name can then be resolved to an IP address through the appropriate DNS records.
For example, consider this illustrative configuration:
| Record Type | Hostname | Points To |
|---|---|---|
| CNAME | www.example.com | website.example.net |
In this example, www.example.com is an alias for website.example.net.
The CNAME record does not contain an IP address. It contains another hostname.
This distinction matters when configuring websites, content delivery networks, and external services.
Understanding CNAME Lookup Results
A CNAME lookup can return several types of information depending on the DNS response and the tool’s implementation.
Hostname
This is the name you entered for the lookup, such as www.example.com.
CNAME Target
The target is the canonical hostname specified in the CNAME record.
For example, if the response shows:
www.example.com → website.example.net
It means the queried hostname is configured as an alias for website.example.net.
TTL (Time to Live)
TTL indicates how long a DNS response may be cached, expressed in seconds.
For example, a TTL of 300 seconds represents five minutes. However, seeing this value does not guarantee that every DNS resolver will update its cached information at exactly the same time.
No CNAME Record Found
If a lookup returns no CNAME record, the hostname may use another DNS record type, such as A or AAAA, or may not have the requested record configured.
A missing CNAME does not automatically mean the website or domain is broken.
DNS Lookup Error
A lookup may fail because of DNS resolution problems, timeouts, an invalid hostname, or a DNS server response indicating that the name does not exist.
The exact error should be examined before changing any DNS settings.
CNAME vs. A vs. AAAA Records
These DNS record types serve different purposes.
| DNS Record | Purpose | Typical Value |
|---|---|---|
| CNAME | Points a hostname to another hostname | website.example.net |
| A | Maps a hostname to an IPv4 address | 192.0.2.10 |
| AAAA | Maps a hostname to an IPv6 address | 2001:db8::10 |
The IP addresses above are documentation examples, not live server addresses.
An A or AAAA record provides an IP address directly. A CNAME record instead refers to another DNS hostname.
Under standard DNS rules, a hostname with a CNAME record cannot have other ordinary DNS record data at the same name. This is one reason DNS configuration errors can occur when administrators try to add conflicting records.
Why Are CNAME Records Used?
Connecting the WWW Subdomain
A common configuration uses a CNAME for www.example.com to point to another hostname associated with the website.
This can make the WWW hostname follow changes to the target’s DNS address records without manually changing the alias itself.
Connecting Third-Party Services
Some website platforms, email-related services, verification systems, and other hosted applications require CNAME records.
The service provider normally supplies the exact hostname and target value to configure.
Always use the values provided by the service rather than guessing the destination.
Content Delivery Networks
Content delivery networks (CDNs) may use CNAME records to connect custom hostnames to their infrastructure.
The required configuration depends on the CDN provider and service.
DNS-Based Domain Verification
Certain services use a unique CNAME record to verify control of a domain or hostname.
In these cases, the record may be used for verification rather than directing website visitors to a server.
Can You Add a CNAME Record to a Root Domain?
A traditional CNAME record should not be configured at the zone apex, often called the root or naked domain.
For example, the zone apex of example.com normally needs records such as SOA and NS. A standard CNAME at that same name would conflict with the DNS rules governing CNAME records.
Some DNS providers offer alternatives called ALIAS, ANAME, or CNAME flattening. These provider-specific features can offer similar convenience without publishing an ordinary CNAME record at the apex.
Check your DNS provider’s documentation before using these alternatives.
How to Fix Common CNAME Problems
1. CNAME Record Not Found
First, confirm that you entered the correct hostname.
A CNAME configured for www.example.com will not necessarily exist for example.com.
Next, open the authoritative DNS management panel and check whether the record has been created and saved.
2. CNAME Points to the Wrong Hostname
Compare the current CNAME target with the exact value supplied by your hosting provider or connected service.
Correct the record in the DNS management panel if it differs.
Avoid changing unrelated DNS records, especially records used for email delivery or domain verification.
3. Old CNAME Target Still Appears
DNS caching may cause a resolver to return an earlier record after a change.
Check the authoritative DNS configuration first, then compare results from other resolvers if necessary.
Allow time for previously cached responses to expire. The delay depends on TTL values and resolver behavior.
4. CNAME Conflicts With Another Record
A standard CNAME record cannot coexist with other ordinary DNS records at the same owner name.
If your DNS provider reports a conflict, inspect the records already configured for that hostname.
Do not delete existing records until you understand their purpose.
5. CNAME Exists but the Website Does Not Work
A correct CNAME does not guarantee that the destination website or application is functioning.
The problem may involve the target hostname, server availability, TLS certificate, hosting configuration, or application settings.
Check the destination service separately before assuming that the CNAME is responsible.
How to Check a CNAME Record Manually
You can check CNAME records without using an online lookup tool.
Windows
Open Command Prompt and enter:
nslookup -type=CNAME www.example.comThe command requests CNAME information for the specified hostname.
Linux and macOS
If the dig utility is installed, enter:
dig www.example.com CNAMEFor a shorter response:
dig +short www.example.com CNAMEThese commands query DNS using the resolver configured for your system unless you explicitly select another DNS server.
Results may differ if a resolver has cached an older record.
Frequently Asked Questions
Is a CNAME record the same as a domain redirect?
No. A CNAME is a DNS alias, not an HTTP redirect.
A browser visiting a hostname with a CNAME does not automatically change its address bar to the CNAME target. Website redirects are handled separately through HTTP responses or other application configuration.
Can a hostname have multiple CNAME records?
A hostname should not have multiple competing CNAME records. A CNAME establishes a canonical alias, and conflicting targets can cause DNS resolution problems.
Does a CNAME record affect website speed?
A CNAME can introduce an additional DNS resolution step, but the actual performance effect depends on DNS caching, resolver behavior, the target configuration, and the hosting infrastructure.
A CNAME record alone does not determine website loading speed or internet connection speed.
Can I use a CNAME for email?
CNAME records are used in some email service configurations, including certain verification and authentication-related setups.
However, MX records used to identify mail exchangers must point to hostnames that resolve appropriately and should not point to CNAME aliases.
Follow your email provider’s official DNS instructions.
Is a CNAME record publicly visible?
Public DNS CNAME records are generally queryable through DNS resolvers. However, visibility depends on the DNS environment, and private or internal DNS configurations may not be accessible through a public lookup service.
Check Your DNS Configuration Carefully
A CNAME lookup is useful when connecting a website to a hosting platform, verifying a third-party service, or investigating a hostname that resolves unexpectedly.
Compare the lookup result with the expected configuration, check the correct hostname, and remember that a DNS alias is only one part of a working website connection.
If the CNAME is correct but your website remains unavailable, investigate the target hostname, hosting service, and web server configuration before changing additional DNS records.