Private-Network DNS Query Routing Between Local and External Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DNS request systems struggle to efficiently manage the direction of queries to multiple nameservers associated with different domains within a computing network, leading to inefficiencies and potential misdirection of requests.
Innovation Solution
A method is implemented where a computing system receives a private IP address and a domain name indication from a coordination service, identifies the DNS request, and forwards it to a local DNS server rather than an external one, using configuration information to associate domains with specific DNS servers, and encapsulates packets with public IP addresses for communication within a private network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If DNS requests are directed to external DNS servers, then public network accessibility is maintained, but network communication overhead increases and resolution efficiency decreases
Solution Approach 1:
The patent segments DNS resolution into two distinct paths: internal DNS servers for private network domains and external DNS servers for public domains. This segmentation allows the system to optimize for each path independently, using local internal servers to reduce communication overhead for internal resources while maintaining external server connectivity for public resources.
Solution Approach 2:
The patent introduces an intermediary DNS server component within the private network that acts as a mediator between clients and external DNS servers. This intermediary handles internal domain resolution locally, reducing the need for external communication and thereby reducing network communication overhead while maintaining efficiency.
2Adaptability or versatility
If multiple nameservers are used for different domains, then domain-specific resolution control is improved, but request direction management complexity increases
Solution Approach 1:
The patent applies local quality by configuring different DNS server selections based on the specific domain being queried. The system maintains localized DNS control for each domain type, allowing administrators to specify which internal or external DNS servers should handle particular domains, thereby achieving domain-specific resolution control without overwhelming complexity.
Solution Approach 2:
The patent implements dynamic DNS server selection based on domain characteristics and network configuration. The system can adaptively determine which DNS server to contact based on real-time conditions and domain requirements, making the request direction management flexible and responsive rather than static and complex.
3Loss of energy
If local DNS servers are used for private network domains, then network communication overhead is reduced, but external network accessibility may be limited
Solution Approach 1:
The patent segments DNS resolution into two distinct paths: internal DNS servers for private network domains and external DNS servers for public domains. This segmentation allows the system to optimize for each path independently, using local internal servers to reduce communication overhead for internal resources while maintaining external server connectivity for public resources.
Solution Approach 2:
The patent implements a multi-functional DNS resolution system that can handle both internal and external domain requests through a unified framework. The same client-side DNS client can selectively contact either internal or external DNS servers depending on the domain, providing universal functionality while optimizing for reduced communication overhead for internal resources.
Data Source
AI summary
The technology described herein manages the direction of domain name system (DNS) queries to different DNS servers. In one implementation, a method of operating a computing system includes receiving, from a coordination service for a private network, a private Internet Protocol (IP) address of a destination on the private network, a public IP address of the destination on a public network, and an indication that a domain name corresponding to the private IP address should be resolved at a local Domain Name System (DNS) executing on the computing element. The method further includes identifying a DNS request generated by an application executing on the computing element and, in response to that identification, forwarding the DNS request to the local DNS rather than an external DNS. In response to receiving the private IP address from the local DNS, the method includes passing the private IP address to the application.