This website uses cookies to ensure you get the best experience.
Learn more.
A DNS change points a service to a new endpoint, but some users continue to reach the old address. What should be considered before assuming Route 53 failed?
Published
- An updated authoritative record instantly flushes every resolver cache worldwide.
- The old application must be unreachable because DNS records physically disconnect servers.
- Changing a security group Name tag forces every client to resolve again.
- Recursive resolver and client caching can retain the prior answer until its cached TTL expires.
Comments — 0
Sign in to comment