New! View global litigation for patent families

US20120173760A1 - Domain name resolution for a hybrid cloud cluster - Google Patents

Domain name resolution for a hybrid cloud cluster Download PDF

Info

Publication number
US20120173760A1
US20120173760A1 US12982820 US98282010A US20120173760A1 US 20120173760 A1 US20120173760 A1 US 20120173760A1 US 12982820 US12982820 US 12982820 US 98282010 A US98282010 A US 98282010A US 20120173760 A1 US20120173760 A1 US 20120173760A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
name
cloud
computer
dns
resolution
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US12982820
Inventor
Mandar U. Jog
Bart C. Vashaw
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/60Details
    • H04L61/6013Proxying of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1505Directories; Name-to-address mapping involving standard directories or standard directory access protocols
    • H04L61/1511Directories; Name-to-address mapping involving standard directories or standard directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • H04L61/1552Mechanisms for table lookup, e.g. between directories; Directory data structures; Synchronization of directories

Abstract

Embodiments of the present invention provide a method, system and computer program product for domain name resolution for a hybrid cloud cluster. In an embodiment of the invention, a method for domain name resolution for a hybrid cloud cluster includes receiving a request for name resolution in a DNS name server proxy executing in memory of a host computer in a public cloud. Thereafter, it can be determined whether or not the request for name resolution implicates a domain name within an Intranet coupled to the proxy over a communications network. Finally, the request for name resolution can be resolved in a DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet. Otherwise, the request for name resolution can be resolved in a DNS name server for the public cloud in response to determining the request not to implicate a domain name within the Intranet.

Description

    BACKGROUND OF THE INVENTION
  • [0001]
    1. Field of the Invention
  • [0002]
    The present invention relates to hybrid cloud cluster deployment and more particularly to domain name resolution in a hybrid cloud cluster.
  • [0003]
    2. Description of the Related Art
  • [0004]
    Network computing, at its core, relates to the transport of data between addressable computing endpoints in a network of computing endpoints. Integral to network computing is the universal way in which data is addressed so as to be delivered to an intended end point. In this regard, the Internet protocol (IP) is the principal communications protocol used for relaying packets of data across an internetwork using the IP suite. Responsible for routing packets across network boundaries, IP is the primary protocol that establishes the Internet. The domain name system, however, remains the enabler of global computing by bridging the complexity of the IP address with a human factors friendly domain name.
  • [0005]
    The domain name system (DNS) is a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network. The domain name system associates various information with domain names assigned to each of the participating entities. Most importantly, the domain name system translates domain names meaningful to humans into the numerical identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide. The backbone of the domain name system is the DNS server. Each domain in the DNS enjoys at least one authoritative DNS name server that publishes information about that domain and the name servers of any domains subordinate to the domain. The top of the hierarchy is served by the root name servers—specifically, the servers to query when resolving a top-level domain name (TLD).
  • [0006]
    While the architecture and operation of the DNS has become a generally understood principal of computing in respect to the Internet, managing the DNS in a hybrid cloud computing environment is not without its challenges. In this regard, cloud computing refers to Internet-based computing in which shared resources, software, and information are provided to computers and other devices on demand, analogous to the delivery of power in the municipal electricity grid. Generally, the typical cloud computing infrastructure consists of services delivered through common centers and built on host servers. Clouds often appear as single points of access for the computing needs of the consumer. Further, commercial cloud computing offerings generally are expected to meet quality of service (QoS) requirements of customers, and typically include service level agreements (SLAs).
  • [0007]
    A hybrid cloud computing environment is one that consists of both public cloud machine instances (the “public cloud”) and private cloud machine instances such as physical or virtual machines within the firewall, otherwise known as the Intranet or the private enterprise. A machine image can be securely dispensed into the public cloud and with the establishment of a secure tunnel, can be made to look as if the machine image is part of the private enterprise. It is also possible to deploy a set of machines according to some pattern, for instance a cluster can be deployed into specific public clouds. When this cluster is dispensed into the public cloud, it remains necessary for the set of machines in the public cloud to communicate with one another as well as with machines disposed within the Intranet. Thus, the machines in the public cloud must be able to resolve domain names in both the public cloud and the private enterprise.
  • [0008]
    The public cloud typically assigns machines both public and private hostnames that are resolvable to external and internal IP addresses, respectively. The internal addresses ensure internal-only resolution of addresses. Also, the private enterprise name is typically not resolvable in the Internet, but only within the Intranet. Thus, no one DNS name server can resolve both the internal names of the public cloud and also the internal names of the private enterprise. There are several ways that this difficulty has been addressed.
  • [0009]
    First, only private enterprise names have been used, but two drawbacks result: (1) all connections within the cluster now must traverse the Internet, through at least two secure pipes, and an exceptional performance penalty results large enough to likely be completely unacceptable; and (2) some services and/or ports in the public cloud instance may be configured to only accept connections from inside the public cloud, or only from outside the private enterprise. Second, the DNS name server of the public cloud has been manually configured in the cluster to be deployed. This DNS name server must parse out resolution queries for public cloud addresses to the public cloud DNS name server, and private enterprise addresses to the private enterprise DNS name server. This course of action introduces possible errors and also performance penalties.
  • BRIEF SUMMARY OF THE INVENTION
  • [0010]
    Embodiments of the present invention address deficiencies of the art in respect to DNS name server configuration for a hybrid cloud computing environment and provide a novel and non-obvious method, system and computer program product for domain name resolution for a hybrid cloud cluster. In an embodiment of the invention, a method for domain name resolution for a hybrid cloud cluster includes receiving a request for name resolution in a DNS name server proxy executing in memory of a host computer in a public cloud. Thereafter, it can be determined whether or not the request for name resolution implicates a domain name within an Intranet coupled to the proxy over a communications network. Finally, the request for name resolution can be resolved in a DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet. Otherwise, the request for name resolution can be resolved in a DNS name server for the public cloud in response to determining the request not to implicate a domain name within the Intranet.
  • [0011]
    In another embodiment of the invention, a DNS data processing system can be configured for domain name resolution for a hybrid cloud cluster. The system can include a public cloud with a DNS name server providing name resolution for name resolution requests in the public cloud. The system also can include an Intranet separated from the public cloud by a firewall, the public cloud and the Intranet forming a hybrid cloud. The Intranet further can include a DNS name server providing name resolution for name resolution requests in the Intranet. Finally, the system can include a DNS name server proxy disposed in the public cloud. The proxy can include program code enabled to determine whether or not a request for name resolution received in the proxy implicates a domain name within the Intranet and to resolve the request for name resolution in the DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet, but to resolve the request for name resolution in the DNS name server for the public cloud in response to determining the request not to implicate a domain name within the Intranet.
  • [0012]
    Additional aspects of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The aspects of the invention will be realized and attained by means of the elements and combinations particularly pointed out in the appended claims. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
  • BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS
  • [0013]
    The accompanying drawings, which are incorporated in and constitute part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. The embodiments illustrated herein are presently preferred, it being understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown, wherein:
  • [0014]
    FIG. 1 is a pictorial illustration of a process for domain name resolution for a hybrid cloud cluster;
  • [0015]
    FIG. 2 is a schematic illustration of a DNS data processing system configured for domain name resolution for a hybrid cloud cluster; and,
  • [0016]
    FIG. 3 is a flow chart illustrating a process for domain name resolution for a hybrid cloud cluster.
  • DETAILED DESCRIPTION OF THE INVENTION
  • [0017]
    Embodiments of the invention provide for domain name resolution for a hybrid cloud cluster. In accordance with an embodiment of the invention, a DNS name server proxy can be deployed as part of a cluster of virtual machines operating in a public cloud computing environment, and the machines in the cluster can be configured to route name resolution requests to the DNS name server proxy. The DNS name server proxy can enjoy a communicative linkage both with a DNS name server local to the public cloud computing environment and also a DNS name disposed behind a firewall in an Intranet. The DNS name server proxy can receive name resolution requests from the cluster of virtual machines and can resolve the requests through the use of the DNS name servers in the public cloud and the Intranet by way of the communicative linkages according to a domain for the requests. For requests implicating the Intranet, the DNS name server in the Intranet can be used. In contrast, for requests implicating domains outside of the Intranet, the DNS name server of the public cloud can be used.
  • [0018]
    In further illustration, FIG. 1 pictorially shows a process for domain name resolution for a hybrid cloud cluster. As shown in FIG. 1, a private cloud—namely an Intranet 110 protected from public access by way of a firewall 130 can subsist along with a public cloud 120. The public cloud 120 can include a local DNS name server 150. Likewise, the Intranet 110 can include a local DNS name server 140. A cluster of virtual machines 160 can be deployed into the public cloud 120. Finally, a cloud deployment management module 170 can configure and deploy a DNS name server proxy 180 into the public cloud 120 for the cluster of virtual machines 160 to resolve name resolution requests received in the public cloud for names associated with the Intranet 110 using the DNS name server 140 in the Intranet 110, but to use the DNS name server 150 in the public cloud to resolve requests for other names.
  • [0019]
    The process described in connection with the DNS name server proxy 180 of FIG. 1 can be implemented in a DNS data processing system for hybrid cloud computing. In yet further illustration, FIG. 2 schematically shows a DNS data processing system configured for domain name resolution for a hybrid cloud cluster. The system can include a public cloud 200 communicatively coupled to an Intranet 250 over communicative linkage 260 in order to form a hybrid cloud computing environment. For instance, the communicative linkage 260 can be a secure tunnel.
  • [0020]
    The public cloud can include one or more host computers 210, each with at least one processor and memory. The host computers 210 cooperatively can be managed by a cloud computing environment 220 upon which multiple different virtual machines 240 can execute in a cluster. The virtual machines 240, in turn, can manage the operation of computer program logic deployed into the cluster of virtual machines 240.
  • [0021]
    The cloud computing environment 220 also can include one or more DNS name servers 230, for example, those referenced by localhost within the cloud operating environment. Of note, a DNS name server proxy 300 also can be included in the set of virtual machines 240 and the virtual machines 240 can be configured to route name resolution requests to the DNS name server proxy 300. In this regard, the DNS name server proxy 300 can include program code such than when executed by one or more of the host computers 210, can process name resolution requests by using the DNS name server 230 of the public cloud 200 for domains external to the Intranet 250, but by using a DNS name server (not shown) within the Intranet 250 for domains internal to the Intranet 250.
  • [0022]
    In even yet further illustration of the operation of the DNS name server proxy 300, FIG. 3 is a flow chart illustrating a process for domain name resolution for a hybrid cloud cluster. Beginning in block 310, a DNS name resolution request can be received in the proxy. In decision block 320, it can be determined whether or not the request involves a domain name associated with the Intranet. If so, in block 330 a DNS name server disposed within the Intranet can be used to resolve the domain name of the resolution request. Otherwise, if the request involves a domain name not associated with the Intranet, a DNS name server for the public cloud can be used to resolve the domain name of the resolution request.
  • [0023]
    As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
  • [0024]
    Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • [0025]
    A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • [0026]
    Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, radiofrequency, and the like, or any suitable combination of the foregoing. Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language and conventional procedural programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • [0027]
    Aspects of the present invention have been described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. In this regard, the flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. For instance, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
  • [0028]
    It also will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • [0029]
    These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks. The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • [0030]
    Finally, the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
  • [0031]
    The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
  • [0032]
    Having thus described the invention of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the invention defined in the appended claims as follows:

Claims (8)

  1. 1.-4. (canceled)
  2. 5. A domain name system (DNS) data processing system configured for domain name resolution for a hybrid cloud cluster, the system comprising:
    a public cloud;
    a DNS name server providing name resolution for name resolution requests in the public cloud;
    an Intranet separated from the public cloud by a firewall;
    a DNS name server providing name resolution for name resolution requests in the Intranet; and,
    a DNS name server proxy disposed in the public cloud, the proxy comprising program code enabled to determine whether or not a request for name resolution received in the proxy implicates a domain name within the Intranet and to resolve the request for name resolution in the DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet, but to resolve the request for name resolution in the DNS name server for the public cloud in response to determining the request not to implicate a domain name within the Intranet.
  3. 6. The system of claim 1, wherein the Intranet is coupled to the proxy by way of a secure tunnel through the firewall.
  4. 7. The system of claim 1, further comprising a cluster of virtual machines disposed in the public cloud, hosting application logic, and issuing name resolution requests from the application logic to the proxy.
  5. 8. A computer program product for domain name resolution for a hybrid cloud cluster, the computer program product comprising:
    a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
    computer readable program code for receiving a request for name resolution in a domain name system (DNS) name server proxy executing in memory of a host computer in a public cloud;
    computer readable program code for determining whether or not the request for name resolution implicates a domain name within an Intranet coupled to the proxy over a communications network; and,
    computer readable program code for resolving the request for name resolution in a DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet, but resolving the request for name resolution in a DNS name server for the public cloud in response to determining the request not to implicate a domain name within the Intranet.
  6. 9. The computer program product of claim 8, wherein the Intranet is coupled to the DNS name server proxy in the public cloud over a secure tunnel.
  7. 10. The computer program product of claim 8, wherein the computer readable program code for resolving the request for name resolution in the DNS name server for the public cloud comprises computer readable program code for passing the request to localhost in the public cloud.
  8. 11. The computer program product of claim 8, wherein the computer readable program code for receiving a request for name resolution in a DNS name server proxy executing in memory of a host computer in a public cloud, comprises computer readable program code for receiving a request from logic executing in a cluster of virtual machines in a public cloud for name resolution in a DNS name server proxy executing in memory of a host computer in the public cloud.
US12982820 2010-12-30 2010-12-30 Domain name resolution for a hybrid cloud cluster Abandoned US20120173760A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12982820 US20120173760A1 (en) 2010-12-30 2010-12-30 Domain name resolution for a hybrid cloud cluster

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US12982820 US20120173760A1 (en) 2010-12-30 2010-12-30 Domain name resolution for a hybrid cloud cluster
US13407114 US9363229B2 (en) 2010-12-30 2012-02-28 Domain name resolution for a hybrid cloud cluster

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13407114 Division US9363229B2 (en) 2010-12-30 2012-02-28 Domain name resolution for a hybrid cloud cluster

Publications (1)

Publication Number Publication Date
US20120173760A1 true true US20120173760A1 (en) 2012-07-05

Family

ID=46381810

Family Applications (2)

Application Number Title Priority Date Filing Date
US12982820 Abandoned US20120173760A1 (en) 2010-12-30 2010-12-30 Domain name resolution for a hybrid cloud cluster
US13407114 Active 2033-11-04 US9363229B2 (en) 2010-12-30 2012-02-28 Domain name resolution for a hybrid cloud cluster

Family Applications After (1)

Application Number Title Priority Date Filing Date
US13407114 Active 2033-11-04 US9363229B2 (en) 2010-12-30 2012-02-28 Domain name resolution for a hybrid cloud cluster

Country Status (1)

Country Link
US (2) US20120173760A1 (en)

Cited By (55)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20130138814A1 (en) * 2011-11-30 2013-05-30 Verizon Patent And Licensing Inc. Enhanced virtualized mobile gateway in cloud computing environment
US20130173795A1 (en) * 2011-12-30 2013-07-04 Verisign, Inc. DNS Package in a Partitioned Network
US9009804B2 (en) 2012-11-30 2015-04-14 Ca, Inc. Method and system for hybrid software as a service user interfaces
US20150205470A1 (en) * 2012-09-14 2015-07-23 Ca, Inc. Providing a user interface with configurable interface components
US9130756B2 (en) 2009-09-04 2015-09-08 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9160703B2 (en) 2010-09-28 2015-10-13 Amazon Technologies, Inc. Request routing management based on network components
US9176894B2 (en) 2009-06-16 2015-11-03 Amazon Technologies, Inc. Managing resources using resource expiration data
US9185012B2 (en) 2010-09-28 2015-11-10 Amazon Technologies, Inc. Latency measurement in resource requests
US9191338B2 (en) 2010-09-28 2015-11-17 Amazon Technologies, Inc. Request routing in a networked environment
US9191458B2 (en) 2009-03-27 2015-11-17 Amazon Technologies, Inc. Request routing using a popularity identifier at a DNS nameserver
US20150333926A1 (en) * 2014-05-14 2015-11-19 International Business Machines Corporation Autonomous multi-node network configuration and self-awareness through establishment of a switch port group
US9208097B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Cache optimization
US9210235B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Client side cache management
US9237114B2 (en) 2009-03-27 2016-01-12 Amazon Technologies, Inc. Managing resources in resource cache components
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9253065B2 (en) 2010-09-28 2016-02-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9332078B2 (en) 2008-03-31 2016-05-03 Amazon Technologies, Inc. Locality based content distribution
US20160191387A1 (en) * 2011-11-11 2016-06-30 Fujitsu Limited Routing method and network transmission apparatus
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9407699B2 (en) 2008-03-31 2016-08-02 Amazon Technologies, Inc. Content management
WO2016130869A1 (en) * 2015-02-15 2016-08-18 Microsoft Technology Licensing, Llc Method and system for integrating on-premise and cloud domain name systems
US20160248625A1 (en) * 2015-02-25 2016-08-25 Aether Services, Taiwan, Ltd. Distributor private cloud management system and management method
US9444759B2 (en) 2008-11-17 2016-09-13 Amazon Technologies, Inc. Service provider registration by a content broker
US9451046B2 (en) 2008-11-17 2016-09-20 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US20160308736A1 (en) * 2013-08-26 2016-10-20 Verisign, Inc. Command performance monitoring
US9479476B2 (en) 2008-03-31 2016-10-25 Amazon Technologies, Inc. Processing of DNS queries
US9497259B1 (en) 2010-09-28 2016-11-15 Amazon Technologies, Inc. Point of presence management in request routing
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9515949B2 (en) 2008-11-17 2016-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US9544394B2 (en) 2008-03-31 2017-01-10 Amazon Technologies, Inc. Network resource identification
US9571389B2 (en) 2008-03-31 2017-02-14 Amazon Technologies, Inc. Request routing based on class
US9608957B2 (en) 2008-06-30 2017-03-28 Amazon Technologies, Inc. Request routing using network computing components
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US20170171206A1 (en) * 2015-12-14 2017-06-15 Neustar, Inc. Domain name system and method of operating using restricted channels
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9734472B2 (en) 2008-11-17 2017-08-15 Amazon Technologies, Inc. Request routing utilizing cost information
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9800539B2 (en) 2010-09-28 2017-10-24 Amazon Technologies, Inc. Request routing management based on network components
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9882767B1 (en) * 2013-07-23 2018-01-30 Zscaler, Inc. Distributed cloud-based dynamic name server surrogation systems and methods
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9930131B2 (en) 2010-11-22 2018-03-27 Amazon Technologies, Inc. Request routing processing

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8805989B2 (en) * 2012-06-25 2014-08-12 Sungard Availability Services, Lp Business continuity on cloud enterprise data centers

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080086574A1 (en) * 2006-10-05 2008-04-10 Limelight Networks, Inc. Remote Domain Name Service
US20100186079A1 (en) * 2009-01-20 2010-07-22 Microsoft Corporation Remote access to private network resources from outside the network
US20100250668A1 (en) * 2004-12-01 2010-09-30 Cisco Technology, Inc. Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device
US20110055385A1 (en) * 2009-08-31 2011-03-03 Accenture Global Services Gmbh Enterprise-level management, control and information aspects of cloud console
US20110320598A1 (en) * 2010-06-28 2011-12-29 Bmc Software, Inc. System and Method for Offering Virtual Private Clouds within a Public Cloud Environment
US8140669B2 (en) * 2009-08-31 2012-03-20 International Business Machines Corporation Resolving hostnames on a private network with a public internet server
US20120167081A1 (en) * 2010-12-22 2012-06-28 Sedayao Jeffrey C Application Service Performance in Cloud Computing

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5777989A (en) 1995-12-19 1998-07-07 International Business Machines Corporation TCP/IP host name resolution for machines on several domains
US8037168B2 (en) * 1999-07-15 2011-10-11 Esdr Network Solutions Llc Method, product, and apparatus for enhancing resolution services, registration services, and search services
US7366794B2 (en) 2001-07-13 2008-04-29 Certicom Corp. Method and apparatus for resolving a web site address when connected with a virtual private network (VPN)
US20030065785A1 (en) 2001-09-28 2003-04-03 Nikhil Jain Method and system for contacting a device on a private network using a specialized domain name server
US20100106852A1 (en) * 2007-10-24 2010-04-29 Kindig Bradley D Systems and methods for providing user personalized media content on a portable device
US7734792B2 (en) 2007-07-25 2010-06-08 Novell, Inc. Secure tunnel domain name management
US20100014536A1 (en) 2008-07-17 2010-01-21 D-Link Corporation Method for building connection channel between network terminals through dynamic domain name sarver
KR101358846B1 (en) 2008-11-17 2014-02-06 퀄컴 인코포레이티드 Remote access to local network
US20110016473A1 (en) * 2009-07-20 2011-01-20 Srinivasan Kattiganehalli Y Managing services for workloads in virtual computing environments
US8874914B2 (en) * 2010-02-05 2014-10-28 Accenture Global Services Limited Secure and automated credential information transfer mechanism
US20120131162A1 (en) * 2010-11-24 2012-05-24 Brandt Mark S Using a web service to delete dns records in a server hosting system
US8825839B2 (en) * 2010-11-24 2014-09-02 Unisys Corporation Snooping DNS messages in a server hosting system providing overlapping address and name spaces

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100250668A1 (en) * 2004-12-01 2010-09-30 Cisco Technology, Inc. Arrangement for selecting a server to provide distributed services from among multiple servers based on a location of a client device
US20080086574A1 (en) * 2006-10-05 2008-04-10 Limelight Networks, Inc. Remote Domain Name Service
US20100186079A1 (en) * 2009-01-20 2010-07-22 Microsoft Corporation Remote access to private network resources from outside the network
US20110055385A1 (en) * 2009-08-31 2011-03-03 Accenture Global Services Gmbh Enterprise-level management, control and information aspects of cloud console
US8140669B2 (en) * 2009-08-31 2012-03-20 International Business Machines Corporation Resolving hostnames on a private network with a public internet server
US20110320598A1 (en) * 2010-06-28 2011-12-29 Bmc Software, Inc. System and Method for Offering Virtual Private Clouds within a Public Cloud Environment
US20120167081A1 (en) * 2010-12-22 2012-06-28 Sedayao Jeffrey C Application Service Performance in Cloud Computing

Cited By (70)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9332078B2 (en) 2008-03-31 2016-05-03 Amazon Technologies, Inc. Locality based content distribution
US9208097B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Cache optimization
US9894168B2 (en) 2008-03-31 2018-02-13 Amazon Technologies, Inc. Locality based content distribution
US9621660B2 (en) 2008-03-31 2017-04-11 Amazon Technologies, Inc. Locality based content distribution
US9887915B2 (en) 2008-03-31 2018-02-06 Amazon Technologies, Inc. Request routing based on class
US9479476B2 (en) 2008-03-31 2016-10-25 Amazon Technologies, Inc. Processing of DNS queries
US9888089B2 (en) 2008-03-31 2018-02-06 Amazon Technologies, Inc. Client side cache management
US9571389B2 (en) 2008-03-31 2017-02-14 Amazon Technologies, Inc. Request routing based on class
US9210235B2 (en) 2008-03-31 2015-12-08 Amazon Technologies, Inc. Client side cache management
US9544394B2 (en) 2008-03-31 2017-01-10 Amazon Technologies, Inc. Network resource identification
US9407699B2 (en) 2008-03-31 2016-08-02 Amazon Technologies, Inc. Content management
US9912740B2 (en) 2008-06-30 2018-03-06 Amazon Technologies, Inc. Latency measurement in resource requests
US9608957B2 (en) 2008-06-30 2017-03-28 Amazon Technologies, Inc. Request routing using network computing components
US9444759B2 (en) 2008-11-17 2016-09-13 Amazon Technologies, Inc. Service provider registration by a content broker
US9590946B2 (en) 2008-11-17 2017-03-07 Amazon Technologies, Inc. Managing content delivery network service providers
US9451046B2 (en) 2008-11-17 2016-09-20 Amazon Technologies, Inc. Managing CDN registration by a storage provider
US9734472B2 (en) 2008-11-17 2017-08-15 Amazon Technologies, Inc. Request routing utilizing cost information
US9787599B2 (en) 2008-11-17 2017-10-10 Amazon Technologies, Inc. Managing content delivery network service providers
US9251112B2 (en) 2008-11-17 2016-02-02 Amazon Technologies, Inc. Managing content delivery network service providers
US9515949B2 (en) 2008-11-17 2016-12-06 Amazon Technologies, Inc. Managing content delivery network service providers
US9191458B2 (en) 2009-03-27 2015-11-17 Amazon Technologies, Inc. Request routing using a popularity identifier at a DNS nameserver
US9237114B2 (en) 2009-03-27 2016-01-12 Amazon Technologies, Inc. Managing resources in resource cache components
US9176894B2 (en) 2009-06-16 2015-11-03 Amazon Technologies, Inc. Managing resources using resource expiration data
US9130756B2 (en) 2009-09-04 2015-09-08 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9712325B2 (en) 2009-09-04 2017-07-18 Amazon Technologies, Inc. Managing secure content in a content delivery network
US9246776B2 (en) 2009-10-02 2016-01-26 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9893957B2 (en) 2009-10-02 2018-02-13 Amazon Technologies, Inc. Forward-based resource delivery network management techniques
US9495338B1 (en) 2010-01-28 2016-11-15 Amazon Technologies, Inc. Content distribution network
US9191338B2 (en) 2010-09-28 2015-11-17 Amazon Technologies, Inc. Request routing in a networked environment
US9185012B2 (en) 2010-09-28 2015-11-10 Amazon Technologies, Inc. Latency measurement in resource requests
US9407681B1 (en) 2010-09-28 2016-08-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9712484B1 (en) 2010-09-28 2017-07-18 Amazon Technologies, Inc. Managing request routing information utilizing client identifiers
US9800539B2 (en) 2010-09-28 2017-10-24 Amazon Technologies, Inc. Request routing management based on network components
US9794216B2 (en) 2010-09-28 2017-10-17 Amazon Technologies, Inc. Request routing in a networked environment
US9497259B1 (en) 2010-09-28 2016-11-15 Amazon Technologies, Inc. Point of presence management in request routing
US9787775B1 (en) 2010-09-28 2017-10-10 Amazon Technologies, Inc. Point of presence management in request routing
US9253065B2 (en) 2010-09-28 2016-02-02 Amazon Technologies, Inc. Latency measurement in resource requests
US9160703B2 (en) 2010-09-28 2015-10-13 Amazon Technologies, Inc. Request routing management based on network components
US9930131B2 (en) 2010-11-22 2018-03-27 Amazon Technologies, Inc. Request routing processing
US9391949B1 (en) 2010-12-03 2016-07-12 Amazon Technologies, Inc. Request routing processing
US20160191387A1 (en) * 2011-11-11 2016-06-30 Fujitsu Limited Routing method and network transmission apparatus
US20130138814A1 (en) * 2011-11-30 2013-05-30 Verizon Patent And Licensing Inc. Enhanced virtualized mobile gateway in cloud computing environment
US9386077B2 (en) * 2011-11-30 2016-07-05 Verizon Patent And Licensing Inc. Enhanced virtualized mobile gateway in cloud computing environment
US8874790B2 (en) * 2011-12-30 2014-10-28 Verisign, Inc. DNS package in a partitioned network
US9912543B2 (en) 2011-12-30 2018-03-06 Verisign, Inc. DNS package in a partitioned network
US20130173795A1 (en) * 2011-12-30 2013-07-04 Verisign, Inc. DNS Package in a Partitioned Network
US9628554B2 (en) 2012-02-10 2017-04-18 Amazon Technologies, Inc. Dynamic content delivery
US9154551B1 (en) 2012-06-11 2015-10-06 Amazon Technologies, Inc. Processing DNS queries to identify pre-processing information
US9525659B1 (en) 2012-09-04 2016-12-20 Amazon Technologies, Inc. Request routing utilizing point of presence load information
US20150205470A1 (en) * 2012-09-14 2015-07-23 Ca, Inc. Providing a user interface with configurable interface components
US9323577B2 (en) 2012-09-20 2016-04-26 Amazon Technologies, Inc. Automated profiling of resource usage
US9135048B2 (en) 2012-09-20 2015-09-15 Amazon Technologies, Inc. Automated profiling of resource usage
US9009804B2 (en) 2012-11-30 2015-04-14 Ca, Inc. Method and system for hybrid software as a service user interfaces
US9929959B2 (en) 2013-06-04 2018-03-27 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9294391B1 (en) 2013-06-04 2016-03-22 Amazon Technologies, Inc. Managing network computing components utilizing request routing
US9882767B1 (en) * 2013-07-23 2018-01-30 Zscaler, Inc. Distributed cloud-based dynamic name server surrogation systems and methods
US20160308736A1 (en) * 2013-08-26 2016-10-20 Verisign, Inc. Command performance monitoring
US9497140B2 (en) * 2014-05-14 2016-11-15 International Business Machines Corporation Autonomous multi-node network configuration and self-awareness through establishment of a switch port group
US20150333926A1 (en) * 2014-05-14 2015-11-19 International Business Machines Corporation Autonomous multi-node network configuration and self-awareness through establishment of a switch port group
WO2016130869A1 (en) * 2015-02-15 2016-08-18 Microsoft Technology Licensing, Llc Method and system for integrating on-premise and cloud domain name systems
US20160248625A1 (en) * 2015-02-25 2016-08-25 Aether Services, Taiwan, Ltd. Distributor private cloud management system and management method
US9887932B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9887931B1 (en) 2015-03-30 2018-02-06 Amazon Technologies, Inc. Traffic surge management for points of presence
US9819567B1 (en) 2015-03-30 2017-11-14 Amazon Technologies, Inc. Traffic surge management for points of presence
US9832141B1 (en) 2015-05-13 2017-11-28 Amazon Technologies, Inc. Routing based request correlation
US9742795B1 (en) 2015-09-24 2017-08-22 Amazon Technologies, Inc. Mitigating network attacks
US9774619B1 (en) 2015-09-24 2017-09-26 Amazon Technologies, Inc. Mitigating network attacks
US9794281B1 (en) 2015-09-24 2017-10-17 Amazon Technologies, Inc. Identifying sources of network attacks
US9871794B2 (en) * 2015-12-14 2018-01-16 Neustar, Inc. Domain name system and method of operating using restricted channels
US20170171206A1 (en) * 2015-12-14 2017-06-15 Neustar, Inc. Domain name system and method of operating using restricted channels

Also Published As

Publication number Publication date Type
US9363229B2 (en) 2016-06-07 grant
US20120215901A1 (en) 2012-08-23 application

Similar Documents

Publication Publication Date Title
US7228359B1 (en) Methods and apparatus for providing domain name service based on a client identifier
US20030009547A1 (en) Method and system for restricting and enhancing topology displays for multi-customer logical networks within a network management system
US8612627B1 (en) Managing encoded multi-part communications for provided computer networks
US20130058346A1 (en) Distributed Routing Domains in Multi-Tenant Datacenter Virtual Networks
US8046456B1 (en) Using virtual networking devices to manage external connections
US7991859B1 (en) Using virtual networking devices to connect managed computer networks
US20120182992A1 (en) Hypervisor routing between networks in a virtual networking environment
US8230050B1 (en) Providing access to configurable private computer networks
US8131852B1 (en) Using virtual networking devices to manage routing communications between connected computer networks
US20120287931A1 (en) Techniques for securing a virtualized computing environment using a physical network switch
US8201237B1 (en) Establishing secure remote access to private computer networks
US8224971B1 (en) Using virtual networking devices and routing information to initiate external actions
US20090019181A1 (en) Method and System for Preventing Service Disruption of Internet Protocol (IP) Based Services Due To Domain Name Resolution Failures
US20140052877A1 (en) Method and apparatus for tenant programmable logical network for multi-tenancy cloud datacenters
US20110022711A1 (en) Dynamically migrating computer networks
US20140254603A1 (en) Interoperability for distributed overlay virtual environments
US8194680B1 (en) Managing communications for modified computer networks
US7865586B2 (en) Configuring communications between computing nodes
US20090249473A1 (en) Authorizing communications between computing nodes
US8683023B1 (en) Managing communications involving external nodes of provided computer networks
US20090248896A1 (en) Embedding overlay virtual network addresses in underlying substrate network addresses
US8644188B1 (en) Providing virtual networking functionality for managed computer networks
US8224931B1 (en) Managing use of intermediate destination computing nodes for provided computer networks
US20130166737A1 (en) Duplicate ip address detection by a dhcp relay agent
US8396946B1 (en) Managing integration of external nodes into provided computer networks

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOG, MANDAR U.;VASHAW, BART C.;REEL/FRAME:025930/0252

Effective date: 20110112