Provisioning tool for a content delivery network (CDN)

• US 9,647,983 B2
• Filed: 12/22/2014
• Issued: 05/09/2017
• Est. Priority Date: 05/19/2003
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Lohner, Martin, Kushman, Nathaniel A., Mitton, Todd, Yurovitsky, Michael, Dixit, Abhijit, Nygren, Erik L., Hanono Wachman, Silvina Z.
• Primary Examiner(s): Vostal, O. C.
• Application Number:
  US14/579,691
• Publication Number:
  US 20150180826A1
• Time in Patent Office: 869 Days
• Field of Search: 709223
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/365 Application layer names, e.g. buddy names, unstructured names chosen by a user or home appliance name
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• 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/3025 Domain name generation or assignment
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/5014 using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
• CPC Class Codes: H04L 61/5076 Update or notification mechanisms, e.g. DynDNS
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

A tool that allows a CDN customer, partner, or other authorized entity to create a DNS canonical name (CNAME) on the content delivery network without having to contact the content delivery network service provider directly.

Claims

1. A system for provisioning DNS canonical names in a distributed network on behalf of given entities that use the distributed network, wherein the distributed network includes a set of one or more name servers, comprising:

a first subsystem executing in a hardware element and comprising a management server, an associated database, and a web portal including a graphical user interface, by which given entities that use the distributed network identify canonical name change requests, the management server having an associated application programming interface (API) that exports a set of methods that enable a given entity, using the graphical user interface, to create, delete and/or edit a canonical name for use in the distributed network,

wherein a given canonical name change request is associated with a given action selected from a set of actions that include creating, editing and deleting canonical names that are used in the distributed network; and

a second subsystem executing in a hardware element and in communication with the first subsystem to receive information from the first subsystem and, upon validation, to convert the information into one or more DNS zone files, and to install the DNS zone files to the one or more name servers, the information including the canonical name entry.

2. The system as described in claim 1 wherein the first subsystem includes a portal through which the given entities identify canonical name change requests.

3. The system as described in claim 1 wherein the second subsystem provides the information to the one or more name servers via a zone transfer.

4. The system as described in claim 1 wherein the second subsystem receives the information from the first subsystem periodically.

5. The system as described in claim 1 wherein the second subsystem reports given status information to the first subsystem.

6. The system as described in claim 1 wherein the first subsystem comprises:

code responsive to entry of a single hostname in the graphical user interface for generating at least first and second canonical names for use in the distributed network.

7. The system as described in claim 6 wherein the first and second canonical names are associated with one of:

given geographical regions, given network access types, and given service types.

8. The system as described in claim 1 further including a mechanism responsive to entry of the hostname for validating whether a canonical name to be generated from the hostname meets a given criteria.

9. The system as described in claim 8 wherein the given criteria is that the given entity is authorized to associate given content with the hostname.

10. The system as described in claim 1 wherein at least one method of the set of methods enables the given entity to edit more than one canonical name at a time.

11. The system as described in claim 1 wherein the distributed network is a content delivery network.

12. A computer program product in a non-transitory computer readable medium for use in provisioning DNS canonical names in a distributed network on behalf of given entities that use the distributed network, comprising:

a management server, an associated database, and a web portal including a graphical user interface, by which given entities identify canonical name change requests, the management server having an associated application programming interface (API) that exports a set of methods that enable a given entity, using the graphical user interface, to create, delete and/or edit a canonical name for use in the distributed network, wherein a given canonical name change request is associated with a given action selected from a set of actions that include creating, editing and deleting canonical names that are used in the distributed network; and

a second subsystem executing in a hardware element and in communication with the first subsystem to receive information from the first subsystem and, upon validation, to convert the information into one or more DNS zone files, and to install the DNS zone files to the one or more name servers, the information including the canonical name entry.