ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Web browsers

ERR_NAME_NOT_RESOLVED

ERR_NAME_NOT_RESOLVED in Google Chrome: the name cannot be resolved

Verified with sources3 sourcesReviewed Oct 3, 2026
Technician coming? See the 2 steps they must show you

Risk level

Low

Usually safe to check without specialist tools.

Urgency

Medium

Quick answer

Chrome could not translate the site's name into an IP address: the name does not exist or has moved to a different address. Check the address, try other sites and, if they all fail, check your connection and router.

Safety first

Stop and check this first

  • Do not change the DNS servers of a company device on your own; ask the administrator.

Safe checks you can perform

  • The site's address
  • Other sites and the DNS probe code
  • Modem, router and provider
  • The domain's DNS records

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Check of the provider's DNS
  • Do not attempt this professional task: Review recent DNS changes

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Check of the provider's DNS

    What they doThe internet service provider checks its DNS servers if no name resolves on your line.

    They must show youtheir test result.

    In writingticket number and fix.

  2. Review recent DNS changes

    What they doThe domain administrator reviews the zone and the change history of the name's records.

    They must show youthe lookup before and after the change.

    In writingthe record modified and the date.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. The site's address

    No special tools

    Who:
    you.
    How:
    check the address character by character against the official one.
    Result that matters:
    whether there was a typo.
    If there was a typo:
    correct it; if it opens, that was the cause.
    If it is correct:
    continue with other sites.
    Evidence to keep:
    the exact address tried.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  2. Other sites and the DNS probe code

    No special tools

    Who:
    you.
    How:
    open other sites and look at whether the error page shows a DNS_PROBE_FINISHED code at the bottom.
    Result that matters:
    whether every name fails or only this one.
    If all fail or you see DNS_PROBE_FINISHED_NO_INTERNET or BAD_CONFIG:
    it points to your connection or DNS; check the router.
    If only this name fails:
    it points to the site's domain; test from another network.
    Evidence to keep:
    a screenshot of the bottom of the error page.

    Evidence: Chromium source - components/error_page/common/net_error_info.h (DNS probe status) · Google Chrome Help - Fix connection and loading errors in Chrome

  3. Modem, router and provider

    No special tools

    Who:
    you.
    How:
    restart the modem and router; if it continues, contact your internet service provider.
    Result that matters:
    whether names resolve again.
    If they do:
    the router or the line was the source.
    If they still do not resolve on your network but do on mobile data:
    ask the provider to check its DNS.
    Evidence to keep:
    restart times and the provider's answer.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

  4. The domain's DNS records

    Tools required

    Who:
    the domain administrator.
    How:
    query the name on the authoritative servers and check for recent changes in the zone.
    Result that matters:
    whether the name returns the expected address.
    If it does not exist or returns an old address:
    fix the zone; that is the cause.
    If it returns the right address:
    the failure is in the visitor's resolver.
    Evidence to keep:
    the lookup with time, server and answer.

    Only the domain owner or its DNS provider. If you do not administer it, do not do it: report the name and the time.

    Evidence: RFC 8020 - NXDOMAIN: There Really Is Nothing Underneath

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Google Chrome
Product type
Web browsers

Known code variants

  • ERR_NAME_NOT_RESOLVED
  • ERR_NAME_NOT_RESOLVED (-105)
  • ERR_NAME_NOT_RESOLVED Chrome
  • net::ERR_NAME_NOT_RESOLVED

What it means

Chromium defines ERR_NAME_NOT_RESOLVED (-105) as the host name could not be resolved. Chrome Help explains it as the hostname (web address) not existing or now having a different IP address. Unlike DNS_PROBE_FINISHED_NXDOMAIN, which is the conclusion of Chrome's DNS probe, this code does not say whether your DNS servers or the site's name are failing; Chromium also has probe results such as no internet or a bad DNS configuration.

Warnings and stop conditions

  • Loweditorial warning

    Do not change the DNS servers of a company device on your own; ask the administrator.

    Evidence: Google Chrome Help - Fix connection and loading errors in Chrome

Symptoms and causes

Probable causes · in order

  • Misspelled or non-existent namePossible

    Confirmed by correcting the address or checking that the site opens from another network.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

  • The site recently changed addressPossible

    Chrome Help mentions that the name may now have a different IP address; only the domain owner can confirm it.

    Evidence: Google Chrome Help - Get help with common error messages in Chrome

  • DNS or connection on your sidePossible

    If no name resolves, Chrome's probe can conclude there is no internet connection or the DNS configuration is wrong.

    Evidence: Chromium source - components/error_page/common/net_error_info.h (DNS probe status) · Google Chrome Help - Fix connection and loading errors in Chrome

Virtual technician

Does ERR_NAME_NOT_RESOLVED still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Chromium source - net/base/net_error_list.h (network error list)

    The Chromium Authors · 2026 · official_doc

  2. 2

    Chromium source - components/error_page/common/net_error_info.h (DNS probe status)

    The Chromium Authors · 2026 · official_doc

  3. 3

    Google Chrome Help - Get help with common error messages in Chrome

    Google · 2026 · official_doc

Sources: Chromium source - net/base/net_error_list.h (network error list) · Chromium source - components/error_page/common/net_error_info.h (DNS probe status) · Google Chrome Help - Get help with common error messages in Chromereviewed 2026-10-03 · verified

Was this entry useful?