This website uses cookies to ensure you get the best experience.
Learn more.
A team lowers a DNS TTL immediately at cutover and expects all clients to forget the old value instantly. What is the problem?
Published
- DNS TTL is unrelated to caching in every resolver.
- Previously cached answers can retain the earlier TTL until they expire.
- Every client closes existing connections when the zone is edited.
- A lower TTL automatically copies database writes.
Comments — 0
Sign in to comment