Question

Why does it take between 24 to 48 hours for changes made to a hosted zone in Amazon Route53 to reflect globally?

B. DNS resolvers around the world can only reflect the changes in their cache after the Time To Live (TTL) has expired, it is 24 hours by default.
D. If changes to the hosted zone are made in the same AWS Region as the DNS resolver, it can take between 6 to 12 hours.
A. AWS Name Servers need between 24 to 48 hours to create record sets, update their respective values and process changes.
C. AWS Name Servers around the world update their cache in tandem, it takes between 24 hours to 48 hours for the process to complete.

Answer 1

Changes to a hosted zone in Amazon Route53 can take 24 to 48 hours to reflect globally because DNS resolvers need to update their caches after the TTL expires, which by default is 24 hours.

Step-by-step explanation:

When changes are made to a hosted zone in Amazon Route53, it can take between 24 to 48 hours for changes to reflect globally. This delay is primarily due to the propagation of the new DNS information across the internet. DNS resolvers, which are responsible for translating domain names into IP addresses, cache the results for a certain period, known as the Time To Live (TTL). The default TTL is often set to 24 hours. Once the TTL expires, the resolvers must fetch the updated DNS information, which then becomes available globally. Thus, until all caches have been updated, some users may still be directed to old IP addresses.