Round Robin DNS Load Balancer
There are many different methods for Load Balancing between Servers and Services. For example, hardware can be used
(Kemp LoadMaster, Riverbed, BigIP F5, Netscaler vs.) or software solutions can be used.
I would like to talk about the DNS Round Robin feature, which is a frequently used method today.
As you all know, more than one partner server is set up for the continuity of the services, especially on the Internet.
A problem will arise here.
Clients send a query to DNS server to access these services such as web server, if DNS server client
If he always returns to his queries with the same IP address, an incredible band contraction (traffic) will occur on that service. This is where the DNS Round Robin (Load Balancing) feature comes into play.
Round Robin; DNS works with the method of entering more than one A (Host) Record for the same domain. And the system shares the incoming requests to the servers. In fact, what we call apportionment is that it is done with the Round Robin algorithm, not according to the current load situation. The algorithm queues the servers and sends the incoming request to the first server and sends that server to the back. In this way, the requests are distributed to the servers. The request is sent even if the server is not currently running.
Activating the first DNS – Round Robin feature:
Then we create a zone called (test.guler.com) on the DNS server:
Then you will enter the IP addresses of your partner servers in your Zone record that you have created on DNS (test.guler.com):
That's the deal. After that, you will test Round Robin by pinging from different devices and you will see that each request is directed to different ip addresses.
Umarım faydalı olmuştur. – I hope it was helpful.