Electrical computers and digital processing systems: multicomput – Computer network managing – Computer network access regulating
Reexamination Certificate
2000-08-11
2004-06-22
Vu, Viet D. (Department: 2154)
Electrical computers and digital processing systems: multicomput
Computer network managing
Computer network access regulating
C709S219000, C709S226000, C709S227000
Reexamination Certificate
active
06754706
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Technical Field
The invention relates to Internet protocol networking in a computer environment. More particularly, the invention relates to the routing and load balancing of traffic in a Domain Name System in a computer environment.
2. Description of the Prior Art
Global traffic management systems are at the beginning formulative stages of development. Most systems do not have to manage a large amount of traffic. The systems either do not deal with persistence or synchronization of DNS servers or, if they do, they perform the tasks in a very inefficient and cumbersome way by shipping huge tables between servers.
Domain Name System (DNS) servers in the Internet and in Intranets are sent requests to determine machine IP addresses associated with a given name. DNS servers can perform load balancing by returning different IP addresses for different requests to a server and can also be modified to return IP addresses that are close to an end user in terms of latency.
For example, assume three IP addresses 1.1.1.1, 1.1.1.2 and 1.1.1.3 are valid IP addresses for www.speedera.com. When a DNS server receives a request for the IP address of www.speedera.com, it could return 1.1.1.1 for the first request, 1.1.1.2 request for the second address, etc. This would cause requests for www.speedera.com to be distributed among the three IP addresses and among three machines, if each IP address represents a different machine.
If the DNS server has access to information about the load on the three machines, it could return IP addresses based on machine load to perform load balancing intelligently. Also, if a DNS server has access to information about the latency between various points on the network, it can determine which IP address(es) to return based on the latency between the machine with that IP address and the machine where the request came from.
These features are commonly used in combination to create an advanced load balancing DNS server. More advanced DNS servers can provide support for “persistence”. Some services, such as web shopping carts, require persistence.
“Persistence” is when the first time a request is made for an IP address of a hostname from a given user, a persistent entry is stored on the server that ties that user to the IP address. Subsequent requests from the same user for the IP address of the domain name first requested will return the same IP address that was returned the first time, as long as that IP address can handle the request.
To handle persistence, a DNS server can maintain a table that contains a mapping of machine IP addresses and hostnames to IP addresses. When processing a DNS request, the DNS server consults the table to determine if a persistent entry exists that ties a machine IP address (identifying a group of users) and hostname to IP address.
Persistent tables can be very large. Typically, when multiple DNS servers manage a hostname, each individual server needs access to the persistence table. This leads to a significant amount of network traffic overhead when the tables are kept synchronized between multiple servers.
Most existing approaches simply do not allow more than one load balancing DNS server to be authoritative for a given domain name when using persistence. Persistence is supported when only a single DNS server is authoritative for a given domain name in these approaches.
Other existing solutions that support persistence when more than one DNS server is authoritative for a given domain name, work by keeping all the persistence tables in the authoritative DNS servers synchronized. When a persistent entry is added or deleted, it must be added or deleted to all DNS servers that are authoritative for a given domain name.
Similarly, latency tables and other tables that are keyed off a user group (Client DNS Server) are either kept in a single location or are synchronized across multiple servers where the full latency table is kept on each server.
It would be advantageous to provide a scalable domain name system with persistence and load balancing that provides both persistence and load balancing on a DNS server and reduces the amount of information stored on the server. It would further be advantageous to provide a scalable domain name system with persistence and load balancing that reduces the traffic across the network when table synchronization is used.
SUMMARY OF THE INVENTION
The invention provides a scalable domain name system with persistence and load balancing. The system performs both load balancing and persistence tracking on a DNS server while reducing the amount of information stored on the DNS server. In addition, the invention reduces network traffic required for information synchronization between DNS servers.
A preferred embodiment of the invention receives requests from client DNS servers or other DNS servers. The invention checks to see if the client DNS server is part of the DNS group that the DNS server is authoritative. Each DNS server is associated with a subset of the DNS groups in the network.
If the DNS server is not authoritative for the client DNS server's group, then the request is forwarded to the proper DNS server. Otherwise, the invention checks a persistence table to see if a persistent response is required for the request. If a persistent response is required, the appropriate IP address entry in the table is returned to the requester.
If a persistent response is not required, the invention determines the load, availability, and latency of the content servers from information stored in a latency table to determine the proper content server to reference. The proper content servers address is returned to the requestor.
The DNS server sends any responses to forwarded requests to the client DNS server.
When more than one DNS server is authoritative for an overlapping DNS group, the invention ensures that the persistence and latency tables are synchronized with any other DNS servers. The invention also allows the persistence and latency tables to be located on a set of table servers within the network.
Another aspect of the invention allows the DNS server that a request is forwarded to, to respond directly to the client. The client is redirected to the DNS server.
REFERENCES:
patent: 5729689 (1998-03-01), Allard et al.
patent: 5774660 (1998-06-01), Brendel et al.
patent: 5918228 (1999-06-01), Rich et al.
patent: 6029196 (2000-02-01), Lenz
patent: 6052718 (2000-04-01), Gifford
patent: 6070191 (2000-05-01), Narendran et al.
patent: 6078943 (2000-06-01), Yu
patent: 6092178 (2000-07-01), Jindal et al.
patent: 6112239 (2000-08-01), Kenner et al.
patent: 6118765 (2000-09-01), Phillips
patent: 6119171 (2000-09-01), Alkhatib
patent: 6128279 (2000-10-01), O'Neil et al.
patent: 6173311 (2001-01-01), Hassett et al.
patent: 6182148 (2001-01-01), Tout
patent: 6249801 (2001-06-01), Zisapel et al.
patent: 6292832 (2001-09-01), Shah et al.
patent: 6381627 (2002-04-01), Kwan et al.
patent: 6405252 (2002-06-01), Gupta et al.
patent: 6415323 (2002-07-01), McCanne et al.
patent: 6430619 (2002-08-01), Sitaraman et al.
patent: 6449647 (2002-09-01), Colby et al.
patent: 6546014 (2003-04-01), Kramer et al.
patent: 6560717 (2003-05-01), Scott et al.
patent: 0817020 (1998-01-01), None
patent: 0959601 (1999-11-01), None
patent: WO 99/29083 (1999-06-01), None
patent: WO 00/22526 (2000-04-01), None
Schemers, R.J., “Ibnamed: A Load Balancing Name Server in Perl,” Proceedings of the Systems Administration Conference, Sep. 17, 1995, pp. 1-11, XP002054865 p. 2, left-hand column, para 3; p. 3, left-hand column, para 1.
Y. Rekhter, Oct. 1991, IBM Corpl, www.faqs.org/rfcs/rfc1265.html, pp. 1-7.
Bhattachjarjee, S. et al., “Application-Layer Anycasting,” Proceedings of the IEEE Infocom '97, 4/7-12, 1997, vol. 3, Apr. 7, 1997.
Moore, et al., “Sonar-a Network Proximity Service,” IETF Internet Draft, Feb. 23, 1996, p. 1, para. 2-4, p. 5, para 1, p. 6, para 4-p. 7 para 2.
Guyton, et al., “Locating Nearby Copies of Replicated Internet Services”; Computer Communications Review, Association For Computing Machin
Day Richard David
Garg Vikas
Swildens Eric Sven-Johan
Hickman Palermo & Truong & Becker LLP
Speedera Networks, Inc.
Vu Viet D.
Wong Kirk D.
LandOfFree
Scalable domain name system with persistence and load balancing does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Scalable domain name system with persistence and load balancing, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Scalable domain name system with persistence and load balancing will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3312349