sfw/fix
DNS_PROBE_FINISHED_NXDOMAIN critical

DNS_PROBE_FINISHED_NXDOMAIN

NXDOMAIN means the domain name couldn’t be resolved to an IP — the browser literally can’t find your server.

What you see

This site can’t be reached
example.com’s server IP address could not be found.
DNS_PROBE_FINISHED_NXDOMAIN

What’s actually happening

The browser asked DNS "what’s the IP for this domain?" and got "no such domain." Your server may be perfectly healthy — but with no valid DNS record, no one can reach it. Often follows a DNS change, expired domain, or nameserver switch still propagating.

Common causes

  • Missing or deleted A/AAAA record for the domain
  • Nameservers were changed and DNS is still propagating (up to 48h)
  • The domain registration expired
  • A typo in the DNS record or the domain pointed at the wrong nameservers

How to fix it

  1. Confirm the domain is registered and not expiredCheck the registrar — an expired domain produces NXDOMAIN instantly. Renew it if so.
  2. Verify the A record and nameserversIn your DNS provider, confirm an A record points the apex (and www) at your server’s IP, and that the registrar’s nameservers match your DNS host.
  3. Wait out (or test) propagationAfter a DNS/nameserver change, propagation can take minutes to 48 hours. Use a global DNS propagation checker to see where it’s live, and flush your local DNS cache to rule out a stale local record.

Stop it recurring

Enable registrar auto-renew and lock. Lower TTLs before a planned DNS change so it propagates fast.