Domain not resolving? Troubleshoot DNS step by step

If your browser says This site can't be reached, DNS_PROBE_FINISHED_NXDOMAIN or server IP address could not be found, the domain name is not turning into an IP address. Work through the checks below in order; each one rules out a layer of the DNS chain.

Before you start

• The domain name and the IP address of your hosting (shown in cPanel on the right-hand General Information panel, or in your welcome email).
• Access to the place where the domain is registered. If you registered with MdmHost, manage it from the dashboard.
• A basic idea of how lookups work helps: How DNS resolution works.

Check the domain is registered and active

1. Run the domain through the WHOIS checker.
2. Look at the expiry date and the status. clientHold or serverHold means the registry has switched DNS off, usually because the domain expired or the registrant email was never verified.
3. Renew the domain or click the verification link in the registrar email; DNS returns within a few hours.

Check the nameservers

The WHOIS result lists the nameservers. They must be the ones that hold your DNS zone: your MdmHost hosting nameservers if DNS is managed in cPanel, or Cloudflare's if you use Cloudflare. A typo or old nameservers is the most common cause after moving hosts. Learn the difference in Nameservers vs DNS records.

Check the A record

1. Open cPanel → Domains → Zone Editor and click Manage next to the domain.
2. Confirm there is an A record for the bare domain and for www (or a CNAME for www) pointing to your server IP.
3. Test from your computer:
   Copy

   nslookup example.com 8.8.8.8

   On macOS or Linux you can also use dig +short example.com A.

Record help: Edit DNS records in the cPanel Zone Editor.

Allow time for propagation

Nameserver changes can take up to 24–48 hours worldwide; record changes follow the record's TTL. If public resolvers already return the new IP but your computer doesn't, it's caching, not a fault. See DNS propagation and TTL explained and track DNS propagation.

Clear your local DNS cache

System	Command
Windows	ipconfig /flushdns
macOS	sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux (systemd)	resolvectl flush-caches
Chrome	Open chrome://net-internals/#dns and click Clear host cache

Also check your computer's hosts file for an old entry for the domain.

Troubleshooting

• Works on mobile data but not at home: your router or ISP resolver is caching. Restart the router or switch to 1.1.1.1 / 8.8.8.8.
• Domain resolves but shows the wrong site: the A record points to an old server. Update it to your current IP.
• Only email fails: check MX records instead; see DNS record types explained.
• SERVFAIL: often a DNSSEC mismatch after changing nameservers. Remove the old DS record at the registrar.

Next steps

• Website error codes explained if the domain resolves but the page errors
• Fix common SSL errors
• Still not resolving after 48 hours? Open a support ticket.