4 views
A CNAME record is a type of DNS record that tells the internet that one domain name or subdomain should point to another domain name.
CNAME stands for Canonical Name.
For example, imagine you have:
www.example.com
and you want it to point to:
example.com
You can create a CNAME record that essentially says:
www.example.com → example.com
Instead of directly giving www.example.com an IP address, the CNAME tells DNS to look at another domain name to find the destination.
A simple way to understand it is to think of a CNAME as a nickname or signpost. If someone asks for “www.example.com“, the DNS system can be told, “That’s another name for example.com.”
CNAME records are commonly used for subdomains. For example, you might have:
blog.example.com
pointing to a platform that hosts your blog.
You might also see services instructing you to create something like:
www.example.com → something.provider.com
This allows the external service to manage where the domain ultimately points without requiring you to know or manually update its underlying IP address.
One important distinction is that a CNAME points to another domain name, not directly to an IP address. An A record, on the other hand, points a domain or subdomain directly to an IPv4 address.
For example:
A record
example.com → 192.0.2.10
CNAME record
blog.example.com → example.com
This distinction becomes important when configuring websites, email services, verification systems and third party platforms.
Another important rule is that a traditional CNAME generally should not be placed at the root or apex of a domain, such as:
example.com
It is normally used for subdomains such as:
www.example.com
blog.example.com
shop.example.com
Modern DNS providers may offer special systems such as ALIAS, ANAME or provider specific flattening that provide similar functionality at the root domain.
CNAME records can also be useful when connecting your website to services such as website builders, content delivery networks, verification platforms and other external services. A service may give you a hostname and ask you to create a CNAME pointing your subdomain to that hostname.
For example, a service might tell you:
Name: blog
Type: CNAME
Target: example.provider.com
You would then have:
blog.yourdomain.com → example.provider.com
The exact fields shown in your domain registrar’s DNS panel can vary. Some providers call the first field Name, Host, or Hostname, while the destination may be called Target, Value, or Points to.
One common beginner mistake is entering http:// or https:// in the CNAME target. A CNAME target is normally a hostname, not a complete website URL. So you would generally enter:
example.provider.com
rather than:
https://example.provider.com/page
Another mistake is confusing CNAME records with URL redirects. A CNAME does not mean “send visitors to this web page”. It is a DNS instruction that creates an alias between hostnames. A URL redirect happens at the web server or application level and can send a visitor from one URL to another.
You should also be careful when modifying DNS records because incorrect DNS settings can affect your website, email or other online services connected to your domain.
In simple terms, remember this:
A record = domain name → IP address
CNAME record = domain name → another domain name
Understanding CNAME records is an important step toward understanding how domains, hosting and third party services work together.
If you are building a blog, you may not need to create CNAME records every day. However, sooner or later you may encounter them when connecting your domain to an external platform, configuring a subdomain, verifying ownership of a service or setting up another online tool.
Once you understand what a CNAME does, those instructions become much less intimidating.

Post a reply