Dynamic DNS Traffic Control for Server Availability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional DNS systems do not effectively monitor the availability of application servers, leading to inefficient traffic distribution and potential service delays when servers malfunction or become unavailable.
Innovation Solution
A dynamic traffic controller is introduced to monitor the operational status of application servers and dynamically update DNS server information to direct traffic to healthy servers, using protocols like SNMP and RFC for communication and zone data management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DNS server returns IP addresses based on static zone data without monitoring server availability, then DNS query resolution is simple and fast, but service availability deteriorates when application servers malfunction or become unavailable
Solution Approach 1:
The system performs preliminary actions by having application servers proactively send notifications to the DNS server about their operational status changes before clients query for their IP addresses. This allows the DNS server to maintain an updated mapping between domain names and available servers without needing to actively monitor each server's status, thus improving reliability while avoiding complex monitoring mechanisms.
Solution Approach 2:
The system implements feedback by establishing a notification mechanism where application servers automatically inform the DNS server when they become unavailable or come back online. This feedback loop ensures the DNS server always has current information about server availability, allowing it to direct traffic only to healthy servers and thereby improve service reliability.
2Reliability
If DNS server monitors the condition of all application servers to ensure availability, then service availability improves, but system complexity and resource consumption increase
Solution Approach 1:
The system applies self-service by making application servers responsible for reporting their own operational status to the DNS server. Instead of the DNS server actively monitoring each application server, the application servers autonomously notify the DNS server of their availability changes. This reduces the monitoring burden and resource consumption of the DNS server while maintaining accurate availability information.
Solution Approach 2:
Application servers perform preliminary actions by proactively sending availability notifications to the DNS server before clients need to access them. This allows the DNS server to have up-to-date information without needing to continuously query or monitor server status, thereby reducing resource consumption while maintaining reliability.
3Reliability
If backup servers are deployed with separate domain names, then service reliability improves during primary server failure, but user access time increases due to multiple DNS queries
Solution Approach 1:
The system merges the primary and backup servers under a single domain name in the DNS zone data, rather than using separate domain names. This allows the DNS server to resolve a single domain name to multiple IP addresses (both primary and backup servers), enabling clients to access either server through one DNS query. This maintains service continuity while reducing access time by eliminating the need for multiple sequential DNS queries.
Solution Approach 2:
The system implements dynamic server selection by maintaining multiple IP addresses for the same domain name in the DNS zone data. The DNS server can dynamically direct clients to either the primary or backup server based on current availability information, allowing flexible load distribution and failover without requiring clients to know or query multiple domain names, thus reducing access time while maintaining reliability.
4Productivity
If multiple IP addresses are returned for load balancing, then traffic distribution improves, but traffic may still be directed to overloaded or unavailable servers
Solution Approach 1:
The system implements feedback by having application servers automatically notify the DNS server of their operational status and load conditions. The DNS server uses this feedback information to intelligently select which IP addresses to return in response to DNS queries. This ensures that traffic is distributed to healthy, available servers while avoiding overloaded or malfunctioning ones, thereby improving both traffic distribution efficiency and routing accuracy simultaneously.
Data Source
AI summary
Method and system for a domain name translation service. A plurality of application servers associated with at least one domain name corresponding to at least one Internet Protocol (IP) address are provided. A domain name system (DNS) server hierarchy is configured for providing, based on DNS translation information associated with the requested domain name stored therein, an IP address or a list of IP addresses of the associated application server(s) as a response to a DNS query for a domain name. In addition, a dynamic traffic controller is configured for monitoring the operational status of the application servers and requesting a DNS update to the DNS translation information stored in the DNS server hierarchy based on the operational status of the application servers.