Nameservers vs CNAME Records: Where to Edit DNS

Domain owners frequently run into confusion when setting up third-party web services or host platforms because their domain registration and active DNS management live in different places. If your registrar points to custom nameservers, adding a CNAME record at your domain registrar will do nothing until you add that record at the provider authoritative for your nameservers.

Quick fix

1. Find out which provider currently owns your authoritative nameservers (for example, hosting provider nameservers vs. registrar default nameservers).
2. Log in to the dashboard of the provider matching those nameservers, not necessarily the registrar where you bought the domain name.
3. Locate the DNS Zone Editor or DNS Management menu inside that hosting account.
4. Create the requested CNAME records (for example, setting the host www to point to web2.sourceaudio.com).
5. If you want the registrar to handle your DNS records instead, change your nameservers back to the registrar's default nameservers inside your registrar account.

Why this happens

• Nameservers (NS records) delegate authority: Nameservers tell the global internet which server holds the master copy of your domain's DNS records. Whichever provider's nameservers are listed is the only place where DNS changes take effect.
• CNAME records redirect specific subdomains: A Canonical Name (CNAME) record maps one specific hostname (like www.example.com or secure.example.com) to an external target domain name (like web2.sourceaudio.com).
• Editing the wrong DNS control panel: If your domain is registered at GoDaddy but its nameservers point to HostMonster, GoDaddy's DNS zone file is completely inactive. Adding CNAME records inside GoDaddy will have zero effect until you either add them inside HostMonster or point your nameservers back to GoDaddy.

How to fix it

Step 1: Check your authoritative nameservers

You must determine where your domain's DNS records are currently managed. Open your terminal or command prompt and run a quick dig or nslookup query against your domain:

dig example.com NS +short

On Windows Command Prompt, run:

nslookup -type=NS example.com

If the command returns nameservers like NS1.HOSTMONSTER.COM and NS2.HOSTMONSTER.COM, HostMonster is the DNS host. If it returns GoDaddy nameservers (like domaincontrol.com), GoDaddy is your DNS host.

Step 2: Add CNAME records at your active DNS host

If your domain's nameservers point to your web host (e.g., HostMonster or cPanel hosting), log in to that hosting account's dashboard to add the CNAME record.

1. Log in to your hosting account control panel.
2. Open the Zone Editor or DNS Management area.
3. Select your domain name.
4. Add the first CNAME record:
   • Type: CNAME
   • Name / Host: www (or www.example.com depending on panel interface)
   • Record / Target / Points to: web2.sourceaudio.com
   • TTL: Default (14400 or 3600)
5. Add the second CNAME record:
   • Type: CNAME
   • Name / Host: secure
   • Record / Target / Points to: web2.sourceaudio.com
6. Save the zone file.

Step 3: Alternative option — Switch nameservers back to your registrar

If you do not have active hosting or access to the host where your nameservers are currently pointing, you can switch management back to your domain registrar (such as GoDaddy).

Note: Changing nameservers will break any existing site or email services currently connected through the old hosting provider. Always verify what services are active before changing nameservers.

1. Log in to your domain registrar dashboard.
2. Go to Domain Settings > DNS / Nameservers.
3. Select Change Nameservers and choose Use Default Nameservers.
4. Save your changes. Once propagated, the registrar's internal DNS control panel becomes active, allowing you to add your CNAME records directly there.

Check that it worked

DNS propagation usually takes a few minutes to a few hours depending on your TTL values. You can verify your CNAME record using dig or nslookup:

dig www.example.com CNAME +short

Expected output:

web2.sourceaudio.com.

On Windows:

nslookup -type=CNAME www.example.com

You can also test resolution in your web browser by navigating directly to http://www.example.com or http://secure.example.com to verify that the target service responds.

Prevent it next time

• Keep a central record of where your domain name is registered and which provider hosts its active DNS zone file.
• When connecting third-party platforms (like music hosting, store builders, or landing pages), add records inside your active DNS host rather than changing nameservers unless instructed to delegate the whole domain.
• Lower TTL (Time-To-Live) values to 300 seconds prior to making major DNS or nameserver updates to ensure rapid propagation.

FAQ

Can I add a CNAME record directly to the apex/root domain?

According to standard DNS specifications, a CNAME record cannot coexist with other record types on the exact root/apex domain (e.g., example.com without www), because root domains require SOA and NS records. Most setups use an A record, ALIAS record, or CNAME flattening at the root domain while using standard CNAME records for subdomains like www.

How long does a nameserver change take compared to a CNAME change?

Nameserver updates often take up to 24 to 48 hours to fully propagate globally across all Internet Service Providers, though many resolvers update within 2–4 hours. Individual DNS record changes like CNAMEs propagate much faster, usually within minutes to a few hours depending on the TTL specified on the original record.

What is the difference between an A record and a CNAME record?

An A record maps a hostname directly to an IPv4 address (such as 203.0.113.10). A CNAME record maps an alias hostname to another domain name (such as web2.sourceaudio.com), which then resolves to its target IP address through a secondary DNS lookup.

Simplifying Domain Management with Dhruva Cloud

Managing custom DNS setups across separate registrars and web hosts can quickly get confusing. When you host your site on Dhruva Cloud, you can bring your own domain from any registrar (such as GoDaddy or Namecheap). Simply update your domain's nameservers to point to Dhruva Cloud at your registrar once; Dhruva Cloud automatically sets up your Cloudflare DNS zone, routing, and DDoS protection for you in minutes, complete with automatic free SSL certificates on every site and subdomain.