Application-Layer DNS Routing Around OS Resolver Limits
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DNS configurations face challenges when deployed across multiple devices with varying hardware and software configurations, particularly in managing multiple nameservers for different domains or URLs, leading to configuration complexities and security vulnerabilities.
Innovation Solution
A method where DNS requests are handled by a DNS application before the operating system, determining system limitations and resolving the request accordingly, with a coordination service managing DNS configurations across computing elements, allowing for local rule implementations based on hardware and software configurations, and enabling secure communication using local or external DNS servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If DNS requests are handled by the operating system, then the system uses standard DNS resolution, but it cannot enforce custom nameserver configurations or resolve DNS requests according to specific domain rules
Solution Approach 1:
The patent implements a preliminary DNS resolution step in the application layer before the operating system's DNS resolver is invoked. The application intercepts DNS requests, checks them against custom rules (e.g., domain-specific nameserver mappings), and resolves them according to organizational policies before passing control to the OS, thereby enabling custom DNS configurations without modifying OS behavior
Solution Approach 2:
The patent introduces an intermediary DNS resolution mechanism that sits between the application and the operating system's DNS handler. This intermediary layer evaluates DNS requests against custom rules and determines the appropriate nameserver to use, acting as a mediator that enables flexible DNS configuration while maintaining compatibility with standard OS DNS resolution
2Adaptability or versatility
If multiple nameservers are configured for different domains, then DNS resolution flexibility improves, but configuration complexity across multiple devices increases
Solution Approach 1:
The patent implements a universal DNS rule management system that can be deployed across multiple devices with varying operating systems and hardware configurations. The same set of DNS rules and policies can be applied universally across different devices, eliminating the need for device-specific configuration while maintaining flexible domain-to-nameserver mappings
3Adaptability or versatility
If DNS requests are intercepted and resolved in the application layer, then custom nameserver routing is enabled, but additional processing time is introduced
Solution Approach 1:
The patent implements preliminary DNS rule evaluation in the application layer before OS DNS resolution. By checking DNS requests against custom rules upfront and caching the results, the system enables custom nameserver routing while minimizing additional processing time through efficient rule matching and result caching
Data Source
AI summary
The technology described herein enhances security of domain name system (DNS) requests. In one example, a method includes receiving a DNS request in a DNS application executing on a computing element before the DNS request can be handled by an operating system of the computing element and determining the operating system includes a limitation relevant to the DNS request. The method further includes resolving the DNS request in the DNS application in accordance with the limitation and responding to the DNS request after resolving the DNS request.