16 / 16
| Type | Name | Description | Example |
|---|---|---|---|
| A | Address record | Maps a hostname to an IPv4 address. | example.com → 93.184.216.34 |
| AAAA | IPv6 address | Maps a hostname to an IPv6 address. | example.com → 2606:2800:220:1::1 |
| CNAME | Canonical name | Alias of one name to another. Cannot coexist with other records. | www → example.com |
| MX | Mail exchange | Routes email for the domain. Priority-ordered. | 10 mail.example.com |
| TXT | Text record | Arbitrary text, used for SPF, DKIM, verification. | v=spf1 include:_spf.example.com ~all |
| NS | Name server | Identifies authoritative DNS servers. | ns1.example.com |
| SOA | Start of authority | Authoritative info about the zone. | ns1.example.com hostmaster.example.com |
| PTR | Pointer | Reverse DNS, maps IP to hostname. | 34.216.184.93.in-addr.arpa → example.com |
| SRV | Service locator | Service location (host + port). Used by SIP, XMPP, etc. | _sip._tcp 10 60 5060 sipserver.example.com |
| CAA | Certificate authority | Specifies which CAs can issue certs for the domain. | 0 issue "letsencrypt.org" |
| DNSKEY | DNS key | Public key used in DNSSEC validation. | Key used to sign DNS records |
| DS | Delegation signer | DNSSEC link from parent zone to child. | Hash of DNSKEY in child zone |
| SPF | Sender policy framework | Deprecated, use TXT records with v=spf1 instead. | v=spf1 ip4:192.0.2.0/24 -all |
| DMARC | Email auth policy | TXT record at _dmarc subdomain. | v=DMARC1; p=reject; rua=mailto:r@example.com |
| DKIM | DomainKeys | TXT record at <selector>._domainkey subdomain. | v=DKIM1; k=rsa; p=PUBLIC_KEY |
| ALIAS | Alias (custom) | Like CNAME but works at apex. Vendor-specific (Cloudflare, Route53). | @ ALIAS app.example.com |
How to use
01
Search for a record type
Search by type, like TXT, or by function, like mail. The filter runs across the type, name, and description fields, so you don't need to know the exact record name upfront.
02
Compare against the example
Check your zone file entry against the Example column, which shows realistic values such as 10 mail.example.com for MX, before you save anything at your registrar or DNS host.
03
Copy the type name
Copy the record type with one click when filling in a support ticket, a Terraform resource, or internal documentation, so the name arrives exact every single time.
Why DNS Record Types
- Quick lookup of every common DNS record type.
- Real-world examples for each.
- Includes modern records like CAA, DNSKEY, DMARC, DKIM.
Common questions
What do A and AAAA records actually point to?
An A record maps a hostname to an IPv4 address like 93.184.216.34, while AAAA maps the same kind of name to an IPv6 address. Most production domains publish both so clients on either network stack can reach the server directly.
Why can't I put a CNAME at my domain's apex?
A CNAME can't coexist with other records at the same name, and the apex must also hold SOA and NS records, so the combination is forbidden by the standard. Providers work around this with vendor-specific ALIAS records, which the table lists alongside the official types.
How do MX records decide where email goes?
Each MX entry carries a priority number, and sending servers try the lowest number first, falling back to higher ones if it's unreachable. An entry like 10 mail.example.com means the host mail.example.com receives the domain's mail at priority 10.
What does mx record vs cname mean in practice?
They do unrelated jobs: MX routes a domain's incoming email to specific mail servers, while CNAME aliases one hostname to another for general resolution. The one interaction to remember is that an MX target must be a hostname with an address record, never a CNAME.
Are SPF records still a real DNS type?
The dedicated SPF type exists historically but is deprecated, and the table marks it that way. Modern zones publish the v=spf1 policy string inside an ordinary TXT record at the domain root, which is what every mail receiver actually checks today.
Does this reference include DNSSEC record types?
Yes, DNSKEY and DS are both covered with plain-language descriptions: DNSKEY publishes the public key that signs a zone, and DS lives in the parent zone to create the chain of trust down to the child.
Can a TXT record hold more than SPF values?
Absolutely, TXT is a general-purpose string container, and common txt record uses go well past SPF: DKIM keys at selector._domainkey, DMARC policies at _dmarc, plus the site-verification strings that Google and Microsoft ask you to publish when proving domain ownership.