Fix: Domain Shows “This Site Can’t Be Reached” After DNS Change

Estimated reading: 2 minutes

Seeing “This site can’t be reached” or “ERR_NAME_NOT_RESOLVED” after a DNS change usually means the domain isn’t resolving yet, or there’s a misconfiguration. Here’s how to diagnose and fix it.

Step 1: Check If DNS Has Propagated

DNS changes take time. Before troubleshooting further, check current propagation status:

  • Go to dnschecker.org and enter your domain
  • Check if the A record is returning your Veerhost server IP across most locations
  • If it’s still showing the old IP or blank, propagation is not complete yet — wait up to 48 hours

Step 2: Verify the A Record Is Correct

Log in to your DNS provider and confirm your A record looks exactly like this:

Type: A
Name: @ (or your domain name)
Value: YOUR_VEERHOST_SERVER_IP
TTL: 3600 (or Auto)

Also add a www A record pointing to the same IP so both yourdomain.com and www.yourdomain.com work.

Step 3: Flush Your Local DNS Cache

Your computer may be caching the old DNS result. Flush it:

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Step 4: Check That the Domain Is Added in cPanel

Even if DNS is pointing correctly, the domain must exist in your cPanel account. Go to cPanel → Domains and confirm your domain is listed. If it’s not there, add it via Domains → Create a New Domain.

Step 5: Check for a Conflicting AAAA Record

If you have an IPv6 AAAA record pointing to a wrong or old address, browsers may try IPv6 first and fail. Check your DNS zone for any AAAA records — if you don’t use IPv6, remove them or make sure they point to the correct Veerhost IPv6 address.

Still Not Resolving?

Contact Veerhost support at veerhost.com/support with your domain name and current DNS settings screenshot.

My account