Common DNS Propagation Issues

The most common reasons a DNS change doesn't appear to take effect, and how to tell a real propagation delay from a caching issue on your end.

GUIDE-1.5 · 1 min · Updated March 2026

Most "DNS isn't updating" reports are actually local caching, not propagation. Before assuming something's wrong:

  • Check the record from a public DNS tool rather than your own browser — your ISP or device may be caching the old answer.

  • Confirm the TTL on the old record. A 24-hour TTL means the old value can legitimately stick around for up to a day.

  • Verify you edited the record on the correct domain and the correct nameservers — a domain still pointed at its old registrar's nameservers won't reflect changes made in NameBright.

If a public DNS checker still shows the old value well past the TTL window, contact support with the domain name and the record you changed.

Related