How to set up round-robin for load balancing. I have several A and AAAA proxied records pointing to Cloudflare IPs. I believe this was done for load-balancing but want to ensure it is set up correctly. Should the IPs belong to Cloudflare servers? Does Cloudflare offer some of its servers as load balancers?
Is that what you see when doing a DNS lookup on your domain? If so, that’s normal but isn’t offering you round-robin DNS to your servers.
Or are those multiple A/AAAA records what is set in your Cloudflare DNS? Unless you are using a host that also uses Cloudflare, the IPs in your Cloudflare DNS should not be Cloudflare ones.
If you have multiple A/AAAA records pointing to your origin servers in your Cloudflare DNS and they are all proxied, then the DNS automatically operates on a round-robin basis to find an origin that is up…
If you want more control (such as pools or origins, priorities, geo-steering, etc), then there is a specific load balancer option…
1 Like
If I am understand what you are saying then to set up round-robin correctly (not using load balancing option) I would need to proxy the A records to the server (s) I want to use as load balancers. The IPs should be directed to these servers that are actually hosting the site, app, etc.
These should not be Cloudflare IPs unless the host is Cloudflare or uses Cloudflare (obviously Cloudflare is not the host for my site or apps, but it may be the case that the host uses Cloudflare servers.)
At this moment I see A and AAAA records for my domain, app, admin, api, dashboard, help, email, sip, and autodiscover all pointing to Cloudflare IPs including:
A records pointing to the following IPv4
104.21
104.26
172.67
AAAA records point to IPv6:
2606:4700:xxx
2606:4700:xxx
When I search for these on an IP look up they appear as Cloudflare servers.
I am under the impression they are not doing anything, but I was reading up on load balancing and thought perhaps cloudflare offers its servers as load balancers and when the record is proxied it forwards it to the origin server.
The records are proxied by Cloudflare so the Cloudflare IPs show up because it is proxied. The records actually point to your origin(s).
This is how proxying works, not related to load balancing. Cloudflare. offers load balancing, you’d need to set that up in your account by creating a load balancer and pointing it to the origins.
1 Like
The records would show up as cloudflare IPs on a public search, but I should be able to see that actual IPs that the records are pointing to in my DNS records, no?
The issue is that in my DNS records it seems that the IP address put down was a cloudflare server and not the actual server it should be pointing to.
1 Like
If you moved your domain from one Cloudflare account to another while the records were 
proxied, the initial scan for DNS records would have entered the Cloudflare IPs for any records that it found. You will most likely want to remove the entries with Cloudflare IPs and replace them with real IPs of your origin servers.
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.