INBOX BillionVerify

DNS / DNS Checker

How to Check DNS Records When Email Misbehaves

A DNS change did not take effect or mail breaks and you need to see exactly what the domain publishes.

By BillionVerify Team · Updated

Run this check free on billionverify.com: DNS Checker

Most email authentication problems end in DNS. A record is missing, sits on the wrong name, or has not changed yet. This page shows how to check DNS records, which type to ask for in each mail problem, and how to read an empty answer.

Key facts:

  • DNS answers carry a TTL, and resolvers may keep an answer until that time runs out (RFC 1035).
  • A TXT value is made of strings of at most 255 bytes (RFC 1035). SPF and DKIM receivers join them before reading (RFC 7208, RFC 6376).
  • Per the BillionVerify DNS Checker, the type choices are A, AAAA, MX, TXT, NS and CNAME, and one type is queried per lookup.
  • Per the BillionVerify DNS Checker, A and AAAA answers show each address with its TTL, and MX answers show priority and host.
  • Per the BillionVerify DNS Checker, each IP address can run 10 lookups a minute and 50 an hour.

How to check DNS records step by step

  1. Enter the domain, such as example.com. Use a plain domain name with no scheme, path or email address.
  2. Pick the record type from the list.
  3. Run the lookup and read each line of the answer.

Because only one type is asked per run, a full mail review takes several lookups. Plan them before you start so you stay inside the per-minute allowance.

Which record type answers which mail question

TXT, for SPF and verification values

Ask for TXT on the root domain to see the SPF record. The tool shows every TXT value, so you can spot two v=spf1 entries, which the SPF checker does not warn about. For the DKIM and DMARC names, use their own checkers, because this tool’s domain field does not accept names that contain an underscore.

MX, for where mail is delivered

The answer lists priority and host. Read it the same way as an MX lookup, with the lowest number first.

A and AAAA, for the mail host itself

Each MX host needs an address behind it. Look up the host name from the MX answer as an A or AAAA query. No address means the server cannot be reached.

NS, for who controls DNS

Check NS before you edit anything. If the nameservers point to a different provider than you expected, your edits go to the wrong place.

CNAME, for aliases

Use it to confirm that a name you pointed at a service really is an alias. An empty CNAME answer is normal for a name that holds its own records.

How to read an empty or stale answer

“No records found” means the name exists but has nothing of that type, or the name does not exist. The tool treats both the same way.

A stale answer is different. The tool asks a resolver, so a record you changed a moment ago can still show its old value until the TTL runs out. Compare the TTL against how long ago you saved the change before you decide the edit failed.

A “DNS lookup failed” message means the query itself failed. Run it again.

What to check next

DNS being correct does not make every address deliverable. A perfect record set still bounces mail to inboxes that do not exist. When DNS is clean and bounces continue, send questionable addresses through BillionVerify’s risk checker. It gives 20 free full checks per IP every 24 hours, no sign-up.

Then read the records one by one with the SPF, DKIM and DMARC checkers. If a single recipient is the problem, check that an address is valid before you touch DNS again.

Next checks