ERR_NAME_NOT_RESOLVED (or "server IP address could not be found") means the browser couldn't look up which server your domain points to. Unlike a timeout, it never got as far as contacting the website.
If it's only you
Usually it's an out-of-date DNS cache on your device or network:
- Restart your device and router.
- Clear your browser cache, or try another browser.
- Flush your computer's DNS cache. On Windows, run
ipconfig /flushdnsin Command Prompt. On a Mac, runsudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderin Terminal. - Try a public DNS resolver on your device, such as Google Public DNS (
8.8.8.8) or Cloudflare (1.1.1.1).
If it still fails only for you, your internet provider can help.
If several people see it
Then the domain's DNS needs attention. At the company where your domain is registered, check that:
- The domain is active and hasn't expired.
- Your A records for @ and www exist and point to the IP address shown under Websites in your GUDHOST account.
- Any recent DNS change has had time to update: usually a few hours, up to 72 hours.
DNSSEC
DNSSEC adds a digital signature to your domain's DNS. If it's switched on but the signature no longer matches the DNS records (for example after moving your DNS to a different provider), browsers can't look the domain up at all. A WHOIS lookup shows whether your domain is "signed". If it is and you've recently changed where your DNS is managed, ask your registrar to check DNSSEC or turn it off.
If everything looks right and the error continues, contact support with your domain and we'll take a look.