Propagation

A Record Propagation — How Long It Takes

A record changes typically propagate in minutes to 4 hours. Here's what affects propagation speed and how to check.

What drives wait time

TTL tells resolvers how long they may cache your A record. Until it expires, some users still see the old IP — even when your authoritative DNS is already correct.

Typical timeline

Most A updates show up across major public resolvers within minutes to a few hours. Edge cases (stubborn caches, old TTL) can take longer.

If it looks stuck

Confirm the authoritative zone has the new record, then re-check Propagation. Try a different network or device to rule out local cache.

Check A record propagation

Open Propagation checker →

Step by step

Step 1 Before changing, note TTL — lower TTL speeds the next change.
Step 2 Publish the new A record at your DNS host.
Step 3 Open Propagation checker and select A.
Step 4 Wait until every resolver shows the new IP.
Step 5 If stuck, try another network or flush local DNS — Propagation shows authoritative state.

FAQ

How long does A record propagation usually take?

Minutes to four hours for most resolvers. NS or registrar issues can stretch longer.

How does TTL affect A record propagation?

Resolvers keep the old answer until TTL expires. Lower TTL before a planned change so caches refresh faster.

Why do some resolvers lag behind others?

Each resolver has its own cache and clock. Geographic and ISP differences are normal.

Does Cloudflare proxy vs DNS-only change propagation?

Proxy only affects traffic path to Cloudflare — for raw DNS answers at your authoritative zone, still watch TTL and resolver cache.

How do I verify A propagation step by step?

Use DomainPreflight Propagation — pick A, enter the hostname, confirm all five resolvers return the new IPv4.