MULTI-THREADED NAME SERVER

• US 20010049747A1
• Filed: 08/06/1999
• Published: 12/06/2001
• Est. Priority Date: 08/06/1999
• Status: Abandoned Application

• Current Assignee: NameZero.Com, Inc.
• Original Assignee: NameZero.Com, Inc.
• Inventors: STANBACH, FRANCIS J.
• Application Number:
  US09/369,647
• Publication Number:
  US 20010049747A1
• Time in Patent Office: Days
• US Class Current: 709/245
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/4555 Directories for electronic mail or instant messaging
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A method and apparatus for mapping between a host name and a host address is provided. According to one aspect of the invention, a multi-threaded name server handles multiple concurrent name requests, and is particularly well suited for a host system controlling information relating to a large number of domain names. In a preferred embodiment as described herein, a multi-threaded name server comprises a request dispatcher thread capable of spawning multiple child threads. For each name request received by the request dispatcher thread, the request dispatcher spawns a child thread to handle the request. The child threads query a host name hash table to determine whether the host name hash table comprises a host name matching a host name in the name request. The result is a multi-threaded, non-blocking name server capable of handling multiple concurrent name requests for a large number of domain names. According to a particular embodiment, the multi-threaded name server further comprises a database coherency thread. The database coherency thread continuously or regularly queries a database comprising information corresponding to a plurality of domain names. When information in the database changes, the database coherency thread updates the host name cache to reflect any changes.

Claims

1. A method for identifying an address corresponding to a domain name, the method comprising:

receiving a first request at a request dispatcher thread, said first request comprising a first host name;

spawning a first child thread to said request dispatcher thread;

identifying at least a portion of said first host name in a host name cache;

returning from said first child thread a first host address corresponding to said first host name;

receiving a second request at said request dispatcher thread, said second request comprising a second host name;

spawning a second child thread to said request dispatcher thread, wherein said first child thread and said second child thread are active concurrently and share one or more resources in a program environment;

identifying at least a portion of said second host name in said host name cache; and

returning from said second child thread a second host address corresponding to said second host name.

2. The method of

claim 1

, further comprising:

continuously querying a database by way of a database coherency thread, said database comprising information corresponding to a plurality of host names; and

continuously updating said host name cache by way of said database coherency thread to represent said information corresponding to said plurality of host names.

3. The method of

claim 1

, wherein said first host address and said second host address are the same.

4. The method of

claim 1

, further comprising:

failing to respond to said first request if said first host name is not found in said host name cache; and

failing to respond to said second request if said second host name is not found in said host name cache.

5. The method of

claim 1

, wherein said first host address is a mail server internet protocol address and wherein said second host address is a web server internet protocol address.

6. A method for providing host name services comprising:

executing a non-blocking host name service on one or more processors connected to a network, said non-blocking host name service responding to multiple concurrent host name resolution requests by spawning multi-threaded request handler threads for said multiple concurrent host name resolution requests;

concurrently executing a database coherency thread with said non-blocking host name service, said database coherency thread continuously updating a host name hash table based on changing values in a centralized database; and

returning a host address corresponding to at least one of said multiple concurrent host name resolution requests, said host address extracted from an address table, if data from said at least one of said multiple concurrent host name resolution requests corresponds to data in said host name hash table.

7. The method of

claim 6

, wherein said non-blocking host name service responds to said multiple concurrent host name resolution requests by:

receiving said multiple concurrent host name resolution request at a request dispatcher, wherein said request dispatcher spawns said multi-thread request handler threads; and

responding to each of said multiple concurrent host name resolution requests with its corresponding request handler thread only if said non-blocking host name service is an authority for a host name corresponding to said host name resolution request.

8. A computer readable medium having stored therein one or more sequences of instructions for identifying an address corresponding to a domain name, said one or more sequences of instructions causing one or more processors to perform a plurality of acts, said acts comprising:

receiving a first request at a request dispatcher thread, said first request comprising a first host name;

spawning a first child thread to said request dispatcher thread;

identifying at least a portion of said first host name in a host name cache;

returning from said first child thread a first host address corresponding to said first host name;

receiving a second request at said request dispatcher thread, said second request comprising a second host name;

spawning a second child thread to said request dispatcher thread, wherein said first child thread and said second child thread are active concurrently and share one or more resources in a program environment;

identifying at least a portion of said second host name in said host name cache; and

returning from said second child thread a second host address corresponding to said second host name.

9. The computer readable medium of

claim 8

, said acts further comprising:

continuously querying a database by way of a database coherency thread, said database comprising information corresponding to a plurality of host names; and

continuously updating said host name cache by way of said database coherency thread to represent said information corresponding to said plurality of host names.

10. The computer readable medium of

claim 8

, wherein said first address and said second address are the same.

11. The computer readable medium of

claim 8

, said acts further comprising:

failing to respond to said first request if said first host name is not found in said host name cache; and

failing to respond to said second request if said second host name is not found in said host name cache.

12. The computer readable medium of

claim 8

, wherein said first address is a mail server internet protocol address and wherein said second address is a web server internet protocol address.

14. The multi-threaded domain name server of

claim 12

, wherein said processor is further configured to spawn a second thread, said second thread configured to maintain coherency between said information representative of said plurality of domain names in said table and said plurality of domain names in said database.

13. A multi-threaded domain name server comprising:

a processor;

a memory communicatively coupled to said processor;

a database communicatively coupled to said processor, said database comprising a plurality of domain names;

wherein said memory is configured to store a host name cache, said host name cache comprising information representative of said plurality of domain names in said database; and

wherein

said processor is configured spawn a first thread and a plurality of multi-threaded child threads, said first thread dispatching a plurality of concurrent incoming domain name requests to said plurality of child threads, each of said child threads configured to handle exactly one of said plurality of concurrent incoming domain name requests by identifying data in said host name cache corresponding to exactly one of said incoming domain name requests, and wherein two or more of said child threads are active concurrently.

15. The multi-threaded domain name server of

claim 13

, wherein said processor is further configured to execute a database coherency thread, and wherein said database coherency thread is configured to continuously query said database and update said host name cache to correspond to said database.

16. The multi-threaded domain name server of

claim 13

, wherein said plurality of child threads are individually configured to fail to respond to a corresponding domain name request if a domain name in said corresponding domain name request is not found in said table.

17. The multi-threaded domain name server of

claim 13

, wherein each of said plurality of child threads are configured to return either a mail server internet protocol address or a web server internet protocol address.