|Publication number||WO2013165837 A1|
|Publication date||7 Nov 2013|
|Filing date||26 Apr 2013|
|Priority date||1 May 2012|
|Also published as||EP2845373A1, US9740708, US20130297596|
|Publication number||PCT/2013/38366, PCT/US/13/038366, PCT/US/13/38366, PCT/US/2013/038366, PCT/US/2013/38366, PCT/US13/038366, PCT/US13/38366, PCT/US13038366, PCT/US1338366, PCT/US2013/038366, PCT/US2013/38366, PCT/US2013038366, PCT/US201338366, WO 2013/165837 A1, WO 2013165837 A1, WO 2013165837A1, WO-A1-2013165837, WO2013/165837A1, WO2013165837 A1, WO2013165837A1|
|Inventors||Imad Mouline, Ryan Breen WILLIAM, Frans Wills TIMOTHY, Paul Smith|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (6), Classifications (7), Legal Events (2)|
|External Links: Patentscope, Espacenet|
SYSTEMS AND METHODS FOR DISTANCE AND PERFORMANCE BASED
CROSS-REFERENCE TO RELATED APPLICATIONS
 The present application claims priority to co-pending U.S. Provisional Patent Application Number 61/641,270, entitled "Systems And Methods For Distance And Performance Based Load Balancing", filed May 1, 2012, and is related to U.S. Patent Application Number 13/834,249 entitled "Systems and Methods for Cloud- Aware Domain Name System Management," filed concurrently herewith, and U.S. Patent Application Number 13/834,068, entitled "Systems and Methods for Metric-Based Cloud Management," filed concurrently herewith, the disclosures of which are hereby incorporated herein by reference.
FIELD OF THE INVENTION
 The present disclosure generally relates to DNS management, and more particularly to a DNS management system which provides routing distance and/or performance-based DNS records.
 The Domain Name System (DNS) is a hierarchical distributed naming system for computers, services, or any resource connected the Internet or a private network. A Domain Name Service translates queries for domain names (e.g., yourdomain.com) into IP addresses for the purpose of locating resources worldwide. Whereas domain names are generally understandable and easily remembered by humans, IP addresses are less memorable for humans. For example, the domain name www.example.com translates to the addresses 126.96.36.199 (Internet Protocol version 4 (IPv4)) and 2620:0:2d0:200::10 (Internet Protcol version 6 (IPv6)). The DNS makes it possible to assign domain names to groups of network resources in a meaningful way, and independent of the resources' physical locations.
 The DNS implements a distributed, hierarchical, and redundant database for information associated with Internet domain names and IP addresses. In these domain servers, different record types are used. Two of these record types are an address record (A or AAAA records) and a canonical name record (CNAME record). An A record is most commonly used to map hostnames (i.e., domain names associated with at least one IP address) with the IP address of the host. Thus, given a hostname, an A record will return an IP address. A CNAME record is an alias of a first domain name for a second domain name. Given the first domain name, a CNAME record will return the second domain name. The second domain name can then be used to look up a further domain name (if another CNAME record exists as an alias for the further domain name) or an IP address (if an A record exists for the second domain name). It should be understood that other record types exist as well. For instance, a delegation name record (DNAME record) is similar to a CNAME record, but is an alias for a domain name and all of its subdomain names.
 A simple example of a set of DNS records is illustrated in Fig. 1. When a lookup for "foo.example.com" is performed, the DNS resolver will encounter the CNAME record with a value of "bar.example.com." The resolver will then restart the lookup using "bar.example.com" and find the A record with a value of "192.0.2.23." Thus, the resolver will return the IP address 192.0.2.23.
 DNS issues arise in the context of cloud hosted services. For instance, cloud applications are generally distributed across multiple locations to improve response times and resiliency in the case of failure. From the application's perspective, it does not automatically know where it is distributed, and where the closest name server is. It is frequently the case that an enterprise is unwittingly resolving all DNS queries on a name server thousands of miles away, adding precious seconds to the query latency. This can drastically affect the enterprise's bottom line. For instance, a study by Amazon found that every 100ms of latency costs it 1% in sales. Similarly, Google reports that an extra half-second in search page generation time reduces traffic by 20%.
 The present invention is directed to systems and methods which provide DNS management operable to implement geographic redirection of end users, such as to facilitate decreased latency and/or load balancing with respect to resources distributed across multiple locations. Particularly, the system of embodiments comprises one or more DNS servers which are capable of redirecting users to country-based content delivery networks (CDNs) or the closest cloud region, availability zone, or instance, using routing via distance-based and/or performance-based ordering of DNS records. In an embodiment, the distance-based routing technique is based on a geographical distance between a server and a client.
BRIEF DESCRIPTION OF THE DRAWINGS
 The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings, in which like reference numerals refer to like parts, and in which:
 Fig. 1 illustrates an example set of resource records, according to the prior art;
 Fig. 2 is a block diagram representation of a network and an embodiment of the present invention;
 Fig. 3 is a flowchart of a process for delivering an IP address in accordance with an embodiment of the present invention;
 Fig. 4 is a flowchart of a process for delivering an IP address in accordance with another embodiment of the present invention; and
 Fig. 5 is a flowchart of a process for delivering an IP address in accordance with yet another embodiment of the present invention.
 The DNS namespace is divided in hierarchical tree-like fashion into cascading lower-level domains that are ordered as a reverse-prioritized concatenation of names. Each level is separated by a period and the levels descend in priority from right to left (e.g., sub2.subl.yourcompany.com). Administratively, each level or node in the hierarchy represents a potential boundary of authority for management of the name space. The authority over each level of the name space is delegated to an entity, such as a top-level country's domain registry, or a company or individual registered to use a given sub-domain. These administrative spaces or portions of the DNS are called "DNS zones." DNS zones may consist of only one domain, or may comprise many domains and sub-domains, depending on the administrative authority delegated to the manager. DNS zones are expressed by database elements (e.g., zone files) that are used to technically administer a zone in a DNS management system, for example, using resource records, as discussed above.
|0015] In an embodiment, a DNS management system for a DNS zone is provided which utilizes a novel routing algorithm via distance-based and/or performance-based DNS record ordering. Referring to Fig. 2, the DNS management system 204 is coupled through a network (e.g., Internet 206) to one or more clients, or users, 202, one or more geographically local servers 208, and one or more geographically distant servers 210. The DNS management system 204 may comprise one or more servers, hardware processors, memories, applications, software modules, and/or any number of other hardware or software resources. A network monitor 212 may be coupled to the network 206 to monitor the performance of the local servers 208 and distant servers 210.
 Using a distance-based ordering of DNS records, visiting users may be sent to the geographically closest server node, regardless of their country of origin. In other words, the DNS record (e.g., A or AAAA record) returned to the user is based on the user's geographic location. This provides geographic optimization for load-balancing groups. The distance-based algorithm for selecting DNS records can be used in place of conventional techniques to select and provide DNS records corresponding to load- balancing groups which are geographically closest to the end user, in a completely hands off manner. In an embodiment, load-balancing groups which are equidistant or near- distant to each other can be selected in a round-robin fashion.
 The IP address of the servers being serviced by the DNS management system are often known to the system from their associated DNS entries. Furthermore, the IP address of the querying client is also often known to the DNS management system. By accessing a database of IP address location records (which may comprise millions of such records), the DNS management system can determine with a high degree of accuracy the geographic locations of both the requested server and the requesting client. The geographic location information may also be obtained from geo-location information provided by a user device (e.g., GPS functionality). In an embodiment, the DNS management system can calculate an approximate distance between the client and server based on latitude and longitude coordinates.  Conventional DNS providers approximate the locations of users based on which server the user lands on, due to performance overhead. For instance, many conventional providers use the Internet's natural routing to determine if a user is local to a specific server, and separate the Internet into "zones" based on this routing. However, this natural zone routing technique is often inaccurate since providers will often choose financially economical routes for their data, rather than the closest and highest performance routes, which typically cost more. For example, a user located on the West Coast may be routed to a DNS server located on the East Coast for financial reasons, even though there are closer DNS servers. In the conventional natural zone routing technique, the DNS server will inaccurately assume that the user is located on the East Coast and return DNS records, such as an A record, associated with an East Coast server, even though there may be a closer and better performing server for the user.
(0019] In an embodiment, the DNS management system uses a distance-based routing method to determine which DNS records to deliver to a user. In this method, the DNS management system stores the geographic locations of the IP addresses referenced in the resource records in a memory of the DNS server. This means that the overhead is small and scalable. In an embodiment, the disclosed DNS management system uses a lookup table of IP addresses and their corresponding geographic ownership records to determine the geographic location of the user. This information is used to determine the geographically closest server node. The lookup table may be held in memory in a special, compact, binary format to enable very fast lookup.
 Rather than making assumptions regarding the location of the user based on which server receives a request like the conventional natural zone routing techniques, the distance-based routing technique relies upon accurate information regarding the geographical location of the user. Thus, the disclosed distance-based routing method provides a more accurate, although generally significantly more complex and more load- intensive, means for routing traffic than conventional natural zone routing methods.
 Fig. 3 illustrates the distance-based routing method of translating queries for domain names into IP addresses, which may be performed in the processor and logic of the DNS management system 204 shown in Fig. 2. In step 302, a request is received from a client for an IP address associated with a domain name. The client has an associated client IP address. In step 304, a database of IP address location records is queried to determine a geographic location of the client. Alternatively, the geographic location of the client may be determined based on geo-location information provided by a user device. Based on the location of the client, a list of DNS records of available servers is formed according to geographic proximity. In step 306, the ordered list of DNS record is served to the client. In an embodiment, the DNS management system calculates a geographic distance between the client and server based on latitude and longitude coordinates to determine the geographic proximity to available servers.
 In another embodiment illustrated in Fig. 4, the DNS management system serves DNS records which are ordered based on the performance of available servers. The method illustrated in Fig. 4 may be performed in the processor and logic of the DNS management system 204 shown in Fig. 2. As seen in Fig. 4, the performance of locally available servers is monitored to determine the performance of available servers (step 402). The performance may be measured using conventional metrics, such as availability, response time, etc. In an embodiment, the performance of potential local servers may be monitored using metrics obtained using a network monitoring server 212 or an application which periodically probes the available servers. The network monitoring server may be an external performance monitoring source (e.g., Pingdom, Gomez, and Neustar Webmetrics), which monitors performance as seen by clients, therefore taking into account actual routing, network node performance, etc.
 A request for an IP address associated with a domain name is received from a client (step 404), and a list of DNS records sorted in order of performance is delivered to the requesting client (step 406).
 The performance-based DNS records may be used instead of or in addition to distance-based DNS records, as illustrated in Fig. 5. The method of Fig. 5 may be performed in the processor and logic of the DNS management system 204 shown in Fig. 2. In step 502, the performance of available servers is monitored to determine the performance of available servers in the same manner as previously described. In step 504, a request is received from a client for an IP address associated with a domain name. The client has an associated client IP address. In step 506, the client IP address is used to query a database of IP address location records to determine a geographic location of the client. In step 508, the geographic location is used to determine an ordered list of distance-based routing DNS records corresponding to the geographically closest server node.
 In step 510, the DNS management system selects whether to deliver the distance-based DNS records or the performance-based DNS records. The selection of which record to deliver can be based on certain criteria, such as performance, cost, load balancing, etc. For instance, in one embodiment, the system defaults to providing distance-based DNS records and delivers the performance-based DNS records if the monitoring software indicates that a more geographically distant server will provide better performance to the client. In this instance, the performance-based DNS records may be selected only if it improves performance by a certain threshold as compared to the distance-based routing DNS records. For instance, the system may deliver the performance-based DNS records only if response time is improved by a certain amount. Alternatively, the system may select the performance-based DNS records in view of other considerations, such as load balancing and/or financial issues, even if the distance- based DNS records would deliver equal or better performance than the performance- based DNS records.
 In step 512, the DNS management system delivers the selected DNS records to the client.
 Those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and method steps described in connection with the above described figures and the embodiments disclosed herein can often be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled persons can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. In addition, the grouping of functions within a module, block, circuit or step is for ease of description. Specific functions or steps can be moved from one module, block or circuit to another without departing from the invention.
 Moreover, the various illustrative logical blocks, modules, and methods described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor ("DSP"), an ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
 Additionally, the steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium including a network storage medium. An exemplary storage medium can be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can also reside in an ASIC.
 The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles described herein can be applied to other embodiments without departing from the spirit or scope of the invention. Thus, it is to be understood that the description and drawings presented herein represent a presently preferred embodiment of the invention and are therefore representative of the subject matter which is broadly contemplated by the present invention. It is further understood that the scope of the present invention fully encompasses other embodiments that may become obvious to those skilled in the art and that the scope of the present invention is accordingly limited by nothing other than the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US7653700 *||16 Nov 2000||26 Jan 2010||Microsoft Corporation||System and method for performing client-centric load balancing of multiple globally-dispersed servers|
|US20040210670 *||11 May 2004||21 Oct 2004||Nikolaos Anerousis||System, method and apparatus for network service load and reliability management|
|US20090132648 *||26 Jan 2009||21 May 2009||Eric Sven-Johan Swildens||Content delivery and global traffic management network system|
|US20110055312 *||28 Aug 2009||3 Mar 2011||Apple Inc.||Chunked downloads over a content delivery network|
|US20110093522 *||21 Oct 2009||21 Apr 2011||A10 Networks, Inc.||Method and System to Determine an Application Delivery Server Based on Geo-Location Information|
|US20120079115 *||28 Sep 2010||29 Mar 2012||Richardson David R||Request routing in a networked environment|
|Cooperative Classification||H04L67/1021, H04L67/1008, H04L61/609, H04L61/1511, G06F17/3087, G06F17/30241|
|1 Jan 2014||121||Ep: the epo has been informed by wipo that ep was designated in this application|
Ref document number: 13784559
Country of ref document: EP
Kind code of ref document: A1
|3 Nov 2014||NENP||Non-entry into the national phase in:|
Ref country code: DE