---
title: "DNS_PROBE_FINISHED_NXDOMAIN on Mac: what it means and how to fix it · Kilobat Guides"
url: "https://kilobat.app/guides/dns-probe-finished-nxdomain.html"
description: "Chrome shows DNS_PROBE_FINISHED_NXDOMAIN on your Mac. Learn what the code means, check the name and your DNS servers, and fix the cause."
---

Error messages

# DNS_PROBE_FINISHED_NXDOMAIN in Chrome on Mac

Chrome shows this code when a DNS lookup failed and its own check says the name does not exist. The Chromium source says: “the domain must not exist.”

Applies to: Google Chrome and other Chromium browsers on all current macOS versions. · Checked: 29 October 2026

## Symptoms

- Chrome shows “This site can’t be reached” and the code DNS_PROBE_FINISHED_NXDOMAIN.
- Chrome says that the server IP address could not be found.
- Safari shows “Safari Can’t Find the Server” for the same name.

## Likely causes

- **A typing error in the address.** A wrong name does not exist in DNS.
- **A domain that expired or was removed.** The name existed before, but its owner removed it.
- **A DNS filter.** Some DNS filters and ad blockers answer that a blocked name does not exist.
- **An internal name without the VPN.** Company names exist only in the company's DNS. See [Internal names do not resolve on a VPN](https://kilobat.app/guides/vpn-split-dns-internal-names.html).
- **A wrong DNS server.** A DNS server can give a wrong “no such name” answer.

## How to check

1. Examine the address. Correct any typing errors.
2. Look up the name through the macOS resolver. No address lines means that the lookup failed.

   ```
   dscacheutil -q host -a name example.com
   ```
3. Ask a public DNS server directly. An answer here, but not above, points to your DNS settings.

   ```
   dig +short example.com @1.1.1.1
   ```
4. Show the DNS servers that the Mac uses now.

   ```
   scutil --dns
   ```
5. Open the same address on your phone, on cellular data. If it fails there too, the name does not exist.

## How to fix it

1. If only your DNS fails, set the network's own DNS or a public DNS for a test. See [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found.html).
2. If a DNS filter blocks the name, allow it in the filter.
3. For a company name, connect the VPN first.
4. Flush the DNS cache, then reload. See [Flush the DNS cache on a Mac](https://kilobat.app/guides/flush-dns-cache-mac.html).

## With Kilobat

1. Kilobat's connection doctor tests the name layer by layer: network, proxy, DNS, rules, IPv4, IPv6, TLS and the server. It names the layer that failed.

   ```
   kilobat why example.com
   ```
2. These Kilobat checks are free. AI agents run them through MCP with `diagnose_connection` and `diagnose_network`. See [Find why one site or API won't connect](https://kilobat.app/guides/recipes/why-cant-it-connect.html).

## Questions

**What does NXDOMAIN mean?**

NXDOMAIN is the DNS answer for a name that does not exist.

**When does Chrome show this code?**

Chromium runs a DNS probe after a failed lookup. When the DNS servers work, it reports that the domain does not exist.

## Sources

- [Chromium source: components/error_page/common/net_error_info.h](https://source.chromium.org/chromium/chromium/src/+/main:components/error_page/common/net_error_info.h)
- [Chromium source: components/error_page_strings.grdp](https://source.chromium.org/chromium/chromium/src/+/main:components/error_page_strings.grdp)
- [Google Chrome Help: Fix connection and loading errors in Chrome](https://support.google.com/chrome/answer/6098869)
- [RFC 8020: NXDOMAIN: There Really Is Nothing Underneath](https://www.rfc-editor.org/rfc/rfc8020)
- dscacheutil(1) and dig(1), man page installed with macOS 27.2

Sources checked on 29 October 2026. Man pages are the ones installed with macOS; open one with `man <name>` in Terminal.

## Related guides

- [ERR_NAME_NOT_RESOLVED in Chrome on Mac](https://kilobat.app/guides/err-name-not-resolved.html): Chromium describes this error as: “The host name could not be resolved.” Chrome could not get an address for the site's name.
- [DNS not resolving on a Mac](https://kilobat.app/guides/dns-server-not-found.html): When DNS fails, the Mac cannot change a name such as apple.com into an IP address.
- [Safari can’t find the server on a Mac](https://kilobat.app/guides/safari-cant-find-server.html): “Safari can’t find the server” usually means that the Mac could not get an address for the site name.
- [Flush the DNS cache on a Mac](https://kilobat.app/guides/flush-dns-cache-mac.html): macOS keeps DNS answers for some time.
- [Internal names do not resolve on a VPN](https://kilobat.app/guides/vpn-split-dns-internal-names.html): macOS can send queries for one domain to one DNS server and other queries to another.