Nameserver changes not working

Symptoms

• You changed the nameservers, but the site or email still uses the old settings.
• The nameserver lookup shows the old nameservers after the change.
• The change was accepted, but the domain is still not reachable.

Common causes

• The change has not finished spreading, because of the parent zone and the TTL.
• The new nameservers do not hold the DNS records yet.
• The change was saved at the registrar, but the DNS provider was not set up for the domain.
• A second change was made before the first one finished.

Safe initial checks

1. Check the current nameservers: dig NS yourdomain.com +short.
2. Compare them with the nameservers you entered at the registrar.
3. Check the records at the new provider, and confirm they exist there.

Do not change the nameservers again until the first change has had time to spread.

Step-by-step solutions

1. Not yet spread. Wait for the change to finish. This can take a few hours, and sometimes longer.
2. Records missing at new provider. Add the records at the new provider before you rely on the change. See DNS record types.
3. Wrong nameservers entered. Correct them at the registrar. See Change nameservers.
4. Multiple changes. Keep one set of nameservers, and wait for it to spread before you make another change.

How to confirm the issue is fixed

• dig NS yourdomain.com +short returns the nameservers you intend to use.
• dig A yourdomain.com +short returns the expected address.

When to contact support

Contact support if the nameservers are correct, the records exist at the new provider, and the lookup still shows the old nameservers after a long wait.

Information to include in a support ticket

• The domain name, and the output of dig NS.
• The time you made the change, and the nameservers you entered.

Related articles

• Change nameservers
• DNS not resolving
• Find your DNS provider
• NS records

Last reviewed

2026-10-27