A bit of a newbie question, but I can't quite understand from CloudFlare's own documentation if their Load Balancing is what I want to use (currently we just use CloudFlare's free DNS services, so adding on Load Balancing is not much of an extra monthly cost).
We have an on-prem web-server, and via our fibre internet link it has a public IP address. We also have a backup internet link, in case the fibre connection drops, and that backup link kicks in automatically. The only thing is that when the backup link kicks in it has a different public IP address.
The on-prem web-server is just running IIS, and has about 7 different "hostnames" that can be accessed. Obviously, each of those hostnames has its own "A" record in DNS, all which currently resolve to the public IP address associated with our fibre link. (In the couple of recent instances where the fibre link has dropped, we've had to go and update all of the DNS records to the alternate IP address of the backup internet link, and then change them back once the fibre link was back online).
I see a bit in CloudFlare's documentation about Load Balancing that it says "endpoints" are monitored on a regular basis (every 60 seconds with the basic Load Balancing plan), and the Load Balancer decides which endpoint to direct traffic to. Does that mean I could have the two different public IP addresses "balanced", and as long as the fibre link is up (and the backup link is offline) then traffic will go through to that - otherwise if the fibre goes down, and then the Load Balancer detects that the alternate public IP address is contactable, then it will direct traffic to that?
If that is the case, then what actually happens in the DNS. Do all of the current "A" records get pointed to the Load Balancer's IP address, and then it just deals with everything from there? Thanks in advance for advice!
