Storefront error library · Domain and DNS · Reviewed November 15, 2026
ERR_NAME_NOT_RESOLVED
on a Shopify store.
ERR_NAME_NOT_RESOLVED means a domain name could not be found. Fix it for your Shopify domain’s DNS records, and for scripts left behind by apps on hosts that no longer exist.
The short answer
A domain name could not be looked up: your store’s, or a script host’s. For your own domain, everything: no shopper can reach the store from that hostname. For a dead script host, usually only speed, since the browser waits on a lookup that fails. It costs sales when the missing script was something the page depends on, such as a size chart, bundle or checkout button.
At a glance
ERR_NAME_NOT_RESOLVED in three lines.
| Who can fix it | Whoever manages DNS, or the theme developer for dead script tags |
|---|---|
| Does it cost sales? | Always for your own domain; rarely for a leftover script |
| What Dozenfold does with it | Your own domain: not visible. Dead script hosts: in session timelines and page performance |
| Group | Domain and DNS |
| Last reviewed |
What you see
The exact messages.
The same problem is worded differently by each browser and tool. Search your console and error tracker for all of them.
What it means
In plain English.
The browser asked DNS for the address of a hostname and got no answer. Nothing was sent to any server.
On a store it shows up in two places. When it is your own domain, the whole store is unreachable. When it is a line in the console, one script, font or image on the page points at a host that does not exist any more.
Does it cost sales?
Which steps it can break.
When it happens on the path to purchase, look first at:
- The whole store, when it is your domain
- Features that depended on the dead script
Why it happens on Shopify
The usual causes.
Missing or wrong DNS records
After connecting a domain to Shopify, the bare domain needs an A record to 23.227.38.65 and www a CNAME to shops.myshopify.com. A typo, a missing record or an old record left at the registrar breaks it.
DNS changes still spreading
New records can take a while to reach every resolver; some shoppers see the store, some do not.
An expired domain
When a domain lapses at the registrar, its records stop answering.
Scripts left behind by uninstalled apps
Apps that pasted code into theme.liquid leave it behind when removed. Once the app’s host is gone, every page tries to load it.
Real problem or noise?
Check this before anyone debugs.
Most stores log this error at some level. These signals tell you whether real shoppers are affected.
- RealDig returns nothing for your domain.
- RealA script the page needs lives on the dead host.
- CleanupA leftover tag from an uninstalled app. Remove it for speed.
How to fix it
Reproduce, then fix.
- 01
Check your records
Look up both hostnames. The bare domain should return Shopify’s address and www should point at shops.myshopify.com.
dig +short your-store.com A dig +short www.your-store.com CNAME - 02
Fix them at the DNS host
Edit the records where your nameservers are, which may be Cloudflare rather than the registrar. Remove other A records on the bare domain.
- 03
Remove dead script tags
Search theme.liquid and snippets for the failing host. Remove code left by apps you uninstalled, on a duplicate theme first.
- 04
Renew the domain
If the lookup fails everywhere, check the registration has not expired.
Find it automatically
Know which errors cost orders.
When your own domain does not resolve, no script runs and no browser-side tool can report it; an external uptime check catches it.
For scripts on dead hosts, Dozenfold records each failed script and stylesheet load in the session timeline, and a failed load of your own theme assets opens an issue. Core Web Vitals by page show which scripts slow each page, so a leftover tag is easy to spot.
14-day trial · From $49 a month · Billed through Shopify
Questions
ERR_NAME_NOT_RESOLVED: FAQ.
What DNS records does a Shopify store need?
An A record for the bare domain pointing to 23.227.38.65, and a CNAME for www pointing to shops.myshopify.com, as Shopify’s manual connection guide lists.
Why can some people open my store and others cannot?
DNS changes reach resolvers at different times, and some resolvers cache old answers. Wait, then check again from another network.
Is DNS_PROBE_FINISHED_NXDOMAIN the same error?
Yes. It is how Chrome shows ERR_NAME_NOT_RESOLVED on the page: the name does not exist in DNS.
How do I find scripts left by old apps?
Open the console, look for ERR_NAME_NOT_RESOLVED lines, and search the theme code for that host name.
Written by the Dozenfold team, who build storefront error monitoring for Shopify. Reviewed November 15, 2026 against Shopify: Connecting a third-party domain manually and Chromium net error list (ERR_NAME_NOT_RESOLVED).