IP Library Granted Patent US 10,200,341
Granted Patent B2
US 10,200,341 · App. 15/682,309 · Granted Feb 5, 2019

System and method for automatic configuration of domain names by third parties

Inventors: Arnold Neil Blinn (Hunts Point, WA); Nitin Gupta (Mountain View, CA); Rahul Mahajan (San Francisco, CA)
Assignee: GO DADDY OPERATING COMPANY, LLC
H04L61/1511G06F17/30861H04L67/02H04L67/146H04L67/20H04L67/2814H04L29/08738H04L29/1233H04L29/12066H04L29/12594H04L29/12641H04L61/25H04L61/30H04L61/3025
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,200,341
App. No.
15/682,309
Granted
Feb 5, 2019
Kind
B2
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 (26)

1. A method, comprising:

receiving, by a host comprising 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 registered with a registry to the user and the 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 host are different companies;

accessing, by the host, 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, by the host and 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, by the host 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, wherein the creating the URL redirect to redirect Internet traffic directed to the customer 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, wherein the 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.

2. 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.

3. 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.

4. 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.

5. 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 processor being configured to perform the steps of:

receiving by a host 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 registered with a registry to the user and the 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 host are different companies;

accessing by the host 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, by the host and without further input from the third party service, a DNS entry pointing the custom domain name to a web server; and

creating, by the host 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, wherein the creating the URL redirect to redirect Internet traffic directed to the customer 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, wherein the 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.

6. The system of claim 5 , 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.

7. The system of claim 5 , 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.

8. The system of claim 5 , wherein creating the URL redirect includes pointing the URL redirect to the IP address or domain of the third party service.

Assignments (3)
SECURITY AGREEMENT Recorded Feb 17, 2023
From: GO DADDY OPERATING COMPANY, LLC; GD FINANCE CO, LLC; GODADDY MEDIA TEMPLE INC.; GODADDY.COM, LLC; LANTIRN INCORPORATED; POYNT, LLC
To: ROYAL BANK OF CANADA
Reel/Frame 062782/0489 →
SECURITY AGREEMENT Recorded Oct 12, 2020
From: GO DADDY OPERATING COMPANY, LLC; GD FINANCE CO., INC.
To: BARCLAYS BANK PLC
Reel/Frame 054045/0829 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 21, 2017
From: BLINN, ARNOLD NEIL; GUPTA, NITIN; MAHAJAN, RAHUL
To: GO DADDY OPERATING COMPANY, LLC
Reel/Frame 043348/0700 →
Continuity (3)
Continuation 14742389 · Jun 17, 2015
Continuation 14466953 · Aug 22, 2014
Related Publication 20180026937A1 · Jan 25, 2018