Hello,
I have two A records for the same hostname, and I’m curious about how Cloudflare distributes client requests between the two original servers. Just to note, I don’t have a load balancer configured on Cloudflare.
Thank you in advance.
See here…
1 Like
Thank you for getting back to me.
I understand that Cloudflare employs round-robin load balancing among the original servers. Now, I need to ensure cookie persistence to avoid users having to re-authenticate on my site. Does Cloudflare automatically provide that functionality in my situation?
If you need that functionality, and it isn’t provided by your infrastructure, you’ll need to use the load balancer instead…
We acheive the same using round-robin DNS by having syncronous database replication across the origins, so any of them can handle any individual request at any time.
1 Like
In my scenario, if client 1 visits my website, will Cloudflare consistently serve all of that client’s requests from the same origin server throughout their session, or is there a possibility that the origin server may change during the client’s session?
As I said, you need need to use Cloudflare’s load balancer with session affinity to do that (see the link I posted). Round-robin DNS won’t do it as that directs randomly.
But, Based on Cloudflare’s explanation, what does “one IP address” refer to? Does it mean the first original server?
You are looking at the round-robin DNS. Record choice is random and if that one fails to connect, it will try another at random. This is not want you want for your use case.
If you want session affinity, you need to use the load balancer, not round-robin DNS. Here is the link again…
Thank you very much, it’s all clear to me now.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.