Cloudflare DNS Not Updating

Changed a Cloudflare DNS record but users still see the old answer? Check public resolvers and confirm whether cache, proxying, or delegation is the issue.

Cloudflare changes are fast, but caches still exist

A Cloudflare DNS edit is usually live at Cloudflare's authoritative nameservers quickly. The delay people call propagation is often outside Cloudflare: recursive resolvers keep their old cached answer until TTL expires.

Check the record above across 14 public resolvers. If Cloudflare's own resolver and several others show the new answer, the change is live and the remaining old answers are stale caches. If nobody shows the new answer, check that the domain is delegated to Cloudflare nameservers and that the edited record is in the right zone.

Cloudflare-specific things to check

• Orange-cloud proxying: proxied A and CNAME records return Cloudflare edge IPs, not your origin IP.
• Wrong zone: staging, subdomain zones, and account transfers can lead you to edit the wrong place.
• Flattened CNAMEs: apex CNAME flattening can look different from a literal CNAME lookup.
• DNSSEC DS record: moving to or from Cloudflare without updating DS can create SERVFAIL.

FAQ

Why does Cloudflare show different IPs than my origin?

If the record is proxied, public DNS returns Cloudflare edge addresses by design. Use DNS-only mode if you need DNS to expose the origin IP.

Why do some resolvers still show the old answer?

They cached the previous response before your change. They will re-query Cloudflare when that cached response reaches its TTL.

What if every resolver returns SERVFAIL?

Check DNSSEC first, especially the DS record at the registrar. A DS record pointing at old keys can make validating resolvers refuse the domain.