Why DNS changes take time
Resolvers cache DNS answers based on TTL and provider behavior. After you change a record, some resolvers may still return the old value until their cache refreshes.
What to check
Check the exact hostname and record type. A root domain, www host, API subdomain, MX record, and TXT record can all behave differently.
Common mistakes
Do not repeatedly change records during propagation unless you understand the impact. Changing values again can make troubleshooting harder.
FAQ
Does propagation mean my website works?
No. DNS answers are only one part of website health.
Can I force every resolver to refresh?
Usually no. You can lower TTL before planned changes, but caches still depend on resolver behavior.