When the DNS Lookup seems to misbehave, the cause is usually one of two things: something stopped the tool from running, or it ran but the result is not usable. This guide starts with the fastest checks, then walks through the common problems and exact fixes.
Quick Checks First
- Refresh the page - a stalled session is the most common cause of nothing happening.
- Confirm the input is not empty and actually contains what you meant to submit.
- Try the smallest possible input; if that works, the issue is size, not the tool.
- Turn off browser extensions that block scripts, then reload and test again.
- Update or switch browsers if the problem repeats across sessions.
Common Problems and How to Fix Them
The records do not match what I configured.
Authoritative data may still be propagating or an older value is cached, so wait and requery before changing anything again.
The lookup returns no records.
The name may use different record types or none at all, so check the exact host and whether the zone is published.
MX results show an unexpected priority.
Lower numbers route first, so a provider listing its own values will change the order mail is delivered in.
AAAA is empty but A has entries.
The domain simply has no IPv6 address published, which is valid until an AAAA record is added.
TXT records look truncated.
Long values are split into quoted chunks, so read every part together when checking a verification or policy string.
I queried the wrong record type.
Choose the type that answers your question - addresses, mail routing, aliases and text policies are all separate lookups.
When It Works but the Output Is Poor
If the tool runs fine but the result misses, the problem is almost always the brief, not the software:
- Assuming a cached answer shows live records
- Checking only the apex name
- Ignoring record priorities
- Forgetting propagation delay after a change
How to Stop It Happening Next Time
- Keep a saved prompt template for every task you repeat.
- Change one setting per generation so causes stay obvious.
- Run a two-minute sanity test with known input after any update.
- Note every failure and its fix; a short troubleshooting log pays for itself.
Still Stuck?
Reproduce the problem with the smallest possible input and note the exact steps that triggered it. A one-line description of what you did, what you expected and what happened is enough to get a precise answer from support or a colleague.
Frequently Asked Questions
How long do changes take to appear?
Records carry a time to live, so resolvers keep the old value until it expires and propagation finishes shortly after.
Why do I see different results than my provider shows?
You may be querying a cached copy or a different name server, so requery after the record time to live passes.
Which record types can I query?
Address, alias, mail and text records are covered here, including A, AAAA, CNAME, MX and TXT lookups.
Are my queries stored?
No - queries run for your check with nothing retained.
Related Guides
- DNS Lookup - free online tool
- How to Use DNS Lookup
- What Is a DNS Lookup and How Does It Work?
- DNS Lookup Examples: Real Scenarios and Results
- DNS Lookup for Network Admins and Developers
- Best DNS Lookup Alternatives Worth Trying
- DNS Lookup Tips and Best Practices
- Is DNS Lookup Safe? Free vs Paid
- More network tools and guides