DNS records are the individual rules that tell the internet how to handle your domain. If nameservers are the address book, records are the individual entries in it. This guide explains the records you'll actually encounter.
The records you're most likely to see
| Record | Stands for | What it does |
|---|---|---|
| A | Address | Points your domain to a web server's IPv4 address. The core record for "who hosts this website". |
| AAAA | Address (IPv6) | The same as an A record, but for IPv6 addresses. |
| CNAME | Canonical name | Points one domain to another (e.g. www to the main domain). Often used for subdomains and CDNs. |
| MX | Mail exchanger | Tells other mail servers where to deliver email for your domain. |
| TXT | Text | Free-text fields used for verification and email authentication (SPF, DKIM, DMARC). |
| NS | Nameserver | States which nameservers are authoritative for the domain. |
| SRV | Service | Points at specific services like chat or voice protocols. Rarely needed for standard hosting. |
A record vs CNAME — the important distinction
An A record points a name directly at an IP address. A CNAME points a name at another name, which then has its own A record. Use one A record per hostname for the primary server; use CNAMEs for aliases like www. A domain can have multiple A records (for hosting on the same IP) but not a CNAME and other records on the exact same hostname.
For example, a WebFulHost account uses an A record pointing at the IP address assigned to your account — the address found in your welcome email.
Managing records at WebFulHost
When your domain uses WebFulHost nameservers, you manage its records in the Zone Editor section of cPanel. There you can add, edit or remove A, CNAME, MX and TXT records without touching the domain's nameservers. Find it by logging into cPanel.
Common reasons you'll touch records
- Email delivery: adding SPF and DKIM TXT records is the fix for email going to spam.
- Email hosting elsewhere: repointing MX records to another provider.
- Third-party services: verifying a domain for Google or another provider often needs a TXT record.
Any change spreads over the network exactly like nameserver changes — see DNS Propagation Explained.