Domain name resolution making IP address selections in response to connection status when multiple connections are present

• US 20090182884A1
• Filed: 03/25/2009
• Published: 07/16/2009
• Est. Priority Date: 12/29/2000
• Status: Active Grant

• Current Assignee: Fatpipe Networks Private Ltd.
• Original Assignee: Ragula Systems Incorporated
• Inventors: Ragula, Bhaskar, Datta, Sanchaita
• Granted Patent: US 7,877,510 B2
• Time in Patent Office: Days
• US Class Current: 709/228
• CPC Class Codes: H04L 2101/604 Address structures or formats
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

Methods, configured storage media, and systems are provided for resolving domain names into IP addresses in a path-sensitive manner, namely, a manner that may consider information about a link to a server and/or information about routers and other path components. The IP addresses given in response to domain name resolution requests are selected to provide increased reliability and/or dynamic load-balancing over paths.

Claims

1-21. -21. (canceled)

22. A method for distributing domain name resolution results to at least two servers over at least two paths, the method comprising the steps of:

receiving domain name resolution requests which each request an IP address corresponding to a specified domain name;

selecting between at least two IP addresses based on at least status information of connection components which are neither servers nor clients, the connection components located on respective paths to the at least two servers;

supplying a selected IP address in response to each request, thereby directing traffic over at least two paths through respective connection components; and

over-loading at least one of the servers even though traffic load is distributed over at least two paths to the over-loaded server.

23. The method of claim 22, further comprising setting a domain name time-to-live value before supplying the selected IP address.

24. The method of claim 22, further comprising providing code to aid administration including at least one of the following:

code for maintaining a log, code for sending an alert to a system administrator, authentication code, security code.

25. The method of claim 22, further comprising adding an address to a server for multi-homing.

26. The method of claim 22, wherein the status information includes at least one of:

whether a given router answered a ping, and when a given router was last pinged.

27. The method of claim 22, wherein the status information includes at least an obtained status of a connection component which includes at least one of the following:

a firewall, a bridge, a switch, a packet shaper.

28. A connection-sensitive domain name resolution device, comprising:

a data component identifying IP addresses for at least two paths to each of at least two servers which share a domain name;

a code component which receives a domain name resolution request specifying the domain name, selects an IP address from the data component based on information about the status of paths to the servers, and supplies the selected IP address in response to the domain name resolution request, the IP address selection based on status information about connection components on the paths, and over-loads at least one of the servers even though traffic load is distributed over at least two paths to the over-loaded server.

29. The device of claim 28, wherein IP addresses in the data component identify routers on paths to the servers, and the code component avoids selecting the IP address of a router that is on a path to a server but is not available.

30. The device of claim 28, wherein the connection component acts as at least one of the following:

a firewall, a bridge, a switch, a packet shaper.

31. The device of claim 28, wherein the code component selects the IP address of an under-loaded path, thereby tending to balance the loads on the paths to the over-loaded server.

32. The device of claim 28, in combination with a router.

33. The device of claim 28, in combination with three routers on the paths to the servers.

34. A computer-readable storage medium having a configuration that will cause performance of a method for connection-sensitive domain name resolution when multiple connections to multiple web servers are potentially available, the method comprising:

receiving a domain name resolution request which requests an IP address corresponding to a specified domain name;

selecting an IP address based on status information about a connection component which is neither a server nor a client, the connection component acting instead as at least one of the following;

a router, a firewall, a bridge, a switch, a packet shaper;

supplying the selected IP address in response to the request, thereby directing traffic over a path through the connection component; and

over-loading one of the web servers even though traffic load is distributed over at least two paths to the over-loaded server.

35. The configured medium of claim 34, wherein the method comprises adjusting the time-to-live to be associated with a DNS record for an IP address in a path to the over-loaded server.

36. The configured medium of claim 34, wherein the method comprises providing code to aid administration including at least one of the following:

code for maintaining a log, code for sending an alert to a system administrator, authentication code, security code.

37. The configured medium of claim 34, wherein the status information includes at least one of:

whether a given router answered a ping, and when a given router was last pinged.

38. The configured medium of claim 34, wherein the method avoids selecting the IP address of a router that is on a path to the over-loaded server but is not available.

39. The configured medium of claim 34, wherein the method selects the IP address of an under-loaded path, thereby tending to balance the loads on the paths to the over-loaded server.

40. The configured medium of claim 34, wherein the method comprises performing a router status inquiry to determine the router'"'"'s load.

41. The configured medium of claim 34, wherein the selecting step comprises determining whether a connection responds to pings.