A reference for DNS record types with the rules that cause outages, plus a checker for zone file lines — all offline, with no lookup performed.
13 record types
Each one with its format and the thing people get wrong.
This is a reference. It cannot tell you what is published for a domain — that needs a lookup, which `dig` does.
AAddressMaps a name to an IPv4 address.
A single IPv4 address.
www IN A 192.0.2.1Several A records for one name give round-robin DNS, which is load distribution and not failover — a client that gets a dead address will still try it.
AAAAIPv6 addressMaps a name to an IPv6 address.
A single IPv6 address.
www IN AAAA 2001:db8::1Named for being four times the size of an A record. Publishing one for a host that is not actually reachable over IPv6 causes slow connections, because clients try IPv6 first and wait for it to fail.
CNAMECanonical nameMakes this name an alias for another name.
A fully qualified domain name.
blog IN CNAME hosting.example.net.A CNAME cannot coexist with any other record for the same name, which is why you cannot put one at a zone apex — the apex must have SOA and NS records. Providers work around it with ALIAS or ANAME records, which are not standard.
MXMail exchangeWhere mail for this domain should be delivered.
A priority number and a hostname.
example.com. IN MX 10 mail.example.com.Lower priority wins. The target must be a hostname with an A or AAAA record — pointing an MX at a CNAME or at an IP address is invalid and some mail servers refuse it.
TXTTextArbitrary text. In practice: SPF, DKIM, DMARC and domain-ownership proofs.
One or more quoted strings, each at most 255 characters.
example.com. IN TXT "v=spf1 include:_spf.example.net ~all"A single string is capped at 255 characters, so a long DKIM key must be split into several quoted strings which the resolver concatenates. Splitting it wrongly — or adding a space between the pieces — breaks the key silently.
NSName serverWhich servers are authoritative for this zone.
A hostname.
example.com. IN NS ns1.example.net.The NS records at your registrar and the ones in your zone must agree. When they do not, resolution works from some resolvers and not others, which is a confusing failure to diagnose.
SOAStart of authorityAdministrative information about the zone: the primary server, the contact, and the timers.
Primary NS, contact email (with @ written as a dot), serial, refresh, retry, expire, minimum TTL.
example.com. IN SOA ns1.example.net. admin.example.com. 2026110601 7200 3600 1209600 3600The contact's `@` is written as a dot, so `admin@example.com` becomes `admin.example.com.`. The final field is the negative caching TTL — how long a NXDOMAIN answer is remembered, which is why a newly created record can appear missing for a while.
PTRPointerReverse lookup: maps an address back to a name.
A hostname, under in-addr.arpa or ip6.arpa.
1.2.0.192.in-addr.arpa. IN PTR www.example.com.The address is reversed in the name. Set by whoever controls the IP block — normally your hosting provider — not by you. Mail servers check it, so a missing PTR hurts deliverability.
SRVServiceWhere a particular service lives, including its port.
Priority, weight, port, target hostname. The name is `_service._protocol.domain`.
_sip._tcp.example.com. IN SRV 10 60 5060 sip.example.com.The underscores in the name are required. Weight distributes load between targets of equal priority, so 60 and 40 is a 60/40 split rather than an ordering.
CAACertification authority authorizationWhich certificate authorities may issue certificates for this domain.
A flag, a tag (`issue`, `issuewild` or `iodef`) and a value.
example.com. IN CAA 0 issue "letsencrypt.org"Authorities are required to check this before issuing. Adding one and forgetting an authority you use means renewals start failing weeks later, when the certificate comes up for renewal rather than when you made the change.
ALIAS / ANAMEApex alias (non-standard)A CNAME-like alias that works at a zone apex, resolved by the DNS provider rather than the client.
A hostname. Provider-specific.
example.com. IN ALIAS target.cdn.example.net.Not in any RFC. Each provider implements it differently, and the provider resolves the target and answers with its address — which means the answer is from the provider's point of view on the network, not the client's. That can defeat geographic load balancing.
DNSKEY / DS / RRSIGDNSSEC recordsThe public key, the delegation signer at the parent, and the signatures over each record set.
Binary key and signature material, base64-encoded.
example.com. IN DS 12345 13 2 49FD46E6C4B45C55D4AC…The DS record lives at the parent zone, usually at your registrar, and must match your DNSKEY. A mismatch makes the whole zone fail to resolve for validating resolvers — one of the few DNS mistakes that takes a domain down completely.
HTTPS / SVCBService bindingConnection parameters for a service — ALPN, port, IP hints — in one record.
Priority, target name, and key=value parameters.
example.com. IN HTTPS 1 . alpn="h3,h2" ipv4hint=192.0.2.1Lets a client learn that HTTP/3 is available without first connecting over HTTP/2. Also provides an apex alias when the target is `.`, which is the standards-track answer to the CNAME-at-apex problem.
DNS Record Reference runs entirely on your device — nothing is uploaded, and no DNS lookup is performed.
You’re on the Free plan. Compare plans
DNS has a small number of rules that cause a disproportionate share of outages, and they are all about what you cannot do rather than what you can.
A CNAME cannot coexist with any other record for the same name. That is why you cannot put a CNAME at the zone apex — the apex must have SOA and NS records, so the CNAME is forbidden. Providers offer ALIAS or ANAME records to work around it, and those are proprietary rather than standard, which matters when you move provider.
Only one SPF record may exist per domain. A second one is not additive — it makes the whole evaluation fail with a permanent error, so adding a provider's SPF line beside your existing one breaks mail for everyone rather than for the new sender. Several senders go in one record, within a limit of ten DNS lookups that is easy to exceed.
TTL is a commitment you make in advance. Lowering it before a migration only helps if you do it longer than the old TTL ahead of the change, because resolvers are still holding the previous value. Deciding to lower it on the day is deciding too late.
MX priority is lowest-wins, which reads backwards to most people, and the zone-file checker flags the syntax errors that stop a zone loading at all: a missing trailing dot that turns an absolute name into a relative one, an unquoted TXT value with spaces, a bare `@`.
No DNS query is made. This reads the text you paste and explains the format; what your domain actually resolves to needs a real lookup with `dig` or your provider's console.
Because a CNAME cannot coexist with other records, and the apex must carry SOA and NS. ALIAS and ANAME records solve it at the provider level — they are proprietary, so the behaviour follows the provider rather than the standard.
No. A second one makes evaluation fail permanently rather than combining. Put every sender in one record, and watch the ten-lookup limit that `include:` statements consume quickly.
No. Resolvers hold the old value for its full duration, so lowering the TTL has to happen longer than the old TTL before the change you are preparing for.
The lowest number. MX 10 is tried before MX 20, which reads backwards to most people and is why backup mail servers end up as the primary.
No. No DNS query is made. It explains the formats and checks the text you paste; what your domain actually resolves to needs `dig` or your provider's console.