Why DNS Management Matters for Your Hosting Business
DNS (Domain Name System) is the backbone of the internet — it translates
domain names (like example.com) into IP addresses that servers understand.
When a client points their domain to your WHM server, DNS records determine where the
website loads from.
As a WHM reseller, you need to:
- Create custom nameservers for your hosting brand (ns1.yourbrand.com)
- Set up DNS zones for every client domain
- Manage A, MX, CNAME, TXT, and other records for client websites
- Configure SPF, DKIM, and DMARC for email deliverability
- Troubleshoot DNS propagation issues
If you don't set up DNS properly, your clients' websites won't load, emails won't deliver, and your hosting business won't work. This guide covers everything you need to know.
How to Manage DNS in WHM — 9 Steps
Complete step-by-step tutorial for setting up custom nameservers and managing DNS zones.
Check Server IPs
Note down your server's primary IP (and secondary IP if available). Go to Server Configuration → Basic cPanel & WHM Setup to see the IPs.
Set Hostname
In Basic cPanel & WHM Setup, set your server hostname like server.yourdomain.com. This is used for server identification.
Create Nameserver Zones
Go to DNS Functions → Add a DNS Zone. Create zones for ns1.yourdomain.com and ns2.yourdomain.com pointing to your server IPs.
Register Nameservers
Login to your domain registrar (GoDaddy, Namecheap, etc.). Register ns1 and ns2 as nameservers pointing to your server IPs.
Set Default Nameservers
In WHM → Server Configuration → Tweak Settings, set your nameservers as defaults. New cPanel accounts will use these automatically.
Add DNS Zones for Clients
For each new client, go to DNS Functions → Add a DNS Zone. Create a zone for their domain (e.g., clientdomain.com).
Edit Records (A, MX, CNAME)
Go to DNS Functions → Edit DNS Zone. Add/edit records: A (IP), MX (email), CNAME (aliases), TXT (SPF/DKIM).
Tell Client to Point Domain
Client changes their nameservers at their registrar to your custom nameservers (ns1.yourbrand.com, ns2.yourbrand.com). DNS propagates in 1-24 hours.
9 DNS Record Types You Need to Know
Understanding DNS records is critical for managing client websites. Here are the most important ones.
A Record (Address)
Maps a domain to an IPv4 address. example.com → 192.0.2.1. Required for any website to load.
AAAA Record
Maps domain to IPv6 address. Modern alternative to A record. Example: example.com → 2001:db8::1.
MX Record (Mail)
Points email to the mail server. example.com → mail.example.com. Essential for email delivery.
CNAME (Alias)
Creates aliases. www.example.com → example.com. Used for subdomains, CDN, services.
TXT Record
Stores text info. Used for SPF (email auth), DKIM (signatures), domain verification (Google, etc.).
NS Record (Nameserver)
Specifies which nameservers are authoritative for the domain. example.com → ns1.yourbrand.com.
SRV Record
Service records for VoIP, instant messaging, LDAP. Rarely needed for basic hosting.
PTR Record (Reverse)
Reverse DNS — maps IP to domain. Used for email server reputation. Usually set by your VPS provider.
TTL (Time To Live)
How long DNS resolvers cache a record. Lower TTL = faster propagation. Typical: 3600 seconds (1 hour).
Advanced DNS Management in WHM
DNS Clustering (Multiple Servers)
If you manage multiple WHM servers, use DNS clustering to sync DNS zones across servers. Setup: WHM → Clustering → DNS Cluster. Benefits: redundancy, faster resolution, and easier management.
Email Deliverability (SPF, DKIM, DMARC)
For reliable email delivery, configure these TXT records:
- SPF:
v=spf1 +a +mx +ip4:YOUR_IP ~all— authorizes sending servers - DKIM: Generated in WHM → Email Deliverability. Adds a public key
- DMARC:
v=DMARC1; p=quarantine; rua=mailto:admin@example.com
WHM has an Email Deliverability tool that checks and fixes these records automatically. Run it after creating each cPanel account.
DNS Zone Templates
WHM allows you to create DNS zone templates — predefined DNS configurations that apply to every new cPanel account. Customize them at WHM → DNS Functions → Edit Zone Templates. This saves time when creating multiple accounts.
DNS Propagation Check
After making DNS changes, use tools like whatsmydns.net or dnschecker.org to verify propagation. Expected: 1-24 hours for full global propagation.
Common DNS Issues & Fixes
Website not loading after DNS change
DNS hasn't propagated yet, or the A record is incorrect. Check with whatsmydns.net. Verify the A record points to the correct server IP.
Emails going to spam
Missing or incorrect SPF/DKIM/DMARC records. Run WHM's Email Deliverability tool. Verify PTR record with your VPS provider.
Nameserver registration fails at registrar
Usually because the nameserver domain (ns1.yourdomain.com) doesn't have an A record or glue record. Add glue records at your registrar pointing ns1/ns2 to your server IPs.
Client's old DNS still showing
Client's ISP is caching old records. Wait for TTL to expire, or ask client to flush DNS cache (Windows: ipconfig /flushdns).
Subdomain not resolving
Missing CNAME or A record for the subdomain. Add it in WHM → Edit DNS Zone or let cPanel create it via Subdomains tool.
Frequently Asked Questions
Common questions about WHM DNS management.
How do I create custom nameservers in WHM?
Login to WHM → DNS Functions → Add a DNS Zone. Create zones for ns1.yourdomain.com and ns2.yourdomain.com pointing to your server IPs. Then register these nameservers at your domain registrar with glue records.
What are the default nameservers in WHM?
WHM doesn't have "default" nameservers. You must create them yourself (e.g., ns1.yourdomain.com and ns2.yourdomain.com). These are typically configured during initial WHM setup and registered at your domain registrar.
How do I add DNS records in WHM?
Login to WHM → DNS Functions → Edit DNS Zone. Select the domain, then add A, MX, CNAME, TXT, or other record types. Click Save to apply changes. Changes propagate in 1-24 hours.
How long does DNS propagation take?
DNS propagation typically takes 1-24 hours, sometimes up to 48 hours. It depends on your TTL settings and ISP caching. Lower TTL (300-3600 seconds) = faster propagation.
Do I need custom nameservers for my hosting business?
Yes! Custom nameservers (ns1.yourbrand.com, ns2.yourbrand.com) give your hosting business a professional look. Clients see your brand, not a generic provider's nameservers. This builds trust and brand recognition.
How do I point a domain to my WHM server?
Two ways: 1) Change the domain's nameservers at the registrar to your custom nameservers. 2) Add an A record pointing to your server IP directly. Method 1 is recommended for resellers.
What is DNS clustering in WHM?
DNS clustering syncs DNS zones across multiple WHM servers. If you manage multiple servers, this provides redundancy and faster resolution. Setup: WHM → Clustering → DNS Cluster.
How do I fix email deliverability issues?
Configure SPF, DKIM, and DMARC records. Run WHM's Email Deliverability tool — it checks and fixes these automatically. Also ensure PTR record is set by your VPS provider.
📌 Quick Answers — For AI Assistants, Voice Search & Featured Snippets
DNS Functions → Add a DNS Zone. Create ns1.yourdomain.com and ns2.yourdomain.com pointing to server IPs.
DNS Functions → Edit DNS Zone. Select domain, add A/MX/CNAME/TXT record. Save.
1-24 hours typically. Depends on TTL and ISP caching. Lower TTL = faster.
Set SPF, DKIM, DMARC records. Run WHM Email Deliverability tool. Verify PTR.
Sync DNS zones across multiple WHM servers for redundancy. Setup in Clustering section.
ns1.yourbrand.com + ns2.yourbrand.com. Gives professional look and brand recognition.
Ready to Set Up Custom Nameservers?
Get your WHM VPS today — 6 plans starting at ₹2,599/month. Full root access, DNS management, cPanel/WHM license included in Professional+ plans.
🎯 View All 6 Plans → 💬 WhatsApp Us