DNS propagation is the gap between saving a DNS change and everyone on the internet seeing it, while old answers sit in caches until they expire.
Nothing is being pushed around the world during that gap, and knowing that lets you plan a change so the gap is minutes rather than a day.
What actually changes when you update DNS
Every domain has authoritative name servers: the servers that hold its records and have the final say on them. When you edit a record in your DNS provider's dashboard, say pointing shop.example.com at a new server's IP address, you are editing the records on those servers. The update there is quick, usually seconds, occasionally a few minutes while the provider copies it to all of its own servers.
So the source of truth is updated almost at once. The delay comes from everyone who asked before you made the change.
Caching is the whole story
Very few lookups ever reach an authoritative server. When your browser needs an address, it asks a resolver: a DNS server run by your ISP, your office network, or a public service such as Google Public DNS or Cloudflare's 1.1.1.1. The resolver does the work of finding the answer, then keeps a copy so the next person who asks gets it instantly.
That copy is the point of DNS caching. It keeps lookups fast and stops the authoritative servers being asked the same question millions of times a minute. The price is that a cached copy doesn't know the record has changed. Until it expires, the resolver keeps handing out the old address with complete confidence.
Resolvers aren't the only layer. Your operating system keeps a small DNS cache, most browsers keep their own, and some home routers do too. Each layer holds its answer for a while, so a change has to wait for every copy between a user and the name server to run out.
TTL: how long an answer lives
Every DNS record carries a TTL, short for 'time to live': a number of seconds that tells anyone caching the answer how long they may keep it. A record with a TTL of 3600 may be cached for an hour. When the hour is up, the next lookup has to go back to the authoritative servers and fetch the record again, which picks up any change.
Wondering how this was made? How we make these