What this error means
Public DNS did not return a usable address for the hostname. The browser or proxy message describes the symptom, not necessarily the root cause. HostWithShery therefore checks the DNS resolution and delegation evidence that can be observed publicly before recommending a configuration change.
Most likely causes
These are the first explanations to test because each can produce this exact symptom. Treat them as hypotheses until the matching public evidence is present.
- Missing address record — Verify missing address record from the public Internet and compare it with the value the responsible provider says should be live.
- Wrong nameservers — Compare the delegated nameservers with the servers that actually answer authoritatively; a record edited in a non-authoritative zone has no effect.
- Nonexistent hostname — Verify nonexistent hostname from the public Internet and compare it with the value the responsible provider says should be live.
What to check on your domain
Use the embedded scan to compare the failing layer with adjacent layers that can produce the same visible error. This prevents a DNS change from being used to “fix” a TLS problem, or an SSL-mode change from masking an origin failure.
- Missing address record — Verify missing address record from the public Internet and compare it with the value the responsible provider says should be live.
- Wrong nameservers — Compare the delegated nameservers with the servers that actually answer authoritatively; a record edited in a non-authoritative zone has no effect.
- Nonexistent hostname — Verify nonexistent hostname from the public Internet and compare it with the value the responsible provider says should be live.
- Run DNS lookup — Verify run DNS lookup from the public Internet and compare it with the value the responsible provider says should be live.
- Check delegation — Verify check delegation from the public Internet and compare it with the value the responsible provider says should be live.
Fixes in the recommended order
Change the smallest confirmed layer first. Preserve working DNS and mail records, document the current value, apply one repair, and then retest before moving to the next possibility.
- 1. Run DNS lookup. Confirm the public result after this step before making another unrelated change.
- 2. Check delegation. Confirm the public result after this step before making another unrelated change.
- 3. Restore A/AAAA/CNAME. Confirm the public result after this step before making another unrelated change.
How to confirm the repair
Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire.
If the error remains
Capture the checked hostname, exact timestamp, final DNS addresses, redirect/TLS result and the failing public status before escalating. That evidence gives a hosting or provider support team something testable instead of only the browser message. If results differ by resolver or network, include those differences rather than assuming the failure is universal.
What not to change
Do not replace nameservers, delete unrelated mail records, disable security controls, remove IPv6 blindly or purge the entire configuration merely because this message appears. Diagnose the failing layer first; broad changes can turn one isolated fault into several independent faults.
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.