ROUTING CLIENT REQUESTS

• US 20140304386A1
• Filed: 06/16/2014
• Published: 10/09/2014
• Est. Priority Date: 02/02/2011
• Status: Abandoned Application

• Current Assignee: Fortinet Inc.
• Original Assignee: Fortinet Inc.
• Inventors: Lyon, Barrett Gibson
• Application Number:
  US14/306,176
• Publication Number:
  US 20140304386A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories

Abstract

Methods and systems for routing client requests are provided. According to one embodiment, a request handling server facilitates servicing of client requests for content published by a content publisher. A Domain Name System (DNS) service and a web service are provided by the request handling server. A rule for managing services provided by the request handling server to the content publisher is obtained by the request handling server. One or both of the DNS service and the web service are enabled by the request handling server for the content publisher based on the rule.

Claims

1. A method comprising:

providing, by a request handling server, a Domain Name System (DNS) service and a web service;

obtaining, by the request handling server, a rule for managing services provided by the request handling server to a content publisher; and

enabling, by the request handling server, one or both of the DNS service and the web service for the content publisher based on the rule.

2. The method of claim 1, further comprising:

obtaining, by the request handling server, a ruleset for managing traffic of the content publisher;

receiving, by the request handling server, a request associated with the content publisher;

when the received request comprises a content request, then directly servicing, by the request handling server, the request or redirecting, by the request handling server, the request to another server capable of handling the request based on the ruleset; and

when the received request comprises a DNS request, then responding to the DNS request, by the request handling server, with a DNS response based on the ruleset.

3. The method of claim 2, wherein the ruleset is generated by a rules engine of the request handling server based on various inputs.

4. The method of claim 3, wherein the various inputs comprise one or more of an algorithm to identify a least cost option for servicing requests associated with the content publisher, log feeds of the content publisher and monitored network data.

5. The method of claim 4, wherein the monitored network data comprises average throughput, latency and time to first byte in a given geographical region.

6. The method of claim 4, wherein the algorithm is based at least in part on one or more of a required Quality of Service (QoS), security specifications, cost constraints, geographical specifications and associated content delivery networks (CDNs).

7. The method of claim 2, wherein the DNS response comprises one or more of an Internet Protocol (IP) address, a canonical name (CNAME) record and a name server (NS) record.

8. The method of claim 2, wherein the DNS response comprises an IP address of a content server, a content delivery network (CDN) or the request handling server.

9. The method of claim 1, wherein the rule for managing services provided by the request handling server to a content publisher is based on a geographical region of the request handling server.

12. The request-handling server of claim 2, wherein the ruleset is generated by a rules engine of the request handling server based on various inputs.

13. The request-handling server of claim 12, wherein the various inputs comprise one or more of an algorithm to identify a least cost option for servicing requests associated with the content publisher, log feeds of the content publisher and monitored network data.

14. The request-handling server of claim 13, wherein the monitored network data comprises average throughput, latency and time to first byte in a given geographical region.

15. The request-handling server of claim 13, wherein the algorithm is based at least in part on one or more of a required Quality of Service (QoS), security specifications, cost constraints, geographical specifications and associated content delivery networks (CDNs).

10. A request-handling server comprising:

a non-transitory storage device having tangibly embodied therein one or more routines operable to facilitate servicing of client requests for content published by a content publisher; and

one or more processors coupled to the non-transitory storage device and operable to execute the one or more routines to perform a method comprising;

providing a Domain Name System (DNS) service and a web service;

obtaining a rule for managing services provided to the content publisher; and

enabling one or both of the DNS service and the web service for the content publisher based on the rule.

11. The request-handling server of claim 10, wherein the method further comprises:

obtaining a ruleset for managing traffic of the content publisher;

receiving a request associated with the content publisher;

when the received request comprises a content request, then directly servicing the request or redirecting the request to another server capable of handling the request based on the ruleset; and

when the received request comprises a DNS request, then responding to the DNS request with a DNS response based on the ruleset.

16. The request-handling server of claim 11, wherein the DNS response comprises one or more of an Internet Protocol (IP) address, a canonical name (CNAME) record and a name server (NS) record.

17. The request-handling server of claim 11, wherein the DNS response comprises an IP address of a content server, a content delivery network (CDN) or the request handling server.

18. The request-handling server of claim 10, wherein the rule for managing services provided by the request handling server to a content publisher is based on a geographical region of the request handling server.