Website
DNS Records Explained for Website Owners
A plain-language guide to A, AAAA, CNAME, MX, and TXT records with a safe change sequence.
On this page
Direct answer: DNS records map names to destinations or service instructions. For a website task, identify the exact hostname and record purpose before changing anything: A and AAAA route to addresses, CNAME aliases one name to another, MX routes mail, and TXT carries verification or policy data.
Common DNS record types
| Type | What it contains | Typical website task |
|---|---|---|
| A | An IPv4 address. | Point a hostname to a server address supplied by the host. |
| AAAA | An IPv6 address. | Provide an IPv6 route when the destination supports it. |
| CNAME | Another hostname, not a URL with a path. | Connect a subdomain to a hosted service. |
| MX | Mail-server hostname and priority. | Route incoming email independently of the web server. |
| TXT | Text supplied for verification or policy. | Verify domain ownership or publish email authentication policy. |
| NS | Authoritative name servers. | Delegate DNS service; changing this can affect the entire zone. |
Read a record as a set of fields
Record type, name, value, TTL, and provider-specific proxy behavior all matter. An A record for the root hostname is not interchangeable with a CNAME for a subdomain. A proxy service can change what is publicly returned while the authoritative DNS record remains different.
Safe change sequence
- Inventory the current zone and identify mail, verification, and application dependencies.
- Confirm the exact hostname and destination with the service owner.
- Export or record the before state and choose a low-risk change window.
- Make one small change, then query authoritative and recursive resolvers.
- Verify HTTPS, redirects, mail, and application health before making a second change.
DNS propagation is a cache behavior, not a reason to make repeated blind edits. If a certificate mismatch or redirect loop appears, use the before record and the service’s documented rollback path. Never include project credentials or private incident details in a public example.
DNS is not an HTTP redirect
A CNAME aliases a hostname during DNS resolution; it does not send a visitor to a different URL in the address bar. HTTPS certificates and HTTP redirects must still work at the destination. Likewise, changing a website’s A record should not require deleting the domain’s mail or verification records.
How to check the result
Use your provider’s lookup view or a DNS lookup utility. For example, these commands query a reserved example domain; replace it with the hostname you are checking:
dig example.com A
dig www.example.com CNAME
dig example.com MXCompare the requested record type and hostname with the intended change. Cached answers can differ until their TTL expires; lowering a TTL later does not erase an answer already cached. If DNS returns the expected destination but the browser shows the wrong site, investigate the web server, certificate and redirect configuration instead of repeatedly changing records.
Before moving a WordPress site, include DNS checks in the pre-launch checklist. For an isolated test copy, keep the staging environment separate from live routing.
Sources & further reading
This guide separates documented platform behavior from interpretation and identifies the source behind material claims.