Website not working after changing nameservers (DNS)

For hosting customers · Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Good to know
  5. Still not working?

After you change a domain's nameservers at the registrar, or its A record, the internet does not switch at once: resolvers keep the old answer until it expires. Usually that is a few hours; a nameserver change at the registrar can take up to 48 hours. Site Check shows you exactly what the internet sees now.

Symptoms

  • The domain still shows the old website or the old host's page.
  • The browser says "This site can't be reached", "server IP address could not be found" or DNS_PROBE_FINISHED_NXDOMAIN.
  • It works for some people (or on mobile data) and not for others.
  • The certificate stays at Waiting for DNS on the SSL/TLS page.

Causes

Most likely first:

  1. The change is still spreading (DNS caches).
  2. The nameservers at the registrar are wrong — a typo, only one of the two, or the registrar's own DNS still in use.
  3. The domain's DNS is hosted elsewhere and its A record (or www) still points to the old server.
  4. An AAAA (IPv6) record still points to the old server, so visitors with IPv6 reach the old site.
  5. DNSSEC is still on at the registrar (a DS record) from the old DNS provider, so the domain does not resolve at all.

Fix

Check what the internet sees

  1. Open Site Check (section Advanced), choose the website and click Check.
  2. Read the lines:
    • Address in DNS: … (this server) is correct. NOT this server (…) means the name still points elsewhere; none: the name does not resolve means there is no answer at all.
    • Nameservers: the DNS servers that answer for the domain now.
    • Answer for visitors: what visitors get through public DNS.

From your own computer you can also ask a public resolver:

dig +short example.com A @1.1.1.1
dig +short example.com NS @1.1.1.1

On Windows: nslookup example.com 1.1.1.1.

1. Still spreading

If the nameservers or address are already correct in Site Check, wait. Clear your own cache: restart the browser, or on Windows run ipconfig /flushdns. Mobile data often sees the new answer first.

2. Wrong nameservers at the registrar

  1. Open Home or Zone Editor (section Domains) in the control panel. Both show the nameservers to use.
  2. At your domain registrar, set exactly these nameservers (both of them) and remove any others.
  3. Save. Site Check's Nameservers line shows them once the registrar has published the change.

3. DNS hosted elsewhere

If you keep your DNS at the registrar or another provider, add the records there instead:

  • An A record for the domain and for www with the server's address (shown in Site Check after "NOT this server").
  • For email, the MX, SPF, DKIM and DMARC records: Email Accounts → Email deliverability lists them with Copy buttons.

4. Old AAAA record

Remove or correct the AAAA records of the domain and www wherever your DNS is hosted. A certificate is not issued while an AAAA record points to another server.

5. DNSSEC from the old provider

If the domain does not resolve at all after a move, remove the old DS record at the registrar. To use DNSSEC with this server, turn it on in Zone Editor (Turn on DNSSEC) and add the new DS record shown there.

Good to know

  • Records you change in Zone Editor are live on this server's nameservers at once; resolvers that still have the old record keep it until its TTL runs out.
  • Once the domain points here, the free certificate is requested automatically within a few hours. Click Check now on the SSL/TLS page to request it at once.
  • Email keeps arriving at the old server until the MX record points here too.

Still not working?

If Site Check shows (this server) but the site still does not open, see Website shows the default page. If your host has turned on the AI assistant, click Ask the AI assistant what is wrong on Site Check.

Was this article helpful?

Still stuck?

Ask the AI about your exact situation — it answers from this knowledge base — or contact us.