DNS Proxy for Hybrid Cloud Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In hybrid cloud computing environments, existing methods for domain name resolution are inefficient, as they either require all connections to traverse the Internet, leading to performance penalties, or introduce errors by manually configuring DNS name servers to parse resolution queries between public and private cloud addresses.
Innovation Solution
A DNS name server proxy is deployed in the public cloud to determine whether a domain name request is internal or external, routing requests to either the Intranet or public cloud DNS name servers accordingly, optimizing resolution processes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all connections traverse the Internet for domain name resolution in hybrid cloud environments, then external accessibility is maintained, but performance deteriorates due to network latency and bandwidth consumption
Solution Approach 1:
The DNS resolution system is segmented into multiple components: a local DNS server within the hybrid cloud environment, a DNS proxy, and external DNS servers. This segmentation allows internal domain names to be resolved locally without traversing the entire Internet, while external domains continue to use standard Internet DNS resolution, thus maintaining external accessibility while improving internal resolution performance
Solution Approach 2:
A DNS proxy is introduced as an intermediary component between the hybrid cloud environment and external DNS servers. The proxy intercepts DNS resolution requests, determines whether the domain name is internal or external, and routes appropriate requests to local or external DNS servers accordingly. This intermediary enables intelligent routing that maintains external accessibility while optimizing internal resolution performance
2Adaptability or versatility
If DNS name servers are manually configured to parse resolution queries between public and private cloud addresses, then resolution capability is improved, but error rate increases due to configuration complexity
Solution Approach 1:
The DNS proxy implements automatic domain name classification and routing without requiring manual configuration of parse rules. The system autonomously determines whether a domain name is internal or external based on the domain name itself, and automatically routes the request to the appropriate DNS server. This self-service approach eliminates manual configuration errors while maintaining high resolution capability
Solution Approach 2:
The system changes the parameter of domain name resolution from manually configured routing to automatic routing based on domain name analysis. By analyzing the domain name parameters (such as whether it matches internal domain patterns), the system dynamically determines the appropriate resolution path without requiring manual configuration, thus improving both capability and accuracy
3Device complexity
If a single DNS name server is used for both public cloud and private enterprise domains, then system complexity is reduced, but resolution accuracy deteriorates due to inability to resolve both internal name spaces
Solution Approach 1:
The DNS system is segmented into multiple specialized servers: a local DNS server for private enterprise domains and public cloud DNS servers for external domains. The DNS proxy orchestrates this segmentation by routing requests to the appropriate server based on the domain name. This segmentation enables accurate resolution of both internal name spaces while maintaining manageable system complexity through automated routing
Solution Approach 2:
The DNS proxy acts as an intermediary that manages the complexity of multiple DNS servers without exposing it to the applications. It automatically determines which DNS server should handle each request, thereby enabling accurate resolution of both private and public domains while keeping the system complexity hidden from end users and applications
Data Source
AI summary
Embodiments of the present invention provide a method, system and computer program product for domain name resolution for a hybrid cloud cluster. In an embodiment of the invention, a method for domain name resolution for a hybrid cloud cluster includes receiving a request for name resolution in a DNS name server proxy executing in memory of a host computer in a public cloud. Thereafter, it can be determined whether or not the request for name resolution implicates a domain name within an Intranet coupled to the proxy over a communications network. Finally, the request for name resolution can be resolved in a DNS name server disposed in the Intranet in response to determining the request to implicate a domain name within the Intranet.