I see what you mean. However the availability checking should be done by the load balancer, not the client side.
The client simply asks a DNS server to resolve a domain to an IP so it can access it; the DNS server then answers the client with an IP of a server that's optimal for the client (based on location, server load etc). But normally there are layers of load balancing going on and you combine these two types of methods, so the DNS server in that case returns the IP of a load balancer server, and the load balancer server relays/forwards the user requests to the actual, hidden end servers.
I was answering to your second solution where the dns resolves to multiple ip. A ha loadbalancer is a must have if you need to send load to multiple servers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I see what you mean. However the availability checking should be done by the load balancer, not the client side.
The client simply asks a DNS server to resolve a domain to an IP so it can access it; the DNS server then answers the client with an IP of a server that's optimal for the client (based on location, server load etc). But normally there are layers of load balancing going on and you combine these two types of methods, so the DNS server in that case returns the IP of a load balancer server, and the load balancer server relays/forwards the user requests to the actual, hidden end servers.
I was answering to your second solution where the dns resolves to multiple ip. A ha loadbalancer is a must have if you need to send load to multiple servers.