System and method for creating subdomains or directories for a domain name

• US 9,953,105 B1
• Filed: 11/14/2014
• Issued: 04/24/2018
• Est. Priority Date: 10/01/2014
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Inventors: Gupta, Nitin
• Primary Examiner(s): Hoang, Son T
• Application Number:
  US14/542,224
• Time in Patent Office: 1,257 Days
• Field of Search: None
• CPC Class Codes: G06F 16/9017 using directory or table look-up use of a directory or look-up table in file systems G06F16/13
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Domain name mappings are created using a system and method. A registration of a first domain name by a user associated with a user account is detected and a Domain Name System (DNS) server is accessed to identify a second domain name selected from a plurality of domain names associated with the user account. Without input from the user, a subdomain for the second domain name is created by modifying a DNS record of the second domain name or a directory at the second domain name is created. The subdomain or the directory correspond to a top-level domain (TLD) of the first domain name. A redirect from the subdomain or the directory of the second domain name is created to the first domain name or from the first domain name to the at least one of the subdomain and the directory of the second domain name.

Claims

1. A method comprising:

detecting, by a computing device, a registration of a first domain name by a user associated with a user account;

automatically accessing, by the computing device and without input from the user, a Domain Name System (DNS) server to identify a second domain name selected from a plurality of domain names associated with the user account, the identified second domain name at least partially matches the registered first domain name;

automatically creating, by the computing device and without input from the user, a directory at the second domain name, a name of the created directory comprising a top-level domain (TLD) of the first domain name; and

automatically configuring, by the computing device and without input from the user, a redirect from the created directory of the second domain name to the first domain name or from the first domain name to the created directory of the second domain name.

2. The method of claim 1, wherein the configuring the redirect further comprises configuring at least one of a Hypertext Transfer Protocol (HTTP) 301 redirect, an HTTP 302 redirect, a Meta Refresh redirect, and a DNS redirect.

3. The method of claim 1, wherein the plurality of domain names associated with the user account is sorted into at least one project associated with the user account, and wherein the second domain name comprises a primary domain name of the at least one project and wherein the first domain name comprises a secondary domain name mapped to the primary domain name within the at least one project.

4. The method of claim 3, further comprising:

creating automatically, by the computing device, the directory for the second domain name in response to the computing device identifying the first domain name, wherein the identifying the first domain name further comprises identifying that the first domain name has been mapped to the second domain name within the at least one project.

5. The method of claim 1, further comprising enabling the user of the user account to override the redirect.

6. The method of claim 1, further comprising:

presenting to the user of the user account with at least one proposal for the redirect prior to the configuring the redirect; and

configuring automatically the redirect in response to receipt of a positive response from the user with respect to the at least one proposal.

7. The method of claim 1, further comprising:

enabling the user of the user account to alter a user account setting to enable or disable automatically creating, by the computing device, the directory; and

creating automatically, by the computing device, the directory when the user account setting enables the automatically creating the directory.

8. The method of claim 1, further comprising:

enabling the user of the user account to alter a user account setting to enable or disable automatically configuring by the computing device the redirect; and

configuring automatically, by the computing device, the redirect when the user account setting enables the automatically configuring the redirect.

9. A system, comprising:

a computing device, implemented at least partially by hardware, in communication with a Domain Name System (DNS) and being configured to perform the following steps of;

detecting, by the computing device, a registration of a first domain name by a user associated with a user account;

automatically accessing, by the computing device and without input from the user, the DNS server to identify a second domain name selected from a plurality of domain names associated with the user account, the identified second domain name at least partially matches the registered first domain name;

automatically creating, by the computing device and without input from the user, a directory at the second domain name, a name of the created directory comprising a top-level domain (TLD) of the first domain name; and

automatically configuring, by the computing device and without input from the user, a redirect from the created directory of the second domain name to the first domain name or from the first domain name to the created directory of the second domain name.

10. The system of claim 9, wherein the computing device is configured to:

configure automatically at least one of a Hypertext Transfer Protocol (HTTP) 301 redirect, an HTTP 302 redirect, a Meta Refresh redirect, and a DNS redirect from the directory of the second domain name to the first domain name.

11. The system of claim 9, wherein the computing device is configured to:

sort the plurality of domain names into at least one project associated with the user account, wherein the second domain name comprises a primary domain name of the at least one project and wherein the first domain name comprises a secondary domain name mapped to the primary domain name within the at least one project.

12. The system of claim 11, wherein the computing device is configured to:

identify the first domain name by identifying that the first domain name has been mapped to the second domain name within the at least one project; and

create automatically the directory for the second domain name in response to the computing device identifying the first domain name.

13. The system of claim 9, wherein the computing device is configured to:

enable the user of the user account to override the redirect.

14. The system of claim 9, wherein the computing device is configured to:

present to the user of the user account with at least one proposal for the redirect prior to configuring the redirect; and

configure automatically the redirect in response to receipt of a positive response from the user with respect to the at least one proposal.

15. The system of claim 9, wherein the computing device is configured to:

enable the user of the user account to alter a user account setting to enable or disable automatically creating by the computing device the directory; and

create automatically the directory when the user account setting enables creating the directory.

16. The system of claim 9, wherein the computing device is configured to:

enable the user of the user account to alter a user account setting to enable or disable automatically configuring by the computing device the redirect; and

configure automatically the redirect when the user account setting enables configuring the redirect.

17. A server device, implemented at least partially by hardware, configured to:

detect a registration of a first domain name by a user associated with a user account;

automatically access, without input from the user, a Domain Name System (DNS) server to identify a second domain name selected from a plurality of domain names associated with the user account, the identified second domain name at least partially matches the registered first domain name;

automatically create, without input from the user, a directory at the second domain name, a name of the created directory comprising a top-level domain (TLD) of the first domain name; and

automatically configure, without input from the user, a redirect from the created directory of the second domain name to the first domain name or from the first domain name to the created directory of the second domain name.

18. The server device of claim 17, further configured to:

sort the plurality of domain names into at least one project associated with the user account, wherein the first domain name comprises a primary domain name of the at least one project and wherein the second domain name comprises a secondary domain name mapped to the primary domain name within the at least one project.

19. The server device of claim 18, further configured to:

create automatically the directory for the first domain name in response to the second domain name being mapped to the first domain name within the at least one project; and

configure automatically the redirect in response to the second domain name being mapped to the first domain name within the at least one project.

20. The server device of claim 17, further configured to:

enable the user of the user account to alter at least one user account setting to enable or disable at least one of automatically creating by the server device the directory and automatically configuring by the server device the redirect; and

at least one of create automatically the directory and configure automatically the redirect according to the at least one user account setting.