CA2310277C - Enhanced domain name service - Google Patents
Enhanced domain name service Download PDFInfo
- Publication number
- CA2310277C CA2310277C CA002310277A CA2310277A CA2310277C CA 2310277 C CA2310277 C CA 2310277C CA 002310277 A CA002310277 A CA 002310277A CA 2310277 A CA2310277 A CA 2310277A CA 2310277 C CA2310277 C CA 2310277C
- Authority
- CA
- Canada
- Prior art keywords
- cache server
- domain
- local
- local cache
- server
- 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.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
A system (300) prefetches most frequently used domain names and stores the domain name data (320) at local cache servers (310), It generates validity codes (330) to enable error checking for valid domain names at the local cache servers (310) without accessing root servers (130). A cache server (310) obtains, stores, and propagates updated or new DNS data to local cache servers (340) at predetermined intervals. Users can obtain Internet protocol addresses of domain names directly from local cache servers (310), thus eliminating processing delays over the Internet.
Description
Enhanced Domain Name Service Background Art is The present invention relates generally to enhanced domain name servers (DNS), and more particularly, to efficiently processing domain name (DN) queries in a network.
The Internet has experienced explosive growth in recent years and provides a vast resource of information on a wide array of topics. The Internet 2o requires-DNS for providing Internet Protocol (IP) addresses corresponding to the DNs. The response time of any DNS query, however, is highly dependent on the latency of the Internet. In addition, the availability of any response varies with the packet loss rate of the Internet. DNS developers attempted to address these problems by including a cache memory in local servers. Fig. 1 is a state 2s diagram showing a process flow of traditional DNS processing.
To access a remote computer over the Internet, a user types in the DN or URL of that remote computer (e.g., www.example.com) using a browserat a local computer 110 (step 160). Most Internet connections begin by a query to a local server 120 to obtain the IP address of that computer (e.g., 126.96.41.1 ).
3o To do so, local server 120 looks in its local cache storing previous queries. If the current query is for an IP address that matches a previous query, local server 120 can respond to the query immediately using the information stored in the local cache.
If local server 120 does not find the answer in the local cache, however, 3s local server 120 relays the query to a root server 130 (step 161 ). Root server 130, or more precisely the "top level domain server," knows the address of all "remote servers" that manage second level names (e.g., example.com). Root server 130 transmits redirection information, i.e., name and IP address of th_e remote server (e.g., dns.example.com) to local server 120 (step 162).
4o Thereafter, local server 120 repeats the query, this time to the specified remote WO 99/Z7680 _ Z _ PCT/US98I21239 s server 140 (e.g., dns.example.com) (step 163). Remote server 140, in turn, transmits the IP address of the requested DN to local server 120 (step 164).
Local server 120 stores a copy of this answer in its local cache and provides an answer to local computer 110 (step 165). Using the IP address, local computer 110 establishes connection with remote computer 150 (step 166).
to Subsequently, if local computer 110 repeats the same query (step 167), local server 120 looks in the local cache and will find the IP address. Local server 120 then transmits the address to local computer 110 without having to access other components of the network (step 168), thus enabling local computer 110 to establish connection to remote computer 150 (step 169).
is Referring to Fig. 2, a special case occurs when a user mistypes or guesses the DN, making up such names as "www.i-dont-really-know.com" (step 200). Similar to the above-explained process flow, local server 120 checks its local cache. But since local server 120 will not find the DN in the local cache, it relays the query to root server 130 (step 201 ). Thereafter, root server 130 2o checks a reference database to determine whether the DN exits and returns an error message to local server 120 (step 202). Local server 120, in turn, relays the error message to local computer 110 (step 203).
Some local servers keep a copy of these error messages, but typically only for a short period of time since a name that is not found one day may well 2s be registered the next. Moreover, copies of error messages are only useful if users keep repeating the exact same mistake, an unlikely event. In practice, most wrong guesses result in a transaction to one of the root servers, thus extending the DN processing time and subjecting communications to problems with Internet traffic.
3o Moreover, due to the dramatic increase in the size of the Internet since the late 1980's, the caching technique no longer provides high quality results.
Typically, fewer than 85% of queries are served in less than three seconds.
This is expected to worsen as the Internet grows.
Therefore, it is desirable to increase the efficiency in processing DN
3s queries for connecting local computers to remote computers.
It is also desirable to provide efficient processing of invalid DNs.
Disclosure of the Inyention Accordingly, the present invention is directed to an enhanced DN service that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.
Specifically, a method consistent with the present invention for processing I)N
requests comprises the following steps. Initially, the system prefetches most frequently used (MFU) domain names and associated domain addresses. It then transmits to a local server the prefetched MFU DNs and the associated domain addresses, wherein the local server uses the prefetched MFU DNs and the associated to domain addresses to process DN requests.
A system consistent with the present invention for processing DN requests comprises prefetching means and transmitting means. Initially, the prefetching means prefetches MFU DNs and associated domain addresses. The transmitting means then transmits to a local server the prefetched MFU DNs and the associated domain 1 s addresses, wherein the local server uses the prefetched MFU DNs and the associated domain addresses to process DN requests.
In accordance with one aspect of the present invention there is provided a method for reducing the number of erroneous domain requests forwarded to domain name server (DNS) root servers from a local computer, the local computer being 2o connected to a local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table and being connected to one or more remote root servers, the method comprising the steps of receiving a user request for a domain name, in response to said request, accessing the most frequently used domain names table in the local cache server, if the domain name is not in the 2s most frequently used domain names table, generating a code check to access the validity code table in the local cache server, if the generated code check is not in the validity code table, returning an error message to the local computer, and if the generated code check is in the validity code table, forwarding the request to one of said remote root servers.
3a In accordance with another aspect of the present invention there is provided a system for processing with reduced processing time domain requests at a local computer, said system comprising a local cache server connected to the local computer and storing a most frequently used domain names table with associated domain addresses and a validity code table, a plurality of remote root servers connected to the local computer, means for receiving a user request for a domain name, means for accessing the most frequently used domain names table in said local cache server in response to said user request, means for generating a code check to access the validity table in said local cache server if the domain name is not in the most frequently used domain table, means for returning an error message to the local computer if the generated code check is not in the validity code table, and means for forwarding the request to one of said remote root servers if the generated code check is in the validity code table.
In accordance with yet another aspect of the present invention there is ~5 provided an article of manufacture capable of configuring a local cache server connected to a local computer to process domain name requests, the local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table, the article comprising a computer-readable medium having computer readable code embodied therein for causing the local cache server to perform, the steps of receiving user request for a domain name, accessing the most frequently used domain names table in the local cache server in response to said request, generating a code check to access the validity code table in the local cache server if the domain name is not in the most frequently used domain names table, returning an error message to the local computer if the generated code check is not in the validity code table, and forwarding the request to a remote root server connected to the local computer if the generated code check is in the validity code table.
3b Brief Description of the Drawings The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a state diagram showing a process flow of traditional DNS processing of a DN request;
Fig. 2 is a state diagram showing a process flow of traditional DNS processing of a DN request for an invalid DN;
Fig. 3 is a diagram showing an example of a network consistent with one to embodiment of the present invention;
Fig. ~ is a functional block diagram showing service elements of the network consistent with one embodiment of the present invention;
Fig. 5 is a state diagram showing a process flow of DNS processing consistent with one embodiment of the present invention; and 15 Fig. 6 is a state diagram showing a process flow of DNS processing of an invalid DN consistent with one embodiment of the present invention.
WO 99IZ7680 _ 4 _ PCT/US981Z1239 Best Mode for Carrvina Out the Invention Reference will now be made in detail to the present preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings. Where appropriate, the same reference numerals io refer to the same or similar elements. The appended claims define the scope of the invention; the following description does not limit that scope.
Fig. 3 shows an example of a network environment consistent with one embodiment of the present invention. In network 300, local computer 110 is coupled to a local cache server 310 over network connections. Local cache is server 310 also connects to a cache server 340 and root server 130. Local cache server 310 includes a most frequently used domain names (MFU DNs) table 320 and a validity code table 330. Local cache server 310 preferably is a high-end network server having capacity to hold a few million records in its database and high-speed network access.
2o Fig. 4 is a functional block diagram showing service elements of network 300 consistent with one embodiment of the present invention. A central DNS
cache server includes a central DNS database 410, a spider lookup 415, a refresh process 420, a cache administrator 425, a feedback process 430, ISP
control cache servers 435, replicators 440, and edge cache servers 445. In one 2s embodiment consistent with the present invention, the central DNS cache server can be operated by a commercial service, which would send updates to ISP
control cache servers 435, typically operated by Internet Service Providers (ISPs). ISP control cache server 435, in turn, replicates the cache updates to edge cache servers 445. The updates are preferably sent over TCP-IP
3o connections. ISP control cache servers 435 or edge cache servers 445 of Fig. 4 are examples of local cache server 310 in Fig. 3.
According to the present invention, local cache servers 310, located near local computers 110, contain a large portion of the DNS data. Thus, in most cases, requests from local computers 110 will be serviced directly by local 3s cache servers 310. The DNS data contained in local cache servers 310 are not collected by the local cache servers 310 themselves, as in the prior art systems, but rather are provided by cache servers 340. Specifically, cache servers 340 update local cache servers 310 on a predetermined basis by providing DNS
records consisting preferably of three data sets. The type and scope of data ao included in the MFU DNs may vary, however.
wo ~m~o _ 5 _ PCT/US98IZ1239 s The first data set is a list of the most active names together with the corresponding name and address records, i.e., DNS records of type NS (DNS
record containing DNS names of the DNS servers that hold information about the specified domain) and type A (DNS record containing the IP address of a computer identified by a DNS name). For each DNS record, central DNS
io database 410 stores the name (name of the node to which the resource record pertains), type and class of the record, time to live (TTL) variable, length (specifying the length of the data field), and data (field describing the resource).
TTL is the estimated life expectancy during which the DNS record remains current. The TTL can be set and reset to a certain predetermined value is including periodic or discrete preset times.
The second data set is a complete listing of the existing names at the root level and, preferably, also second level DNs of the most frequently accessed domain, e.g., ".com." A listing of second level domains is a flat file of names such as "bellcore.com." These names have two components, the second level 2o domain name and the name of the "top level domain." This data set contains a full listing of all names that are registered in a monitored top level domain.
The present invention generates validity codes using a standard technique, e.g., a hash coding (explained below), and produces for each DN a hash code, which is preferably an integer number. A complete list of hash codes or validity codes, 2s but not the list of names, is transmitted to local cache servers 310 for use in error checking as will be explained below.
The third data set is a listing of the highest levels of the DNS inverse tree used by servers to locate the origin of Internet connections. The inverse tree contains names that are derived from IP addresses. For example, the address 30 "192.4.18.101" can be used to build the inverse name "101.18.4.192.in-addr.arpa." These names are used by servers to retrieve the domain names of clients. Each level of the naming hierarchy may be handled by a different server. The first level is typically handled by a registry, the second level by an Internet Service Provider or by a large organization, and the third level by a ss retail ISP or by the manager of a local network, i.e., "edge cache servers." By caching DNS information at the first two levels, the queries can be directed immediately to the remote server that can transform the inverse name into the actual name of the machine that uses the IP address, in the present examp_ie, "seawind.bellcore.com."
Web lookup 415 employs web spiders, which are software processes that visit web sites and automatically explore their contents, to obtain MFU DNs.
From the web content, web spiders extract names of other sites, which the web spiders can visit next, thus, exploring a large part of the Internet. Web spiders are typically used to build large index databases for index servers such as YAHOOT"", ALTAVISTAT"" and EXCITET"". One embodiment consistent with the present invention employs web spiders to discover new web sites. Web spiders only obtain an approximation of the MFU DNs because they collect most frequently accessed references, which is a different property from MFU DNs. The collection of MFU DNs obtained by web spiders are supplemented by feedback is process 430. Feedback process of ISP control cache servers 435 and edge local cache servers 445 collect statistics of the MFU DNs and send this data to central DNS database 410.
Refresh process 420 queries central DNS database 410 at intervals corresponding to TTL to determine whether the information in central DNS
2o database 410 has changed to ensure that local cache server 310 always contains up-to-date information. In one embodiment consistent with the present invention, refresh process 420 need not conduct a full update. In many cases, TTL may be set to a relatively short value, such as one day, because managers of the records might update the next day. DNS database 410, in such cases, 2s may be refreshed every day. In one preferred embodiment of the present invention, TTL is set to a level so that the information would not be updated too frequently, which would effectively preclude caching.
There is no need to perform a full update unless the information actually changes. If the information does not change, cache administrator 425 only 3o needs to send a message that essentially revalidates the current information. If refresh process 420 determines that the information actually changed, cache administrator 425 extracts the information from central DNS database 410 and selects only actual updates or new information to propagate to ISP control cache servers 435 and edge cache servers 445. For example, an update is 3s necessary when a new DN is added to central DNS database 410 by spider lookup 415 or feedback process 430. Replicator 440 of ISP control cache server 435 replicates the updates or new information to the next level of cache servers, i.e., edge cache servers 445. Replicator 440 of edge cache servers 445, in tum, replicates the updates or new information to other cache servers.
wo 99/Z7680 - ~ - PCTNS98/21239 s Thus, referring to Fig. 5, according to one embodiment consistent with the present invention, cache server 340 transmits DNS data to local cache server 310 at predetermined intervals, or TTL (step 501 ). The data includes the three types of data sets explained above, and subsequent transmissions need only contain updates to the existing DNS data at local cache server 310. Local io cache server 310 receives the DNS data or updates and updates MFU DNs table 320 (step 502). MFU DNs table 320, containing the three data sets, is preferably stored in cache for fast access.
When a user types in a user request, i.e., the DN or URL of a remote computer (e.g., www.example.com) using a browser at a local computer 110 is (step 502), local cache server 310 accesses MFU DNs table 320. If local cache server 310 finds the answer, which will be the case in most instances, local cache server 310 transmits the corresponding IP address to local computer 110 (step 503). Using the lP address, local computer 110 establishes connection with remote computer 150 (step 504). Thus, local cache server 310 responds to 2o queries directly, significantly reducing DNS processing time.
A different scenario occurs for DN requests of invalid names. In the present invention, cache server 340 generates validity codes of valid DN names to be stored in validity code table 330 of local cache server 310. In this manner, local cache server 310 checks its local cache to determine whether the 2s requested DN is valid without having to access root server 130. Since the memory capacity of local cache at local cache server 310 is limited, in one embodiment consistent with the present invention, local cache server 310 stores the validity codes of all top level domains as well as second level DNs of the most frequently accessed domain, e.g., ".com."
so Accordingly, referring to Fig. 6, root server 130 of ".com" provides a full listing of second level DNs to cache server 340 (step 600). Cache server 340 preferably generates validity codes of the top level domains and ".com" using hash coding. Cache server 340 transmits the validity codes to local cache server 310 (step 601 ). Although there are many ways to implement the hash 3s coding, the following Java method provides one example:
WO 99127680 - $ - PCT/US98/21239 to int hash (String domainName) int x, r, I;
char c;
x=0;
for (I=0; i<domainName.length(); I++){
r = (x»24)&255;
X«=8.
X~=r;
x ~_ (r«1 );
c = domainName.charAt(I);
if (c =_ '.') x ~= 37;
2o else if (c =_' ') x ~= 36;
else x "_ ((Character.digit(c, 36))&255);
2s return(x);
This algorithm returns a 32 bit integer, whose value is a function of the domain 3o name:
Domain name Hash code bellcore.com 370308165 inria.fr 1008476717 nsa 622275647 nsa.gov 623459329 Other hash coding techniques may be implemented to generate codes requiring much less memory than the full DNs to reduce the memory requirement of local cache server 310. The same technique should be used 3s consistently, however, within a single network platform by various components, e.g., local cache server 310, cache server 340, and cache administrator 425.
Additionally, the technique implemented should preferably be programmed to return results that only depend on the DNs and not the supporting platform.
wo ~m6so - 9 - PGT/US98n1239 s Accordingly, when a user types in the DN or URL of a remote computer (e.g., www.i-dont-really-know.com) using a browser at a local computer 110 (step 602), local cache server 310 accesses MFU DNs table 320. If local cache server 310 does not find the answer, rather than relaying the query to root server 130, local cache server 310 generates a check code of the DN in the io query using hash coding or other technique implemented in network 300. If the generated check code is not in validity code table 330, local cache server 310 transmits an error message to local computer 110 (step 603). Thus, local cache server 310 reduces processing time for queries for invalid DNs by eliminating the need to access root server 130. In the rare instance when the DN is not in is the MFU DNs table 320 and the check code matches one of the entries in validity code table 330, local cache server 310 processes the DN query in the traditional manner.
Systems and methods consistent with the present invention improve the efficiency of DN processing by storing MFU DNs and validity codes at local 2o cache servers. Such systems and methods process DN queries without accessing remote servers or root servers, thus, significantly reducing processing time. The central server is periodically updated with new and revised DN data and the central server propagates the updates to edge cache servers.
2s It will be apparent to those skilled in the art that various modifications and variations can be made in the systems and methods of the present invention without departing from the scope or spirit of the invention. For example, Internet has been used as an exemplary network setting. The teachings of the present application, however, may be easily adapted and applied in other network so settings by one ordinary skilled in the art. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the invention indicated by the following claims.
The Internet has experienced explosive growth in recent years and provides a vast resource of information on a wide array of topics. The Internet 2o requires-DNS for providing Internet Protocol (IP) addresses corresponding to the DNs. The response time of any DNS query, however, is highly dependent on the latency of the Internet. In addition, the availability of any response varies with the packet loss rate of the Internet. DNS developers attempted to address these problems by including a cache memory in local servers. Fig. 1 is a state 2s diagram showing a process flow of traditional DNS processing.
To access a remote computer over the Internet, a user types in the DN or URL of that remote computer (e.g., www.example.com) using a browserat a local computer 110 (step 160). Most Internet connections begin by a query to a local server 120 to obtain the IP address of that computer (e.g., 126.96.41.1 ).
3o To do so, local server 120 looks in its local cache storing previous queries. If the current query is for an IP address that matches a previous query, local server 120 can respond to the query immediately using the information stored in the local cache.
If local server 120 does not find the answer in the local cache, however, 3s local server 120 relays the query to a root server 130 (step 161 ). Root server 130, or more precisely the "top level domain server," knows the address of all "remote servers" that manage second level names (e.g., example.com). Root server 130 transmits redirection information, i.e., name and IP address of th_e remote server (e.g., dns.example.com) to local server 120 (step 162).
4o Thereafter, local server 120 repeats the query, this time to the specified remote WO 99/Z7680 _ Z _ PCT/US98I21239 s server 140 (e.g., dns.example.com) (step 163). Remote server 140, in turn, transmits the IP address of the requested DN to local server 120 (step 164).
Local server 120 stores a copy of this answer in its local cache and provides an answer to local computer 110 (step 165). Using the IP address, local computer 110 establishes connection with remote computer 150 (step 166).
to Subsequently, if local computer 110 repeats the same query (step 167), local server 120 looks in the local cache and will find the IP address. Local server 120 then transmits the address to local computer 110 without having to access other components of the network (step 168), thus enabling local computer 110 to establish connection to remote computer 150 (step 169).
is Referring to Fig. 2, a special case occurs when a user mistypes or guesses the DN, making up such names as "www.i-dont-really-know.com" (step 200). Similar to the above-explained process flow, local server 120 checks its local cache. But since local server 120 will not find the DN in the local cache, it relays the query to root server 130 (step 201 ). Thereafter, root server 130 2o checks a reference database to determine whether the DN exits and returns an error message to local server 120 (step 202). Local server 120, in turn, relays the error message to local computer 110 (step 203).
Some local servers keep a copy of these error messages, but typically only for a short period of time since a name that is not found one day may well 2s be registered the next. Moreover, copies of error messages are only useful if users keep repeating the exact same mistake, an unlikely event. In practice, most wrong guesses result in a transaction to one of the root servers, thus extending the DN processing time and subjecting communications to problems with Internet traffic.
3o Moreover, due to the dramatic increase in the size of the Internet since the late 1980's, the caching technique no longer provides high quality results.
Typically, fewer than 85% of queries are served in less than three seconds.
This is expected to worsen as the Internet grows.
Therefore, it is desirable to increase the efficiency in processing DN
3s queries for connecting local computers to remote computers.
It is also desirable to provide efficient processing of invalid DNs.
Disclosure of the Inyention Accordingly, the present invention is directed to an enhanced DN service that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.
Specifically, a method consistent with the present invention for processing I)N
requests comprises the following steps. Initially, the system prefetches most frequently used (MFU) domain names and associated domain addresses. It then transmits to a local server the prefetched MFU DNs and the associated domain addresses, wherein the local server uses the prefetched MFU DNs and the associated to domain addresses to process DN requests.
A system consistent with the present invention for processing DN requests comprises prefetching means and transmitting means. Initially, the prefetching means prefetches MFU DNs and associated domain addresses. The transmitting means then transmits to a local server the prefetched MFU DNs and the associated domain 1 s addresses, wherein the local server uses the prefetched MFU DNs and the associated domain addresses to process DN requests.
In accordance with one aspect of the present invention there is provided a method for reducing the number of erroneous domain requests forwarded to domain name server (DNS) root servers from a local computer, the local computer being 2o connected to a local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table and being connected to one or more remote root servers, the method comprising the steps of receiving a user request for a domain name, in response to said request, accessing the most frequently used domain names table in the local cache server, if the domain name is not in the 2s most frequently used domain names table, generating a code check to access the validity code table in the local cache server, if the generated code check is not in the validity code table, returning an error message to the local computer, and if the generated code check is in the validity code table, forwarding the request to one of said remote root servers.
3a In accordance with another aspect of the present invention there is provided a system for processing with reduced processing time domain requests at a local computer, said system comprising a local cache server connected to the local computer and storing a most frequently used domain names table with associated domain addresses and a validity code table, a plurality of remote root servers connected to the local computer, means for receiving a user request for a domain name, means for accessing the most frequently used domain names table in said local cache server in response to said user request, means for generating a code check to access the validity table in said local cache server if the domain name is not in the most frequently used domain table, means for returning an error message to the local computer if the generated code check is not in the validity code table, and means for forwarding the request to one of said remote root servers if the generated code check is in the validity code table.
In accordance with yet another aspect of the present invention there is ~5 provided an article of manufacture capable of configuring a local cache server connected to a local computer to process domain name requests, the local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table, the article comprising a computer-readable medium having computer readable code embodied therein for causing the local cache server to perform, the steps of receiving user request for a domain name, accessing the most frequently used domain names table in the local cache server in response to said request, generating a code check to access the validity code table in the local cache server if the domain name is not in the most frequently used domain names table, returning an error message to the local computer if the generated code check is not in the validity code table, and forwarding the request to a remote root server connected to the local computer if the generated code check is in the validity code table.
3b Brief Description of the Drawings The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate the invention and together with the description, serve to explain the principles of the invention.
Fig. 1 is a state diagram showing a process flow of traditional DNS processing of a DN request;
Fig. 2 is a state diagram showing a process flow of traditional DNS processing of a DN request for an invalid DN;
Fig. 3 is a diagram showing an example of a network consistent with one to embodiment of the present invention;
Fig. ~ is a functional block diagram showing service elements of the network consistent with one embodiment of the present invention;
Fig. 5 is a state diagram showing a process flow of DNS processing consistent with one embodiment of the present invention; and 15 Fig. 6 is a state diagram showing a process flow of DNS processing of an invalid DN consistent with one embodiment of the present invention.
WO 99IZ7680 _ 4 _ PCT/US981Z1239 Best Mode for Carrvina Out the Invention Reference will now be made in detail to the present preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings. Where appropriate, the same reference numerals io refer to the same or similar elements. The appended claims define the scope of the invention; the following description does not limit that scope.
Fig. 3 shows an example of a network environment consistent with one embodiment of the present invention. In network 300, local computer 110 is coupled to a local cache server 310 over network connections. Local cache is server 310 also connects to a cache server 340 and root server 130. Local cache server 310 includes a most frequently used domain names (MFU DNs) table 320 and a validity code table 330. Local cache server 310 preferably is a high-end network server having capacity to hold a few million records in its database and high-speed network access.
2o Fig. 4 is a functional block diagram showing service elements of network 300 consistent with one embodiment of the present invention. A central DNS
cache server includes a central DNS database 410, a spider lookup 415, a refresh process 420, a cache administrator 425, a feedback process 430, ISP
control cache servers 435, replicators 440, and edge cache servers 445. In one 2s embodiment consistent with the present invention, the central DNS cache server can be operated by a commercial service, which would send updates to ISP
control cache servers 435, typically operated by Internet Service Providers (ISPs). ISP control cache server 435, in turn, replicates the cache updates to edge cache servers 445. The updates are preferably sent over TCP-IP
3o connections. ISP control cache servers 435 or edge cache servers 445 of Fig. 4 are examples of local cache server 310 in Fig. 3.
According to the present invention, local cache servers 310, located near local computers 110, contain a large portion of the DNS data. Thus, in most cases, requests from local computers 110 will be serviced directly by local 3s cache servers 310. The DNS data contained in local cache servers 310 are not collected by the local cache servers 310 themselves, as in the prior art systems, but rather are provided by cache servers 340. Specifically, cache servers 340 update local cache servers 310 on a predetermined basis by providing DNS
records consisting preferably of three data sets. The type and scope of data ao included in the MFU DNs may vary, however.
wo ~m~o _ 5 _ PCT/US98IZ1239 s The first data set is a list of the most active names together with the corresponding name and address records, i.e., DNS records of type NS (DNS
record containing DNS names of the DNS servers that hold information about the specified domain) and type A (DNS record containing the IP address of a computer identified by a DNS name). For each DNS record, central DNS
io database 410 stores the name (name of the node to which the resource record pertains), type and class of the record, time to live (TTL) variable, length (specifying the length of the data field), and data (field describing the resource).
TTL is the estimated life expectancy during which the DNS record remains current. The TTL can be set and reset to a certain predetermined value is including periodic or discrete preset times.
The second data set is a complete listing of the existing names at the root level and, preferably, also second level DNs of the most frequently accessed domain, e.g., ".com." A listing of second level domains is a flat file of names such as "bellcore.com." These names have two components, the second level 2o domain name and the name of the "top level domain." This data set contains a full listing of all names that are registered in a monitored top level domain.
The present invention generates validity codes using a standard technique, e.g., a hash coding (explained below), and produces for each DN a hash code, which is preferably an integer number. A complete list of hash codes or validity codes, 2s but not the list of names, is transmitted to local cache servers 310 for use in error checking as will be explained below.
The third data set is a listing of the highest levels of the DNS inverse tree used by servers to locate the origin of Internet connections. The inverse tree contains names that are derived from IP addresses. For example, the address 30 "192.4.18.101" can be used to build the inverse name "101.18.4.192.in-addr.arpa." These names are used by servers to retrieve the domain names of clients. Each level of the naming hierarchy may be handled by a different server. The first level is typically handled by a registry, the second level by an Internet Service Provider or by a large organization, and the third level by a ss retail ISP or by the manager of a local network, i.e., "edge cache servers." By caching DNS information at the first two levels, the queries can be directed immediately to the remote server that can transform the inverse name into the actual name of the machine that uses the IP address, in the present examp_ie, "seawind.bellcore.com."
Web lookup 415 employs web spiders, which are software processes that visit web sites and automatically explore their contents, to obtain MFU DNs.
From the web content, web spiders extract names of other sites, which the web spiders can visit next, thus, exploring a large part of the Internet. Web spiders are typically used to build large index databases for index servers such as YAHOOT"", ALTAVISTAT"" and EXCITET"". One embodiment consistent with the present invention employs web spiders to discover new web sites. Web spiders only obtain an approximation of the MFU DNs because they collect most frequently accessed references, which is a different property from MFU DNs. The collection of MFU DNs obtained by web spiders are supplemented by feedback is process 430. Feedback process of ISP control cache servers 435 and edge local cache servers 445 collect statistics of the MFU DNs and send this data to central DNS database 410.
Refresh process 420 queries central DNS database 410 at intervals corresponding to TTL to determine whether the information in central DNS
2o database 410 has changed to ensure that local cache server 310 always contains up-to-date information. In one embodiment consistent with the present invention, refresh process 420 need not conduct a full update. In many cases, TTL may be set to a relatively short value, such as one day, because managers of the records might update the next day. DNS database 410, in such cases, 2s may be refreshed every day. In one preferred embodiment of the present invention, TTL is set to a level so that the information would not be updated too frequently, which would effectively preclude caching.
There is no need to perform a full update unless the information actually changes. If the information does not change, cache administrator 425 only 3o needs to send a message that essentially revalidates the current information. If refresh process 420 determines that the information actually changed, cache administrator 425 extracts the information from central DNS database 410 and selects only actual updates or new information to propagate to ISP control cache servers 435 and edge cache servers 445. For example, an update is 3s necessary when a new DN is added to central DNS database 410 by spider lookup 415 or feedback process 430. Replicator 440 of ISP control cache server 435 replicates the updates or new information to the next level of cache servers, i.e., edge cache servers 445. Replicator 440 of edge cache servers 445, in tum, replicates the updates or new information to other cache servers.
wo 99/Z7680 - ~ - PCTNS98/21239 s Thus, referring to Fig. 5, according to one embodiment consistent with the present invention, cache server 340 transmits DNS data to local cache server 310 at predetermined intervals, or TTL (step 501 ). The data includes the three types of data sets explained above, and subsequent transmissions need only contain updates to the existing DNS data at local cache server 310. Local io cache server 310 receives the DNS data or updates and updates MFU DNs table 320 (step 502). MFU DNs table 320, containing the three data sets, is preferably stored in cache for fast access.
When a user types in a user request, i.e., the DN or URL of a remote computer (e.g., www.example.com) using a browser at a local computer 110 is (step 502), local cache server 310 accesses MFU DNs table 320. If local cache server 310 finds the answer, which will be the case in most instances, local cache server 310 transmits the corresponding IP address to local computer 110 (step 503). Using the lP address, local computer 110 establishes connection with remote computer 150 (step 504). Thus, local cache server 310 responds to 2o queries directly, significantly reducing DNS processing time.
A different scenario occurs for DN requests of invalid names. In the present invention, cache server 340 generates validity codes of valid DN names to be stored in validity code table 330 of local cache server 310. In this manner, local cache server 310 checks its local cache to determine whether the 2s requested DN is valid without having to access root server 130. Since the memory capacity of local cache at local cache server 310 is limited, in one embodiment consistent with the present invention, local cache server 310 stores the validity codes of all top level domains as well as second level DNs of the most frequently accessed domain, e.g., ".com."
so Accordingly, referring to Fig. 6, root server 130 of ".com" provides a full listing of second level DNs to cache server 340 (step 600). Cache server 340 preferably generates validity codes of the top level domains and ".com" using hash coding. Cache server 340 transmits the validity codes to local cache server 310 (step 601 ). Although there are many ways to implement the hash 3s coding, the following Java method provides one example:
WO 99127680 - $ - PCT/US98/21239 to int hash (String domainName) int x, r, I;
char c;
x=0;
for (I=0; i<domainName.length(); I++){
r = (x»24)&255;
X«=8.
X~=r;
x ~_ (r«1 );
c = domainName.charAt(I);
if (c =_ '.') x ~= 37;
2o else if (c =_' ') x ~= 36;
else x "_ ((Character.digit(c, 36))&255);
2s return(x);
This algorithm returns a 32 bit integer, whose value is a function of the domain 3o name:
Domain name Hash code bellcore.com 370308165 inria.fr 1008476717 nsa 622275647 nsa.gov 623459329 Other hash coding techniques may be implemented to generate codes requiring much less memory than the full DNs to reduce the memory requirement of local cache server 310. The same technique should be used 3s consistently, however, within a single network platform by various components, e.g., local cache server 310, cache server 340, and cache administrator 425.
Additionally, the technique implemented should preferably be programmed to return results that only depend on the DNs and not the supporting platform.
wo ~m6so - 9 - PGT/US98n1239 s Accordingly, when a user types in the DN or URL of a remote computer (e.g., www.i-dont-really-know.com) using a browser at a local computer 110 (step 602), local cache server 310 accesses MFU DNs table 320. If local cache server 310 does not find the answer, rather than relaying the query to root server 130, local cache server 310 generates a check code of the DN in the io query using hash coding or other technique implemented in network 300. If the generated check code is not in validity code table 330, local cache server 310 transmits an error message to local computer 110 (step 603). Thus, local cache server 310 reduces processing time for queries for invalid DNs by eliminating the need to access root server 130. In the rare instance when the DN is not in is the MFU DNs table 320 and the check code matches one of the entries in validity code table 330, local cache server 310 processes the DN query in the traditional manner.
Systems and methods consistent with the present invention improve the efficiency of DN processing by storing MFU DNs and validity codes at local 2o cache servers. Such systems and methods process DN queries without accessing remote servers or root servers, thus, significantly reducing processing time. The central server is periodically updated with new and revised DN data and the central server propagates the updates to edge cache servers.
2s It will be apparent to those skilled in the art that various modifications and variations can be made in the systems and methods of the present invention without departing from the scope or spirit of the invention. For example, Internet has been used as an exemplary network setting. The teachings of the present application, however, may be easily adapted and applied in other network so settings by one ordinary skilled in the art. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with the true scope and spirit of the invention indicated by the following claims.
Claims (10)
1. A method for reducing the number of erroneous domain requests forwarded to domain name server (DNS) root servers from a local computer, the local computer being connected to a local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table and being connected to one or more remote root servers, the method comprising the steps of receiving a user request for a domain name, in response to said request, accessing the most frequently used domain names table in the local cache server, if the domain name is not in the most frequently used domain names table, generating a code check to access the validity code table in the local cache server, if the generated code check is not in the validity code table, returning an error message to the local computer, and if the generated code check is in the validity code table, forwarding the request to one of said remote root servers.
2. The method in accordance with claim 1 wherein the validity code table is a list of hash codes that completely represent the population of a domain.
3. The method in accordance with claim 2, further comprising the step of periodically updating the validity code table from a network cache server.
4. The method in accordance with claim 1, further comprising the step of periodically updating the local cache server from a network cache server, the network cache server providing the local cache server with a first data set comprising the most frequently used domain numbers and their associated domain addresses and a second data set comprising a complete listing of the existing domain names.
5. The method in accordance with claim 4 further comprising the network cache server providing the local cache server with a third data set comprising a listing of the highest levels of a domain name inverse tree
6. A method for enhancing the efficiency of a local cache server associated with a local computer for processing time domain requests, said method comprising the steps of populating the local cache server with a first set of data comprising the most frequently used domain numbers and populating the local cache server with a second set of data maintained by a network cache server, said second set of data comprising a complete listing of existing domain names to provide a validity code table at the local cache server.
7. The method in accordance with claim 6 wherein the validity code table at the local cache server is a list of hash codes that completely represent the population of the domain.
8. A system for processing with reduced processing time domain requests at a local computer, said system comprising a local cache server connected to the local computer and storing a most frequently used domain names table with associated domain addresses and a validity code table, a plurality of remote root servers connected to the local computer, means for receiving a user request for a domain name, means for accessing the most frequently used domain names table in said local cache server in response to said user request, means for generating a code check to access the validity table in said local cache server if the domain name is not in the most frequently used domain table, means for returning an error message to the local computer if the generated code check is not in the validity code table, and means for forwarding the request to one of said remote root servers if the generated code check is in the validity code table.
9. The system in accordance with claim 8 further comprising a network cache server, means for updating said local cache server from said network cache server, said network cache server providing said local cache server with a first data set comprising the most frequently used domain numbers and their associated domain addresses, a second data set comprising a complete listing of the existing domain names, and a third data set comprising a listing of the highest levels of a domain name inverse tree.
10. An article of manufacture capable of configuring a local cache server connected to a local computer to process domain name requests, the local cache server storing a most frequently used domain names table with associated domain addresses and a validity code table, the article comprising a computer-readable medium having computer readable code embodied therein for causing the local cache server to perform, the steps of receiving user request for a domain name, accessing the most frequently used domain names table in the local cache server in response to said request, generating a code check to access the validity code table in the local cache server if the domain name is not in the most frequently used domain names table, returning an error message to the local computer if the generated code check is not in the validity code table, and forwarding the request to a remote root server connected to the local computer if the generated code check is in the validity code table.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US6622797P | 1997-11-20 | 1997-11-20 | |
| US60/066,227 | 1997-11-20 | ||
| US09/135,619 US6016512A (en) | 1997-11-20 | 1998-08-18 | Enhanced domain name service using a most frequently used domain names table and a validity code table |
| US09/135,619 | 1998-08-18 | ||
| PCT/US1998/021239 WO1999027680A1 (en) | 1997-11-20 | 1998-10-07 | Enhanced domain name service |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2310277A1 CA2310277A1 (en) | 1999-06-03 |
| CA2310277C true CA2310277C (en) | 2005-06-14 |
Family
ID=26746501
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002310277A Expired - Fee Related CA2310277C (en) | 1997-11-20 | 1998-10-07 | Enhanced domain name service |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US6016512A (en) |
| EP (1) | EP1046256A1 (en) |
| JP (1) | JP2001524778A (en) |
| AU (1) | AU9793298A (en) |
| CA (1) | CA2310277C (en) |
| MY (1) | MY118161A (en) |
| TW (1) | TW399382B (en) |
| WO (1) | WO1999027680A1 (en) |
Families Citing this family (213)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7103794B2 (en) | 1998-06-08 | 2006-09-05 | Cacheflow, Inc. | Network object cache engine |
| US6393526B1 (en) | 1997-10-28 | 2002-05-21 | Cache Plan, Inc. | Shared cache parsing and pre-fetch |
| US6262987B1 (en) * | 1998-03-26 | 2001-07-17 | Compaq Computer Corp | System and method for reducing latencies while translating internet host name-address bindings |
| US6185608B1 (en) * | 1998-06-12 | 2001-02-06 | International Business Machines Corporation | Caching dynamic web pages |
| US6427187B2 (en) | 1998-07-31 | 2002-07-30 | Cache Flow, Inc. | Multiple cache communication |
| CA2349520C (en) * | 1998-10-30 | 2011-05-17 | Science Applications International Corporation | An agile network protocol for secure communications with assured system availability |
| US7188180B2 (en) * | 1998-10-30 | 2007-03-06 | Vimetx, Inc. | Method for establishing secure communication link between computers of virtual private network |
| US10511573B2 (en) | 1998-10-30 | 2019-12-17 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
| US6502135B1 (en) * | 1998-10-30 | 2002-12-31 | Science Applications International Corporation | Agile network protocol for secure communications with assured system availability |
| US7418504B2 (en) | 1998-10-30 | 2008-08-26 | Virnetx, Inc. | Agile network protocol for secure communications using secure domain names |
| US6374294B1 (en) * | 1998-12-23 | 2002-04-16 | Nortel Networks Limited | Method and apparatus for negating invalid networking addresses |
| US6351767B1 (en) * | 1999-01-25 | 2002-02-26 | International Business Machines Corporation | Method and system for automatically caching dynamic content based on a cacheability determination |
| ATE414942T1 (en) * | 1999-02-26 | 2008-12-15 | Henry Haugland | MASS PRODUCTION OF INDIVIDUAL VIRTUAL SERVERS, VIRTUAL WEBSITES AND VIRTUAL WEB OBJECTS |
| US6351743B1 (en) * | 1999-05-26 | 2002-02-26 | Lucent Technologies Inc. | Method and apparatus for operating domain name servers |
| NL1012721C2 (en) * | 1999-07-28 | 2001-01-30 | Benno Henricus Nicolaas Hijl | Device for registration, addressing, structuring and finding entities and data, based on identification codes. |
| US6449657B2 (en) * | 1999-08-06 | 2002-09-10 | Namezero.Com, Inc. | Internet hosting system |
| WO2001011443A2 (en) * | 1999-08-06 | 2001-02-15 | Namezero.Com, Inc. | Internet hosting system |
| CN1379946A (en) * | 1999-10-15 | 2002-11-13 | 汤姆森特许公司 | System for processing internet domain names and addresses |
| US6532490B1 (en) * | 1999-11-10 | 2003-03-11 | Bellsouth Intellectual Property Corporation | Methods and elements to reduce the number of quieries to a foreign network element |
| KR100856149B1 (en) * | 1999-11-26 | 2008-09-03 | 네테카 인코포레이티드 | Electronic mail server |
| EP1109375A3 (en) * | 1999-12-18 | 2004-02-11 | Roke Manor Research Limited | Improvements in or relating to long latency or error prone links |
| GB9929884D0 (en) * | 1999-12-18 | 2000-02-09 | Roke Manor Research | Transparent DNS cache |
| US6947440B2 (en) * | 2000-02-15 | 2005-09-20 | Gilat Satellite Networks, Ltd. | System and method for internet page acceleration including multicast transmissions |
| JP2004500774A (en) * | 2000-03-03 | 2004-01-08 | クゥアルコム・インコーポレイテッド | Method and apparatus for joining a group communication service in an existing communication system |
| DK1269714T3 (en) * | 2000-03-30 | 2007-01-08 | Intel Corp | Method and apparatus for distributed temporary storage |
| US6976090B2 (en) * | 2000-04-20 | 2005-12-13 | Actona Technologies Ltd. | Differentiated content and application delivery via internet |
| US6898623B1 (en) * | 2000-06-16 | 2005-05-24 | Hewlett-Packard Development Company L.P. | Simplified configuration of an internet-enabled device |
| US6728785B1 (en) | 2000-06-23 | 2004-04-27 | Cloudshield Technologies, Inc. | System and method for dynamic compression of data |
| US7003555B1 (en) * | 2000-06-23 | 2006-02-21 | Cloudshield Technologies, Inc. | Apparatus and method for domain name resolution |
| US9444785B2 (en) | 2000-06-23 | 2016-09-13 | Cloudshield Technologies, Inc. | Transparent provisioning of network access to an application |
| US7114008B2 (en) * | 2000-06-23 | 2006-09-26 | Cloudshield Technologies, Inc. | Edge adapter architecture apparatus and method |
| US8204082B2 (en) | 2000-06-23 | 2012-06-19 | Cloudshield Technologies, Inc. | Transparent provisioning of services over a network |
| US6829654B1 (en) | 2000-06-23 | 2004-12-07 | Cloudshield Technologies, Inc. | Apparatus and method for virtual edge placement of web sites |
| US7032031B2 (en) * | 2000-06-23 | 2006-04-18 | Cloudshield Technologies, Inc. | Edge adapter apparatus and method |
| US7318107B1 (en) | 2000-06-30 | 2008-01-08 | Intel Corporation | System and method for automatic stream fail-over |
| US7020709B1 (en) | 2000-06-30 | 2006-03-28 | Intel Corporation | System and method for fault tolerant stream splitting |
| US7814180B2 (en) * | 2000-07-13 | 2010-10-12 | Infoblox, Inc. | Domain name service server |
| US6701329B1 (en) * | 2000-09-14 | 2004-03-02 | Microsoft Corporation | Aging and scavenging of DNS resource records |
| WO2002029593A1 (en) * | 2000-10-02 | 2002-04-11 | Enic Corporation | Determining alternative textual identifiers, such as for registered domain names |
| US7117262B2 (en) * | 2000-11-01 | 2006-10-03 | Inktomi Corporation | Cooperative management of distributed network caches |
| CN100339846C (en) * | 2000-11-01 | 2007-09-26 | 斯雷普内姆斯·Com公司 | Domain Name acquisition and management system and method |
| US6651141B2 (en) | 2000-12-29 | 2003-11-18 | Intel Corporation | System and method for populating cache servers with popular media contents |
| WO2002063832A1 (en) * | 2001-02-05 | 2002-08-15 | Personity, Inc. | A system and method for filtering unavailable devices in a presence and availability management system |
| US7254226B1 (en) | 2001-05-08 | 2007-08-07 | At&T Intellectual Property, Inc. | Call waiting priority alert |
| US7082502B2 (en) * | 2001-05-15 | 2006-07-25 | Cloudshield Technologies, Inc. | Apparatus and method for interfacing with a high speed bi-directional network using a shared memory to store packet data |
| US7210022B2 (en) | 2001-05-15 | 2007-04-24 | Cloudshield Technologies, Inc. | Apparatus and method for interconnecting a processor to co-processors using a shared memory as the communication interface |
| US7890129B2 (en) | 2001-05-15 | 2011-02-15 | Eric Rosen | Method and apparatus for delivering information to an idle mobile station in a group communication network |
| US20040233892A1 (en) * | 2001-05-16 | 2004-11-25 | Roberts Linda Ann | Priority caller alert |
| US20020178238A1 (en) * | 2001-05-23 | 2002-11-28 | Thomas Fletcher | Caching address information in a communications system |
| US7085358B2 (en) | 2001-06-25 | 2006-08-01 | Bellsouth Intellectual Property Corporation | Visual caller identification |
| US7012999B2 (en) * | 2001-06-25 | 2006-03-14 | Bellsouth Intellectual Property Corporation | Audio caller identification |
| US7359987B2 (en) * | 2001-07-05 | 2008-04-15 | Enom, Inc. | Method and system for providing static addresses for Internet connected devices even if the underlying address is dynamic |
| US7315614B2 (en) * | 2001-08-14 | 2008-01-01 | At&T Delaware Intellectual Property, Inc. | Remote notification of communications |
| US7403768B2 (en) * | 2001-08-14 | 2008-07-22 | At&T Delaware Intellectual Property, Inc. | Method for using AIN to deliver caller ID to text/alpha-numeric pagers as well as other wireless devices, for calls delivered to wireless network |
| US7269249B2 (en) * | 2001-09-28 | 2007-09-11 | At&T Bls Intellectual Property, Inc. | Systems and methods for providing user profile information in conjunction with an enhanced caller information system |
| US7769823B2 (en) * | 2001-09-28 | 2010-08-03 | F5 Networks, Inc. | Method and system for distributing requests for content |
| US7079837B1 (en) * | 2001-11-06 | 2006-07-18 | Bellsouth Intellectual Property Corporation | Caller identification queue for wireless telephones |
| US20030093562A1 (en) * | 2001-11-13 | 2003-05-15 | Padala Chandrashekar R. | Efficient peer to peer discovery |
| US7315618B1 (en) * | 2001-12-27 | 2008-01-01 | At&T Bls Intellectual Property, Inc. | Voice caller ID |
| US20040064565A1 (en) * | 2002-02-06 | 2004-04-01 | International Business Machines Corporation | Obtaining location information using a rejection model |
| US9167036B2 (en) | 2002-02-14 | 2015-10-20 | Level 3 Communications, Llc | Managed object replication and delivery |
| US8533282B2 (en) * | 2002-02-25 | 2013-09-10 | Broadcom Corporation | System, method and computer program product for selectively caching domain name system information on a network gateway |
| US7152118B2 (en) * | 2002-02-25 | 2006-12-19 | Broadcom Corporation | System, method and computer program product for caching domain name system information on a network gateway |
| JP3883452B2 (en) * | 2002-03-04 | 2007-02-21 | 富士通株式会社 | Communications system |
| US7206388B2 (en) * | 2002-03-18 | 2007-04-17 | Openwave Systems Inc. | System and method for providing voice-activated presence information |
| US7343397B2 (en) * | 2002-03-29 | 2008-03-11 | Lucent Technologies Inc. | Method and apparatus for performing predictive caching of DNS requests by correlating IP addresses |
| US20050073999A1 (en) * | 2002-05-13 | 2005-04-07 | Bellsouth Intellectual Property Corporation | Delivery of profile-based third party content associated with an incoming communication |
| US20040215823A1 (en) * | 2002-06-28 | 2004-10-28 | Kleinfelter Kevin P. | System and method for reducing DNS lookup traffic in a computer data network |
| US7127488B1 (en) * | 2002-07-23 | 2006-10-24 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a caller in an internet-based communication system |
| US7139374B1 (en) * | 2002-07-23 | 2006-11-21 | Bellsouth Intellectual Property Corp. | System and method for gathering information related to a geographical location of a callee in a public switched telephone network |
| US7623645B1 (en) * | 2002-07-23 | 2009-11-24 | At&T Intellectual Property, I, L.P. | System and method for gathering information related to a geographical location of a caller in a public switched telephone network |
| JP3757917B2 (en) * | 2002-08-20 | 2006-03-22 | 日本電気株式会社 | Packet transfer device, packet transfer method resolution server, DNS server, network system, and program |
| US7254642B2 (en) * | 2003-01-30 | 2007-08-07 | International Business Machines Corporation | Method and apparatus for local IP address translation |
| US7463727B2 (en) * | 2003-04-18 | 2008-12-09 | At&T International Property, I, L.P. | Caller ID messaging device |
| US7978833B2 (en) * | 2003-04-18 | 2011-07-12 | At&T Intellectual Property I, L.P. | Private caller ID messaging |
| US7283625B2 (en) * | 2003-04-18 | 2007-10-16 | At&T Bls Intellectual Property, Inc. | Caller ID messaging telecommunications services |
| US7280646B2 (en) * | 2003-04-18 | 2007-10-09 | At&T Bls Intellectual Property, Inc. | Dynamic Caller ID messaging |
| US7443964B2 (en) * | 2003-04-18 | 2008-10-28 | At&T Intellectual Property, I,L.P. | Caller ID messaging |
| US7496607B2 (en) * | 2003-08-29 | 2009-02-24 | Yahoo! Inc. | Method and system for maintaining synchronization between a local data cache and a data store |
| US8160580B2 (en) * | 2003-09-15 | 2012-04-17 | Qualcomm Incorporated | Systems and methods for home carrier determination using a centralized server |
| US20050086385A1 (en) * | 2003-10-20 | 2005-04-21 | Gordon Rouleau | Passive connection backup |
| US7609832B2 (en) * | 2003-11-06 | 2009-10-27 | At&T Intellectual Property, I,L.P. | Real-time client survey systems and methods |
| US7623849B2 (en) * | 2003-11-13 | 2009-11-24 | At&T Intellectual Property, I, L.P. | Method, system, and storage medium for providing comprehensive originator identification services |
| US7672444B2 (en) | 2003-12-24 | 2010-03-02 | At&T Intellectual Property, I, L.P. | Client survey systems and methods using caller identification information |
| US6970546B2 (en) * | 2004-01-12 | 2005-11-29 | Bellsouth Intellecutal Property Corp. | Intelligent remote caller ID |
| FI116444B (en) * | 2004-03-25 | 2005-11-15 | Teliasonera Finland Oyj | Mediation of a contact between data transmission networks |
| US7523193B2 (en) * | 2004-05-18 | 2009-04-21 | International Business Machines Corporation | Method and apparatus for DNS pre-fetching for multiple clients |
| US8161184B2 (en) * | 2004-06-25 | 2012-04-17 | Apple Inc. | Method and apparatus for facilitating long-lived DNS queries |
| US8676922B1 (en) | 2004-06-30 | 2014-03-18 | Google Inc. | Automatic proxy setting modification |
| US7437364B1 (en) * | 2004-06-30 | 2008-10-14 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
| US20060002540A1 (en) * | 2004-07-02 | 2006-01-05 | Barrett Kreiner | Real-time customer service representative workload management |
| US8195136B2 (en) * | 2004-07-15 | 2012-06-05 | At&T Intellectual Property I, L.P. | Methods of providing caller identification information and related registries and radiotelephone networks |
| US7984163B2 (en) * | 2005-01-13 | 2011-07-19 | Flash Networks, Inc. | Method and system for optimizing DNS queries |
| US20060271395A1 (en) * | 2005-05-25 | 2006-11-30 | Harris Steven T | Distributed object identity in a virtual machine cluster |
| US7567582B2 (en) * | 2005-08-19 | 2009-07-28 | Microsoft Corporation | Branch office DNS storage and resolution |
| US20070088815A1 (en) * | 2005-10-13 | 2007-04-19 | Kenneth Ma | Automated setup and test confirmation of dynamic DNS service |
| JP4668775B2 (en) * | 2005-11-28 | 2011-04-13 | 株式会社日立製作所 | DNS server device |
| KR100776047B1 (en) * | 2006-01-19 | 2007-11-16 | 삼성전자주식회사 | Operating method of domain name system for updating adress information of server and domain name system of enabling the method |
| US8886771B2 (en) * | 2006-05-15 | 2014-11-11 | Cisco Technology, Inc. | Method and system for providing distributed allowed domains in a data network |
| US8234379B2 (en) * | 2006-09-14 | 2012-07-31 | Afilias Limited | System and method for facilitating distribution of limited resources |
| EP2078279A4 (en) * | 2006-10-24 | 2011-09-28 | Afilias Ltd | Supply chain discovery services |
| WO2008087633A2 (en) * | 2007-01-17 | 2008-07-24 | Traffix Communication Systems Ltd. | Method for statistics based performance optimization of regenerated code |
| US8812651B1 (en) | 2007-02-15 | 2014-08-19 | Google Inc. | Systems and methods for client cache awareness |
| CN100502367C (en) * | 2007-04-04 | 2009-06-17 | 华为技术有限公司 | Method and device for saving domain name system record |
| US8028090B2 (en) | 2008-11-17 | 2011-09-27 | Amazon Technologies, Inc. | Request routing utilizing client location information |
| US7991910B2 (en) | 2008-11-17 | 2011-08-02 | Amazon Technologies, Inc. | Updating routing information based on client location |
| US8243909B2 (en) | 2007-08-22 | 2012-08-14 | At&T Intellectual Property I, L.P. | Programmable caller ID |
| US8160226B2 (en) | 2007-08-22 | 2012-04-17 | At&T Intellectual Property I, L.P. | Key word programmable caller ID |
| WO2009111869A1 (en) * | 2008-03-10 | 2009-09-17 | Afilias Limited | Platform independent idn e-mail storage translation |
| US7970820B1 (en) | 2008-03-31 | 2011-06-28 | Amazon Technologies, Inc. | Locality based content distribution |
| US8156243B2 (en) * | 2008-03-31 | 2012-04-10 | Amazon Technologies, Inc. | Request routing |
| US8321568B2 (en) * | 2008-03-31 | 2012-11-27 | Amazon Technologies, Inc. | Content management |
| US8447831B1 (en) | 2008-03-31 | 2013-05-21 | Amazon Technologies, Inc. | Incentive driven content delivery |
| US8606996B2 (en) | 2008-03-31 | 2013-12-10 | Amazon Technologies, Inc. | Cache optimization |
| US8601090B1 (en) | 2008-03-31 | 2013-12-03 | Amazon Technologies, Inc. | Network resource identification |
| US8533293B1 (en) | 2008-03-31 | 2013-09-10 | Amazon Technologies, Inc. | Client side cache management |
| US7962597B2 (en) | 2008-03-31 | 2011-06-14 | Amazon Technologies, Inc. | Request routing based on class |
| US9762692B2 (en) * | 2008-04-04 | 2017-09-12 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
| US10924573B2 (en) | 2008-04-04 | 2021-02-16 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
| US8930538B2 (en) | 2008-04-04 | 2015-01-06 | Level 3 Communications, Llc | Handling long-tail content in a content delivery network (CDN) |
| US9407681B1 (en) | 2010-09-28 | 2016-08-02 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US7925782B2 (en) * | 2008-06-30 | 2011-04-12 | Amazon Technologies, Inc. | Request routing using network computing components |
| US9912740B2 (en) | 2008-06-30 | 2018-03-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US8677018B2 (en) * | 2008-08-25 | 2014-03-18 | Google Inc. | Parallel, side-effect based DNS pre-caching |
| US9197486B2 (en) * | 2008-08-29 | 2015-11-24 | Google Inc. | Adaptive accelerated application startup |
| US8521880B1 (en) | 2008-11-17 | 2013-08-27 | Amazon Technologies, Inc. | Managing content delivery network service providers |
| US8060616B1 (en) | 2008-11-17 | 2011-11-15 | Amazon Technologies, Inc. | Managing CDN registration by a storage provider |
| US8065417B1 (en) | 2008-11-17 | 2011-11-22 | Amazon Technologies, Inc. | Service provider registration by a content broker |
| US8732309B1 (en) | 2008-11-17 | 2014-05-20 | Amazon Technologies, Inc. | Request routing utilizing cost information |
| US8122098B1 (en) | 2008-11-17 | 2012-02-21 | Amazon Technologies, Inc. | Managing content delivery network service providers by a content broker |
| US8073940B1 (en) | 2008-11-17 | 2011-12-06 | Amazon Technologies, Inc. | Managing content delivery network service providers |
| US8688837B1 (en) | 2009-03-27 | 2014-04-01 | Amazon Technologies, Inc. | Dynamically translating resource identifiers for request routing using popularity information |
| US8412823B1 (en) | 2009-03-27 | 2013-04-02 | Amazon Technologies, Inc. | Managing tracking information entries in resource cache components |
| US8521851B1 (en) | 2009-03-27 | 2013-08-27 | Amazon Technologies, Inc. | DNS query processing using resource identifiers specifying an application broker |
| US8756341B1 (en) | 2009-03-27 | 2014-06-17 | Amazon Technologies, Inc. | Request routing utilizing popularity information |
| EP2237518A1 (en) * | 2009-03-30 | 2010-10-06 | Mitsubishi Electric Corporation | Pre-pushing of popular content in a network of end-user equipments |
| US9225794B2 (en) | 2009-03-31 | 2015-12-29 | Google Inc. | Adaptive DNS pre-resolution |
| US8782236B1 (en) | 2009-06-16 | 2014-07-15 | Amazon Technologies, Inc. | Managing resources using resource expiration data |
| US8397073B1 (en) | 2009-09-04 | 2013-03-12 | Amazon Technologies, Inc. | Managing secure content in a content delivery network |
| US8433771B1 (en) | 2009-10-02 | 2013-04-30 | Amazon Technologies, Inc. | Distribution network with forward resource propagation |
| US20110137980A1 (en) * | 2009-12-08 | 2011-06-09 | Samsung Electronics Co., Ltd. | Method and apparatus for using service of plurality of internet service providers |
| US9495338B1 (en) | 2010-01-28 | 2016-11-15 | Amazon Technologies, Inc. | Content distribution network |
| US8819148B2 (en) * | 2010-03-10 | 2014-08-26 | Afilias Limited | Alternate E-mail delivery |
| FR2958104A1 (en) * | 2010-03-26 | 2011-09-30 | France Telecom | DNS SERVER, GATEWAYS AND METHODS FOR MANAGING AN IDENTIFIER OF A PORTS RANGE IN DATA TRANSMISSION. |
| US9058381B2 (en) * | 2010-04-20 | 2015-06-16 | Verisign, Inc. | Method of and apparatus for identifying machine-generated textual identifiers |
| CN101895591B (en) * | 2010-07-23 | 2012-10-31 | 北京邮电大学 | Method and domain name server for increasing robustness of credible Internet domain name service |
| TWI415425B (en) * | 2010-07-26 | 2013-11-11 | Chunghwa Telecom Co Ltd | The home network gateway provides a domain name assignment method for multiple WAN connections |
| US8756272B1 (en) | 2010-08-26 | 2014-06-17 | Amazon Technologies, Inc. | Processing encoded content |
| EP2426894B1 (en) * | 2010-09-03 | 2015-02-18 | Deutsche Telekom AG | System and method of processing DNS request and DNS reply |
| US10958501B1 (en) | 2010-09-28 | 2021-03-23 | Amazon Technologies, Inc. | Request routing information based on client IP groupings |
| US9003035B1 (en) | 2010-09-28 | 2015-04-07 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US8577992B1 (en) | 2010-09-28 | 2013-11-05 | Amazon Technologies, Inc. | Request routing management based on network components |
| US10097398B1 (en) | 2010-09-28 | 2018-10-09 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US8938526B1 (en) | 2010-09-28 | 2015-01-20 | Amazon Technologies, Inc. | Request routing management based on network components |
| US8468247B1 (en) | 2010-09-28 | 2013-06-18 | Amazon Technologies, Inc. | Point of presence management in request routing |
| US8819283B2 (en) | 2010-09-28 | 2014-08-26 | Amazon Technologies, Inc. | Request routing in a networked environment |
| US9712484B1 (en) | 2010-09-28 | 2017-07-18 | Amazon Technologies, Inc. | Managing request routing information utilizing client identifiers |
| US8930513B1 (en) | 2010-09-28 | 2015-01-06 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US8924528B1 (en) | 2010-09-28 | 2014-12-30 | Amazon Technologies, Inc. | Latency measurement in resource requests |
| US8452874B2 (en) | 2010-11-22 | 2013-05-28 | Amazon Technologies, Inc. | Request routing processing |
| US9391949B1 (en) | 2010-12-03 | 2016-07-12 | Amazon Technologies, Inc. | Request routing processing |
| US8626950B1 (en) | 2010-12-03 | 2014-01-07 | Amazon Technologies, Inc. | Request routing processing |
| US10467042B1 (en) | 2011-04-27 | 2019-11-05 | Amazon Technologies, Inc. | Optimized deployment based upon customer locality |
| US20150135010A1 (en) * | 2011-09-07 | 2015-05-14 | Scott Thomas MacQuarrie | High availability system, replicator and method |
| EP2759075A4 (en) | 2011-09-23 | 2015-06-03 | Gilat Satellite Networks Ltd | Decentralized caching system |
| US8904009B1 (en) | 2012-02-10 | 2014-12-02 | Amazon Technologies, Inc. | Dynamic content delivery |
| US10021179B1 (en) | 2012-02-21 | 2018-07-10 | Amazon Technologies, Inc. | Local resource delivery network |
| US9172674B1 (en) | 2012-03-21 | 2015-10-27 | Amazon Technologies, Inc. | Managing request routing information utilizing performance information |
| US10623408B1 (en) | 2012-04-02 | 2020-04-14 | Amazon Technologies, Inc. | Context sensitive object management |
| 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 |
| 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 |
| US10205698B1 (en) | 2012-12-19 | 2019-02-12 | Amazon Technologies, Inc. | Source-dependent address resolution |
| US9430543B2 (en) * | 2013-03-15 | 2016-08-30 | Wal-Mart Stores, Inc. | Incrementally updating a large key-value store |
| US9294391B1 (en) | 2013-06-04 | 2016-03-22 | Amazon Technologies, Inc. | Managing network computing components utilizing request routing |
| KR102093166B1 (en) * | 2013-09-13 | 2020-03-25 | 에스케이텔레콤 주식회사 | A method for reducing connection time to website and an apparatus for the method |
| KR101524733B1 (en) * | 2013-10-22 | 2015-06-01 | 에스케이텔레콤 주식회사 | A mobile terminal for connecting to website through ip network and a method for reducing connection time to the website |
| US10097448B1 (en) | 2014-12-18 | 2018-10-09 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| US10091096B1 (en) | 2014-12-18 | 2018-10-02 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| US10033627B1 (en) | 2014-12-18 | 2018-07-24 | Amazon Technologies, Inc. | Routing mode and point-of-presence selection service |
| US10225326B1 (en) | 2015-03-23 | 2019-03-05 | Amazon Technologies, Inc. | Point of presence based data uploading |
| US9819567B1 (en) | 2015-03-30 | 2017-11-14 | 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 |
| US9887932B1 (en) | 2015-03-30 | 2018-02-06 | 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 |
| US10616179B1 (en) | 2015-06-25 | 2020-04-07 | Amazon Technologies, Inc. | Selective routing of domain name system (DNS) requests |
| US10097566B1 (en) | 2015-07-31 | 2018-10-09 | Amazon Technologies, Inc. | Identifying targets of network attacks |
| US9794281B1 (en) | 2015-09-24 | 2017-10-17 | Amazon Technologies, Inc. | Identifying sources of network attacks |
| 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 |
| US10498762B1 (en) | 2015-10-22 | 2019-12-03 | Versafe Ltd. | Methods for hypertext markup language (HTML) input field obfuscation and devices thereof |
| US10270878B1 (en) | 2015-11-10 | 2019-04-23 | Amazon Technologies, Inc. | Routing for origin-facing points of presence |
| US10257307B1 (en) | 2015-12-11 | 2019-04-09 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
| US10049051B1 (en) | 2015-12-11 | 2018-08-14 | Amazon Technologies, Inc. | Reserved cache space in content delivery networks |
| US10348639B2 (en) | 2015-12-18 | 2019-07-09 | Amazon Technologies, Inc. | Use of virtual endpoints to improve data transmission rates |
| US10075551B1 (en) | 2016-06-06 | 2018-09-11 | Amazon Technologies, Inc. | Request management for hierarchical cache |
| US10110694B1 (en) | 2016-06-29 | 2018-10-23 | Amazon Technologies, Inc. | Adaptive transfer rate for retrieving content from a server |
| US9992086B1 (en) | 2016-08-23 | 2018-06-05 | Amazon Technologies, Inc. | External health checking of virtual private cloud network environments |
| US10033691B1 (en) | 2016-08-24 | 2018-07-24 | Amazon Technologies, Inc. | Adaptive resolution of domain name requests in virtual private cloud network environments |
| US10616250B2 (en) | 2016-10-05 | 2020-04-07 | Amazon Technologies, Inc. | Network addresses with encoded DNS-level information |
| US10831549B1 (en) | 2016-12-27 | 2020-11-10 | Amazon Technologies, Inc. | Multi-region request-driven code execution system |
| US10372499B1 (en) | 2016-12-27 | 2019-08-06 | Amazon Technologies, Inc. | Efficient region selection system for executing request-driven code |
| US10938884B1 (en) | 2017-01-30 | 2021-03-02 | Amazon Technologies, Inc. | Origin server cloaking using virtual private cloud network environments |
| US10503613B1 (en) | 2017-04-21 | 2019-12-10 | Amazon Technologies, Inc. | Efficient serving of resources during server unavailability |
| US11075987B1 (en) | 2017-06-12 | 2021-07-27 | Amazon Technologies, Inc. | Load estimating content delivery network |
| US10447648B2 (en) | 2017-06-19 | 2019-10-15 | Amazon Technologies, Inc. | Assignment of a POP to a DNS resolver based on volume of communications over a link between client devices and the POP |
| US10742593B1 (en) | 2017-09-25 | 2020-08-11 | Amazon Technologies, Inc. | Hybrid content request routing system |
| US10592578B1 (en) | 2018-03-07 | 2020-03-17 | Amazon Technologies, Inc. | Predictive content push-enabled content delivery network |
| US10862852B1 (en) | 2018-11-16 | 2020-12-08 | Amazon Technologies, Inc. | Resolution of domain name requests in heterogeneous network environments |
| US11025747B1 (en) | 2018-12-12 | 2021-06-01 | Amazon Technologies, Inc. | Content request pattern-based routing system |
| US10944714B1 (en) | 2019-04-16 | 2021-03-09 | Amazon Technologies, Inc. | Multi-factor domain name resolution |
| CN110351115A (en) * | 2019-05-23 | 2019-10-18 | 中国平安财产保险股份有限公司 | Reduce method, apparatus, computer equipment and the storage medium of network access time delay |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2958388B2 (en) * | 1990-03-14 | 1999-10-06 | 富士ゼロックス株式会社 | Network relay device, relay method, and server |
| US5227778A (en) * | 1991-04-05 | 1993-07-13 | Digital Equipment Corporation | Service name to network address translation in communications network |
| US5434914A (en) * | 1992-12-31 | 1995-07-18 | At&T Corp. | Name translation in communications networks |
| JP4008049B2 (en) * | 1995-03-20 | 2007-11-14 | 富士通株式会社 | Address transmitting apparatus, address transmitting method and address transmitting system |
| US5664185A (en) * | 1995-05-22 | 1997-09-02 | Sterling Commerce, Inc. | Nameserver administration system and method |
| US5777989A (en) * | 1995-12-19 | 1998-07-07 | International Business Machines Corporation | TCP/IP host name resolution for machines on several domains |
| US5864854A (en) * | 1996-01-05 | 1999-01-26 | Lsi Logic Corporation | System and method for maintaining a shared cache look-up table |
-
1998
- 1998-08-18 US US09/135,619 patent/US6016512A/en not_active Expired - Lifetime
- 1998-10-07 CA CA002310277A patent/CA2310277C/en not_active Expired - Fee Related
- 1998-10-07 WO PCT/US1998/021239 patent/WO1999027680A1/en not_active Application Discontinuation
- 1998-10-07 JP JP2000522703A patent/JP2001524778A/en active Pending
- 1998-10-07 AU AU97932/98A patent/AU9793298A/en not_active Abandoned
- 1998-10-07 EP EP98952168A patent/EP1046256A1/en not_active Withdrawn
- 1998-11-11 TW TW087118782A patent/TW399382B/en not_active IP Right Cessation
- 1998-11-19 MY MYPI98005259A patent/MY118161A/en unknown
Also Published As
| Publication number | Publication date |
|---|---|
| MY118161A (en) | 2004-09-30 |
| EP1046256A1 (en) | 2000-10-25 |
| WO1999027680A1 (en) | 1999-06-03 |
| JP2001524778A (en) | 2001-12-04 |
| TW399382B (en) | 2000-07-21 |
| AU9793298A (en) | 1999-06-15 |
| US6016512A (en) | 2000-01-18 |
| CA2310277A1 (en) | 1999-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2310277C (en) | Enhanced domain name service | |
| Povey et al. | A distributed internet cache | |
| EP0955761B1 (en) | Method and server for accessing a network directory | |
| US6757733B2 (en) | Apparatus and method for improving performance of proxy server arrays that use persistent connections | |
| EP1493094B1 (en) | Method and system for tiered distribution in a content delivery network | |
| US7653747B2 (en) | Resolving virtual network names | |
| US8606926B2 (en) | Recursive DNS nameserver | |
| US6834302B1 (en) | Dynamic topology notification extensions for the domain name system | |
| US20040073707A1 (en) | Generating a list of network addresses for pre-loading a network address cache via multicast | |
| JP3725376B2 (en) | DNS inquiry apparatus, DNS inquiry method, and recording medium | |
| US20070208877A1 (en) | Method and Apparatus for Providing Name Services | |
| US20070204040A1 (en) | System and method for domain name filtering through the domain name system | |
| WO2000052594A2 (en) | Scalable and efficient domain name resolution | |
| Vingralek et al. | Web++: A System for Fast and Reliable Web Service. | |
| WO2009087620A2 (en) | Data distribution using dns | |
| US20050005027A1 (en) | Method and system for obtaining data through an IP transmission network by using an optimized domain name server | |
| CN103380607A (en) | DNS client address and RR TTL updating method, device and system | |
| US20020199020A1 (en) | Method and system for resolving names on a network gateway having multiple distinct network interfaces | |
| WO2002039699A1 (en) | Domain name system extensions to support reverse proxy operations and layer-7 redirection | |
| AU5756000A (en) | Distributed virtual web cache implemented entirely in software | |
| Bergner | Improving performance of modern peer-to-peer services | |
| KR20050003598A (en) | Domain name service provide system and method using dual domain name server | |
| JP2002259333A (en) | Method for transferring contents | |
| EP1141840B1 (en) | Arrangement and method related to distributed caching | |
| KR20010090090A (en) | A system and method to reduce the domain name resolving time with domain proxy server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |