Skip to content
gohacks.dev
Web

DNS Record Types

A reference of DNS record types with what each one is for and an example: A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA, PTR, HTTPS, SVCB, DNSSEC records and more.

Free · No sign-up · Your inputs stay in your browser

Reference

DNS record types

TypeWhat it isExample and notes
AIPv4 addressexample.com. 300 IN A 203.0.113.10
AAAAIPv6 addressexample.com. 300 IN AAAA 2001:db8::10
CNAMEAlias to another nameMust be the only record at its name, so never at the zone apex.
ALIAS / ANAMEApex alias (provider feature)Not a real record type: the DNS host resolves the target and answers with A/AAAA. Cloudflare calls it CNAME flattening.
MXMail server, with a priority10 mx1.example.net. Lower number is tried first. Must point at a name, never an IP or a CNAME.
TXTFree textSPF, DKIM, DMARC, domain verification. 255 bytes per string, several strings per record.
NSDelegates a zone to name serversMust match at the registrar and in the zone.
SOAStart of authorityPrimary server, admin email, serial and timers. One per zone.
SRVService location_sip._tcp.example.com. SRV 10 60 5060 sip.example.com. (priority weight port target)
CAAWhich CAs may issue certificates0 issue "letsencrypt.org"
PTRReverse DNS: IP to nameSet by whoever owns the IP range (your host), not in your zone. Mail servers need one that matches.
HTTPSHTTPS service binding (RFC 9460)Advertises HTTP/3 (alpn=h3) and ECH keys; also works at the apex like an alias.
SVCBGeneral service bindingThe generic form HTTPS is built on.
DSDelegation signer (DNSSEC)Hash of the child zone's key, published in the parent zone via the registrar.
DNSKEYDNSSEC public key
RRSIGDNSSEC signatureGenerated by signing, never written by hand.
TLSADANE certificate association_25._tcp.mx.example.com. Pins the TLS key for SMTP or HTTPS.
NAPTRNaming authority pointerUsed by SIP and ENUM telephony.
SSHFPSSH host key fingerprintLets ssh verify a host key from DNSSEC-signed DNS (VerifyHostKeyDNS).
SPF (type 99)ObsoleteRFC 7208 removed it. Publish SPF as TXT.

TTL is in seconds and is how long resolvers may cache the answer: lower it a day before a migration, raise it afterwards. dig example.com TYPE +short queries one type; dig @1.1.1.1 asks a public resolver instead of your own.

The newer ones

HTTPS and SVCB records (RFC 9460) let a domain advertise HTTP/3 support and Encrypted Client Hello keys in the DNS answer, and an HTTPS record at the apex can point at another name, something CNAME cannot do there. CAA tells certificate authorities which of them may issue. TLSA publishes a TLS key for DANE.

Querying

dig example.com MX +short asks for one type; dig @1.1.1.1 example.com asks a public resolver rather than your own, which helps when testing a change that your resolver still has cached.

Share

Frequently asked questions

Can a domain's apex be a CNAME?
No. The apex has SOA and NS records, and a CNAME must be alone at its name. Providers offer ALIAS, ANAME or flattening to get the same effect.
How long does a DNS change take?
As long as the old record's TTL, at most, for resolvers that cached it. Lower the TTL a day before a planned change.
Is what I paste sent anywhere?
No. The tool runs entirely in your browser with JavaScript. Nothing you type or paste is sent to our server or stored.

Keep planning

Similar tools