DNS-Based VPN Management for Lower Bandwidth Use

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for managing virtual private networks (VPNs) while effectively limiting bandwidth and network resource consumption.

Innovation Solution

A DNS-based system is employed to manage VPNs by gathering data at a DNS server, maintaining it in a DNS table, and providing a portion of this data to client devices to establish and maintain VPN nodes through public networks, using determined VPN modes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional VPN management methods are used, then VPN connections can be established, but bandwidth and network resource consumption increase

Engineering Contradiction:
ImproveVPN connection securityVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

A DNS server acts as an intermediary between client devices and VPN servers. The DNS server receives DNS queries from clients, determines appropriate VPN servers based on query parameters, and returns server information. This intermediary approach enables intelligent VPN routing that optimizes bandwidth usage while maintaining secure connections, resolving the contradiction between security and resource consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes operational parameters by using DNS query parameters (such as geographic location, network conditions, and server capacity) to dynamically select optimal VPN servers. This parameter-based selection allows the system to adjust VPN connection characteristics in real-time, reducing bandwidth consumption while maintaining connection security.

Inventive Principle:
Principle #35Parameter changes

2Measurement precision

If comprehensive VPN data is stored at DNS server, then VPN management accuracy improves, but DNS server storage requirements increase

Engineering Contradiction:
ImproveVPN data accuracyVSAvoidstorage capacity
Core Design Contradiction:
Measurement precisionVSQuantity of substance

Solution Approach 1:

The system segments VPN data into two categories: comprehensive VPN server information stored at the DNS server for accurate management, and client-specific query parameters handled locally. The DNS server stores essential VPN configuration data and server information rather than all possible client data, achieving accurate VPN management with reduced storage requirements.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system extracts only the necessary VPN data and server information needed for accurate VPN management and stores it at the DNS server. Non-essential data is either stored locally at client devices or retrieved on-demand, reducing the overall storage burden on the DNS server while maintaining management accuracy.

Inventive Principle:
Principle #2Taking out (Extraction)

3Productivity

If DNS-based VPN management is implemented, then bandwidth optimization improves, but system complexity increases

Engineering Contradiction:
Improvebandwidth efficiencyVSAvoidsystem architecture
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The DNS server performs multiple functions: it handles standard DNS queries for domain name resolution and simultaneously manages VPN server selection based on DNS query parameters. This multi-functionality approach integrates VPN management into the existing DNS infrastructure, improving bandwidth efficiency without significantly increasing system complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

By using the DNS server as an intermediary that already exists in the network infrastructure, the system avoids adding complex new architecture. The DNS server's existing client base and infrastructure are leveraged to provide intelligent VPN routing, achieving bandwidth optimization through a familiar system rather than a complex new one.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250323896A1Domain name system based VPN management
Publication Date: 2025.10.16 THREATSTOP
  • US20250323896A1 patent drawing
  • US20250323896A1 patent drawing
  • US20250323896A1 patent drawing

AI summary

VPN data for building and maintaining VPNs through a public network is gathered. The VPN data is maintained, at a DNS server, as part of a DNS table. A portion of the VPN data is provided as part of a DNS view of the DNS table to a client device. A VPN mode indicating a manner to establish a VPN node for the client device through the public network is determined using the portion of the VPN data. When the client device is coupled to the public network the VPN node is established and maintained according to the VPN mode using the portion of the VPN data.