hard20 pts · first answer countsdnsmulti-region

DNS failover that did not fail over

You fail over a region by changing a DNS record with a 60 s TTL. Twenty minutes later, a large share of mobile and JVM clients still hit the dead region. What is the most likely reason?

A.DNS changes always take 24 hours to propagateB.The new region has a different TLS certificateC.Clients or runtimes cache DNS longer than the TTL or keep long-lived connections open, so they never re-resolveD.The record TTL was too low, so resolvers ignored it

Discussion 0

Join free to post in the discussion.

DNS failover that did not fail over

Discussion 0

Related questions