A team lowers a DNS TTL immediately at cutover and expects all clients to forget the old value instantly. What is the problem?

Published
  1. DNS TTL is unrelated to caching in every resolver.
  2. Previously cached answers can retain the earlier TTL until they expire.
  3. Every client closes existing connections when the zone is edited.
  4. A lower TTL automatically copies database writes.

Comments — 0