DNS not propagating: verify the authoritative change

What does this mean?

A DNS change is published on authoritative servers, then recursive resolvers may continue returning cached older data. Waiting cannot fix a record saved in the wrong zone or an incorrect nameserver delegation. Treat differences between results as evidence to investigate, rather than a guarantee that more time will solve everything.

What should I check first?

Save the previous records and the intended new values. Check the registrar’s nameserver setting, then compare it with the DNS provider where you made the edit. If those are different providers, you may have edited an inactive zone. Record the exact name and record type, not just the domain.

How can I diagnose the cause?

Use the nameserver checker and query A, AAAA or MX as appropriate. Compare with the authoritative provider’s own zone display and, if available, a direct authoritative query through its diagnostics. Check whether a missing name was previously queried; negative answers can be cached too.

How do I fix it safely?

Correct the zone or delegation only when the discrepancy is clear. Preserve email records and DNSSEC arrangements when changing nameservers. If the authoritative data is correct, allow caches based on the old TTL to expire; lowering TTL after an answer was cached does not shorten that existing cache.

Verify the fix and know when to contact your provider

Retest at recorded intervals instead of making repeated conflicting edits. Ask the DNS provider to inspect delegation, authoritative consistency or DNSSEC if results remain wrong. Supply the record name, type, expected value, observed answers, TTLs and change time; do not send an account password.

Work through these checks in order

1. Compare the registrar’s current nameservers with the provider panel where you edited the record. If they identify different services, stop editing until you locate the authoritative zone.
2. Write down the queried name, type, expected value and answer TTL. Compare a provider authoritative diagnostic with the recursive lookup; a cached old answer is different from an authoritative wrong value.
3. If the authoritative zone is wrong, correct that value after a backup. If it is right, watch recorded answers over time and check DNSSEC or delegation with the provider when queries return failure.

Which tool can help?

DNS lookup · Nameserver checker · MX record checker

DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.