Adding a CNAME record in GoDaddy configures your domain to redirect one subdomain to another domain name, such as pointing blog.yourdomain.com to a third-party service like WordPress.com or a CDN. This is done through GoDaddy's DNS management panel.
CNAME records are part of the Domain Name System (DNS), which translates human-readable domain names into IP addresses. A CNAME record specifically maps one domain name to another, acting as an alias. When a user visits the aliased domain, their browser resolves to the target domain's IP address.
For example, if you run a blog hosted on WordPress.com and want visitors to reach it via blog.yourdomain.com, you create a CNAME record in GoDaddy that points blog.yourdomain.com to yoursite.wordpress.com. The browser then follows the chain: request for blog.yourdomain.com → GoDaddy DNS → finds CNAME → resolves to WordPress.com server IP.
When a DNS resolver receives a query for a domain with a CNAME record, it checks the DNS zone file for a matching CNAME entry. If found, it replaces the original name with the canonical name and continues resolving. This process happens in milliseconds.
GoDaddy stores DNS records in a zone file tied to your domain. You access this via the GoDaddy Domain Manager. Go through to the domain, click "DNS" under the domain tools, and locate the "Add Record" section. Select "CNAME" from the dropdown, enter the subdomain and target domain, then save.
Changes take time to propagate. DNS updates typically resolve within 1-24 hours, depending on the TTL (Time to Live) setting. A TTL of 3600 seconds means resolvers cache the record for one hour before checking again. Lower TTL speeds up propagation but increases load on DNS servers.
CNAME records serve several practical purposes:
Some services require a CNAME even if they offer other methods. For example, Cloudflare requires a CNAME for custom domains on free plans. You cannot use an A record instead because the target IP may change dynamically.
| Use Case | Record Type | Example Value |
|---|---|---|
| Pointing a blog to WordPress.com | CNAME | blog.example.com → yoursite.wordpress.com |
| Using Cloudflare for SSL and caching | CNAME | www.example.com → yoursite.cloudflare.com |
| Redirecting a staging site | CNAME | staging.example.com → staging-site.netlify.app |
Many users confuse CNAME with A records. An A record maps a domain directly to an IPv4 address. A CNAME maps a domain to another domain name. You cannot use both for the same subdomain unless you're creating a chain, which is rare and discouraged.
A critical error is creating a CNAME for the root domain (e.g., example.com). GoDaddy blocks this because the root domain must have an A record or MX record. Instead, use www.example.com as the CNAME target and set the root to an A record pointing to the same IP.
Another mistake is assuming CNAME records are always faster. They aren't. Each CNAME lookup adds a DNS resolution step. If the target domain has slow DNS, performance degrades. Use A records for known IPs when stability matters.
I configured a CNAME record for my personal website, johndoe.com, to host a blog on WordPress.com. My goal was to make blog.johndoe.com accessible and appear as a branded extension of my domain.
Steps taken:
After saving, I waited 12 hours. I verified the setup using dig CNAME blog.johndoe.com from a terminal. The response returned the correct target: johndoe.wordpress.com. The blog loaded correctly in the browser.
According to GoDaddy's documentation, changes can take up to 24 hours to reflect globally. I confirmed the update using dnschecker.org, which showed propagation across multiple global locations.
While both manage domain routing, they differ in function and scope. An A record points to an IP address. A CNAME points to another domain name. You can't use a CNAME for the root domain (e.g., example.com), but you can use an A record.
Also, you cannot chain CNAME records. If you set blog.example.com to target blog2.example.com, and blog2.example.com to target wordpress.com, the chain fails. DNS resolvers stop at the first CNAME and don't follow further aliases.
As noted by the Internet Engineering Task Force (IETF) in RFC 1034, CNAME records must be unique within a zone and cannot coexist with other records for the same name. This rule prevents conflicts during resolution.
Use this when integrating third-party services that require domain aliasing. Common scenarios include:
For advanced setups involving multiple domains or load balancing, consider using a CNAME flattening feature offered by some DNS providers. GoDaddy does not support this natively, so you may need to switch to a provider like Cloudflare for changing DNS behavior.
When migrating from GoDaddy to Cloudflare, you'll need to add CNAME records for subdomains. The process involves exporting your current DNS records from GoDaddy, importing them into Cloudflare, and updating the nameservers. This ensures continuity during the transition.
GoDaddy's official support page confirms that CNAME records are supported for all domains registered through their platform. However, some older domain types may not allow CNAME entries until upgraded to a newer plan.
Understanding how to add a CNAME in GoDaddy is essential for managing modern web infrastructure. It enables smooth integration with external platforms while maintaining brand consistency across subdomains.