I had a question about the zero-downtime-failover feature included with business plans. We currently have an A record registered with a single IP address. In the DNS UI, this record appears as ‘Proxied’. I would like to add a second IP to the same domain, that points to a duplicate k8s cluster hosting identical content as the original cluster. The intention is that both clusters will serve content simultaneously, and if one goes down, Cloudflare will stop sending requests to that cluster. It sounds like the zero-downtime-failover feature would work for our use case.
However, a colleague had some concerns. While describing the feature, I mentioned the concept of ‘round robin’ DNS (I realize that the implementation is probably not traditional round robin DNS, but it helped in explaining the feature). They found this doc that mentions the drawbacks of using round robin for fail overs: https://www.cloudflare.com/learning/dns/glossary/round-robin-dns/ . Their main concern was about end-users caching 1 of the 2 records, and continuing to make requests to the failed cluster. However, I’m not sure this applies to domains that are ‘Proxied’. When I resolve the domain from my local machine, I get a series of 3 addresses that don’t match the IP that our A record points to. In that case, we shouldn’t have to worry about end-user DNS caching.
Can anyone comment as to whether these are valid concerns?