Is it possible to set up non-round robin DNS load balancing?

Is it possible to set up non-round robin DNS load balancing?

Desired functionality: *Note Server A is a clone of Server B

Scenario 1 - No fault : [Incoming request] -> [DigitalOcean DNS ] -> [Server A responding]

Scenario 2 - Server A Fault: [Incoming request] -> [DigitalOcean DNS] -> [Server A NOT responding] -> [Server B responds]

Scenario 3 - Server A & Server B Fault [Me] -> [Bar] -> [Beer]

*Note, yes I read this:

And the load balancing section here:

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

You can use HAProxy for load balancing, there are articles about it here: <br> <br>here: <br> <br>and here: <br> <br> <br>With a single HAProxy node, this woulds still leave a single point of failure. Since DO doesn’t support floating IPs (yet) you can’t scale this up to having 2 geodiverse HAProxy nodes. That said, it’s still an improvement over round robin since an app node is far more likely to go down than a slim, hardened HAProxy node. <br> <br>You can also use nginx for load balancing (this is quite popular these days): <br> <br> <br>nginx will have the same issue that HAProxy does, in that you still have a single point of failure. <br> <br>Since DO doesn’t support floating IPs (yet), I’ll mention Amazon’s Route 53 which is capable of intelligent round robin, health checking destination nodes, and geo-diverse hosted DNS, it’s also relatively cheap: <br> <br> <br>You can use Route 53 in conjunction with DO droplets. I believe DO is working on their own implementation of floating IPs to solve the super high availability problem.