DNS Lookup: the question this tool answers

Retrieve the DNS records that control where a domain, website and mail system resolve. The live result starts with A, then uses AAAA and CNAME to confirm or challenge the first interpretation. A healthy result here is intentionally scoped to DNS resolution and delegation; it does not claim that unrelated parts of the domain are healthy.

A
AAAA
CNAME
MX
TXT
NS
SOA
CAA

How to read the A, AAAA and CNAME evidence

Start with the value that directly controls the failing service, then use the other signals to confirm or challenge that interpretation. A single record or response can look correct while another hostname, IP family, redirect or mail-authentication path still fails. The tool therefore keeps the raw observed value visible and explains how the signals relate.

A — An A record publishes an IPv4 destination. Compare it with the hosting target and with AAAA separately so a correct IPv4 route does not hide a conflicting IPv6 route.
AAAA — Compare IPv4 and IPv6 separately. A healthy A record can hide a broken AAAA path that affects only visitors whose network prefers IPv6.
CNAME — A CNAME aliases one hostname to another. Confirm the alias target is the provider-assigned hostname and that no conflicting address record exists at the same owner name.
MX — Read the public MX priorities and targets, then verify that each target itself resolves. A visible MX record is not enough if its mail hostname is broken.
TXT — Verify TXT from the public Internet and compare it with the value the responsible provider says should be live.
NS — Compare the delegated nameservers with the servers that actually answer authoritatively; a record edited in a non-authoritative zone has no effect.
SOA — Verify SOA from the public Internet and compare it with the value the responsible provider says should be live.
CAA — Verify CAA from the public Internet and compare it with the value the responsible provider says should be live.

Common dns lookup failure patterns

The most useful warnings are mismatches rather than isolated missing fields. A can be absent or stale; AAAA can point somewhere different from the expected provider; and CNAME can reveal a second path that behaves differently. If public sources disagree, first decide whether the difference comes from authoritative data, caching, a separate hostname, IPv6, or another protocol layer before editing configuration.

What to change — and what not to change

Change the smallest setting that the evidence proves is wrong. Compare the observed A with the current value supplied by the responsible provider, save the existing value, make one correction, and retest. Do not replace nameservers, delete unrelated MX/TXT records, disable TLS controls or remove IPv6 simply because DNS Lookup shows a warning in another layer. Broad changes can turn one isolated problem into several independent outages.

How HostWithShery runs DNS Lookup

The submitted public input is normalized and validated before any server-side request is made. HostWithShery then obtains A and AAAA using the appropriate public DNS, HTTP, TLS or mail protocol and adds CNAME plus MX where it materially changes the interpretation. URL-based checks are restricted to public destinations, and redirect targets are revalidated instead of being trusted automatically.

How to interpret conflicting dns lookup signals

When A looks correct but AAAA or CNAME disagrees, do not treat the whole domain as broken. Isolate the public path that differs, identify whether it belongs to DNS resolution and delegation, and verify that path against the authoritative provider value before making a change. HostWithShery keeps these signals separate so a healthy value in one layer cannot mask a failure in another.

When a dns lookup result is inconclusive

This is a public-configuration diagnostic. Network filtering, private control-panel settings, split-horizon DNS, provider-internal state and transient routing conditions can limit what can be confirmed from outside the account. Public diagnostics cannot see private control-panel state, unpublished origin addresses, provider account status or split-horizon/internal DNS. If the remote service times out, blocks automated requests or hides a signal, the result stays inconclusive instead of inventing a provider or configuration. That distinction matters when the next step is a potentially disruptive DNS, SSL or mail change.

How to verify the repair

Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire. Repeat DNS Lookup after the change and compare the same A, AAAA and CNAME evidence that exposed the problem. A provider dashboard saying “saved” is not enough when the public Internet still returns the old value.

What to check next if DNS Lookup is healthy

If A, AAAA and CNAME now agree but the user-facing problem remains, move to the adjacent layer instead of editing the same setting repeatedly. Use the related diagnostics on this page to test the next plausible cause, and keep the previous result as evidence when escalating to a hosting, DNS or email provider.

Which DNS record answers which question

A and AAAA publish address endpoints, CNAME aliases one hostname to another, MX controls inbound mail routing, TXT commonly carries verification and mail-authentication policy, NS identifies authoritative servers, SOA describes the zone authority, and CAA can restrict certificate issuance. Read the record that controls the failing service instead of treating the whole DNS response as one health score.

Authoritative DNS versus a cached resolver answer

If a recursive resolver still shows an old address, query the authoritative nameservers before changing the zone again. When authority already publishes the intended value, the remaining difference can be cache lifetime. When authoritative servers disagree with each other, waiting for “propagation” will not repair the source inconsistency.

Technical references

These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.