Local DNS Server Persistent Cache for Branch Office Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In enterprise networks, existing DNS server models face issues with network bandwidth usage and record availability, particularly when secondary DNS servers copy records from primary servers, leading to potential gaps in record updates and communication disruptions during connection failures.
Innovation Solution
Implementing a local Domain Name Service (DNS) server with a persistent cache at each branch office that represents itself as authoritative, allowing it to store and manage local records, reducing reliance on the enterprise hub and minimizing network traffic by caching records for local clients and resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If secondary DNS servers copy records from primary DNS servers, then local record availability is improved, but network bandwidth consumption increases and record update timeliness deteriorates
Solution Approach 1:
The patent extracts the essential function of DNS record storage and makes it persistent at the branch office level. By storing DNS records persistently in the local DNS server cache, the system obtains local record availability without requiring continuous copying from primary servers, thus avoiding excessive network bandwidth consumption while maintaining reliability.
2Reliability
If secondary DNS servers copy records from primary DNS servers, then local record availability is improved, but record update timeliness deteriorates
Solution Approach 1:
The patent implements preliminary action by persistently storing DNS records in the local cache before they are needed. When DNS records are received from primary servers, they are immediately persisted locally, ensuring both availability and timely updates without waiting for periodic copying operations.
3Loss of energy
If stub/forwarder DNS servers use non-authoritative model, then network bandwidth usage is reduced, but host name resolution reliability deteriorates during connection failures
Solution Approach 1:
The patent applies beforehand cushioning by implementing persistent local storage of DNS records. This creates a buffer that allows the branch office DNS server to continue resolving host names locally even when connection to the enterprise hub fails, thus maintaining reliability without increasing normal network bandwidth usage.
4Speed
If branch office DNS server represents itself as authoritative, then local host name resolution speed is improved, but network traffic increases
Solution Approach 1:
The patent implements self-service by enabling the branch office DNS server to autonomously resolve host names using its persistent local cache. The server serves itself as an authoritative DNS server for local records, providing fast resolution without needing to query the enterprise hub, thus improving speed while minimizing network traffic.
Data Source
AI summary
Maintaining DNS records. A computing network system includes a local Domain Name Service (DNS) server connected to one or more local clients or resources at a local branch office in an enterprise network. The local DNS server advertises to the local clients or resources at the local branch office that the DNS server is authoritative. The DNS server receives record information for the local clients or resources. An attempt is made to forward the record information to an enterprise hub DNS server. The record information is stored persistently in a cache. Storing the record information persistently in cache may be performed selectively or non-selectively. When performed selectively, the record information is stored or not stored depending on some result or other action. For example, the result may be stored or not stored depending on the results of attempting to forward to an enterprise hub DNS server.