What is propagation?

“DNS propagation” is a common name for the time it takes different DNS resolvers to use updated information. A DNS change is published by the authoritative DNS provider, while recursive resolvers may keep an older answer in cache until its time to live (TTL) expires. The update is not a single switch that changes everywhere at once.

What affects how quickly you see a change?

• The TTL on the record that changed and how long a resolver cached the previous answer.
• Whether the domain's nameserver delegation points to the DNS provider you edited.
• Local device, browser, or network caching.
• DNSSEC configuration, if enabled; a stale DS record can cause lookup failures.

Checks to make after changing DNS

1. Confirm the domain is using the intended nameservers at its registrar.
2. Check the record in the authoritative DNS zone and compare it with the value supplied by your hosting provider.
3. Test from more than one network or use a DNS lookup tool to compare resolver answers.
4. Keep MX, SPF, DKIM, and other email records in place if you are only changing website routing.

The time required depends on the old TTL and the resolver. Some users may see a change quickly while others continue to receive a cached answer longer. If results remain wrong after the relevant TTL has passed, recheck the nameserver delegation, record value, and DNSSEC status, then contact your registrar or hosting provider with the domain and records you changed.

For the choice between nameservers and individual records, see nameservers vs. DNS records.