Device-specific

    ERR_NAME_NOT_RESOLVED on Windows

    Why it happens on Windows

    A stale entry in the Windows hosts file or a leftover VPN DNS suffix overrides public DNS, so the name resolves to nothing.

    The fix on Windows

    Run ipconfig /flushdns in an elevated prompt, then inspect C:\\Windows\\System32\\drivers\\etc\\hosts for the domain and remove any stale line.

    Is ERR_NAME_NOT_RESOLVED happening on your domain?

    Resolving the name from outside your machine shows whether public resolvers can find a record, helping distinguish a public DNS issue from a local resolver or network problem.

    Free, no signup. Runs from outside your network, which is the only way to tell a server fault from a local one.

    If that didn't fix it

    Windows has its own failure mode, but ERR_NAME_NOT_RESOLVED has a wider set of causes that apply everywhere. The most common one overall is: no dns record exists for the hostname.

    All causes and fixes for ERR_NAME_NOT_RESOLVED

    ERR_NAME_NOT_RESOLVED on other platforms and devices

    Chrome
    Cloudflare
    Android

    Monitor this continuously with LemWatch

    A one-off err_name_not_resolved monitoring shows you today. LemWatch re-runs the same checks around the clock and alerts you the moment something breaks — free for up to 10 sites, no card needed.

    Last verified: by the Lemwatch research team.