Names Organizer
Windows 10 & 11 Buy license · $49.95
DNS and security

Nameserver Change Not Working? Troubleshooting DNS Propagation

Nameserver change not working? Check the change at the registry, understand TTL and caching, verify the new DNS zone and fix the common mistakes.

Updated 5 minute read The Names Organizer team

If a nameserver change is not working, first check whether the registry actually has the new nameservers: run an RDAP lookup on the domain or nslookup -type=ns yourdomain.com against a public resolver. If the registry still lists the old ones, the change was never saved, usually because of a typo, a registrar lock or a domain status that blocks updates. If the registry shows the new ones, the change worked and you are waiting for caches to expire, which for .com can take up to 48 hours. If it still fails after that, the new DNS zone is missing records, so the domain now points at a provider that does not know what to answer.

Below is a step-by-step way to find which of those three situations you are in, and the fix for each.

How a nameserver change actually works

Nameservers are not DNS records you edit at your DNS host. They are set at your registrar, which sends them to the registry (for example, the .com registry). The registry publishes them in the top-level zone, so resolvers around the world know which servers to ask about your domain.

That gives three places where things can go wrong:

  1. The registrar did not save or send the change.
  2. Resolvers are still using the old nameservers from their cache.
  3. The new nameservers do not have a correct zone for your domain.

Step 1: Check what the registry holds

This is the single most useful check, because the registry is the source of truth.

  • RDAP or WHOIS lookup: the nameserver fields show what the registry has on file. They update within minutes of a successful change for most gTLDs.
  • Query the TLD servers directly: in Command Prompt, run nslookup -type=ns yourdomain.com a.gtld-servers.net for a .com or .net domain. The answer comes straight from the registry's servers, not a cache.

If the old nameservers are still listed, go to Step 2. If the new ones are listed, skip to Step 3.

Step 2: The change did not reach the registry

Common reasons a nameserver change does not stick:

CauseHow to spot itFix
Typo in a nameserver nameRegistrar shows an error, or the saved value is wrongCopy the names exactly from your DNS provider
Change saved in the wrong placeYou edited NS records inside the DNS zone rather than the registrar's nameserver settingUse the registrar's "Nameservers" or "Change nameservers" option
Update blocked by a lockStatus shows clientUpdateProhibited or serverUpdateProhibitedRemove the lock temporarily, or ask your registrar
Domain on hold or expiredStatus shows clientHold, serverHold or redemptionPeriodResolve the billing, verification or expiry issue first
Change pending approvalRegistrar shows the change as pendingCheck email for a confirmation link
Wrong registrar accountYou changed a different domain or accountConfirm the registrar in a lookup and log into that account

If you are not sure what a status code means, see domain status codes explained.

Step 3: The change worked, but caches still hold the old answer

Resolvers cache the nameserver delegation for as long as the registry's TTL says. For .com and .net that TTL is 172,800 seconds, which is 48 hours. Many resolvers pick up the change much sooner, but some will keep sending visitors to the old nameservers until their cached copy expires.

Symptoms of this stage:

  • The site works for some people and not others.
  • It works on mobile data but not on your office network, or the other way round.
  • Different public resolvers give different answers.

To see it for yourself on Windows:

  1. Run nslookup yourdomain.com 8.8.8.8 and nslookup yourdomain.com 1.1.1.1 and compare the IP addresses.
  2. Clear your own PC's cache with ipconfig /flushdns, then restart your browser, which keeps a separate cache.
  3. Remember your router and your internet provider's resolver also cache answers. You cannot clear theirs; you can only wait.

During this window, keep the old nameservers working with the same records. If you shut down the old DNS host the moment you switch, visitors still being sent there will get nothing. Our guide to choosing DNS TTL values explains why lowering TTLs in advance helps with record changes, though it cannot shorten the registry's own nameserver TTL.

Step 4: The new nameservers do not have the right zone

If the registry lists the new nameservers and plenty of time has passed but the site or email still fails, the new DNS host is the problem. Query it directly:

  • nslookup yourdomain.com ns1.newprovider.example (use the real nameserver name). No answer, or "refused", means the zone does not exist there or is not active.
  • nslookup -type=mx yourdomain.com ns1.newprovider.example checks email routing.
  • nslookup -type=txt yourdomain.com ns1.newprovider.example checks SPF and verification records.

Typical mistakes:

  • The domain was never added to the DNS provider's account, or the zone was not activated.
  • Only the website's A record was copied across, so email, subdomains and verification records are missing.
  • The www record was forgotten.
  • DNSSEC is enabled at the registrar with the old provider's DS record, so validating resolvers reject the new answers. Remove or update the DS record to match the new provider.

Before any nameserver change, export or write down every record in the old zone. Moving nameservers moves the whole zone, so anything you do not recreate at the new provider simply stops existing.

More command examples are in how to check DNS records on Windows.

A safe order for changing nameservers

  1. Record every DNS record at the current provider.
  2. Create the zone at the new provider with all the same records.
  3. Query the new nameservers directly and confirm each record answers correctly.
  4. If DNSSEC is on, plan the DS record change with both providers first.
  5. Change the nameservers at the registrar.
  6. Confirm the registry shows the new nameservers.
  7. Keep the old zone running for at least 48 hours.
  8. Check the website, email and any other services, then retire the old zone.

Keeping track of nameservers across your domains

When you manage more than a couple of domains, it is easy to lose track of which ones use which DNS provider, and a nameserver change you did not make is one of the first signs of a hijack. Names Organizer, a domain manager for Windows, records each domain's nameservers and DNS records when it refreshes from WHOIS and RDAP, shows what changed since the last check, and can warn you when nameservers or DNS records change unexpectedly. That makes it easy to confirm a planned change has reached the registry, and to notice the changes you did not plan. Its DNS and nameservers report gives you a printable record of each domain's settings before you move anything, and Names Organizer can save it as PDF or text.

Frequently asked questions

How long does a nameserver change take?

The registry usually updates within minutes, but resolvers may cache the old nameservers for up to the parent zone's TTL, which is often 48 hours for .com.

Why does my site work for some people but not others?

Different resolvers still hold cached answers from the old nameservers. It settles once their cached copies expire.

How do I check which nameservers a domain uses?

On Windows run nslookup -type=ns yourdomain.com, or look up the domain with RDAP, which shows the nameservers the registry holds.

Get three guides like this every month, plus software update notices.Subscribe →