Introduction

A DNS record that never appears to update is usually an authority problem before it is a cache problem. The common failure is editing a dashboard that looks correct but does not control the live zone, or updating the wrong hostname, record type, or environment. This guide is for proving the change exists in the real authoritative source of truth.

Symptoms

  • A recent DNS edit still returns the old IP, CNAME, MX target, or TXT value
  • The provider dashboard shows the new record but public lookups do not
  • The issue started after moving DNS providers or changing nameservers
  • Multiple teams edited DNS and no one is sure which provider is live
  • Cloudflare or another proxy makes it harder to tell what the true DNS answer is

Common Causes

  • The record was changed in a provider that is not authoritative for the domain
  • Registrar nameserver delegation does not match the zone being edited
  • The wrong hostname, subdomain, or record type was updated
  • Duplicate or conflicting records exist in the live zone
  • A proxy layer is hiding the difference between DNS state and delivered traffic

Step-by-Step Fix

  1. Check the registrar-level nameserver delegation first so you know which DNS provider is actually authoritative for the domain.
  2. Query the authoritative nameservers directly and confirm whether the intended record change exists there at all.
  3. Verify you edited the exact live hostname and record type rather than a staging zone, the apex instead of www, or the wrong record family.
  4. Review the zone for duplicate A, AAAA, CNAME, MX, or TXT records that compete with the intended answer.
  5. If a proxy or CDN is enabled, confirm whether you are testing the underlying DNS record or only the proxy edge behavior.
  6. Only after the authoritative zone is confirmed correct should you treat the remaining mismatch as TTL or resolver cache delay.
  7. Re-test with authoritative lookups and several public resolvers after each correction so you can separate a zone mistake from normal caching.
  8. If nameservers were changed recently, confirm the registrar delegation fully matches the intended provider and no old provider is still serving partial answers.
  9. Keep a DNS change checklist that starts with authority verification so future edits are made in the live zone instead of a stale duplicate.