Host DNS Local Cache for Edge Network Connectivity Failures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network connectivity issues between computing devices and DNS services disrupt domain name resolution, leading to failures in workloads and processes, particularly in edge computing environments where centralized datacenters and edge sites are geographically distant.

Innovation Solution

Implementing a host DNS local cache on edge devices to store DNS responses, allowing for resolution of domain names even when the external DNS resolver is unreachable by using cached responses and updating transaction identifiers to match current requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a computing device relies on external DNS services for domain name resolution, then DNS resolution accuracy is maintained, but network connectivity issues cause DNS requests to fail and workloads to be disrupted

Engineering Contradiction:
ImproveDNS resolution reliabilityVSAvoidworkload execution continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent pre-populates a local DNS cache with domain name to IP address mappings before network issues occur. When DNS resolution is needed and external services are unavailable, the computing device queries the local cache and receives pre-stored DNS responses, enabling workloads to continue executing without interruption. This preliminary caching action resolves the contradiction by ensuring DNS reliability independently of network connectivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a local DNS cache as an intermediary component between the computing device and external DNS services. This cache acts as a mediator that can satisfy DNS resolution requests without requiring communication with external DNS servers. The intermediary cache holds pre-resolved domain name mappings, allowing the system to maintain DNS resolution reliability and workload continuity even when external DNS services are inaccessible.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If DNS responses are cached locally on the host device, then DNS resolution continues during network failures, but the system requires additional local storage and cache management complexity

Engineering Contradiction:
ImproveDNS resolution availabilityVSAvoidcache management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates simplified copies of DNS responses (domain name to IP address mappings) and stores them locally in a cache. Instead of implementing complex DNS resolution logic on the host device, the system copies essential DNS data to local storage. This copying approach enables DNS resolution availability during network failures while minimizing cache management complexity, as the cache stores straightforward key-value pairs that require minimal management overhead.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If the computing device uses centralized DNS services from distant datacenters, then centralized DNS management is achieved, but network latency and connectivity issues increase in edge computing environments

Engineering Contradiction:
Improvecentralized DNS managementVSAvoidDNS resolution time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the DNS resolution process into two parts: centralized DNS management for cache population and local cache query for resolution. The host device periodically queries centralized DNS services to populate its local cache, then uses the local cache for subsequent DNS resolutions. This segmentation allows centralized DNS management to maintain adaptability while local caching eliminates network latency for actual DNS resolutions, solving the time loss issue in edge computing environments.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs DNS resolution in advance by having the host device query centralized DNS services and store responses in a local cache before actual DNS needs arise. This preliminary action populates the cache with domain name mappings, so when DNS resolution is required at the edge location, the system can immediately retrieve responses from local storage without experiencing network latency. This maintains centralized DNS management adaptability while eliminating resolution time delays.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12107820B2Host virtual machine domain name system (DNS) cache enabling DNS resolution during network connectivity issues
Publication Date: 2024.10.01 MICROSOFT TECHNOLOGY LICENSING LLC
  • US12107820B2 patent drawing
  • US12107820B2 patent drawing
  • US12107820B2 patent drawing

AI summary

Examples of the present disclosure describe systems and methods for using a host DNS local cache to enable DNS resolution during network connectivity issues. In examples, a DNS request from a virtual environment executing on a host device is received by a DNS forwarder implemented within the host device. The DNS forwarder determines that a DNS resolver external to the host device is unreachable to provide a DNS response for a domain name in the DNS request. In response to determining the DNS resolver is unreachable, the DNS forwarder identifies a DNS response corresponding to the domain name within a DNS local cache implemented within the host device. The DNS forwarder provides the DNS response to the virtual environment to satisfy the DNS request.