Introduction

A domain can stop resolving even when the nameservers and DNS zone look perfectly normal. One common reason is clientHold status at the registrar or registry layer. When that happens, delegation is effectively suspended, so public DNS stops answering no matter how correct your zone records are. The fix is to clear the underlying registrar issue and then verify that delegation returns once the hold is lifted.

Symptoms

  • The domain suddenly stops resolving across public resolvers
  • DNS records still look correct in the provider dashboard
  • WHOIS or registrar status shows clientHold
  • The outage started after missed renewal, contact verification, or abuse review
  • Subdomains fail because the parent domain is no longer delegated

Common Causes

  • The registrar placed the domain on hold after a billing or renewal problem
  • Registrant contact verification was not completed in time
  • A policy, abuse, or fraud review triggered manual suspension
  • Domain transfer or ownership details were left incomplete
  • The user fixed the account issue, but the hold has not been cleared yet

Step-by-Step Fix

  1. Check the domain status in the registrar dashboard or WHOIS output to confirm clientHold is the real cause.
  2. Review recent registrar emails and notices for the exact reason the hold was applied, such as renewal failure, verification, or abuse review.
  3. Resolve the account issue completely, which may mean paying the invoice, confirming contact details, or responding to a compliance request.
  4. Verify the registrar actually removed the hold status rather than only marking the ticket or payment as received.
  5. Once the hold is lifted, re-check the delegation at public resolvers to confirm the domain is returning authoritative answers again.
  6. Compare the active nameserver set after release to make sure no transfer or account change introduced the wrong delegation.
  7. Keep the web server and mail services online during recovery, because traffic may resume as soon as delegation returns.
  8. If the domain still does not resolve after the hold clears, inspect DNSSEC, nameserver glue, and zone publication for a second issue hidden by the original outage.
  9. Add renewal monitoring, registrar notice forwarding, and verified domain contacts so future hold events are caught before the site disappears.