Introduction
A CNAME record (Canonical Name record) is used in DNS to alias one domain or subdomain to another. It’s invaluable when you want one host to point at another domain or subdomain without managing direct IP addresses. With Tublat hosting, you can easily add a CNAME record through cPanel’s DNS management tools. This guide outlines how to do that step by step, best practices, and how to avoid common mistakes.
What Is a CNAME Record & When to Use It
-
A CNAME record points one hostname (alias) to another canonical hostname.
-
It’s useful when you want
www.example.comto aliasexample.com, or when using third-party services likeshop.example.compointing to a hosted shop atservice.provider.com. -
It allows you to change the target host in one place, without updating multiple DNS records.
-
But note: you cannot have a CNAME record coexisting with other record types (A, MX, TXT, etc.) for the same name.
Prerequisites
Before adding a CNAME record, make sure:
-
You have DNS control for the domain in cPanel (Zone Editor / DNS Editor).
-
You know the alias (host) you wish to create (e.g.
www,blog). -
You know the target canonical hostname (e.g.
example.com,service.provider.com). -
There is no conflicting record (A, MX, or CNAME) already present for that exact name.
Step-by-Step: Adding a CNAME Record in cPanel
-
Log in to your Tublat cPanel
Enter viayourdomain.com/cpanelor through your Tublat hosting dashboard. -
Navigate to Zone Editor / DNS management
In cPanel, locate Zone Editor, DNS Zone Editor, or DNS Essentials under the Domains or DNS section. -
Choose the domain to edit
Click Manage next to the domain for which you want to add a CNAME record. -
Add a new record / CNAME record
Click Add Record (or “+ Add”), and select CNAME Record from the record type menu. -
Fill in the CNAME record fields
-
Name / Host: Enter the alias — for example,
wwworblog. -
TTL: Time To Live (in seconds) — default is usually fine (e.g. 3600).
-
Type: Choose CNAME.
-
Target / Canonical name: Enter the full hostname you want the alias to point to (e.g.
example.comorservice.provider.com). -
Do not point it to an IP — CNAME values must be hostnames, not numeric addresses.
-
-
Save / Add the record
Click Save, Add Record, or equivalent to commit the CNAME entry. -
Verify and wait for propagation
-
After saving, the CNAME record should appear in the DNS list.
-
Use
digornslookupor online DNS tools to check that the alias resolves to the target hostname. -
DNS propagation may take minutes to a few hours.
-
Best Practices & Tips
-
Avoid placing a CNAME at the root (apex) of your domain (i.e.
example.com) because that can conflict with other essential records (A, MX). Use@only if your DNS provider supports ALIAS or ANAME records. -
Use www or other subdomains for CNAMEs.
-
Keep TTL moderate — too high slows future changes, too low can increase lookups.
-
Make sure your target hostname has the correct DNS records (A, MX, etc.).
-
Remove or disable conflicting records (A, MX) for the same alias before adding a CNAME.
-
After adding, test the alias in your browser or via command line (e.g.
ping alias.example.com) to confirm resolution.
Common Issues & Troubleshooting
-
Conflict error: You already have an A, MX, TXT, or other record with the same name. Remove or adjust the conflicting record first.
-
CNAME not resolving: DNS propagation delay or TTL cache. Wait and recheck.
-
Target hostname mis-spelled: Typos in the alias or target will break resolution.
-
CNAME at root domain: Most DNS systems disallow CNAME at the apex; you may need alternate record types.
-
Propagation delay: Even after correct setup, DNS caches may make it appear not to work immediately.
-
Circular aliasing: Don’t point a CNAME to itself or to a chain that loops — that causes DNS errors.
Why This Matters for Tublat Users
For Tublat customers, managing DNS via cPanel makes it easy to create domain aliases and integrate third-party services. Correctly setting CNAME records allows you to point subdomains to web apps, services, or other domains without needing to manage IP addresses. This adds flexibility, simplifies future changes, and reduces risk of misconfiguration. Having a clear, easily updatable alias setup helps maintain smooth site operations and eases domain management.