Domain Not Working? How to Diagnose DNS and Propagation Print

  • dns-propagation, nameservers, troubleshooting, dig, caching
  • 0

Check the layers in order

A domain that does not load can fail at any of five layers. Checking them out of order leads to guessing.

  1. Registration — is the domain active, expired, or on hold?
  2. Delegation — do the registry nameservers match the ones you intended?
  3. DNS records — does the zone contain the correct A, CNAME, or MX records?
  4. Hosting — is the domain added to the hosting account and is the site running?
  5. Client — is the browser, OS, or local resolver caching an old answer?

Step 1: Confirm the domain is active

Log in to the registrar and check the domain status. A domain can be:

  • Active — registration is current.
  • Expired — DNS is usually interrupted, and the site will not load.
  • On hold or suspended — often due to verification, abuse, or payment issues.
  • Pending transfer — DNS normally keeps working, but registrar controls may be limited.

If the domain is expired, stop here and see "Domain Expired: Grace Period, Redemption, and How to Restore It". DNS changes will not fix an expired registration.

Step 2: Check the nameservers

dig +short NS example.com

Compare the answer with the nameservers shown at the registrar and the ones SysopHost provided.

  • Empty answer: the domain may be on hold, expired, or not delegated.
  • Old nameservers: the registry has not published the change, or the change was never saved.
  • Only one nameserver: some registrars require at least two. Add the second value.
  • Typo in a hostname: compare character by character.

Step 3: Query the authoritative nameserver

A normal query may return a cached answer. Ask the nameserver that is supposed to hold the zone:

dig @ns1.example.com example.com A
dig @ns1.example.com www.example.com A

Replace ns1.example.com with one of the nameservers returned in Step 2. If the authoritative server returns the record but a public resolver does not, the problem is caching or delegation, not the record itself.

Step 4: Confirm the domain exists in hosting

DNS can be perfect and the site still shows a default page or an error if the domain is not configured in the hosting account.

  • In cPanel, open Domains and confirm the domain is listed with the expected document root.
  • Confirm the document root contains the site's files, usually an index.php or index.html.
  • If the site uses WordPress, confirm wp-config.php exists in the same directory.
  • Check disk and inode usage; a full account can serve errors instead of the site.

See cPanel Tutorial for Beginners for the interface.

Step 5: Separate caching from a real failure

DNS answers are cached for the record's TTL. Test with more than one resolver:

dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com A

If all three agree but your browser does not, clear the browser cache or test in a private window. If they disagree, wait for the TTL to expire; there is no fixed 48-hour guarantee.

A record that does not exist is also cached (negative caching). Adding a new record can take as long as its TTL to appear.

Step 6: Check HTTPS and the browser error

The exact browser message narrows the cause:

Message Likely layer
Server IP address could not be found DNS or delegation
Site cannot be reached / connection timed out Wrong IP, firewall, or server down
Your connection is not private SSL certificate or mixed content
403 Forbidden Hosting permissions or index file
404 Not Found Document root or WordPress permalinks
Database connection error WordPress database, not DNS

For certificate issues, see How to Fix "Not Secure" and Mixed Content Warnings.

If email stopped at the same time

Email depends on MX records. If you changed nameservers without recreating MX, SPF, DKIM, and DMARC records, mail will fail even though the website works.

See SPF, DKIM and DMARC Setup for Google Workspace and How to Set Up Google Workspace With Your Domain.

Verify the fix

  • dig NS returns the intended nameservers.
  • dig A returns the correct server IP.
  • Multiple public resolvers agree.
  • The site loads over HTTPS in a private window.
  • Email still sends and receives, if the domain uses email.

Related articles

  • How to Point Your Domain to SysopHost Hosting
  • How to Change Nameservers Without Breaking Your Website or Email
  • Domain Expired: Grace Period, Redemption, and How to Restore It
  • DNS Record Types Explained: A, AAAA, CNAME, MX, TXT, and CAA
  • cPanel Tutorial for Beginners

If you have completed these checks, contact SysopHost support with the domain, the dig NS and dig A output, the exact browser error, and whether email is affected. Do not send registrar passwords.


Was this answer helpful?

« Back