859 results about "Name resolution" patented technology

A serverless name resolution protocol ensures convergence despite the size of the network, without requiring an ever-increasing cache and with a reasonable numbers of hops. This convergence is ensured through a multi-level cache and a proactive cache initialization strategy. The multi-level cache is built based on a circular number space. Each level contains information from different levels of slivers of the circular space. A mechanism is included to add a level to the multi-level cache when the node determines that the last level is full. A peer-to-peer name resolution protocol (PNRP) includes a mechanism to allow resolution of names which are mapped onto the circular number space through a hash function. Further, the PNRP may also operate with the domain name system by providing each node with an identification consisting of a domain name service (DNS) component and a unique number.

A serverless name resolution protocol ensures convergence despite the size of the network, without requiring an ever-increasing cache and with a reasonable numbers of hops. This convergence is ensured through a multi-level cache and a proactive cache initialization strategy. The multi-level cache is built based on a circular number space. Each level contains information from different levels of slivers of the circular space. A mechanism is included to add a level to the multi-level cache when the node determines that the last level is full. A peer-to-peer name resolution protocol (PNRP) includes a mechanism to allow resolution of names which are mapped onto the circular number space through a hash function. Further, the PNRP may also operate with the domain name system by providing each node with an identification consisting of a domain name service (DNS) component and a unique number.

A serverless name resolution protocol ensures convergence despite the size of the network, without requiring an ever-increasing cache and with a reasonable numbers of hops. This convergence is ensured through a multi-level cache and a proactive cache initialization strategy. The multi-level cache is built based on a circular number space. Each level contains information from different levels of slivers of the circular space. A mechanism is included to add a level to the multi-level cache when the node determines that the last level is full. A peer-to-peer name resolution protocol (PNRP) includes a mechanism to allow resolution of names which are mapped onto the circular number space through a hash function. Further, the PNRP may also operate with the domain name system by providing each node with an identification consisting of a domain name service (DNS) component and a unique number.

The present invention discloses a method and node for acquiring content and a content network, and is related to the field of communications. The method includes: receiving a content request, where the content request at least includes an identifier of requested content; determining whether the content corresponding to the identifier can be acquired locally; if yes, acquired the content corresponding to the identifier locally; otherwise, searching, according to the identifier, a name resolution system for a target node that stores the identifier, and acquiring the content corresponding to the identifier from the target node; where the name resolution system comprises a multilevel DHT and a global content resolution structure, and the global content resolution structure supports name aggregation and longest matching search.

DNS name resolution is integrated into each node in a network storage cluster, to allow load balancing of network addresses, using a weighted random distribution to resolve DNS requests. A node in the cluster gathers statistics on utilization of resources, such as CPU utilization and throughput, on nodes in the cluster and distributes those statistics to all other nodes. Each node uses the same algorithm to generate weights for the various IP addresses of the cluster, based on the statistics distributed to it. The weights are used to generate a weighted list of available network addresses. In response to a DNS request, a DNS in a given node randomly indexes into the weighted address list to resolve requests to a network address. The weights are chosen so that the DNS is likely to pick an IP address which has a low load, to balance port and node usage over time.

Host name data is “looped-back” from a native host name resolver included in a requesting computer system to a name resolution port that is also included in the requesting computer system. A replacement host name resolver monitors the name resolution port for host name data that is incompatible with name resolution techniques utilized by a network. The replacement host name resolver modifies the otherwise incompatible host name data for compatibility with name resolution techniques utilized by the network. Modifying host name data may include changing a transmission protocol associated with the host name data or formatting non-secure host name data for resolution with secure host name resolution techniques. The replacement host name resolver redirects compatible host name data to a module that may cause the host name data to be resolved into a network address. The network address may be provided to the native host name resolver.

A node information storage means stores an entry of node information in which at least an address and a record type are associated with a host name. A search target record deciding means decides a record type of an entry of a search target from a received virtual record type based on a search rule that is a rule specifying a record type of a search target according to a virtual record type. An entry searching means searches the node information storage means, and specifies an entry that corresponds to the entry specifying information received from the terminal device and has the record type decided by the search target record deciding means. A search result transmitting means transmits node information included in the entry specified by the entry searching means to the terminal device.

A system and method for controlling internet traffic controls internet traffic directed to a non-existing domain in a centralized manner. Instead of a non-existing domain response, the user may receive alternative responses such as a landing page including useful information and resourceful suggestions under the control of a global controller. The centralized control over the user's request may be implemented by redirecting a DNS query to the global controller or an optimal search guide server at an individual internet service provider level. Redirection of the DNS query may involve a record modification of a domain name resolution response indicating the non-existing domain.

An extensible data structure for messages in a peer to peer name resolution protocol is presented. This message data structure utilizes a number of fields, each containing a message element. Preferably, the first field is the message header that includes protocol information and identifies the type of message. Each message element contains a number of fields. These message element fields include a type field, a length field, and the content or payload of the message element. In one embodiment, at least ten messages are formed for proper operation of a Peer To Peer Name Resolution Protocol (PNRP), including RESOLVE, RESPONSE, SOLICIT, ADVERTISE, REQUEST, FLOOD, INQUIRE, AUTHORITY, ACK, and REPAIR messages.

An embodiment of the invention comprises a method and apparatus for providing dynamic name resolution services based on information stored and served in a root server. A multi-part reference to the name resolution server is stored on the root servers. By analyzing the reference to the name resolution server, the name resolution server is capable of dynamically generating a canonical name associated with a domain and/or a host name. The domain and/or host name may be further examined by network resource servers to determine further information about a requested resource.

A DNS Proxy unit (A12a) holds the domain name of an encrypted communication target node in a CUG setting table (A125a), intercepts a name resolution request for a communication partner node output from an application (A11x) to a DNS server (B1a), determines by looking up the CUG setting table (A125a) whether the communication partner is an encrypted communication target node, and if the communication partner is an encrypted communication target node, registers the IP address of the name-resolved communication partner in an encrypted communication path setting table (A142a). A data packet sent from the application (A11x) to the IP address is intercepted by a data transmission/reception unit (A14a). A data packet to an IP address registered in the encrypted communication path setting table (A142a) is encrypted by a communication encryption unit (A141a) and transmitted to the communication partner. In this way, in executing encrypted communication with a plurality of communication partners by using a communication encryption function provided by an OS, setting of the encrypted communication target node can be done by using a domain name.

If the communication partner of a client node (A1a) is an encryption communication target node (C1), a DNS Proxy unit (A12a) in the client node rewrites a response to a name resolution request for the communication partner node of an application from the actual IP address of the communication partner node to a loopback address that changes depending on the communication partner. On the basis of the destination loopback address of a data packet transmitted from the application, a communication encryption module (A13a) in the client node identifies the communication partner and the encryption communication path to be used for communication with the communication partner. Hence, encryption communication can simultaneously be executed directly with a plurality of communication partner nodes by using the communication encryption module that operates as an independent process.

A method for ensuring valid and secure peer-to-peer communications in a group structure. Specifically, the system of the present invention presents a method of ensuring secure peer-to-peer group formation, group member addition, group member eviction, group information distribution, etc. Such functionality may be distributed to the individual peers in the group to further enhance the overall security of the group while enhancing flexibility. The P2P group security allows every peer who is a valid member of the group to invite new members. The recipients of these invitations are then able to contact any member of the group to join the group, not only the inviter. Further, groups may function when the group creator is not online. Likewise, the method allows the creation of secure groups with users from different security domains, relying on their security credentials in those domains for initial authentication.

The embodiment of the invention discloses a method, a system and a domain name resolution server for realizing load balancing of a network server. The method comprises: the healthy states of various network servers are monitored, according to the healthy states, the IP address of the network agreement of the network server which exists in the IP list in the domain name resolution DNS server and cannot be visited is deleted, or the address is set as invalid; the DNS server receives the request that network users visit the network server, selects the IP address from the valid IP addresses of the IP list that the request is corresponding to, and the network server which owns the selected IP address provides the network service for the network users. By applying the invention, allocating the network users to a server down can be avoided, allocating the network users to the network server which can be visited can be guaranteed, thus helping the network users to obtain the network service.

Systems and software that enable mapping of a particular network transaction with a specific computer and user in an organization. The network packet may be a live in-transit packet, or a packet that occurred at some time in the past. In a particular implementation, a database currently comprises a collection of records containing fields for username, computer name, IP address of the computer, and logon time. A name resolution is performed by taking an IP address and time as input, and determining from the records in the database what user's computer owned the IP address at that time.

Even if a mistaken reply to a host name resolution request of IPv6 is issued by a DNS contents server, a requesting terminal can still acquire an IPv4 address. When a host name resolution request of IPv6 (AAAA query) is received, a DNS proxy server generates a host name resolution request of IPv4 having an identical domain name, transmits this together with the AAAA query to the DNS contents server, and determines the DNS reply which should be returned to the terminal from the contents of the DNS reply of IPv6 (AAAA reply) and the DNS reply (A reply) of IPv4 received from the DNS contents server. Hence, even if a reply message showing a domain name error is received from the DNS contents server, if the A reply is correct, the DNS proxy server generates an AAAA reply showing that the desired address does not exist, and returns this to the terminal.

A peer-to-peer cache architecture stores peer address certificates in different cache segments according to the number of IDs being stored and their relative distance in the peer name space. The cache instantiates regions of decreased range and increased granularity as additional information from close peers is learned. In a large peer cloud where the number of instantiated IDs is not known, each succeeding cache region covers one tenth of the preceding cache region. For peers with multiple IDs registered locally, the segmented cache of the present invention combines overlapping segments of the same granularity to eliminate the duplication of information that would otherwise occur. A cache tree, an instantiated segment tree, and an uninstantiated segment tree are arranged in red-black trees to simplify the search and proper placement and instantiation of information.

The invention discloses a DNS (Domain Name Server) safety monitoring system and method of a domain name resolution system. The DNS safety monitoring system comprises a data acquisition module and an event analysis module, wherein the data acquisition module is used for acquiring the network data of a DNS and providing the network data to the event analysis module; and the event analysis module isused for analyzing the network data and generating a monitoring result. The system and the method can be used for preventing network attacks such as domain name hijacks, site phishing, zombie attacks, and the like and improving the running stability and reliability of the DNS.

Methods, systems, and gateways are disclosed for automatically setting up a redirector of domain name system (DNS) name requests. A DNS setup packet is transmitted to a remote gateway via a tunnel of a virtual private network (VPN). The setup packet comprises a global name of a home network and a private address of a DNS server in the home network. A DNS setup reply packet is received from the remote gateway via the tunnel. The reply packet comprises a global name of another home network and a private address of a DNS server in the other home network. An application level gateway of the DNS server (DNS-ALG) in the home network is configured dependent upon the DNS setup reply packet to redirect DNS name requests for the global name of the other network to the DNS server in the other network. Methods, systems, and gateways are also disclosed for resolving a domain name request in a DNS.

A security infrastructure and methods are presented that inhibit the ability of a malicious node from disrupting the normal operations of a peer-to-peer network. The methods of the invention allow both secure and insecure identities to be used by nodes by making them self-verifying. When necessary or opportunistic, ID ownership is validated by piggybacking the validation on existing messages. The probability of connecting initially to a malicious node is reduced by randomly selecting to which node to connect. Further, information from malicious nodes is identified and can be disregarded by maintaining information about prior communications that will require a future response. Denial of service attacks are inhibited by allowing the node to disregard requests when its resource utilization exceeds a predetermined limit. The ability for a malicious node to remove a valid node is reduced by requiring that revocation certificates be signed by the node to be removed.

The invention discloses a domain name resolution method and a domain name resolution system in an Internet protocol (IP) network, which are used for solving the problems that: in an Internet service provider (ISP) provided with the access resource of a certain website, an access user of the ISP may access a website server accessed by another ISP, so that an access route is lengthened and packet loss and delay jitter are increased. The domain name resolution method in the IP network comprises the following steps that: when receiving a domain name resolution request carrying a website domain name initiated by the access user, the domain name resolution system queries an IP address which corresponds to the website domain name in a local domain name database and a cache; when the IP address which corresponds to the website domain name is not queried in the local domain name database and the cache, the domain name resolution system acquires a plurality of IP addresses which correspond to the website domain name through iterative query; and the domain name resolution system matches an IP address positioned in an IP address field of the ISP to which the domain name resolution system belongs in the plurality of acquired IP addresses and returns the IP address to the access user. The invention also provides the domain name resolution method and a domain name server (DNS) in the IP network.

The embodiment of the invention provides a webpage access implementation method, a server and a client. The method comprises the following steps that: a third-party domain name resolution server receives a domain name resolution request sent by the client; the third-party domain name resolution server looks up candidate IP (Internet Protocol) addresses corresponding to domain names in a corresponding relation list of website domain names and IP addresses; the third-party domain name resolution server sequences the candidate IP addresses based on a preset sequencing strategy, and takes at least one IP address prioritized in the queue as a target IP address; and the third-party domain name resolution server transmits the target IP address to the client in order that the client accesses a host corresponding to the target IP address. Through adoption of the webpage access implementation method and the third-party domain name resolution server provided by the embodiment of the invention, an appropriate IP address can be provided for the client, and the client can access corresponding hosts according to one or more sequenced IP addresses, so that the success rate of the client in accessing corresponding webpages according to the domain names is increased.