DNS Lookup Troubleshooting: Find Domain Problems Faster

DNS problems often look like website problems. A site will not load, email stops arriving, a new domain works for one person but not another, or a CDN says the record is missing. The application may be fine. The problem may be the name system that tells browsers where to go.

A DNS Lookup tool helps you inspect the records behind a domain and understand what the internet is being told.

DNS can feel mysterious because changes are distributed and cached. Troubleshooting becomes easier when you check one record type at a time.

What DNS Does#

DNS maps human-readable names to technical destinations.

For example:

• A records point a domain to an IPv4 address.
• AAAA records point to an IPv6 address.
• CNAME records point one name to another name.
• MX records tell mail servers where email should go.
• TXT records store verification, SPF, DKIM, DMARC, and other text data.
• NS records identify authoritative nameservers.

When one of these records is wrong, traffic goes to the wrong place or nowhere at all.

Start With Nameservers#

If DNS behaves strangely, check nameservers first. The nameservers are the authority for your domain's records.

Common nameserver problems:

• Domain registrar points to old nameservers.
• DNS records were edited at the wrong provider.
• Nameserver change has not propagated.
• One authoritative nameserver has different data than another.

If you update records in Cloudflare but the domain still uses registrar nameservers, the update will not matter. You changed the wrong source.

Website Not Loading#

For a broken website, check:

• A record.
• AAAA record.
• CNAME record for www.
• Whether root and www point to expected destinations.
• Whether the hosting provider expects a specific CNAME.
• Whether there are conflicting records.

Root domains usually use A, AAAA, or special flattening behavior. Subdomains often use CNAME.

If example.com works but www.example.com fails, the www record is likely missing or wrong.

Email Not Working#

For email issues, check:

• MX records.
• SPF in TXT records.
• DKIM records.
• DMARC records.
• Whether old mail provider records remain.
• Record priority values.

Email providers usually give exact DNS records. Copy them carefully. A missing quote, wrong host name, or extra domain suffix can break verification.

SPF mistakes are common. A domain should generally avoid multiple separate SPF TXT records. Combine rules into one valid SPF record.

Propagation Delays#

DNS changes do not appear everywhere instantly because resolvers cache answers based on TTL values.

If you changed a record and some users still see the old destination:

• Check the TTL.
• Query multiple resolvers.
• Check authoritative nameservers.
• Wait for old cache entries to expire.
• Confirm you changed the right DNS provider.

Propagation is not magic. It is mostly caching plus distributed resolvers.

Use a DNS Propagation Checker when you need to see how records appear from different locations.

CNAME Mistakes#

CNAME records are useful but have rules.

Common mistakes:

• Adding a CNAME at the root when the DNS provider does not support flattening.
• Creating a CNAME that conflicts with another record.
• Pointing a CNAME to a URL instead of a hostname.
• Including https:// in the value.
• Creating loops.

A CNAME value should be a hostname, not a full URL.

Bad:

https://example.hosting.com/app

Better:

example.hosting.com

TXT Verification Problems#

Many services verify domain ownership with TXT records. Verification fails when:

• The host/name field is wrong.
• The value has extra spaces.
• Quotes are handled incorrectly.
• The record was added at the wrong provider.
• The service expects the record on a subdomain.
• There is a delay before the service rechecks.

Always copy both the name and value exactly as shown by the service.

A DNS Troubleshooting Workflow#

1. Confirm the domain and subdomain.
2. Check authoritative nameservers.
3. Query the specific record type.
4. Compare against provider instructions.
5. Check for conflicting records.
6. Query multiple resolvers if propagation is suspected.
7. Wait for TTL if old records are cached.
8. Document the final correct records.

This beats randomly editing records and hoping.

Common DNS Mistakes#

Editing the wrong DNS zone. Very common after moving providers.

Confusing host and value. DNS forms differ by provider.

Leaving stale records. Old records can conflict with new services.

Using URLs where hostnames are expected. DNS does not point to paths.

Changing too many records at once. Make one change, verify, then continue.

The Bottom Line#

DNS troubleshooting is a process of checking authority, record type, expected value, and cache state.

Use lookup tools to inspect what is actually published. Verify nameservers before editing. Treat propagation as cache behavior, not mystery. Most DNS issues become straightforward when you slow down and check the exact record the failing service depends on.