System and method for automatic configuration of domain names by third parties
Systems and methods for creating custom domain name links are provided. At least one server communicatively coupled to a network receives a request to create a custom domain name link to a third party service. The request identifies a custom domain name. The at least one server retrieves, from a third party service link database, an entry for the third party service specifying how to create the custom domain name link for the third party service and he at least one server creates the custom domain name link in accordance with the entry retrieved from the third party service link database.
1. A method, comprising:
receiving, by at least one server communicatively coupled to a network, a request from a user to create a custom domain name link from a custom domain name to a third party service, wherein the third party service is configured to offer an online service to the user and the third party service and the at least one server are different companies;
accessing, by the at least one server, a third party service link database to identify an entry for the third party service specifying either a uniform resource locator (URL) redirect-based custom domain name link or a domain name system (DNS)-based custom domain name link;
when the entry specifies the URL redirect-based custom domain name link for the third party service:
creating, without further input from the user, a first DNS entry pointing the custom domain name to a web server, and
creating, on the web server, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service; and
when the entry specifies the DNS-based custom domain name link for the third party service, creating, without further input from the user, a second DNS entry pointing the custom domain name to the third party service; and
causing the third party service to create a custom domain name mapping that maps the custom domain name to a user account associated with the request.
2. The method of claim 1 , wherein creating, on the web server, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service includes:
prompting the user to provide a user account identifier; and
including the user account identifier in the URL redirect on the web server.
3. The method of claim 2 , wherein including the user account identifier in the URL redirect on the web server includes:
accessing the third party service link database to identify a template for the URL redirect.
4. The method of claim 1 , wherein causing the third party service to create a custom domain name mapping that maps the custom domain name to a user account of the user includes prompting the user to supply authentication credentials for the third party service.
5. The method of claim 1 , wherein the third party service link database identifies an Internet protocol (IP) address or a sub-domain of the third party service and creating the second DNS entry includes pointing the custom domain name to the IP address or sub-domain of the third party service.
6. The method of claim 1 , wherein the request includes a URL and including parsing the URL to identify the third party service.
7. A system, comprising:
a third party service link database storing, for each of a plurality of third party services, at least one entry specifying either a uniform resource locator (URL) redirect-based custom domain name link or a domain name system (DNS)-based custom domain name link; and
a processor, the processor being configured to perform the steps of:
receiving, by at least one server communicatively coupled to a network, a request from a user to create a custom domain name link from a custom domain name to a third party service, wherein the third party service is configured to offer an online service to the user and the third party service and the at least one server are different companies;
accessing, by the at least one server, the third party service link database to identify an entry for the third party service;
when the entry specifies the URL redirect-based custom domain name link for the third party service:
creating, without further input from the user, a first DNS entry pointing the custom domain name to a web server accessible to the at least one server, and
creating, on the web server, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service; and
when the entry specifies the DNS-based custom domain name link for the third party service:
creating, without further input from the user, a second DNS entry pointing the custom domain name to the third party service, and
causing the third party service to create a custom domain name mapping that maps the custom domain name to a user account of the user.
8. The system of claim 7 , wherein the processor is configured to, when creating, on the web server, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service, perform the steps of:
prompting the user to provide a user account identifier; and
including the user account identifier in the URL redirect on the web server.
9. The system of claim 8 , wherein the processor is configured to, when including the user account identifier in the URL redirect on the web server, perform the step of:
accessing the third party service link database to identify a template for the URL redirect.
10. The system of claim 7 , wherein causing the third party service to create a custom domain name mapping that maps the custom domain name to a user account of the user includes the processor performing the step of prompting the user to supply authentication credentials for the third party service.
11. The system of claim 7 , wherein the third party service link database identifies an Internet protocol (IP) address or a sub-domain of the third party service and creating the second DNS entry includes the processor performing the step of pointing the custom domain name to the IP address or sub-domain of the third party service.