"DNS Not Propagating": Read the Authoritative Server

Symptom

Record looks changed in one place and old everywhere else.

Root cause

Resolver caching and TTLs — not the registrar.

Fix, in order

1. Ask the authoritative server directly (the truth)dig @ns1.yourdns.com yourdomain.com A +short
2. Then check your resolverdig yourdomain.com A +short # compare
3. Lower TTL BEFORE making changesTTL 300 # 5 min, day before the move

Prevent it coming back

TTL 300 for anything you might move; 3600+ for stable records.

Run it on clean infra

Spinning up a fresh box to reproduce or escape this error?

Managed cloud hosting

Related

Cloud & DevOps tool comparisons · Hardware build guides

NinjaOps publishes free engineering guides. Some outbound links are affiliate links: they cost you nothing and support the site.

Last reviewed 2026-10-02 · NinjaOps SEO grid · DevOps blog