773 results about "Name server" patented technology

A storage controller has at least one physical data port for a data network including host processors. The storage controller is programmed to provide a plurality of virtual ports for access to storage, and a virtual switch for routing storage access requests from the physical port to the virtual ports. The virtual ports and the virtual switch are defined by software. The virtual ports appear to the hosts as physical ports in the data network. For example, in a Fiber-Channel network, the virtual ports have World Wide Names (WWNs) and are assigned temporary addresses (S_Ds), and the virtual switch provides a name server identifying the WWNs and S_IDs of the virtual ports. For convenient partitioning of storage among host processors, one or more virtual ports are assigned to each host, and a set of storage volumes are made accessible from each virtual port. A host can access storage at a virtual port only if the virtual port has been assigned to the host. Preferably, storage can be accessed through each virtual port by no more than one assigned host, although a shared volume may be accessible from more than one virtual port. The storage controller may provide a service for reporting to a host the virtual ports through which the host can access storage, and the storage volumes that are accessible to the host through each of the virtual ports.

A method and apparatus for determining latency between multiple servers and a client receives requests for content server addresses from local domain names servers (LDNS). POPs that can serve the content are determined and sent latency metric requests. The content server receives the request for latency metrics and looks up the latency metric for the requesting client. Periodic latency probes are sent to the IP addresses in a Latency Management Table. The IP addresses of clients are masked so the latency probes are sent to higher level servers to reduce traffic across the network. The hop count and latency data in the packets sent in response to the latency probes are stored in the Latency Management Table and is used to determine the latency metric from the resident POP to the requesting client before sending the latency metric to the requesting server. The BGP hop count in the Latency Management Table is used for the latency metric upon the first request for an IP address. The latency metric is calculated for subsequent requests of IP addresses using the hop count and RTT data in the Latency Management Table. Latency metrics from POPs are collected and the inverse relationship of the hop counts in a weighted combination with the RTT are used to determine which latency metric indicates the optimal POP. The address of the optimal POP is then sent to the requesting LDNS.

A system and method for balancing the load on virtual servers managed by server array controllers at separate data centers that are geographically distributed on a wide area network such as the Internet is described. The virtual servers provide access to resources associated with a domain name request by a client program. When a Primary Domain Name System (DNS) determined the requested domain name is delegated to a EDNS, the EDNS employs metric information and statistics to resolve an IP address for a virtual server that is selected by the EDNS to optimally balance the load and provide access to resources associated with the domain name. The EDNS may load balance name servers. Additionally, the name server load balancing system may bridge disparate content delivery networks. Internet addresses are divided into geographical information that is used to delegate traffic. Also, metric information is collected and analyzed to help distribute the traffic.

Round-trip time (RTT) for communication between an edge point of presence (POP) in a content delivery network (CDN) and a local domain name server (LDNS) is determined by resolution of a canonical name (CNAME) record. A first server in a first edge POP in a CDN receives a request to resolve a domain name from a LDNS and transmits a CNAME record including a timestamp indicating when the CNAME record was transmitted to the LDNS. The first server subsequently receives a request from the LDNS to resolve the CNAME record and determines a RTT time indicating the time needed for round-trip transmission between the LDNS and the first server based on the time when the request to resolve the CNAME request was received by the first server and the time indicated by the timestamp.

An information service provider network includes a content gateway to process requests for information from a client terminal. The content gateway includes a router for receiving a domain name server query from an originator associated with a request for information. The router including a database defining a relationship between domain names and addresses associated with accelerated servicing of requests. The router determines whether the domain name of the domain name server query is indexed in the database. The domain name is qualified in response to the domain name being in the database. If qualified, the router sends an address to the originator of the query corresponding in the database to the domain name. The address is to a processor associated with the router that performs accelerated services on the request.

Disclosed is a computer implemented method and computer program product for transmitting a resource record to a requesting computer. An authoritative domain name server receives a DNS query from a requesting computer at a name server. The authoritative domain name server looks up the resource record based on the DNS query, wherein the resource record is associated with an epochal time and a time to live. The authoritative domain name server transmits the resource record response based on the epochal time.

A method and system is presented for bypassing a local Domain Name Server (DNS) when using edge caching servers. Domain names of frequently used business applications that are known to rely upon edge servers, together with the corresponding authoritative DNSs, are listed in both local hosts file and user defined FSFD local configuration file fsfd.conf. When the client computer's browser attempts to resolve a domain name, a File System Filtering Driver (FSFD) in the client computer intercepts the browser's request. If the domain name which is being resolved is found in a local FSFD configuration file fsfd.conf, then the FSFD initiates a DNS request directly to the appropriate authoritative DNS whose IP address gets extracted from the fsfd.conf record, thus bypassing the local DNS. The authoritative DNS returns the IP address for an edge caching server that is topographically proximate to the client computer's browser.

A domain name server is provided with a set of pseudo domains corresponding to typographical variation of registered domains. The domain name server is configured to provide an error-correction response to a query corresponding to a pseudo domain. The domain name server may be implemented as a TLD server, a root server, or as an adjuct to a network DNS cache, among other embodiments.

An automated method for determining domain traffic including receiving at authoritative name server a request to resolve a domain name that has n labels separated by periods. The leftmost label is the first label and the top level domain is the nth label. If the first label of the received domain name includes the string “www”, then a www hit counter and / or a www requesting server counter for the domain name are incremented. If the received domain name has only two labels, then an exact hit counter and / or an exact requesting server counter for the domain name are incremented. If the first label of the received domain name does not include the string “www” and does not have only two labels, then another hit counter and / or another requesting server counter for the domain name are incremented. A domain traffic score is calculated based upon a plurality of the counters, and calculating the domain traffic score includes applying a weighting factor to at least one of the counters.

Systems and methods for scoring a domain web traffic based on DNS traffic requests received at an authoritative name server to resolve the domain name. A request to resolve the domain name is received at an authoritative name server. A counter, such as a server counter or a hit counter, for the domain name is incremented based on the received request. A score, such as a domain traffic score or a domain rank, is calculated based upon a count of the counter. Calculating the score may also include applying a weighting factor to the counters based on information about a requesting set of resolvers and other domains / websites that may be linking and driving traffic to the domain whose traffic score is being calculated. Examples of relevant set of resolvers information may include location, traffic levels, traffic type and architecture of the set of resolvers.

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.

A domain to be published to an enterprise ECDN is associated (either by static configuration or dynamically) with a set of one or more enterprise zones configurable in a hierarchy. When a DNS query arrives for a hostname known to be associated with given content within the control of the ECDN, a DNS server preferably responds in one of three (3) ways: (a) handing back an IP address, e.g., for an ECDN intelligent node that knows how to obtain the requested content from a surrogate or origin server; (b) executing a zone referral to a next (lower) level name server in a zone hierarchy, or (c) CNAMing to another hostname, thereby essentially restarting the lookup procedure. In the latter case, this new CNAME causes the resolution process to start back at the root and resolve a new path, probably along a different path in the hierarchy. At any particular level in the zone hierarchy, preferably there is an associated zone server. That server preferably executes logic that applies the requested hostname against a map, which, using known techniques, may be generated from given (static, dynamic, internally-generated or third party-sourced) performance metrics. Thus, a given name query to ECDN-managed content may be serviced in coordination with various sources of distributed network intelligence. As a result, the invention provides for a distributed, dynamic globally load balanced name service.

A system and method for providing a name service in a peer-to-peer environment is described. A peer group name server may be a standalone name server that may be used in peer-to-peer applications and environments. A network computing platform may be used as a basis for establishing and operating a peer-to-peer network. A peer group name server may cache information about peers, peer groups and other entities. Peers may discover other peers, peer groups and other entities through the peer group name server. A peer group name server may serve as a reverse lookup provider. A peer group name server may act as a registrar for named entities (e.g. peers) in the peer-to-peer networking environment. In one embodiment, peer group name servers may maintain information about other peer group name servers, thus making a network of decentralized peer group name servers.

Software installed in the nodes in a communication network allows them to perform a “name server” function, which entails the management of a dynamic list of the client devices that are connected to the cloud, a “task” function, which entails the receipt and transmission of the packets, and an “authority” function, which entails the determination of the routes of the packets through the cloud. Each node is capable of performing only one function at a time. After completing a job, a node reverts to an undifferentiated, state awaiting its next performance request.

A system and method is disclosed for detecting and / or mitigating an overload condition from one or more first computers, such as a distributed denial of service (DDoS) attack, viral attack, or the like, targeting one or more of a plurality of second computers located on a network. While one or more DDoS attacks are mitigated, a meter, detection apparatus, software, or method, detects the condition being mitigated in a data cleaning center, and provides an alert or notification regarding the mitigated attack.Another preferred embodiment relates, in general terms, to a system and method for detecting and / or mitigating an overload or attempted overload condition targeting a domain name server. A network connection is provided for receiving one or more DNS requests from one or more client computers located on a network. A preferred embodiment includes a processor for providing a response to the one or more DNS requests to the one or more client computers if more than a threshold number of duplicate DNS requests are received.Another preferred embodiment relates, in general terms, to a system and method for detecting and / or mitigating an attempted overload condition targeting a networked computer system that uses a redirection module to divert data until it is deemed to be clean.

The present invention involves a Universal Geographic Database (“UGD”). The UGD is an automated, central or distributed, registry of real-world locations and location-related information for businesses and other entities, analogous to the registry of domain names for Internet and web sites. By this central registry, businesses and other entities are facilitated to post their location and location-related information in a single place, for all users who need or want it; and users can refer to this single place, via the Internet, Web, and other telecommunications devices, to obtain accurate, complete and timely location and location-based information about the registered businesses and other entities. Each record of the UGD is keyed by a proprietary location address (PLA) based on the World Geographic Referencing System (WGRS), and optionally may have one or more proprietary location addresses (PLAs), which also may serve as keys. Associated with the PLA keys, each UGD record generally includes the full name for the business or other entity, its street address, and miscellaneous contact information (e.g., telephone number, facsimile number, e-mail address, internet website address, wireless website address). Other more dynamic, customized information (e.g., store hours, credit cards accepted, inventory, prices, specials, hours, parking) also may be available in the UGD record or linked to the UGD record. Users of any device or service can access the UGD through one or more location name servers (LNS), which can provide access to the UGD or other location-based information linked to the UGD or LNS. Based on the WGRS, PLAs provide, in addition to unique keys for UGD records, a user-friendly notation for location naming in the real-world and on all types of location-sensitive electronic devices, from web phones to in-car navigation systems. Given the UGD, these ULA / PLAs are as important to real-world businesses as their domain names because these WGRS addresses drive real-world commerce to physical business locations just as domain names drive e-commerce Internet or web sites.

A method for operating a cluster of N server nodes to service client requests received on a network. Each client request is directed to one of C customers hosted on the server cluster. Each customer is identified by a domain name, and each server node is identified by an address on a network. In the method of the present invention, the customers are grouped into N groups, each group being assigned to a corresponding one of the server nodes. Configuration information is provided to a Domain Name Server (DNS), the information defining the correspondence between each of the customers and one of the server nodes assigned to one of the groups containing that customer. The DNS provides the address of the server node in response to a message specifying the domain name of the customer. The client then directs its request to the identified server node utilizing the address provided by the DNS. In the preferred embodiment of the present invention, the grouping of the customers depends on a measurement of the computational resources required to service the client requests for each of the customers. In embodiments in which the activity associated with each request is primarily the return of files stored in the cluster, the measurement of computational resources includes the size of the files returned by each client—within a time period and the communication bandwidth needed to service the requests.

To resolve a Uniform Resource Identifier (URI) for use in routing messages in or between IP Multimedia Subsystem (IMS) networks, a query (101;201) is sent to resolve this URI from a device (120;220) to a private name server (121;221). The private name server (121;221) attempts to resolve the URI. In case of failure the method further involves the sending of a new query (104;203) for resolving the URI to a public name server (122;222). The public name server (122;222) resolves the URI in the new query (104;203).

Disclosed is a computer implemented method and computer program product for transmitting a resource record to a requesting computer. An authoritative domain name server receives a DNS query from a requesting computer at a name server. The authoritative domain name server looks up the resource record based on the DNS query, wherein the resource record is associated with an epochal time and a time to live. The authoritative domain name server transmits the resource record response based on the epochal time.

According to the invention, a method and apparatus are disclosed for dynamically assigning a public network address for a private network host in response to a request generated external to the private network. A requesting host desiring access to a host with the private network queries a domain name server for the public network address of the private network host. Then, the domain name sever queries a network address translator of the private network, and receives a reply indicating a dynamically allocated public network address for the specified private network host. The requesting host can then use this returned public network address for communicating with the private network host. In this manner, a set of public addresses can be shared, with a public network address being dynamically allocated to a private network host in response to a request for access by a host external to the private network. Moreover, a public network address is assigned to a private network host for a limited period of time. This time period can be specified as a period of network inactivity related to the public network address, or a specified time duration (e.g., for one hour, from 3:00 PM to 5:00 PM). The aging of these assigned public addresses is processed by the domain name server itself, or by the network address translator which sends a message to the domain name server when an assigned public address is no longer valid for a particular private network host.

A fault-tolerant server group operating in client-server distributed dynamic network system environment includes a master server and at least one back-up server. The master server registers its mastership in a name server. The master server communicates with the client and the back-up servers. Each server in the fault-tolerant server group has a self-monitoring mechanism, ensuring a consistent mastership. The fault-tolerant server group processes the request from the client to generate a processing result. The processing result is sent from the master server to the client.

A method is provided with which a name of a virtual port is not changed when virtualized storage is moved among switches. Information about a creator and a borrower of name information is added to a table including name information and address information of a virtual port of a name server managing the name information and the address information. The name information is provided to plural switches and managed. In addition, name information, which can be used commonly among name servers managing the name information and the address information is pooled in advance, and the name information of the virtual port is borrowed from there.

A client player performs a query to a nameserver against a network map of Internet traffic conditions. The query is made asking for a particular service (e.g., RTSP) via a particular protocol (TCP) in a particular domain. In response, the nameserver returns a set of one or more tokens, with each token defining a machine or, in the preferred embodiment, a group of machines, from which the player should seek to obtain the stream. The player may then optionally perform one or more tests to determine which of a set of servers provides a best quality of service for the stream. That server is then used to retrieve the stream. Periodically, the client player code repeats the query during stream playback to determine whether there is a better source for the stream. If a better source exists, the player performs a switch to the better stream source “on the fly” if appropriate to maintain and / or enhance the quality of service. Preferably, the client player publishes data identifying why it selected a particular server, and such data may be used to augment the network map used for subsequent request routing determinations.

A method is described for directing a user of a mobile device from a current location to a product, wherein an identification code of the product is recorded in the mobile device and transmitted to a name server. The identification code is used in the name server among others for loading product-related data into the mobile device, e.g. a geographical location where the product can be bought. Following this, the user of the mobile device can go to said geographic location. For directing said user to the product, a direct contactless connection is established between said mobile device and a RFID element with which said product is marked, by using the same identification code or product-related data previously supplied by the name server.

A method and system for connecting a guest browser with a proxy includes: sending a registration request for a proxy from a peer to a proxy director; selecting a proxy by the proxy director and sending a proxy name to the peer; sending a registration request with a peer name and the proxy name from the peer to a dynamic domain name server (DNS); and registering a dynamic DNS record with a DNS name server by the dynamic DNS to associate the peer name with the proxy name. Thus, the dynamic DNS is used to convert the registration request from the peer to standard DNS. When a guest browser wants to connect to the peer, it performs a standard DNS look-up for the peer name at the DNS name server, which tells it which proxy to connect to. No proprietary locator service is needed to accomplish this connection.

The present invention provides methods and systems for registering unlimited non-ICANN top-level domain (TLD) names that are created on demand, and for utilizing them in a network environment in parallel with those specified by the Internet Corporation for Assigned Names and Numbers (ICANN) or other authority authorized to approve standardized top-level domain names. One embodiment of the present invention provides systems and methods for registering a non-ICANN TLD name by mapping it to an IP address using a predefined mapping function, assigning the resulting IP address to a server system that acts as the name server for TLD name, and subsequently using the said predefined function when a user enters an Internet address containing said TLD name on a client computer in order to compute the IP address of the said name server and access it. Further, one embodiment of the present invention is operable with proxy servers.

A system and method for a mobile data access network to make policy control and charging decisions based on domain name queries. A mobile device sends a query about a domain name associated with a service a user of the mobile device wishes to engage. The access network carries the domain name query from a mobile device to a domain name server. The access network detects the domain name query and copies the queried domain name. The access network uses the queried domain name to make an incomplete policy decision. The policy decision is incomplete because one or more service data flow filters in the decision lack addresses for providers of the service. The access network detects a response to the domain name query and copies a service provider address from the response. The access network uses the service provider address to complete the policy decision.

An intelligent traffic redirection system performs global load balancing for Web sites located at mirrored data centers. The system relies on a network map that is generated continuously, preferably for the user-base of the entire Internet. Instead of probing each local name server (or other host) that is connectable to the mirrored data centers, the network map identifies connectivity with respect to a much smaller set of proxy points, called “core” (or “common”) points. A core point is representative of a set of local name servers (or other hosts) that, from a data center's perspective, share the point. To discover a core point, an incremental trace route is executed from each of the set of mirrored data centers to a local name server that may be used by client to resolve a request for a replica stored at the data centers. An intersection of the trace routes at a common routing point is then identified. Thus, for example, the common routing point may be the first common point for the trace routes when viewed from the perspective of the data centers (or the last common point for the trace routes when viewed from the perspective of the local name server). The common routing point is then identified as the core point for the local name server.