Integrated DNS Package for Network-Isolated Name Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In confined networks, such as national or corporate networks, domain name resolution fails when partitioned or isolated from the global Internet due to reliance on external DNS servers, leading to access failures even for websites within the network boundary.
Innovation Solution
A DNS hardware package with integrated DNS hierarchy databases and a recursive name server that prioritizes internal DNS servers for resolution, enabling self-sufficient domain name services within the network, including caching, blocking, redirecting, and bypassing DNSSEC validation as needed.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If DNS queries are made to external DNS servers for domain name resolution, then domain name resolution can be performed, but network partition or isolation prevents access to external DNS servers causing resolution failure
Solution Approach 1:
The DNS system is segmented into local and external components. A local DNS server is deployed within the network boundary, separating the resolution function from external DNS servers. This segmentation allows the network to maintain domain name resolution capability even when isolated from external networks, as the local DNS server can independently resolve domain names using locally cached or pre-loaded DNS data.
Solution Approach 2:
DNS data is pre-loaded into the local DNS server before network isolation occurs. The system performs preliminary actions by caching DNS records and maintaining a local DNS database in advance, ensuring that domain name resolution can continue without external connectivity. This preliminary preparation of DNS data enables the network to operate independently during partition or isolation events.
2Reliability
If DNS data is cached locally to enable resolution during network isolation, then resolution availability improves, but transaction latency increases due to local cache access
Solution Approach 1:
The DNS resolution system dynamically switches between local cache access and external DNS server queries based on network conditions and data freshness requirements. When external connectivity is available, the system queries external servers for updated records. When isolated, it falls back to local caching. This dynamic behavior optimizes the balance between resolution availability and latency, accessing local cache only when necessary to maintain service continuity.
3Productivity
If the network relies on external DNS servers, then comprehensive domain name resolution is achieved, but vulnerability to external attacks increases
Solution Approach 1:
A local DNS server acts as an intermediary between internal network resources and external DNS infrastructure. This intermediary layer provides comprehensive domain name resolution by querying external DNS servers when needed, while simultaneously protecting the internal network from external attacks. The local DNS server filters and validates DNS responses, blocking malicious content before it reaches internal systems, thus maintaining resolution capability while reducing attack surface.
Data Source
AI summary
A Domain Name System (“DNS”) package, a non-transitory computer-readable medium, and a method for providing domain name resolution services are disclosed. The system can include one or more built-in DNS hierarchy databases configured for deployment within a network, wherein the one or more built-in DNS hierarchy databases stores DNS records. The system can also include a recursive name server, wherein the recursive name server is configured to query the one or more built-in DNS hierarchy databases during domain name resolution, the recursive name server configured to select the one or more built-in DNS hierarchy databases based on a policy indicating a preference for the one or more built-in DNS hierarchy databases over a domain name server located outside of the network. Furthermore, the system can include a recursive name server database configured to store DNS records for the recursive name server.