Using virtual domain name service (DNS) zones for enterprise content delivery

• US 7,478,148 B2
• Filed: 01/16/2002
• Issued: 01/13/2009
• Est. Priority Date: 01/16/2001
• Status: Active Grant

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Akamai Technologies, Inc.
• Inventors: Neerdaels, Charles J.
• Primary Examiner(s): Jean; Frantz B
• Application Number:
  US10/466,797
• Publication Number:
  US 20040194102A1
• Time in Patent Office: 2,554 Days
• Field of Search: 709/232, 709/226, 709/203, 709/223, 718/105, 726/11, 726/15
• US Class Current: 709/223
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• 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/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 61/59 using proxies for addressing
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A domain to be published to an enterprise ECDN is associated with a set of one or more enterprise zones configurable in a hierarchy. When a DNS query arrives for a hostname known to be associated with given content within the control of the ECDN, a DNS server responds by: (a) handing back an IP address, e.g., for an ECDN intelligent node that knows how to obtain the requested content from a surrogate or origin server; (b) executing a zone referral to a next (lower) level name server in a zone hierarchy, or (c) CNAMing to another hostname. In the latter case, this new CNAME causes the resolution process to start back at the root and resolve a new path, probably along a different path in the hierarchy. At any particular level in the zone hierarchy, preferably there is an associated zone server. That server executes logic that applies the requested hostname against a map that may be generated from given performance metrics. Thus, a given name query to ECDN-managed content may be serviced in coordination with various sources of distributed network intelligence.

Claims

1. A method of content delivery involving a first entity and a second entity comprising:

having each of the first and second entities operate an enterprise content delivery network (ECDN) behind an enterprise firewall, wherein each of the first and second entities has a private namespace that is not resolvable through public Internet DNS;

having the first entity delegate to the second entity responsibility for managing a virtual zone associated with the private namespace of the first entity; and

in response to a request generated by an end user in the second entity, the request being associated with the virtual zone, retrieving a private object published by the first entity.

2. The method as described in claim 1 wherein at least one of the enterprise content delivery networks is part of an Internet content delivery network (ICDN).

3. The method as described in claim 2 wherein at least one of the enterprise content delivery networks is managed as part of the ICDN.

4. The method as described in claim 1 wherein the private object is retrieved by a relay located within a demilitarized zone (DMZ) of the second entity.

5. The method as described in claim 4 wherein the relay located within the DMZ of the second entity communicates with a relay located within a DMZ of the first entity.

6. The method as described in claim 5 wherein the relay located within the DMZ of the second entity communicates with the DMZ of the first entity over a secure link.

7. The method as described in claim 6 wherein the virtual zone is resolved without reference to the public Internet DNS.

8. The method as described in claim 4 wherein the relay comprises a surrogate origin server and a zone name server.

9. The method as described in claim 1 wherein the first and second entities are distinct enterprises.

10. A method of content delivery involving a first entity and a second entity, comprising:

having each of the first and second entities operate an enterprise content delivery network (ECDN) behind an enterprise firewall, wherein each of the first and second entities has a private namespace that is not resolvable through public Internet DNS;

deploying a first relay within the first entity;

deploying a second relay within the second entity;

having the first entity delegate to the second entity responsibility for managing a virtual zone associated with the private namespace of the first entity; and

in response to a request generated by an end user in the second entity, the request being associated with the virtual zone, retrieving a private object published by the first entity.

11. The method as described in claim 10 wherein each of the first and second relays comprises a surrogate origin server and a zone name server.

12. The method as described in claim 11 wherein the private object is retrieved by the second relay.

13. The method as described in claim 12 wherein the second relay retrieves the private object using the surrogate origin server in the first relay.

14. The method as described in claim 10 wherein the first and second entities are distinct enterprises.

15. The method as described in claim 10 wherein the virtual zone is resolved without reference to the public Internet DNS.

16. A method of content delivery, comprising:

having an entity establish an enterprise content delivery network (ECDN) behind an enterprise firewall, wherein the entity has a private namespace that is not resolvable through public Internet DNS;

having the entity receive a delegation of responsibility for managing a virtual zone associated with a private namespace of a second entity, wherein the second entity is distinct from the entity, and wherein the entity receives the delegation from the second entity; and

in response to a request generated by an end user behind the enterprise firewall in the entity, the request being associated with the virtual zone, having the entity retrieve a private object published by the second entity.