Route53 Domain resolution problem

Question

We created two route53 zones recently and created corresponding NS records at provider where we bought that domains. For some reason domains are not resolving from different places. For example: from my personal laptop it started resolving only after flushing cache on https://1.1.1.1/purge-cache/ page (I’m using 1.1.1.1 as my DNS server), in our Kubernetes cluster domains are not resolving correctly event after recreating coreDNS pods, the same problem exists on few more laptops/PCs, they still resolving records from our route53 zones to IP address that are assigned to root domain.

I’m supposing that some DNS authorities still caching old NS records for these zones but they were created 4 days ago, so all that records should be refreshed

Answer

What are the TTL values on the records that are being cached? Route 53 (as with most DNS resolvers) generally cache records for the time specific in the TTL and that's a difficult behaviour to get around - the usual fix being "change the TTL" but you have to wait for the original value to expire first.

Route53 Domain resolution problem

Relevant content