DNS (Domain Name System) is the system that translates human-readable domain names like example.com into IP addresses that computers use to communicate. DNS records are the individual instructions within this system that control how your domain behaves.
How DNS Works
When someone types your domain into a browser:
- The browser asks a DNS resolver "Where is example.com?"
- The resolver checks your domain's nameservers
- The nameservers return the appropriate DNS records
- The browser connects to the IP address specified in the record
Common DNS Record Types
A Record (Address)
The most fundamental record. It maps a domain name to an IPv4 address.
| Host | Type | Value | TTL |
|---|---|---|---|
| @ | A | 103.28.xx.xx | 3600 |
| www | A | 103.28.xx.xx | 3600 |
- @ represents the root domain (example.com)
- www is a subdomain (www.example.com)
- Both should typically point to the same IP
AAAA Record (IPv6 Address)
Same as an A record but for IPv6 addresses. Use this if your hosting supports IPv6.
| Host | Type | Value | TTL |
|---|---|---|---|
| @ | AAAA | 2001:db8::1 | 3600 |
CNAME Record (Canonical Name)
Creates an alias that points one domain name to another. Cannot be used on the root domain (@).
| Host | Type | Value | TTL |
|---|---|---|---|
| blog | CNAME | example.com | 3600 |
| shop | CNAME | myshopify.com | 3600 |
MX Record (Mail Exchange)
Directs email to your mail server. Priority determines which server is tried first (lower = higher priority).
| Host | Type | Priority | Value | TTL |
|---|---|---|---|---|
| @ | MX | 0 | mail.example.com | 3600 |
| @ | MX | 10 | backup-mail.example.com | 3600 |
TXT Record (Text)
Stores text-based information. Used for domain verification, email security, and other services.
| Host | Type | Value | TTL |
|---|---|---|---|
| @ | TXT | v=spf1 include:_spf.cynet.com.my ~all | 3600 |
| @ | TXT | google-site-verification=abc123 | 3600 |
- SPF — Specifies which mail servers can send email on your behalf
- DKIM — Adds a digital signature to outgoing emails
- DMARC — Tells receiving servers how to handle failed SPF/DKIM checks
- Domain verification — Google Search Console, Microsoft 365, etc.
NS Record (Nameserver)
Specifies which nameservers are authoritative for your domain. These are usually set at your domain registrar.
| Host | Type | Value |
|---|---|---|
| @ | NS | ns1.cynet.com.my |
| @ | NS | ns2.cynet.com.my |
SRV Record (Service)
Points to a specific service running on a specific port. Used by applications like VoIP, XMPP, and Microsoft Teams.
Managing DNS Records at Cynet
Via cPanel (if using Cynet nameservers)
- Log in to cPanel
- Go to Domains → Zone Editor
- Click Manage next to your domain
- Add, edit, or delete records as needed
Via Client Area (domain management)
- Log in to the Cynet client area
- Go to Domains → My Domains
- Click on your domain → DNS Management
DNS Propagation
After changing DNS records, the changes need to propagate across the internet. This can take:
- TTL-based: Most changes take effect within the TTL period (commonly 1–4 hours)
- Nameserver changes: Can take up to 24–48 hours for full global propagation
- New domains: Usually resolve within 1–2 hours
Best Practices
- Keep TTL reasonable: 3600 seconds (1 hour) is a good default. Lower it before planned changes, then raise it back.
- Don't mix CNAME with other records: A CNAME on a hostname means no other records can exist for that hostname.
- Always set up email security: Configure SPF, DKIM, and DMARC to prevent email spoofing.
- Document your changes: Keep a record of what you changed and why, so you can revert if something breaks.
- Use Cynet nameservers: For the simplest management experience, point your domain to Cynet's nameservers and manage everything from cPanel.