Error guide / Домен не резолвиться після зміни NS

Domain not resolving after an NS change or migration

After you change NS servers or move to a new host, the domain can go dark for a while: old DNS data still lives in providers' caches while the new data spreads gradually. This is called DNS propagation, and it takes anywhere from a few minutes to 24-48 hours. If a full day has passed and the site still won't resolve, some record got lost along the way.

What causes it

Usually it's an unfinished migration: the NS were changed, but the new host has no DNS zone with an A record yet, or the A record still points to the old IP. Less often the registrar is at fault: the new NS were saved with a typo or never applied.

How to fix it

1. Check via WHOIS which NS servers the domain currently uses: the new ones, not the old.
2. On the new host, make sure the DNS zone exists and the A record points to the current server IP. In cPanel that's the Zone Editor.
3. Compare the old and new IP: if the A record still shows the old server, fix it.
4. Give propagation time: usually up to 24 hours, sometimes 48. There's no way to speed it up from your side.
5. Flush your own DNS cache (ipconfig /flushdns) so you're not seeing the old address locally.
6. Run the domain through the tool below: it shows the current NS and where the name resolves now.

Related errors

• DNS_PROBE_FINISHED_NXDOMAIN DNS_PROBE_FINISHED_NXDOMAIN error
• ERR_NAME_NOT_RESOLVED ERR_NAME_NOT_RESOLVED error
• DNS_PROBE_FINISHED_NO_INTERNET DNS_PROBE_FINISHED_NO_INTERNET error
• This site can't be reached This site can't be reached