A domain to be published to an enterprise ECDN is associated (either by static configuration or dynamically) 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 preferably responds in one of three (3) ways: (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, thereby essentially restarting the lookup procedure. 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 preferably executes logic that applies the requested
hostname against a map, which, using known techniques, may be generated from given (static, dynamic, internally-generated or
third party-sourced) performance
metrics. Thus, a given name query to ECDN-managed content may be serviced in coordination with various sources of distributed
network intelligence. As a result, the invention provides for a distributed, dynamic globally load balanced name service.