# US 2018/0026937 A1 · System and method for automatic configuration of domain names by third parties > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2018/0026937 A1 - Document ID: US20180026937A1 - Status: Published application - Kind: A1 - Application number: 15/682,309 - Filed: 2017-08-21 - Published: 2018-01-25 - Earliest claimed: 2014-08-22 - Assignees: Go Daddy Operating Company, LLC - Applicants: Go Daddy Operating Company, LLC - Inventors: Arnold Neil Blinn; Nitin Gupta; Rahul Mahajan - Web page: https://patentgrep.com/patent/US20180026937A1 ## CPC - H04L 61/4511: using domain name system [DNS] - G06F 16/95: Retrieval from the web - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding - H04L 67/53: using third party service providers - H04L 67/563: Data redirection of data network streams - H04L 61/25: of the same type - H04L 61/30: Managing network names, e.g. use of aliases or nicknames (name-to-address mapping H04L61/45) - H04L 61/3025: {Domain name generation or assignment} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract 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. ## Claims ### Claim 1 A method, comprising: receiving, by at least one server communicatively coupled to a network, a request from a third party service to create a custom domain name link to the third party service on behalf of a user, the request identifying a custom domain name and the third party service; accessing, by the at least one server, a third party service link database to identify an entry for the third party service specifying an Internet protocol (IP) address or a domain of the third party service; creating, without further input from the third party service, a DNS entry pointing the custom domain name to a web server accessible to the at least one server; and creating, on the web server and without further input from the third party service, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service. ### Claim 2 (depends on 1) The method of claim 1, wherein the entry in the third party service link database includes a variable and the request includes a value and including replacing the variable in the entry with the value when creating the DNS entry. ### Claim 3 (depends on 1) The method of claim 1, wherein creating, on the web server, the URL redirect to redirect Internet traffic directed to the custom domain name to the third party service includes: determining, using the request, a user account identifier; and including the user account identifier in the URL redirect on the web server. ### Claim 4 (depends on 3) The method of claim 3, 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. ### Claim 5 (depends on 1) The method of claim 1, further comprising: 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; and prompting the third party service to supply authentication credentials for the third party service. ### Claim 6 (depends on 1) The method of claim 1, wherein creating the URL redirect includes pointing the URL redirect to the IP address or domain of the third party service. ### Claim 7 A method, comprising: receiving, by at least one server communicatively coupled to a network, a request from a third party service to create a custom domain name link to the third party service on behalf of a user, the request identifying a custom domain name and the third party service; accessing, by the at least one server, a third party service link database to identify an entry for the third party service specifying an Internet protocol (IP) address or domain of the third party service; and creating, without further input from the third party service, a DNS entry pointing the custom domain name to the IP address or the domain of the third party service. ### Claim 8 (depends on 7) The method of claim 7, wherein the request is received from a third party service or a browser plug-in. ### Claim 9 (depends on 7) The method of claim 7, wherein creating the DNS entry includes accessing the third party service link database to identify a template for the third party service. ### Claim 10 (depends on 7) The method of claim 7, further comprising: 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; and prompting the third party service to supply authentication credentials for the third party service. ### Claim 11 (depends on 7) The method of claim 7, wherein the entry in the third party service link database includes a variable and the request includes a value and including replacing the variable in the entry with the value when creating the DNS entry. ### Claim 12 A system, comprising: a third party service link database storing, for each of a plurality of third party services, a template for a custom domain name link; and a processor, the processing being configured to perform the steps of: receiving a request from a third party service to create a custom domain name link to the third party service on behalf of a user, the request identifying a custom domain name and the third party service; accessing the third party service link database to identify an entry for the third party service specifying an Internet protocol (IP) address or a domain of the third party service; creating, without further input from the third party service, a DNS entry pointing the custom domain name to a web server; and creating, on the web server and without further input from the third party service, a URL redirect to redirect Internet traffic directed to the custom domain name to the third party service. ### Claim 13 (depends on 12) The system of claim 12, wherein the entry in the third party service link database includes a variable and the request includes a value and including replacing the variable in the entry with the value when creating the DNS entry. ### Claim 14 (depends on 12) The system of claim 12, 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: determining, using the request, a user account identifier; and including the user account identifier in the URL redirect on the web server. ### Claim 15 (depends on 14) The system of claim 14, 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. ### Claim 16 (depends on 12) The system of claim 12, wherein the processor is further configured to perform the steps of: 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; and prompting the third party service to supply authentication credentials for the third party service. ### Claim 17 (depends on 12) The system of claim 12, wherein creating the URL redirect includes pointing the URL redirect to the IP address or domain of the third party service.