Select location & language
  • Österreich German
  • Australia English
  • België Dutch
  • Canada English
  • Schweiz German
  • Deutschland German
  • Eesti English
  • Ελλάδα English
  • España Spanish
  • France French
  • Hrvatska English
  • Italia English
  • Latvija English
  • Lietuva English
  • Nederland Dutch
  • Norge Norwegian
  • Polska Polish
  • Portugal Portuguese
  • Slovensko English
  • Suomi Finnish
  • Sverige Swedish
  • United Kingdom English
  • United States English
  • American Samoa English
  • Andorra English
  • Anguilla English
  • Antarctica English
  • Bermuda English
  • British Indian Ocean Territory English
  • British Virgin Islands English
  • Cayman Islands English
  • Christmas Island English
  • Città del Vaticano English
  • Cocos (Keeling) Islands English
  • Falkland Islands English
  • French Southern Territories English
  • Gibraltar English
  • Guadeloupe French
  • Guam English
  • Guernsey English
  • Guyane française French
  • Heard & McDonald Islands English
  • Ireland English
  • Isle of Man English
  • Jersey English
  • Liechtenstein German
  • Luxembourg French
  • Malta English
  • Martinique French
  • Mayotte English
  • Monaco French
  • Montserrat English
  • New Zealand English
  • Norfolk Island English
  • Northern Mariana Islands English
  • Pitcairn Islands English
  • Puerto Rico Spanish
  • Réunion English
  • San Marino English
  • Slovenija English
  • St. Barthélemy English
  • St. Helena English
  • St. Martin English
  • St. Pierre & Miquelon English
  • Svalbard & Jan Mayen English
  • Turks & Caicos Islands English
  • U.S. Outlying Islands English
  • U.S. Virgin Islands English
  • Åland Islands English
  • Κύπρος English
  • Црна Гора English

What Is a CNAME Record and When Should You Use One?

1 min read

A CNAME record (Canonical Name record) is a type of DNS entry that points one domain name to another domain name, rather than to an IP address. Think of it as an alias: instead of saying “this name lives at this IP”, a CNAME says “this name is really just another name for that one”. CNAME records are extremely common when connecting third-party services to your domain.

How a CNAME differs from an A record #

The key difference is what each record points to. An A record maps a name directly to a numeric IP address, while a CNAME maps a name to another hostname, which is then resolved to an IP. This matters because if the target’s IP ever changes, a CNAME keeps working automatically, whereas an A record would need updating. In short:

  • A record: name to IP address (for example, yourdomain.com to 192.0.2.10).
  • CNAME: name to another name (for example, www.yourdomain.com to yourdomain.com).

Common uses for CNAME records #

  • The www version: pointing www.yourdomain.com to your root domain.
  • Third-party tools: connecting services like email marketing platforms, help desks, or website builders that ask you to add a CNAME.
  • Verification: some providers use a CNAME to confirm you own the domain.
  • Subdomains for external services: pointing shop.yourdomain.com to a hosted store platform.

How to add a CNAME record #

  • Log in to your DNS manager or control panel.
  • Open the DNS or Zone Editor section.
  • Create a new CNAME record.
  • Enter the subdomain name in the host field (for example, www or shop).
  • Enter the target hostname in the value field, exactly as the service provided.
  • Save and allow time for propagation.

Important rules to remember #

There are a couple of limits worth knowing. A CNAME cannot be used on the root domain (the bare “yourdomain.com”) in standard DNS, so the root normally uses an A record while “www” uses a CNAME. Also, a hostname that has a CNAME should not have other records of the same name, as this causes conflicts.

Troubleshooting #

  • Service not verifying: confirm the target value matches exactly, with no trailing typos.
  • Conflict errors: remove any duplicate records for the same host.
  • Not resolving yet: allow time for propagation and re-check with a DNS lookup.

Need help? #

If a third-party service is asking for a CNAME and you are unsure where to put it, our support team can add it correctly for you over live chat.

What are your feelings