Troubleshooting “Domain Not Resolving” Issues

“My domain isn’t loading” covers a wide range of underlying problems, from a freshly-changed nameserver still propagating to a typo in an A record, to a registrar lock you forgot about. This guide walks through the diagnostics in order — from the cheapest 30-second checks to the deeper investigations.

Work through the steps in order. Each one rules out a category of cause and points to the next thing to check.

Step 1 — Is it actually broken, or is it cache?

Before assuming the domain is broken, rule out cached results:

• Test from a different network — your phone on mobile data, or a friend’s connection. If it loads there but not on yours, your local DNS cache is stale.
• Try in incognito mode. Browser cache shouldn’t normally matter for DNS, but it occasionally does.
• Test via whatsmydns.net — enter your domain, select “A” record. If servers worldwide return the right IP, the domain works. The problem is local to you.

If it’s local to you, flush DNS:

• Windows: open PowerShell, run ipconfig /flushdns
• macOS: Terminal, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Linux: sudo systemd-resolve --flush-caches or sudo systemctl restart systemd-resolved
• Browser: Chrome, open chrome://net-internals/#dns → Clear host cache.

If it’s broken for everyone, continue to step 2.

Step 2 — Check the nameservers

From terminal:

dig yourdomain.com NS +short

Or via web at whatsmydns.net with “NS” selected.

Expected output: ns1.iwebvault.com and ns2.iwebvault.com (or your branded nameservers if you’ve set them up).

What it might actually show, and what it means:

• Old registrar’s default nameservers (e.g. dns1.registrar.com) — you haven’t changed nameservers yet, or the change is still propagating. If you changed them less than 4 hours ago, wait. If > 24 hours, recheck the registrar control panel — change may not have actually saved.
• “NXDOMAIN” or empty result — domain doesn’t exist or isn’t registered. Check the domain spelling. Verify renewal hasn’t expired.
• iWebVault nameservers but site still doesn’t load — nameservers are right, problem is elsewhere. Continue to step 3.
• Mix of old and new nameservers — propagation in progress. Wait, retry in an hour.

Step 3 — Check the A record

dig yourdomain.com A +short

Expected: your server’s IP address (from welcome email).

What you might see:

• No result — there’s no A record. Log into cPanel → Zone Editor (or DirectAdmin → DNS Management) and add one: Host @, Type A, Value your server IP.
• Wrong IP — old server IP from a previous host, or a typo. Update the A record to your current server IP.
• Correct IP but site still doesn’t load — DNS is fine, issue is with the web server. Continue to step 4.

Step 4 — Test the IP directly

If DNS resolves to the right IP but your site doesn’t load, the problem is at the server. Test by accessing the IP directly (or by adding a hosts-file override):

• Visit http://[your-server-ip]/ — should show a default cPanel/DirectAdmin landing page or your site (depending on server config).
• If even the IP doesn’t respond, the server itself or its firewall is the issue. Open a ticket — the server may be down or blocking the IP you’re testing from.

For more precise testing, add a hosts-file override to make your local computer use the right IP for the domain (bypassing DNS):

• Windows: edit C:WindowsSystem32driversetchosts as Administrator.
• macOS/Linux: sudo nano /etc/hosts

Add a line: 185.123.45.67 yourdomain.com www.yourdomain.com. Save. Visit the domain — your browser will use the IP you specified, regardless of DNS. Useful for testing whether the site works “if only DNS would catch up”.

Step 5 — Check for registrar issues

If DNS records look right but the domain is still not resolving, check the registrar side:

• Has the domain expired? Use whois.com to check the domain’s expiration date. Expired domains stop resolving after a grace period.
• Is the domain in “ClientHold” status? Visible in WHOIS lookup. ClientHold means the registrar has suspended the domain, usually for payment issues or policy violations. Contact the registrar.
• Is the domain in “Pending Transfer” status? If a transfer is in progress, DNS sometimes pauses. Wait for the transfer to complete.

Step 6 — Common-cause checklist

If steps 1-5 haven’t found the issue, work through this list:

• Cloudflare proxy enabled? If you use Cloudflare, the orange-cloud icon means traffic goes through Cloudflare. Your origin IP should be in Cloudflare’s DNS, not your nameservers. If Cloudflare is on but origin IP is misconfigured, the site fails.
• Wrong document root? If your site files are in public_html/blog/ but the domain expects them in public_html/, you’ll get a blank page or 404.
• .htaccess broken? If your site is configured but every request 500s, suspect a recent .htaccess change. Rename it via File Manager to .htaccess.bak to disable temporarily.
• SSL certificate expired or mismatched? Modern browsers may block sites with bad certificates entirely. Check at SSL Labs. If broken, run AutoSSL in cPanel/DirectAdmin.
• Firewall blocking your visitor IP? If only specific people see the issue (e.g. you from your office, but not others), CSF or another firewall has blocked the IP. Check cPanel → ConfigServer Security → search IP; unblock if needed.
• HSTS pinning — if you previously had SSL and changed something that broke it, your browser may refuse to load HTTP versions. Clear browser HSTS cache (Chrome: chrome://net-internals/#hsts).
• DNSSEC mismatch — if DNSSEC is enabled at the registrar but the zone keys don’t match, validation fails and resolvers reject the domain. Disable DNSSEC at the registrar, wait for propagation, re-enable later if needed.

Step 7 — Get diagnostic info before opening a ticket

If none of the above resolves it, our support team can dig deeper — but the ticket gets answered in one reply instead of three if you include the following:

• The exact domain (no spaces, no typos).
• The error you see — copy/paste, don’t paraphrase. “This site can’t be reached”, “DNS_PROBE_FINISHED_NXDOMAIN”, “502 Bad Gateway”, etc.
• What you’ve already checked — nameservers, A record, registrar status. The output of dig yourdomain.com NS +short and dig yourdomain.com A +short is gold.
• Recent changes — what did you change in the past 24-48 hours? New plugin, edited .htaccess, changed DNS, transferred the domain.
• Whether it works from any device or network at all.

Open a ticket here with all the above. We’ll have a definitive answer back in one reply rather than asking back-and-forth.

What’s next

• Setting up DNS records cleanly: DNS records explained.
• Just changed nameservers? Transfer vs nameserver change.
• Need to renew or update WHOIS? Manage via your client area.

About 80% of “domain not resolving” issues are one of three things: propagation still in progress, nameservers never actually saved at the registrar, or a missing/wrong A record. Work the diagnostics in order and you’ll find the cause faster than guessing.