DNS changes not working or not showing yet

Updated 2026-10-29

On this page
  1. Symptoms
  2. Causes
  3. Fix
  4. Still not working?

Symptoms

  • You added or changed a record in Zone Editor, but the website, email or verification still uses the old value.
  • You changed the nameservers at your registrar, but the domain still shows the old website.
  • A service says it cannot find your TXT or CNAME record.

Causes

  1. The domain does not use this server's nameservers. Then another DNS provider answers, and records changed here have no effect.
  2. The old answer is still cached. Other DNS servers keep an answer for its TTL (often 4 hours, up to 1 week).
  3. A hostname without the trailing dot. mail.example.org in a CNAME or MX record becomes mail.example.org.example.com.
  4. The name includes the domain. A record named www.example.com (without a dot at the end) becomes www.example.com.example.com.
  5. Nameserver change still spreading. Registries and internet providers can take up to 48 hours.
  6. A record that conflicts with another. For example a CNAME on a name that also has an A record. The DNS server refuses the change and keeps serving the zone as it was.

Fix

1. Check where the DNS is hosted. Open Site Check (section Advanced), choose the domain and click Check. It shows the domain's nameservers in public DNS. If they are not the ones shown in Zone Editor, make the change at that DNS provider, or point the domain here.

2. Wait for the TTL. The record list shows each record's TTL in seconds. Your change reaches everyone at the latest when the old TTL has passed. To make the next change faster, lower the TTL (for example to 300) a day before.

3 and 4. Correct the record. Delete the wrong record and add it again: the Name is only the part before your domain (www, not www.example.com), and hostnames end with a dot (mail.example.org.). The list shows the full name, so www.example.com.example.com. reveals the mistake.

5. Wait, then check again. Use Site Check after a few hours.

6. Remove the conflict. Delete either the CNAME or the other records for that name, then add what you need.

Still not working?

  • Check from outside your network, for example with the dig command:
    dig +short www.example.com A @1.1.1.1
  • Ask your hosting provider and give them the domain, the record and what you expect it to show.
Was this article helpful?

Still stuck?

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