SYSTEM AND METHOD FOR DOMAIN MANAGEMENT AND MIGRATION

• US 20170142061A1
• Filed: 01/30/2017
• Published: 05/18/2017
• Est. Priority Date: 11/12/2013
• Status: Active Grant

• Current Assignee: III Holdings 1, LLC
• Original Assignee: III Holdings 1, LLC
• Inventors: Feinleib, David A., Burnett, R. Alan
• Granted Patent: US 10,530,743 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 61/302 Administrative registration, e.g. for domain names at internet corporation for assigned names and numbers [ICANN]
• 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 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/06 specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/306 User profiles

Abstract

A system and method for managing domain registrations across multiple domain registrars, and for migrating domains from one or more server computers to one or more other server computers. More specifically but not exclusively, disclosure relates to software processes, algorithms, and protocols for the management and movement of domains, as accessed across a network.

Claims

1. A data migration method implemented by a server, comprising:

receiving a user login to a user'"'"'s account;

provide available domains associated with the user'"'"'s account;

receiving a selection of at least one of the available domains;

migrating the at least one of the available domains from a first database of a first server to a second database of a second server;

receiving account information corresponding to the user; and

registering the selected available domain with the user'"'"'s account.

2. The data migration method implemented by the server of claim 1, further comprising migrating a domain using an IP address of the domain from the first database of the first server to the second database of the second server.

3. The data migration method implemented by the server of claim 1, further comprising migrating a domain using a fully qualified domain name (FQDN) of a web site from the first database of the first server to the second database of the second server.

4. The data migration method implemented by the server of claim 3, further comprising deducing an IP address of the web site to migrate the domain using the FQDN from the first database of the first server to the second database of the second server.

5. The data migration method implemented by the server of claim 1, further comprising detecting the available domains associated with the user'"'"'s accounts.

6. The data migration method implemented by the server of claim 5, wherein the detecting the available domains includes accepting an inputted user list of individual domains with associated usernames and passwords.

7. The data migration method implemented by the server of claim 5, wherein the detecting the available domains includes accessing all domains associated with an administrative username and password on the first server.

8. The data migration method implemented by the server of claim 5, wherein the detecting the available domains includes screen-scraping domain data from a control panel of the first server accessed via a username, password, and IP address of the control panel.

9. The data migration method implemented by the server of claim 1, wherein the migrating includes at least one of an active migration mode and passive migration mode.

10. The data migration method implemented by the server of claim 9, wherein the active migration mode includes accessing the first server via a secure shell connection.

11. The data migration method implemented by the server of claim 9, wherein the passive migration mode includes downloading files via File Transfer Protocol (FTP).

12. The data migration method implemented by the server of claim 10, wherein the active migration mode further includes migrating user selected database tables.

13. The data migration method implemented by the server of claim 12, wherein the migrating the user selected database tables include:

running a dump command of the user selected database tables to create a database dump file;

compressing the database dump file;

recursively, for each httpdocs sub-directory, executing a tar command to wrap files associated with the domain into a single file; and

compressing the single file.

14. A non-transitory computer-readable medium storing executable instructions that, in response to execution, cause a server computer to perform data migration operations, comprising:

receiving a user login to a user'"'"'s account;

provide available domains associated with the user'"'"'s accounts;

receiving a selection of at least one of the available domains;

migrating the at least one of the available domains from a first database of a first server to a second database of a second server;

receiving account information corresponding to the user; and

registering the selected available domain with the user'"'"'s account.

15. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 14, further comprising migrating a domain using an IP address of the domain from the first database of the first server to the second database of the second server.

16. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 14, further comprising:

migrating a domain using a fully qualified domain name (FQDN) of a web site from the first database of the first server to the second database of the second server; and

deducing an IP address of the web site to migrate the domain using the FQDN from the first database of the first server to the second database of the second server.

17. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 14, further comprising detecting the available domains associated with the user'"'"'s accounts, wherein the detecting the available domains includes at least one of:

accepting an inputted user list of individual domains with associated usernames and passwords;

accessing all domains associated with an administrative username and password on the first server; and

screen-scraping domain data from a control panel of the first server accessed via a username, password, and IP address of the control panel.

18. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 14,

wherein the migrating includes at least one of an active migration mode and passive migration mode,

wherein the active migration mode includes accessing the first server via a secure shell connection, and

wherein the passive migration mode includes downloading files via File Transfer Protocol (FTP).

19. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 18, wherein the active migration mode further includes migrating user selected database tables.

20. The non-transitory computer-readable medium storing executable instructions that, in response to execution, cause the server computer to perform the data migration operations of claim 19, wherein the migrating the user selected database tables include:

running a dump command of the user selected database tables to create a database dump file;

compressing the database dump file;

recursively, for each http docs sub-directory, executing a tar command to wrap files associated with the domain into a single file; and

compressing the single file.