NET::ERR_NAME_NOT_RESOLVED: Causes and How to Fix It
DevOps Team
Last Updated: Oct 08, 2026
Total View: 90
DNS Resolution Errors Keeping Your Website Offline?
If net::ERR_NAME_NOT_RESOLVED is blocking website access, incorrect DNS records, domain settings, or network issues may be responsible. Get expert help to restore connectivity and prevent disruptions.
- DNS configuration troubleshooting
- Domain resolution checks
- Browser & network diagnostics
- Server connectivity validation
The NET::ERR_NAME_NOT_RESOLVED error occurs when your browser can’t convert a site’s domain name into an IP address. Typically, this issue is caused by a DNS resolution failure that prevents the browser from finding the server for the requested site.
It happens in Google Chrome or any other Chromium-based browser when you try to visit a website, use a web application, or check the freshly configured domain. Possible reasons for the DNS resolution failure include incorrect DNS settings, expired DNS records, local cache issues, a VPN conflict, and a misconfigured domain.
You can fix most DNS resolution errors without changing major settings on your computer. In this guide, we will cover why you get NET::ERR_NAME_NOT_RESOLVED and how to fix it on various platforms.
What Does NET::ERR_NAME_NOT_RESOLVED Mean?
NET::ERR_NAME_NOT_RESOLVED is a browser error indicating that the domain name could not be resolved into an IP address.
Whenever you enter a website address, such as example.com, your browser relies on the Domain Name System (DNS) to identify the IP address associated with that domain. Once it resolves the address, the browser can try to connect to the destination server.
If DNS resolution fails, the browser cannot establish that connection and may display NET::ERR_NAME_NOT_RESOLVED.
This problem can occur at several levels, including your device, network, DNS resolver, or the website’s DNS configuration. It doesn’t necessarily mean the website’s application server is down.
What Causes the NET::ERR_NAME_NOT_RESOLVED Error?
Understanding the underlying cause helps you avoid unnecessary troubleshooting.
Incorrect DNS Configuration
Your device may be using DNS servers that are unavailable, misconfigured, or unable to resolve the requested domain. Incorrect DNS records on the website’s side can also prevent successful resolution.
Corrupted or Outdated DNS Cache
Operating systems and browsers temporarily store DNS lookup results to speed up subsequent requests. Cached negative responses or outdated entries may cause resolution problems until the cache expires or you clear it.
Domain Registration or DNS Record Issues
An expired domain, incorrect nameserver delegation, or missing DNS records can prevent browsers from finding a website.
For example, if a domain has no valid A or AAAA record and no other applicable address record, DNS resolution may fail when a browser tries to connect.
VPN, Proxy, or Security Software Interference
VPN applications, proxy configurations, firewalls, and endpoint security tools can affect DNS requests.
Some corporate networks also apply DNS filtering policies that intentionally prevent certain domains from resolving.
Local Network Problems
Router configuration issues, unreliable DNS connectivity, or temporary internet service provider problems can interrupt DNS lookups.
These issues may affect several websites, not just a single domain.
How to Fix NET::ERR_NAME_NOT_RESOLVED?
Follow these troubleshooting methods in order. Start with simple checks before changing network or server settings.
Verify the Website URL and Internet Connection
Start by checking whether the website address contains spelling mistakes or an incorrect domain extension.
Next, open another website to determine whether your internet connection is working.
If multiple websites fail to load, the problem may involve your network or DNS resolver. If only one domain fails, investigate that domain’s DNS records and configuration.
You can also test the website using another device or network to narrow down the problem.
Clear the DNS Cache
Your system may be storing outdated DNS information. Clearing the cache forces the operating system to request fresh DNS information.
For Windows:
Open Command Prompt and run:
ipconfig /flushdns
After receiving the confirmation message, close and reopen your browser.
For Linux systems using systemd-resolved:
sudo resolvectl flush-caches
The exact command depends on your Linux distribution and DNS caching service.
For macOS:
On many recent macOS versions, you can run:
sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder
Restart the browser and check whether the domain resolves.
Change Your DNS Server
If your current DNS resolver is having issues, try another resolver to see if that helps.
Common public DNS services include:
| DNS provider | Primary DNS | Secondary DNS |
|---|---|---|
| Google Public DNS | 8.8.8.8 | 8.8.4.4 |
| Cloudflare DNS | 1.1.1.1 | 1.0.0.1 |
On Windows, open your network adapter settings, locate the IPv4 DNS configuration, and enter the preferred resolver addresses.
Before making changes on a corporate network, confirm whether your organization requires internal DNS servers. Public resolvers may not resolve private company domains.
Check DNS Resolution Using Command-Line Tools
The nslookup command helps determine whether a DNS server can resolve the requested domain.
Run:
nslookup example.com
If the command returns a valid IP address, the DNS lookup succeeded through the queried resolver.
You can also query a specific DNS server:
nslookup example.com 8.8.8.8
Compare the results from your default resolver and the public resolver.
If one resolves the domain while another fails, the issue may involve resolver configuration, filtering, or cached DNS information.
On Linux and macOS, the dig utility provides additional diagnostic information:
dig example.com
To inspect nameserver records:
dig example.com NS
These commands are particularly useful for developers managing DNS records and cloud-hosted applications.
Disable VPN or Proxy Temporarily
If the error appears only when connected to a VPN, disconnect temporarily and test the website again.
Similarly, check whether your browser or operating system is configured to use a proxy.
A misconfigured proxy or VPN DNS policy can interfere with domain resolution.
For managed corporate devices, coordinate with your IT administrator rather than permanently disabling security controls.
Inspect the Hosts File
The hosts file allows your operating system to map domain names to IP addresses locally.
Incorrect entries may redirect requests or prevent expected access.
Common locations include:
Windows:
C:\Windows\System32\drivers\etc\hosts
Linux and macOS:
/etc/hosts
Open the file with appropriate permissions and look for incorrect mappings involving the affected domain.
Remove or correct only entries you understand. Some mappings may be required for development environments or internal applications.
Restart Your Router and Browser
If DNS resolution still fails, restart your browser and router.
Restarting the router may clear temporary network problems and refresh its connection with the internet service provider.
If the issue persists across multiple devices, contact your ISP or network administrator for additional troubleshooting.
How to Prevent DNS Resolution Errors?
Although DNS failures may not always be preventable, a few key practices will decrease their incidence and impact.
Monitor Domain and DNS Status
Monitor the status of domains, including the domain’s expiration date, authoritative nameservers, and key DNS records.
Automated monitoring can alert administrators to unexpected DNS updates or DNS lookups prior to impacting too many end-users.
Ensure Reliable DNS Setup
Select a DNS service which provides redundancy, monitoring, and adequate security measures.
In business critical situations, DNS availability should be considered when evaluating infrastructure needs, not just as an independent setup exercise.
Perform DNS Changes in a Testing Environment
Before making any changes to DNS records in production, check the desired IP addresses, hostnames, and routes.
In the event of an infrastructure migration, consider setting lower TTLs before the expected change to minimize the impact of cached answers post migration.
For applications using automated deployment workflows, incorporate relevant infrastructure checks into the release process. You can explore our Deployment Strategies guide for related deployment planning concepts.
Maintain Proper Network Security
Use trusted DNS resolvers, maintain appropriate firewall rules, and periodically review VPN and proxy configurations.
Avoid disabling security software as a permanent workaround. Instead, identify the configuration responsible for blocking legitimate DNS requests.
How Moon Technolabs Helps Resolve DNS and Infrastructure Issues
DNS issues may get complicated especially in cases where the cloud infrastructure or other environments are involved.
Moon Technolabs offers cloud computing, DevOps, and software development services that can help companies solve their problems with infrastructure and application connectivity.
Depending on the specific needs of the project, our experts can help configure DNS, design cloud infrastructure, troubleshoot deployments, and optimize infrastructure.
If you need to migrate a website, configure a cloud-based application, or investigate recurring connectivity issues, performing a technical assessment may prove helpful.
Conclusion
The error “NET::ERR_NAME_NOT_RESOLVED” happens when the browser is not able to resolve the domain name into an IP address. It can be due to as simple an issue as a wrong URL entry or outdated DNS cache, or even more complex problems like corrupt DNS records, nameservers or networking issues.
To begin with, check your internet connection, flush the DNS cache and do some DNS diagnostics for the domain. If you have a production site that is facing this issue, then check your authoritative DNS configuration.
The location of the problem will help you find a working solution and avoid making unnecessary changes to systems that are working fine.
The DevOps Team at Moon Technolabs consists of experienced engineers and cloud specialists who share insights on modern software delivery and infrastructure management. With expertise in AWS, Azure, CI/CD pipelines, containerization, and cloud-native architectures, the team contributes practical knowledge drawn from real-world projects. Their content focuses on automation, scalability, cloud cost optimization, and best practices that help businesses build reliable and efficient development ecosystems.
Get in Touch With Us
Submitting the form below will ensure a prompt response from us.
