Pathway-specific, registry-integrated domain name registration system

• US 7,904,898 B2
• Filed: 08/13/2003
• Issued: 03/08/2011
• Est. Priority Date: 08/13/2002
• Status: Active Grant

• Current Assignee: Web.com Group, Inc.
• Original Assignee: SnapNames.com, Inc.
• Inventors: King, Raymond, Biesecker, Blake, Bayles, Len
• Primary Examiner(s): Vo; Ted T
• Application Number:
  US10/641,395
• Publication Number:
  US 20040172463A1
• Time in Patent Office: 2,764 Days
• Field of Search: 717100-101, 717163-165, 717120-121, 717168-171, 717174-178, 709/203, 709/223, 709/226
• US Class Current: 717/171
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]

Abstract

Embodiments of the present invention reliably effect successive registrations of a domain name through implementing a backorder system (504) integrated with the registry (520) maintaining the current registration for the domain name. Because the backorder system (504) is directly integrated with the registry (520), a successful new registration can be achieved following the lapse of the current registration. The registry can employ modified registration control logic and new and modified registry commands (324). These modifications to the standard registration system enable a registry (520) to limit successive registrations of the domain name to an entity, such as a registrar (500), that employs the backorder service (504).

Claims

1. In a domain name registration system in which a registry maintains a current registration for a particular domain name, a method for effecting a succeeding registration of the particular registered domain name by backordering the particular domain name with the registry, the method comprising the steps of:

provisioning a backorder system to receive a request to backorder a domain name having a current registration maintained by a registry;

receiving the backorder request for the domain name prior to expiration of the current registration of the domain name;

storing the backorder request in both a backorder service database 302 and in the registry 320; and

implementing one or more new registry commands 324c for receiving a request at the registry to add a succeeding registration of the backordered domain name following expiration of the current registration, wherein;

the new registry commands include a RIPEN_NAME command available only to the backorder system to ripen a backorder request stored in the registry into a new registration;

at the registry, checking for the presence of a corresponding stored backorder request in response to receiving an ADD command; and

responsive to a backorder being already stored in the registry, granting the request for the succeeding registration of the domain name if it comes from the backorder system as a RIPEN_NAME command 324c, and blocking the ADD command for the succeeding registration if it does not come from the backorder system.

2. The method of claim 1 further comprising the step of storing the backorder request in a data source 302 maintained by the backorder system.

3. The method of claim 2 further comprising the step of synchronizing the backorder system data source 302 with the registry data source 326.

4. The method of claim 1 and further comprising:

receiving a second request for a succeeding registration of the domain name, storing the second request in the data source maintained by the registry;

and the registry granting the first request before the second request, so as to define an ordered backorder queue encompassing the first request and second request.

5. The method of claim 1 wherein the new registry commands available only to the backorder system include a command to add a backorder request whereby the backorder system communicates the backorder request to the registry.

6. The method of claim 1 wherein the one or more registry commands include a qualified add command, the qualified add command being available to an interested entity, other than the backorder system, to request the subsequent registration of the domain name.

7. The method of claim 6 wherein the one or more registry commands further include a status-check command, in response to which the registry checks its data source for the existence of a backorder request directed to the domain name that is the target of the status-check command.

8. The method of claim 7 wherein the status-check command is implemented in response to the registry receiving the qualified add command.

9. The method of claim 7 wherein, following the lapse of the current registration, if the status-check command verifies that no backorder request exists, the registry can grant a first received succeeding registration request of the interested entity.

10. The method of claim 1 wherein the backorder system receives the backorder request from a registrar.

11. The method of claim 1 wherein the backorder system receives the backorder request from a current registrant of the domain name.

12. The method of claim 1 wherein the backorder system receives the backorder request from a prospective registrant of the domain name.

13. The method of claim 1 wherein the registry is a thick registry.

14. The method of claim 1 wherein the provisioning step includes provisioning the backorder system as an internal component of the registry.

15. The method of claim 1 further comprising:

receiving a confirmation from the registry that the domain name has been registered.

16. A machine-readable medium on which are stored computer program instructions for performing the method for effecting a succeeding registration of the domain name by backordering the domain name with the registry in advance of the current registration lapsing according to claim 1.

17. A method for establishing an orderly succession of registrations for a domain name maintained by a registry, the method comprising the steps of:

collecting one or more backorder requests with a backorder system, each backorder request identifying a desired domain name having a current registration maintained by a registry and requesting a succeeding registration of the desired domain name for an interested entity;

communicating the one or more backorder requests to the registry in the order in which the backorder requests were received;

in response to the registry purging a current registration for the desired domain name, requesting the succeeding registration of the desired domain name through the backorder system for the interested entity corresponding to a first-received of the one or more backorder requests; and

in response to the registry adding the desired domain name to a registry domain database, receiving a confirmation of the addition from the registry.

18. The method of claim 17 further comprising the step of implementing one or more registry commands by which the registry only enables the succeeding registration when requested by the backorder system for the interested entity corresponding to the first-received backorder request.

19. The method of claim 18 wherein the one or more registry commands include a command to ripen the backorder, the ripen command being available only to the backorder system for use in fulfilling the first received backorder request.

20. The method of claim 19 wherein the one or more registry commands further include a command, available only to the backorder system, to delete a previously collected backorder request;

and

the method further comprising the step of, responsive to the first-received backorder request being deleted or ripened, enabling the ripen command for fulfillment of a second-received backorder request.

21. The method of claim 17 further comprising the step of implementing a registry command enabling a qualified addition of a new registration for the desired domain name, wherein:

the registry denies the qualified addition command during the current registration;

the registry denies the qualified addition command after the current registration is purged if the one or more backorder requests have been communicated to the registry; and

the registry approves the qualified addition command after the current registration is purged if no backorder request has been communicated to the registry.

22. The method of claim 17 wherein the backorder system can collect the one or more backorder requests from a registrar or registrant.

23. The method of claim 17 wherein the registry is a thick registry.

24. The method of claim 17 further comprising the step of provisioning the backorder system as an internal component of the registry.

25. A machine-readable medium on which are stored computer program instructions for performing the method for establishing an orderly succession of registrations for a domain name maintained by a registry according to claim 17.

26. A method for orderly processing multiple requests for a succeeding registration of a desired domain name, the method comprising the steps of:

offering an interface to a backorder service to receive one or more requests for a succeeding registration of a domain name having a current registration maintained by a registry;

communicating the one or more requests to the registry along with a suggested order for fulfilling the one or more requests upon a lapse in the current registration;

implementing a first registry command for use by the backorder service to request the succeeding registration;

implementing a second registry command for use by one or more other interested entities to request the succeeding registration;

rendering the first registry command effective, and the second registry command ineffective, for requesting the succeeding registration for the domain name corresponding to the one or more communicated backorder requests, whereby a successful succeeding registration request can only come from the backorder service when there are one or more backorder requests; and

registering the domain name upon receiving a registration request for the succeeding registration from the backorder service.

27. The method of claim 26 further comprising the step of enabling a second succeeding registration by the one or more other interested entities through the second registry command for a second domain that does not have a corresponding backorder request.

28. The method of claim 26 further comprising:

receiving a confirmation from the registry that the domain name has been registered.

29. A machine-readable medium on which are stored computer program instructions for performing the method for orderly processing multiple requests for a succeeding registration of a desired domain name according to claim 26.

30. A system for processing a backorder for a registered domain name, comprising:

a backorder system that receives a request to backorder a domain name having a current registration; and

a registry maintaining the current registration for the domain name;

wherein the registry includes;

a data source storing an indication that the domain name has a corresponding backorder request;

an application programming interface bifurcating a first registry command available to the backorder management system from a second registry command available to one or more entities other than the backorder management system, wherein the first and second registry commands provide domain name registration functionality; and

a registration management system with access to the data source to detect the backorder indication, and, upon detecting the backorder indication, disabling the second registry command to block a successive registration by the one or more entities, and enabling the first registry command to allow the successive registration by the backorder management system, and wherein the registration management system registers the domain name upon receiving a registration request.

31. The system of claim 30 wherein the first registry command is a ripen-backorder command to effect a registration for a backordered domain name.

32. The system of claim 30 wherein the second registry command is a modified add-registration command.

33. The system of claim 32 wherein the add-registration command is modified to require the registry to check the data source to detect the backorder indication.

34. The system of claim 30 wherein the register maintains the data source locally.

35. The method of claim 30 wherein the registry is chosen from a group consisting of a thick registry, a thin registry, and a registry offering combined registry-registrar functionality.

36. The system of claim 30 wherein the backorder system receives a confirmation from the registry that the domain name has been registered.

37. An Internet domain name registration system comprising:

a registry that implements one or more registry commands accessible by one or more registrars to manage current registrations for one or more domain names maintained by the registry;

a registry data source storing records indicating which of the domain names maintained by the registry have corresponding backorder requests;

a backorder system administering collection and processing of the backorder requests and communicating with the registry to update the registry data source with a current status of the backorder requests;

customized registry commands requiring the registry to identify the domain names having corresponding backorder requests before the registry grants a registration, to preclude a subsequent registration of the identified domain names by a registrar, and to afford the backorder system the opportunity to effect the subsequent registrations; and

wherein the registry registers the domain names having corresponding backorder requests upon receiving a registration request.

38. The system of claim 37 wherein the customized registry commands include a ripen-backorder registry command available only to the backorder system to effect a subsequent registration of a domain name having a corresponding backorder, the subsequent registration following a lapse in a current registration for the domain name.

39. The system of claim 37 wherein the customized registry commands include a check-status command available to the registrar to determine a registration status for a specific domain name and a backorder status for the specific domain name.

40. The system of claim 39 wherein the customized registry commands further include a modified add-registration command accessible by the registrar, the modified add-registration command requiring implementation of the check-status command.

41. The system of claim 40 wherein the add-registration command fails in response to the check-status command identifying that the registration status or backorder status are valid.

42. The system of claim 37 wherein the registry data source is a database locally maintained by the registry.

43. The system of claim 37 wherein the backorder system receives a confirmation from the registry that the domain names that had corresponding backorder requests have been registered.