Quick answer: This error means your browser couldn't find the domain in DNS. Restart your router, flush your DNS cache, and switch your DNS to 1.1.1.1 or 8.8.8.8. If it's your own website, check that your domain hasn't expired and that the nameservers and A record are correct.
When you type a web address, your browser asks a DNS server for the site's IP address. NXDOMAIN means "non-existent domain": the DNS server couldn't find it. This happens for one of two reasons:
- Your device or network has a DNS problem (stale cache, bad DNS server, VPN, or router issue).
- The domain has no valid DNS (expired domain, wrong nameservers, missing A record, or recent changes still propagating).
Step 1: Is it your device or the website?
- Open the site on your phone using mobile data (Wi-Fi off), or
- Check the domain on whatsmydns.net (select
Arecord).
| Result | Meaning | What to do |
|---|---|---|
| Site works elsewhere | Problem is your device or network | Follow Fixes for Visitors |
| Site fails everywhere | Problem is the domain's DNS | Follow Fixes for Website Owners |
Fixes for Visitors (Your Device)
Try these in order. Most people are fixed by step 3 or 4.
1. Check the URL for typos
One wrong letter (for example, gogle.com) causes this exact error. Retype the address carefully.
2. Restart your router
Unplug your router, wait 30 seconds, and plug it back in.
3. Flush your DNS cache
Windows: Open Command Prompt as Administrator and run:
ipconfig /flushdns
macOS: Open Terminal and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Linux:
sudo resolvectl flush-caches
Chrome: Paste this in the address bar and click Clear host cache:
chrome://net-internals/#dns
Android / iPhone: Turn Airplane Mode on for 10 seconds, then off.
4. Change your DNS server
| Provider | Primary | Secondary |
|---|---|---|
| Cloudflare | 1.1.1.1 | 1.0.0.1 |
| 8.8.8.8 | 8.8.4.4 |
- Windows: Settings → Network & Internet → your connection → DNS server assignment → Edit → Manual.
- macOS: System Settings → Network → your connection → Details → DNS.
- Android: Settings → Network & Internet → Private DNS → enter
one.one.one.oneordns.google. - iPhone: Settings → Wi-Fi → tap (i) next to your network → Configure DNS → Manual.
5. Turn off VPN, proxy, or ad-blocker
These can block or misroute DNS lookups. Disable them and reload the page.
6. Reset network settings (Windows)
Run these in Command Prompt as Administrator, then restart your PC:
ipconfig /release ipconfig /renew netsh int ip reset netsh winsock reset
7. Check your hosts file
Remove any lines that mention the domain:
- Windows:
C:\Windows\System32\drivers\etc\hosts(open Notepad as Administrator) - macOS / Linux:
sudo nano /etc/hosts
Fixes for Website Owners (Your Domain)
1. Check the domain hasn't expired
Log in to your registrar and confirm the domain is active. An expired domain loses its DNS right away. After you renew, DNS usually comes back within a few hours.
2. Verify your nameservers
Check the current nameservers:
nslookup -type=ns yourdomain.com
If they don't match the nameservers in your Visioning Cloud welcome email, update them at your registrar.
3. Make sure an A record exists
In cPanel → Zone Editor, confirm these records:
| Type | Name | Value |
|---|---|---|
| A | yourdomain.com | Your server IP |
| CNAME | www | yourdomain.com |
If only www fails, the www record is missing.
4. Wait for DNS propagation
After changing nameservers or records, every network can take from a few minutes up to 24–48 hours to update. Track progress on whatsmydns.net.
Tip: Don't switch nameservers back and forth while waiting. Each change restarts propagation.
FAQ
Why does the site open on mobile data but not Wi-Fi?
Your Wi-Fi network's DNS is giving a stale answer. Restart the router, flush DNS, or switch to 1.1.1.1.
Is this error a virus?
No, it's a DNS lookup failure. If it appears on many sites, check your DNS settings and hosts file for unwanted changes.
I just moved my site to Visioning Cloud. Why do I see this?
Your new nameservers are probably still propagating. Wait a few hours and flush your DNS cache.
Still not working?
Open a support ticket with your domain name and a screenshot of the error, and our team will check your DNS for you.