HHostWithSheryWebsite & Domain Troubleshooting ToolsCheck a domain
Menu
Troubleshooting areaReviewed 2026-08-13By HostWithShery technical editorial

DNS Tools

Inspect resolution, nameservers, propagation, DNSSEC, CAA, reverse DNS and IPv6 behavior.

Start with evidence from your own domain before changing DNS, SSL or mail settings.
Check your own configuration

DNS Lookup

This page is preconfigured with the DNS Lookup that best matches this problem.

No accountPublic evidence only
Live public check

Returns public A, AAAA, CNAME, MX, TXT, NS, SOA and CAA data.

No account · Public configuration only
On this page
Browse this section

Choose the focused diagnostic

Every important page in this area is linked here with a normal crawlable link, so you can choose by task instead of searching through a long generic list.

DNS diagnostics

DNS LookupRetrieve the DNS records that control where a domain, website and mail system resolve.Open →DNS Propagation CheckerCompare DNS answers from genuine regional probes and label each result with the location that performed the query.Open →Nameserver CheckerInspect delegation and authoritative nameservers, then compare whether the servers return consistent public DNS data.Open →DNSSEC CheckerCheck whether DNSSEC is published and whether the delegation exposes the expected security records.Open →CAA CheckerRetrieve CAA records that restrict which certificate authorities may issue certificates for a domain.Open →Reverse DNS CheckerResolve PTR records for a public IP and compare the reverse hostname with forward DNS where relevant.Open →IPv6 Website CheckerDetect AAAA records and verify whether the website actually responds over the published IPv6 endpoint.Open →

DNS Tools: what this section covers

DNS Tools follow the chain from delegation to the record returned to a visitor. The section separates authoritative nameservers, recursive caches, A/AAAA/CNAME destinations, MX routing, DNSSEC/CAA policy and TTL so “DNS propagation” is not used as a catch-all explanation for every mismatch.

Signals that matter for DNS

The pages here interpret DNS resolution and delegation evidence through the following search tasks and configuration concepts. They are included because they help separate causes, not to repeat a keyword a fixed number of times.

  • Dns tools — Verify dns tools from the public Internet and compare it with the value the responsible provider says should be live.
  • Dns checker — Verify dns checker from the public Internet and compare it with the value the responsible provider says should be live.
  • Dns troubleshooting — Verify dns troubleshooting from the public Internet and compare it with the value the responsible provider says should be live.

Which DNS Tools check to start with

Start with DNS Lookup when you need the live record set, Nameserver Checker when delegation or authority is suspect, and Propagation Checker when independent locations/resolvers disagree. Use DNSSEC, CAA, reverse-DNS or IPv6 tools only when those specific signals are relevant to the symptom.

Diagnosis first, raw evidence second

The interface surfaces the highest-impact explanation and its confidence before raw protocol output. For DNS, that means a visitor can see what probably failed and what to change while an advanced user can still inspect the DNS, certificate, header, resolver or provider evidence behind the conclusion.

What a repaired DNS problem should look like

Fix the authoritative source first. If authoritative servers already return the intended value, another edit can make the incident worse; compare recursive answers and the previous TTL instead. If authoritative servers disagree with one another, waiting for caches will not repair the source inconsistency.

Validate the DNS resolution and delegation change

Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire. Re-run the same focused tool that exposed the problem so a dashboard status, cache or unrelated healthy signal is not mistaken for proof of the repair.

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.