Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
ERR_NAME_NOT_RESOLVED means your browser cannot translate the requested hostname into an IP address. Start with the exact domain or subdomain, then verify the domain’s active status, authoritative nameservers, and DNS records. The message points to DNS or the network path—not automatically to a WordPress plugin, theme, or core problem.
What ERR_NAME_NOT_RESOLVED means
A browser shows ERR_NAME_NOT_RESOLVED when DNS resolution fails for the hostname in the address bar. The hostname may be misspelled, a DNS record may be missing or pointed at the wrong destination, nameserver delegation may be incorrect, or a recent DNS change may not have reached every resolver yet.
Check the complete hostname. The root domain, www, and other subdomains can use separate DNS records, so one may work while another returns the error.
This is different from a WordPress application failure. WordPress documentation treats database-connection errors, PHP errors, failed upgrades, and critical errors as separate categories. Do not edit WordPress files, disable plugins, or switch themes solely because this DNS error appears.
Fix the error in the right order
1. Recheck the address
- Retype the domain instead of relying on an old bookmark.
- Check spelling, punctuation, and the top-level domain.
- Test the root domain and
wwwseparately if both are intended to work. - Check any subdomain shown in the failing URL, such as
shop.example.comorstaging.example.com.
2. Confirm the domain is active
Sign in to the registrar or domain-management account and check that the domain has not expired, been suspended, or entered a registration-hold state. Identify the nameservers currently delegated for the domain. Those nameservers identify the DNS provider whose zone is authoritative.
3. Inspect DNS at the authoritative provider
Open the DNS control panel belonging to the active nameservers, not merely the dashboard where you last edited a record. Confirm that the zone-apex record exists for the root domain and that a record exists for the failing subdomain.
- An A record maps a hostname to an IPv4 address.
- An AAAA record maps a hostname to an IPv6 address.
- A CNAME record aliases a hostname to another hostname.
- Required mail records, including MX records, must be preserved when DNS authority changes.
Use the host’s documented target values. There is no universal WordPress IP address: the correct records depend on your hosting provider, CDN, and domain setup. A record changed at a non-authoritative provider will not change public DNS answers.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →4. Check nameserver or hosting changes
If you recently moved DNS, changed hosts, or connected the domain to WordPress.com, verify the complete zone at the new authoritative provider. WordPress.com advises adding necessary records at WordPress.com before changing nameservers to it. Some hosts use nameservers; others instruct you to keep your existing nameservers and add specific A-record or CNAME values instead.
Rank #3
Compare the current delegation with the provider’s setup instructions. A nameserver move can make the old provider’s records irrelevant, so recreate web, verification, redirect, and mail records at the provider that now has authority.
5. Allow time for propagation—but do not wait blindly
WordPress.com Support states: “DNS changes can take up to 72 hours to take effect across the internet. This delay is called propagation.” The support guide was last reviewed August 19, 2026. Learn WordPress describes propagation as ranging from a couple of hours to up to 72 hours, depending on several factors.
Propagation is not proof that the configuration is correct. If the error continues after a genuine change, recheck nameserver delegation and the records at the authoritative provider instead of assuming more waiting will solve it.
6. Compare another network
Open the site using mobile data or a different Wi-Fi network. If it works there but not on your usual connection, investigate the affected client or network path: local DNS caching, a router or network DNS service, filtering, or an ISP resolver may be involved. This comparison narrows the layer but does not identify the exact local cause by itself.
If the hostname fails on multiple unrelated networks, prioritize the domain, nameserver, and authoritative-record checks.
7. Escalate to the provider responsible for the failing layer
- Registrar: ask it to confirm domain status and nameserver delegation.
- DNS provider or CDN: ask it to verify the zone, required records, and whether the hostname is resolving.
- Web host: ask for the intended DNS targets and help when records appear correct but the site remains unreachable.
- Network or ISP: contact it when the domain resolves elsewhere but consistently fails only on one connection.
Provide the exact failing hostname, when the problem began, recent DNS or hosting changes, and whether the site works on another network. Do not describe a later HTTP error as the same problem: once DNS resolves, errors such as timeouts, connection refusals, TLS warnings, or WordPress critical errors belong to a different layer.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use these comparisons to narrow the cause
| Comparison | What it can indicate | What it does not prove |
|---|---|---|
Root domain versus www or another subdomain |
One hostname may be missing its record or configured differently. | It does not prove the working hostname’s setup is correct for the failing one. |
| One network versus another | The affected connection or resolver deserves investigation. | It does not identify whether the cause is cache, filtering, router, or ISP behavior. |
| Current versus recently changed nameservers or records | Delegation, an incomplete zone, or propagation may be involved. | Propagation time does not guarantee valid records. |
| DNS failure versus a later web or WordPress error | DNS may be working if the browser reaches an HTTP response or WordPress error page. | A WordPress application fix cannot repair a hostname that does not resolve. |
Common mistakes to avoid
- Editing DNS at a provider that is no longer authoritative.
- Checking only the apex domain while the failing URL uses
wwwor another subdomain. - Changing nameservers without copying required web and mail records.
- Assuming a 72-hour window means the records are correct.
- Disabling WordPress plugins or changing themes before DNS resolution works.
- Replacing a host’s documented target with a guessed IP address.
When the site still does not resolve
After confirming the exact hostname, domain status, authoritative nameservers, and records, ask the responsible DNS provider or host to check delegation and resolution from its side. Include timestamps and results from both your normal connection and an alternate network. If DNS begins resolving but the page then shows a server, TLS, or WordPress error, continue troubleshooting that newly reached layer rather than repeating DNS changes.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
