DNS Server Rescue Mode for Traffic Overload Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing techniques for managing traffic overload on DNS servers are complex, resource-intensive, and ineffective in handling network attacks, particularly those caused by compromised backend or authoritative servers, leading to service disruptions and latency issues.
Innovation Solution
Implementing a 'rescue mode' in DNS servers that segregates requests based on cache availability, using Time to Live (TTL) to provide expired responses for the first set, relaying uncacheable requests to backend servers, and dynamically managing traffic to maintain service continuity during overloads.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing techniques for managing traffic overload are implemented, then service continuity may be maintained, but the system becomes complex and resource-intensive
Solution Approach 1:
The patent segments traffic into different categories (first set, second set, third set) based on cache availability and request characteristics. This segmentation allows the DNS server to apply different handling strategies to different traffic types, maintaining service continuity while avoiding the need for a single complex overload management system.
2Reliability
If traffic monitoring and management policies are implemented, then service continuity is maintained, but processing time and resource consumption increase
Solution Approach 1:
The patent performs preliminary actions by pre-segmenting traffic into different sets based on cache availability before overload occurs. The DNS server is pre-configured with policies for handling each traffic set, allowing rapid response during overload conditions without requiring complex real-time analysis, thus reducing processing time while maintaining service continuity.
3Reliability
If comprehensive traffic management is implemented, then service continuity is improved, but the system consumes more resources
Solution Approach 1:
The patent applies partial action by selectively managing different sets of traffic differently. Not all traffic requires the same level of management resources - cached requests are handled efficiently without heavy management overhead, while non-cached requests receive appropriate routing. This selective approach maintains service continuity while optimizing resource consumption.
4Productivity
If detailed traffic segregation and policy implementation are used, then request processing efficiency is improved, but device complexity increases
Solution Approach 1:
The patent applies local quality by implementing different handling characteristics for different traffic sets. Cached requests (first set) receive fast local responses, uncached requests (second set) are routed to backend servers, and other requests (third set) follow alternative paths. Each traffic set receives the quality of service appropriate to its characteristics, improving overall processing efficiency without requiring uniform complex management across all traffic.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Method(s) and System(s) for managing traffic-overload on Domain Name System (DNS) server during a network overload are described. The described system(s) may implement method(s) that include monitoring of traffic associated with the DNS server and identifying an occurrence of an event. Thereafter, activating (deactivating) a rescue mode upon identifying the occurrence of the event. The method may further include implementing one or more policies for handling traffic associated with the DNS server during the rescue mode. In implementing the one or more policies, the method includes processing a first set of requests for which corresponding responses stored in the cache have expired based on Time to Live (TTL) of corresponding responses. Furthermore, the method includes transmission of the corresponding responses with expired data to the client devices.