Kamran Mushtaq
Back to Hosting & Deployment
Hosting & Deployment

CNAME (Canonical Name) Record

Added: June 25, 2026

Definition

A CNAME (Canonical Name) Record is a DNS record that makes one domain/subdomain act as an alias of another domain. Instead of pointing directly to an IP address, it points to another hostname. It sits in the flow: Domain → Nameserver → DNS → CNAME Record → Target Domain → A Record → IP Address → Server Its role is to redirect DNS lookups from one name to another, so multiple names can use the same destination.

What Problem It Solves

  • Prevents managing the same IP address in multiple places.
  • If the destination server's IP changes, you only update one DNS record.
  • Makes it easy to connect subdomains to cloud services, CDNs, hosting platforms, and SaaS applications.

What Happens If Not Used

  • You may need separate A Records for every subdomain.
  • IP changes require updating many records.
  • DNS management becomes harder and more error-prone.

Easy Wording

A CNAME Record tells DNS: "This name is just another name for that domain."

Layman Example

Think of "Support Desk" as a sign pointing people to the "Customer Service Office." People follow the sign and end up at the same place without needing a separate office.

Technical Example

DNS Setup

www.example.com → CNAME → app.hostingplatform.com app.hostingplatform.com → A Record → 203.0.113.10

Request Flow

  • User enters www.example.com.
  • DNS finds the CNAME record.
  • DNS follows it to app.hostingplatform.com.
  • DNS finds the A Record of that domain.
  • DNS gets IP 203.0.113.10.
  • Browser connects to the server.
  • Website loads. Result: www.example.com reaches the server without storing the IP directly.