Chrome keeps its own DNS cache separate from the operating system, so it can show NXDOMAIN after the OS cache has already been cleared.
Chrome keeps its own DNS cache separate from the operating system, so it can show NXDOMAIN after the OS cache has already been cleared.
Visit chrome://net-internals/#dns and click Clear host cache, then chrome://net-internals/#sockets and flush socket pools before retrying.
Chrome has its own failure mode, but DNS_PROBE_FINISHED_NXDOMAIN has a wider set of causes. The most common one overall is: The A or CNAME record for the hostname does not exist.
Add the missing record at the DNS provider. Remember that the apex and www are separate records.
The DNS lookup queries public resolvers directly and shows the A, AAAA, CNAME and NS records that actually exist — which instantly separates 'record missing' from 'my resolver is stale'.
Chrome keeps its own DNS cache separate from the operating system, so it can show NXDOMAIN after the OS cache has already been cleared.
Visit chrome://net-internals/#dns and click Clear host cache, then chrome://net-internals/#sockets and flush socket pools before retrying.
The DNS lookup completed and the authoritative answer was 'this name does not exist'. Either the record is genuinely missing, the domain lapsed, or a recent DNS change has not propagated to the resolver you are using.