Fix DNS_PROBE_FINISHED_NXDOMAIN After Changing Nameservers

Updated on Nov 15, 2026
Mila H
5 MINS READ
Table of Contents
Fix NXDOMAIN After Changing Nameservers

To fix dns_probe_finished_nxdomain after a nameserver change, you must check that the parent zone lists the correct nameservers and that every new server has your website records. You can clear local caches only after those checks pass.

Changing nameservers does not copy DNS records. This guide separates missing names, wrong delegation, cached answers, and DNSSEC errors so you can fix the right setting.

Identify the Cause of the DNS Failure

For dns_probe_finished_nxdomain after a nameserver change, you must check the exact hostname that fails. For example, example.com, www.example.com, or another subdomain. Each result tells you something different:

Result Meaning
NXDOMAIN The requested name does not exist; with an alias, its target may be missing.
NOERROR without the requested record The name exists, but that record type is absent: NODATA.
SERVFAIL Resolution failed; check DNSSEC, server health, and delegation.
Timeout No reply arrived; check reachability.

Missing AAAA records alone do not mean NXDOMAIN. NODATA and NXDOMAIN are different DNS responses. If you see dns_probe_finished_nxdomain after a nameserver change, waiting may not help. Missing DNS records must be added.

Check Your DNS Setup

Use this checklist to find where the DNS lookup fails, from your domain settings to your browser.

  1. Your domain is active and has no DNS hold.
  2. The parent zone lists the correct nameservers.
  3. Every listed nameserver answers queries for your domain.
  4. Your website hostname and any alias targets exist.
  5. The parent DS record matches your current DNSSEC setup, if used.
  6. Public DNS resolvers return the expected records.
  7. Your browser can resolve the hostname.

Your registrar controls which nameservers your domain uses. Your DNS host stores your DNS records. Changing NS records at your DNS host alone does not change the nameservers listed at the parent zone.

For future moves, you can use this nameserver migration checklist. Keep both old and new DNS zones working until cached DNS data expires.

1. Check the Parent Nameservers

At this point, you can start by checking that the parent zone lists the nameservers assigned by your new DNS provider. Install dig on Ubuntu or Debian:

Bash
sudo apt updatesudo apt install dnsutils -y

Set your domain, then trace the lookup:

Bash
DOMAIN="example.com"dig +trace "$DOMAIN" A

Replace example.com with your domain in every command. Check that the parent zone lists your new DNS provider’s nameservers. The +trace option shows the DNS lookup steps, but it does not check DNSSEC.

For a .com domain, check the parent nameservers directly:

Bash
PARENT_NS=$(dig +short com. NS | head -n1)dig @"$PARENT_NS" "$DOMAIN" NS +norecurse

For other domain extensions, use the parent zone shown in the trace. Do not assume it is always the last part of your domain.

If the parent lists the wrong nameservers, update them at your registrar. For custom nameservers like ns1.example.com, also check their registered IP addresses, called glue records.

If the trace times out, try another network. Your current network may be blocking DNS traffic.

2. Check Records on All Nameservers

Check each nameserver to make sure it answers for your domain and returns the expected DNS records. Replace these example nameservers with your own:

Bash
for ns in ns1.provider.example ns2.provider.example; do  echo "=== $ns ==="  dig @"$ns" "$DOMAIN" SOA +norecurse  dig @"$ns" "$DOMAIN" A +norecurse  dig @"$ns" "$DOMAIN" AAAA +norecurse  dig @"$ns" "www.$DOMAIN" CNAME +norecurse  dig @"$ns" "www.$DOMAIN" A +norecurse  dig @"$ns" "www.$DOMAIN" AAAA +norecursedone

Check for status: NOERROR, the expected DNS records, and the aa flag in each reply. If a server refuses the query or does not have your domain’s DNS zone, contact your DNS host. Test all assigned nameservers, not just one. 

At the DNS host:

  • Restore missing A records using your real IPv4 address.
  • Add AAAA only when the service has working IPv6.
  • Restore the intended www A/AAAA records or CNAME.
  • Check any CNAME target with dig target.example A and dig target.example AAAA.

For dns_probe_finished_nxdomain after a nameserver change, check that your CNAME points to a name that exists. Do not add other regular DNS records at the same name as a CNAME. To point your root domain to another name, use your DNS provider’s alias or CNAME flattening feature.

3. Check Domain Status and DNSSEC

If the parent zone does not list your nameservers, check your registrar dashboard and ICANN Lookup. Look for an expired domain, incomplete verification, or a clientHold or serverHold status. These holds keep your domain out of DNS. Contact your registrar to fix the issue; changing DNS records will not remove the hold.

When checking dns_probe_finished_nxdomain after a nameserver change, you must  troubleshoot SERVFAIL separately:

Bash
dig @1.1.1.1 "$DOMAIN" A +dnssecdig @1.1.1.1 "$DOMAIN" A +dnssec +cdflag

If only the second query works, DNSSEC may be causing the problem. This test alone does not confirm it.

Check the DS records using the parent nameserver found in the above steps:

Bash
dig @"$PARENT_NS" "$DOMAIN" DS +norecurse +dnssecdig @ns1.provider.example "$DOMAIN" DNSKEY +norecurse +dnssec

An old DS record may still point to your previous DNS provider’s keys. Use the 
DNSSEC SERVFAIL troubleshooting guide to check that it matches your current keys. Keep DS settings at your registrar in sync with DNSSEC at your DNS host. Do not turn off signing until the DS record is removed and cached copies have expired.

4. Check for Cached DNS Errors

Compare public DNS results with your nameservers’ answers to see whether the problem is fixed or old errors are still cached:

Bash
for resolver in 1.1.1.1 8.8.8.8; do  dig @"$resolver" "$DOMAIN" A  dig @"$resolver" "www.$DOMAIN" Adone

Use DNSViz to visually check delegation and DNSSEC. Use DNSChecker to test NS and A records from different locations. These tests do not show whether every DNS cache has updated.

If your nameservers return the correct records but a resolver still returns NXDOMAIN, check the SOA record’s TTL in the reply’s AUTHORITY section. DNS errors are cached too. Their starting cache time is the lower of the SOA TTL and SOA MINIMUM values. Lowering the TTL now will not clear errors already cached.

Then, clear your local DNS cache:

Bash
# Windows Command Promptipconfig /flushdns # Linux using systemd-resolvedsudo resolvectl flush-caches

Restart your browser. If Secure DNS is enabled, your browser may use a different DNS server than your system.

Conclusion

To fix dns_probe_finished_nxdomain after a nameserver change, you must check your nameserver setup, DNS records, and caches. Use the registrar for parent NS, glue, holds, and DS changes; use the DNS host for zone records and signing.

Once resolution works, PerLod domain management provides a place to manage registration and DNS settings.