DNS SRV Failover for Network Service Load Distribution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing load balancing methods using DNS SRV records can lead to server overload and service deterioration when the penultimate available server fails, causing quality of service issues and potential server failures.
Innovation Solution
A method that determines a secondary server for failover based on load distribution data and prioritization values, allowing it to take over even when other primary servers are still available, thereby distributing network service requests and reducing server load.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If load distribution is implemented using DNS SRV records with prioritization values, then service availability is improved through failover capability, but server overload occurs when the penultimate available server fails
Solution Approach 1:
The patent applies preliminary action by pre-configuring secondary servers with failover prioritization values in DNS SRV records. When a primary server fails, the system proactively redirects traffic to secondary servers before overload occurs on remaining primary servers. This preventive redirection avoids the harmful effect of server overload while maintaining service availability.
Solution Approach 2:
The patent uses DNS SRV records as an intermediary mechanism to mediate between failed primary servers and secondary servers. The failover prioritization value in the SRV records acts as a mediator that automatically directs client devices to appropriate secondary servers, preventing direct overload on remaining primary servers while ensuring continuous service availability.
2Object-affected harmful factors
If secondary servers are used for failover when primary servers fail, then server load is reduced and overload is prevented, but configuration complexity increases
Solution Approach 1:
The patent applies self-service by enabling the DNS system to automatically manage failover configurations without requiring complex manual setup. Secondary servers are configured with failover prioritization values that allow them to self-activate when primary servers fail, reducing the need for complex manual configuration and intervention while effectively preventing server overload.
Solution Approach 2:
The patent uses parameter changes by introducing failover prioritization values as a new parameter in DNS SRV records. This parameter enables automatic failover behavior without requiring complex configuration structures. By changing the DNS record parameter set to include failover priorities, the system achieves simplified configuration while effectively distributing load and preventing server overload.
Data Source
Figure 1~2
Figure 3~4
Figure 5
AI summary
The invention relates to a method for improved load balancing with regard to the provision of a network service in a computer network, wherein the computer network comprises several servers for providing the network service to a client device, wherein the several servers comprise several primary servers, wherein the several servers comprise at least one secondary server for failover, wherein the computer network has a Domain Name System (DNS) server for providing Service Resource Record (SRV) data records, wherein the Service Resource Record (SRV) data records comprise load balancing data and prioritization data, wherein the client device is connected to the computer network for use of the network service, wherein the method comprises the following steps: -- Determining, by the client device, a first server,wherein the first server is selected from the multiple primary servers based on the load balancing data of the Service Resource Record (SRV) records, -- providing - in the event that the first server is available to provide the network service to the client device - the network service to the client device by the first server, and - in the event that the first server fails to provide the network service to the client device and another of the multiple primary servers is available to provide the network service to the client device - determining, by the client device, a second server from the at least one secondary server, wherein the second server is determined based on the load balancing data of the Service Resource Record (SRV) records from the at least one secondary server,where, if the second server is available for service use by the client device, the network service is provided to the client device by the second server.