What should I check when DNS results look wrong?

A DNS answer only makes sense with its record type and resolver in view. Choose the record that matches the question you are trying to answer.

Published and maintained by Utilook

Choose the record type for the question

A returns IPv4 addresses and AAAA returns IPv6 addresses. CNAME aliases one DNS name to another; it is not an IP address. MX names mail exchangers, often with priorities, and NS identifies authoritative nameservers for a zone or delegation.

TXT carries text used for verification, SPF, and other policies. CAA states which certificate authorities may issue certificates for a domain; it is not itself the site's TLS certificate. Utilook DNS Lookup supports exactly A, AAAA, CNAME, MX, TXT, NS, and CAA.

Choose the record type for the question
Your situationWhat to choose or check
Find a web server's IP addressOpen the lookup and select A or AAAA.DNS Lookup
Check where incoming mail is routedSelect MX and read both the priority and server name.DNS Lookup
Check domain verification or SPF textSelect TXT. A successful lookup does not validate the policy's contents.DNS Lookup

Read the number and server name in an MX answer

In the illustration, 10 and 20 are mail-exchanger preferences: the lower number is preferred among MX records for the same owner. The following text is the mail server's name. TTL 300 is measured in seconds, not a deadline for worldwide changes. These are invented explanatory values; a live lookup of example.com need not return them.

Illustrative values — not a live lookup result
MX  10 mail.example.com.    TTL 300
MX  20 backup.example.com.  TTL 300

TTL describes caching, not a global deadline

A record's TTL tells a resolver how long the answer may be cached. It does not promise that a DNS change will be visible worldwide within that time. Different resolvers may have cached an earlier value at different moments; negative answers may be cached too.

Rather than imagining a single worldwide propagation process, compare the queried type and name, then recheck after caches have had time to expire. A single lookup is a view from one resolver at one moment.

Check these in order when an answer is empty or old

A domain can exist without the selected record type. Utilook reports no matching answer as a no-answer error; a name that does not exist is reported separately. Neither by itself proves that the whole website or mail service is down.

Try the record type that matches your question and check the exact hostname. For example, no MX answer for a subdomain does not by itself diagnose the parent domain's mail setup.

  1. Check whether you queried the parent domain or a particular subdomain.
  2. Confirm that the chosen record type matches your question.
  3. After a change, allow for the cache and observation time, then query again. Keep no-answer, name-not-found, and resolver errors distinct.

How this lookup is performed

The browser sends the entered domain and record type to the Utilook backend. The backend asks Cloudflare's DNS-over-HTTPS resolver and returns up to 100 matching records with their TTL values; a request can time out after four seconds. The domain and type are therefore also sent to that external resolver.

This feature does not save the queried domain or answers in its database. Successful runs are counted separately. The result reflects Cloudflare's resolver, not a direct query to every authoritative server.

Reproduced results and failure conditions

Reproduce the difference between an answer and no answer

Purpose
Avoid interpreting every lookup failure as a website outage.
Input
Domain utilook.com / A or MX
Success fixture: Status 0, A 192.0.2.20, TTL 300
Empty fixture: Status 0, Answer []
Conditions
Local service-function response fixtures checked on 2026-11-12. 192.0.2.20 is a documentation address, not Utilook's actual IP. This is not a public DNS measurement.
Observed result
A fixture: 192.0.2.20 / TTL 300
Empty answer: no_answer
Status 3: not_found
Interpretation
An absent name (not_found) differs from no answer of the selected type (no_answer). TTL 300 concerns caching, not a worldwide update deadline.
Limits and failure conditions
The development environment's real DNS-over-HTTPS attempt returned resolver_error, so it did not establish current public DNS answers. Fixtures must not be used to infer production records.
Next action
Check the name and type in DNS Lookup. For a resolver error, check connectivity, retry, then compare the authoritative configuration.

Put it into practice

References

Verification scope and change record

Published and maintained by Utilook · Example checked:

Utilook's tool implementation and the added examples were compared using code, automated browsers and the stated environments. Live network observations and fixtures are identified separately. This date does not represent verification of the entire site, legal compliance or operational logs.

  • This revision adds inputs, conditions, observed results, interpretation, limits and next actions while preserving existing explanations and samples.
Report an error or unclear explanation