Multi-Domain Configuration Handling in Edge Network Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current CDN configuration models are not aligned with cloud providers' third-party models, making it difficult for CDN service providers to efficiently deliver content to multiple third-party digital properties, as they are billed based on traffic and require awareness of these properties for proper delivery.
Innovation Solution
A multi-domain configuration (MDC) feature that allows a single edge server configuration to support unlimited third-party domains by leveraging DNS lookups and CNAME chains to determine appropriate content handling metadata, enabling instant provisioning and scalable performance without requiring additional configuration changes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single edge server configuration is used to support multiple third-party domains, then scalability and management ease are improved, but the complexity of determining correct content handling metadata increases
Solution Approach 1:
The patent introduces DNS as an intermediary mechanism between the edge server and third-party domains. The edge server performs DNS lookups on unknown host headers to resolve them to CNAMEs, which then map to appropriate content handling metadata. This intermediary DNS resolution process enables a single configuration to support multiple domains without increasing operational complexity at the edge server.
Solution Approach 2:
The system enables self-service through automated DNS-based domain identification. When an edge server receives a request with an unknown host header, it automatically performs DNS resolution and uses the CNAME response to self-determine the correct content handling metadata, eliminating the need for manual configuration or complex decision logic.
2Adaptability or versatility
If DNS lookups and CNAME chains are used for domain resolution, then adaptability to unlimited domains is improved, but processing time increases
Solution Approach 1:
The patent implements preliminary action by performing DNS lookups in advance during the request processing phase. The edge server proactively resolves host headers to CNAMEs before content delivery, so that when actual content requests arrive, the domain mapping information is already prepared and cached, reducing processing time.
Solution Approach 2:
The system uses CNAME (canonical name) records as copies that point to the actual domain names. These CNAME chains create reusable reference mappings that can be quickly resolved multiple times without repeating the full DNS resolution process, effectively copying the resolution result for efficient subsequent access.
Data Source
AI summary
An Internet infrastructure delivery platform operated by a provider enables HTTP-based service to identified third parties at large scale. The platform provides this service to one or more cloud providers. The approach enables the CDN platform provider (the first party) to service third party traffic on behalf of the cloud provider (the second party). In operation, an edge server handling mechanism leverages DNS to determine if a request with an unknown host header should be serviced. Before serving a response, and assuming the host header includes an unrecognized name, the edge server resolves the host header and obtains an intermediate response, typically a list of aliases (e.g., DNS CNAMEs). The edge server checks the returned CNAME list to determine how to respond to the original request. Using just a single edge configuration, the CDN service provider can support instant provisioning of a cloud provider's identified third party traffic.