MANAGING TRAFFIC-OVERLOAD ON A SERVER
First Claim
1. A method for managing traffic-overload in a DNS server during a network overload, the method comprising:
- monitoring traffic associated with the DNS server, wherein the traffic includes at least one of a plurality of requests received by the DNS server and a plurality of responses transmitted by the DNS server;
identifying an occurrence of an event to trigger a rescue mode, wherein the rescue mode enables implementation of at least one policy for handling of the traffic associated with the DNS server; and
implementing the at least one policy upon occurrence of the event, for handling the traffic, wherein the at least one policy comprises;
segregating the plurality of requests into a first set of requests, a second set of requests, and a third set of requests based on availability of responses in a cache corresponding to the plurality of requests, and a Time to Live (TTL) associated with the responses, wherein the cache is associated with the DNS server;
processing, without communicating with a backend server, the first set of requests from amongst the plurality of requests for which a first set of responses stored in a cache has expired based on the TTL, wherein the first set of responses include at least one response each request from amongst the first set of requests; and
transmitting the first set of responses to a plurality of client devices, wherein the first set of responses includes expired data.
1 Assignment
0 Petitions
Accused Products
Abstract
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 and implementing one or more policies for handling the traffic during the rescue mode. In implementing the one or more policies, the method includes segregating the traffic into three sets of requests based on availability of responses in a cache, and a Time to Live
(TTL) associated with the responses. Further, the method includes processing a first set of requests for which corresponding responses stored in the cache have expired based on TTL of corresponding responses. Furthermore, the method includes transmission of the corresponding responses with expired data to the client devices.
-
Citations
14 Claims
-
1. A method for managing traffic-overload in a DNS server during a network overload, the method comprising:
-
monitoring traffic associated with the DNS server, wherein the traffic includes at least one of a plurality of requests received by the DNS server and a plurality of responses transmitted by the DNS server; identifying an occurrence of an event to trigger a rescue mode, wherein the rescue mode enables implementation of at least one policy for handling of the traffic associated with the DNS server; and implementing the at least one policy upon occurrence of the event, for handling the traffic, wherein the at least one policy comprises; segregating the plurality of requests into a first set of requests, a second set of requests, and a third set of requests based on availability of responses in a cache corresponding to the plurality of requests, and a Time to Live (TTL) associated with the responses, wherein the cache is associated with the DNS server; processing, without communicating with a backend server, the first set of requests from amongst the plurality of requests for which a first set of responses stored in a cache has expired based on the TTL, wherein the first set of responses include at least one response each request from amongst the first set of requests; and transmitting the first set of responses to a plurality of client devices, wherein the first set of responses includes expired data. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A DNS server for managing traffic-overload, the DNS server comprising:
-
a processor; a traffic monitoring module coupled to the processor, wherein the traffic monitoring module is to monitor traffic associated with the DNS server, wherein the traffic includes at least one of a plurality of requests received by the DNS server and a plurality of responses transmitted by the DNS server; an analytics module coupled to the processor, wherein the analytics module is to; identify an occurrence of an event to trigger a rescue mode, wherein the rescue mode enables implementation of at least one policy for handling of the traffic associated with the DNS server; and implement the at least one policy upon occurrence of the event, for handling the traffic, wherein the at least one policy comprises; segregate the plurality of requests into a first set of requests, a second set of requests, and a third set of requests based on availability of responses in a cache corresponding to the plurality of requests, and a Time to Live (TTL) associated with the responses, wherein the cache is associated with the DNS server process without communicating with a backend server, the first set of requests from amongst the plurality of requests for which a first set of responses stored in a cache has expired based on the TTL, wherein the first set of responses include at least one response for each request from amongst the first set of requests; a communication module coupled to the processor, wherein the communication module is to transmit the first set of responses to a plurality of client devices, wherein the first set of responses includes expired data. - View Dependent Claims (11, 12, 13, 14)
-
Specification