DNS records are one of the most important components of website hosting, email delivery, and server administration. Whether you are managing a website in cPanel, configuring business email, or migrating hosting providers, understanding basic DNS records helps avoid downtime, email issues, and configuration errors.
This guide explains the most common DNS records used in web hosting, cPanel, websites, and webmail, including their purpose, technical definition, simple explanation, and examples.
What is DNS?
DNS or Domain Name System acts like the internet’s phonebook. It converts domain names such as:
www.example.com
into server IP addresses such as:
192.0.2.10
Without DNS, browsers and devices would not know where your website or email server is located.

Common DNS records used in web hosting and cPanel
A record

Technical definition
Maps a hostname or domain to an IPv4 address.
Simple explanation
Connects your domain name to your web server.
Common usage
- Website hosting
- VPS hosting
- Dedicated servers
- cPanel hosting
Example
example.com. A 192.0.2.10
AAAA record
Technical definition
Maps a hostname to an IPv6 address.
Simple explanation
Same as an A record, but for newer IPv6 internet addresses.
Common usage
- IPv6-enabled hosting
- Modern server environments
Example
example.com. AAAA 2001:db8::10
CNAME record
Technical definition
Creates an alias from one hostname to another hostname.
Simple explanation
Makes one domain or subdomain point to another domain.
Common usage
- www subdomains
- CDN integrations
- Shopify and SaaS platforms
Example
www CNAME example.com.
MX record
Technical definition
Specifies the mail server responsible for receiving email for a domain.
Simple explanation
Tells the internet where your emails should be delivered.
Common usage
- Business email
- Webmail
- Google Workspace
- Microsoft 365
Example
example.com. MX 10 mail.example.com.
TXT record
Technical definition
Stores text-based information associated with a domain.
Simple explanation
Used for verification and email security settings.
Common usage
- SPF
- DKIM
- DMARC
- Domain verification
Example
example.com. TXT "v=spf1 +a +mx ~all"
NS record
Technical definition
Defines the authoritative nameservers for a domain.
Simple explanation
Tells the internet who manages your DNS.
Common usage
- Cloudflare DNS
- Hosting provider DNS
- Domain delegation
Example
example.com. NS ns1.hostingprovider.com. example.com. NS ns2.hostingprovider.com.
SOA record
Technical definition
Contains administrative information about the DNS zone.
Simple explanation
Acts as the main control record for your DNS settings.
Common usage
- DNS zone management
- DNS synchronization
PTR record
Technical definition
Maps an IP address back to a hostname.
Simple explanation
Performs reverse DNS lookups.
Common usage
- Mail server validation
- Spam prevention
- VPS hosting
- SRV record
Technical definition
Defines the hostname and port for specific internet services.
Simple explanation
Helps applications automatically find the correct service server.
Common usage
- Microsoft services
- SIP and VoIP
- LDAP
CAA record
Technical definition
Specifies which Certificate Authorities can issue SSL certificates for a domain.
Simple explanation
Controls who is allowed to create SSL certificates for your website.
Common usage
- SSL security
- Let’s Encrypt restrictions
Example
example.com. CAA 0 issue "letsencrypt.org"
Common email-related DNS records
SPF record
Technical definition
Defines which servers are authorized to send email for a domain.
Simple explanation
Helps prevent fake emails and spoofing.
Example
example.com. TXT "v=spf1 +a +mx ~all"
DKIM record
Technical definition
Uses cryptographic signatures to verify outgoing email authenticity.
Simple explanation
Adds a digital signature to emails to prove legitimacy.
DMARC record
Technical definition
Defines email validation policies and reporting instructions.
Simple explanation
Tells mail providers what to do with suspicious or fake emails.
Example
_dmarc TXT "v=DMARC1; p=none;"
What is TTL in DNS?
Technical definition
TTL or Time To Live defines how long DNS resolvers cache a DNS record before requesting an updated version.
Simple explanation
TTL tells the internet how long to remember your DNS settings before checking for updates again.
Example TTL
example.com. 3600 IN A 192.0.2.10
Meaning
- 3600 seconds = 1 hour
- DNS systems will cache the record for one hour
Common TTL values
| TTL | Equivalent | Usage |
| 300 | 5 minutes | Testing and migrations |
| 600 | 10 minutes | Faster DNS updates |
| 3600 | 1 hour | Standard DNS setup |
| 14400 | 4 hours | Common cPanel default |
| 86400 | 24 hours | Stable production environment |
Typical cPanel DNS setup example
example.com. A 192.0.2.10 www CNAME example.com. mail A 192.0.2.10 example.com. MX 10 mail.example.com. example.com. TXT "v=spf1 +a +mx ~all"
This setup is commonly used for:
- Website hosting
- Webmail
- SMTP email
- cPanel hosting environments
Using:
- cPanel
- WHM
Final notes
Understanding DNS records is essential for:
- Website management
- Email setup
- Hosting migration
- SSL configuration
- cPanel administration
- Troubleshooting website and mail issues
Incorrect DNS records can cause:
- Website downtime
- Broken email delivery
- SSL problems
- Slow DNS propagation
Before making DNS changes, always verify:
- Correct record type
- Proper hostname
- Accurate server IP
- TTL settings
- Email provider requirements
For professional web hosting, DNS management, website migration, and technical support services, visit: iBuild.PH Web Solutions and Services