System and method for facilitating distribution of limited resources

1. A system for distributing a limited resource selected from a plurality of limited resources in response to requests from a plurality of requestors, the system comprising:

a main server configured to provide standard application server functionality, including administering the plurality of limited resources, and to implement a first connectivity policy for limiting connectivity thereto;

a drop zone server that supports a limited number of commands for accessing the drop zone server, submitting requests thereto, and for verifying the connectivity thereto, the drop zone server configured to:

implement at least a subset of functionality provided by the main server for administering the plurality of limited resources;

receive resource requests directly from the plurality of requestors for the selected limited resource on behalf of the main server; and

implement a second connectivity policy, for limiting connectivity thereto, the second connectivity policy allows a lesser number of connections per requestor than the first connectivity policy; and

a drop zone control module configured to communicate with both the main server and the drop zone server to determine when the selected limited resource expires from the main server, parse the drop zone server for corresponding resource requests, determine which of the plurality of requestors is to receive the selected limited resource and distribute the selected limited resource accordingly.

2. The system of claim 1 , wherein the drop zone server is further configured to make the plurality of limited resources available simultaneously.

3. The system of claim 2 , where the plurality of limited resources comprises all limited resources expiring on a given day.

4. The system of claim 2 , wherein the selected limited resource is a previously used domain name; the resource request is a registration request; the main server is a main registry server configured to provide domain name system functionality.

5. The system of claim 2 , wherein the selected limited resource is a new domain name; the resource request is a registration request; and the main server is a main registry server configured to provide domain name system functionality.

6. The system of claim 2 , wherein the selected limited resource is an auction item; the resource request is a bid on the auction item; and the main server is a main auction server configured to provide auction functionality.

7. The system of claim 1 , wherein the second connectivity policy limits each client to three connections.

8. A non-transitory computer readable medium having stored thereon instructions, which, when executed by a computer, cause the computer to implement the steps of:

determining a plurality of limited resources expiring from a main server during a predetermined expiration period, the main server configured to administer the plurality of limited resources, and to implement a first connectivity policy for limiting connectivity thereto;

making the plurality of limited resources available simultaneously on a drop zone server, the drop zone server configured to implement at least a subset of functionality provided by the main server and to implement a second connectivity policy, for limiting connectivity thereto, the second connectivity policy allows a lesser number of connections per requestor than the first connectivity policy;

the drop zone server supports limited number of commands for accessing the drop zone server, submitting requests thereto, and for verifying the connectivity thereto;

allowing resource requests to be received at the drop zone server directly from a plurality of clients for a registration period starting at a predetermined time; and

processing the resource requests after the registration period by correlating the limited resources with the resource requests.

9. The non-transitory computer readable medium of claim 8 , wherein the plurality of limited resources comprises all limited resources expiring during a given day.

10. The non-transitory computer readable medium of claim 8 , wherein the limited resources are processed as they expire.

11. The non-transitory computer readable medium of claim 8 , wherein duplicate resource requests are maintained and processed in a sequence in which they are received.

12. The non-transitory computer readable medium of claim 11 , wherein if one of the resource requests fails, a subsequent duplicate resource request is processed.

13. The non-transitory computer readable medium of claim 12 , wherein the resource request fails due to insufficient funds in an account of a corresponding requesting client.

14. The non-transitory computer readable medium of claim 8 , further comprising instructions for providing a connection period prior to allowing the resource requests for enabling the clients to ensure that they can establish a connection.

15. The non-transitory computer readable medium of claim 8 , wherein the limited resource is a previously used domain name; the resource request is a registration request; and the client is a registrar.

16. The non-transitory computer readable medium of claim 8 , wherein the limited resource is a new domain name; the resource request is a registration request; and the client is a registrar.

17. The non-transitory computer readable medium of claim 8 , wherein the limited resource is an auction item; the resource request is a bid on the limited resource; and the client is a bidder.

18. A system for distributing a domain name in response to requests from a plurality of requestors, the system comprising:

a main server configured to provide standard domain name server functionality, including administering the domain name, and to implement a first connectivity policy for limiting connectivity thereto;

a drop zone server that supports a limited number of commands for accessing the drop zone server, submitting requests thereto, and for verifying the connectivity thereto, the drop zone server configured to:

implement at least a subset of functionality provided by the main server for connecting with the plurality of requestors and receiving registration requests for the domain name;

receive registration requests directly from the plurality of requestors for the domain name on behalf of the main server; and

implement a second connectivity policy, for limiting connectivity thereto, the second connectivity policy allows a lesser number of connections per requestor than the first connectivity policy; and

a drop zone control module configured to communicate with both the main server and the drop zone server to determine when the domain name expires from the main server, parse the drop zone server for corresponding resource requests, determine which of the plurality of requestors is to receive the domain name, and distribute the domain name accordingly.