Mesh Network DNS Resource Sharing via Local Exit Devices

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In mesh networks, user devices face challenges in accessing domain name service (DNS) resources efficiently, leading to potential privacy compromises and delays when querying domain information for external devices, as they often rely on public DNS servers, which can expose private information and introduce latency.

Innovation Solution

The method involves user devices sharing DNS resources within the mesh network by utilizing local DNS servers connected to a local area network (LAN), where one user device forwards DNS queries to a local DNS server and returns the domain information to other devices, thereby avoiding public DNS servers and maintaining privacy and reducing latency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If user devices rely on public DNS servers for domain queries in mesh networks, then domain information can be obtained, but private information may be exposed and latency increases

Engineering Contradiction:
Improveprivacy protectionVSAvoidDNS query latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent introduces local DNS servers as intermediary components within the mesh network. Instead of directly querying public DNS servers, user devices route DNS queries through nearby mesh network devices that have local DNS servers. This intermediary approach protects user privacy by preventing direct exposure to public DNS servers while maintaining efficient domain resolution through localized queries, thereby resolving the contradiction between privacy protection and latency reduction

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If user devices use local DNS servers through mesh network sharing, then privacy is protected and latency is reduced, but network complexity increases

Engineering Contradiction:
Improveprivacy protectionVSAvoidnetwork configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service mechanisms where mesh network devices automatically discover and share their local DNS server capabilities with other network participants. Devices autonomously register their DNS server information in the mesh network and dynamically route queries without requiring manual configuration from users. This self-organizing behavior reduces network configuration complexity while maintaining the privacy and performance benefits of local DNS server utilization

Inventive Principle:
Principle #25Self-service

3Productivity

If DNS resources are shared across the mesh network, then resource utilization is optimized, but network traffic overhead increases

Engineering Contradiction:
Improveresource utilization efficiencyVSAvoidnetwork traffic overhead
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent applies local quality by enabling DNS query routing to preferentially select the nearest or most appropriate local DNS server within the mesh network based on geographic proximity or network distance. This localized approach ensures that DNS queries are resolved by the closest available DNS resource, optimizing resource utilization efficiency while minimizing network traffic overhead by avoiding unnecessary long-distance transmissions across the entire mesh network

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12126591B1Sharing domain name service resources in a mesh network
Publication Date: 2024.10.22 UAB 360 IT
  • US12126591B1 patent drawing
  • US12126591B1 patent drawing
  • US12126591B1 patent drawing

AI summary

The disclosure describes a mesh network including a first device and a second device, which acts as an exit device with respect to the first device such that communication between the first device and an external device, outside the mesh network, is communicated via the second device. The first device receives access information utilized by the second device to access a DNS server in a LAN that includes the second device, and transmits a meshnet query packet that includes a DNS query for domain information associated with the external device. The first device receives, based on transmitting the meshnet query packet, the domain information associated with the external device, and transmits a meshnet initiation packet that includes a network communication for communicating with the external device, the network communication including the domain information. Various other aspects are contemplated.