Experience-Aware DNS Querying for Reliable Server Selection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current DNS systems randomly select server IP addresses for connection without considering the actual service experience of the servers, leading to unpredictable service performance.

Innovation Solution

A DNS query method that involves obtaining server experience information for multiple IP addresses through a communication device, allowing for optimized DNS responses based on service experience data to select the most suitable IP address for connection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DNS server feeds back multiple IP addresses randomly, then the DNS response is simple and fast, but the service performance becomes unpredictable and unreliable

Engineering Contradiction:
Improveservice performance reliabilityVSAvoidDNS response complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by collecting server experience information (response time, success rate, user feedback) before DNS resolution. This historical data is stored and retrieved during the DNS query process, enabling the system to make informed selections without adding complexity to the core DNS resolution mechanism.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring server performance metrics (response time, connection success rate, user complaints) and using this information to adjust future DNS responses. The feedback loop ensures that servers with poor performance are progressively excluded from responses while maintaining system simplicity.

Inventive Principle:
Principle #23Feedback

2Productivity

If DNS server uses server experience information to select IP addresses, then service quality improves, but the DNS query process becomes more complex

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidDNS query process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system introduces an intermediary layer (experience information database and selection module) that mediates between the DNS query process and server selection. This intermediary handles the complexity of experience data collection, storage, and processing, allowing the core DNS resolution to remain simple while benefiting from intelligent server selection.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the selection parameter from random choice to experience-based scoring. By transforming the selection criterion into a quantitative parameter (weighted average of response time, success rate, and user feedback), the system achieves improved productivity without significantly complicating the DNS query process.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If terminal selects IP address randomly from DNS response, then the process is simple and fast, but service experience becomes unpredictable

Engineering Contradiction:
Improveservice experience reliabilityVSAvoidIP selection simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system enables self-service by automatically incorporating server experience information into DNS responses without requiring manual intervention from terminals or users. The intelligent selection is performed transparently in the background, maintaining ease of operation while dramatically improving service experience reliability through automated, data-driven decisions.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12445411B2DNS query method and device
Publication Date: 2025.10.14 VIVO MOBILE COMM CO LTD
  • US12445411B2 patent drawing
  • US12445411B2 patent drawing
  • US12445411B2 patent drawing

AI summary

A DNS query method includes receiving, by a first communication device, a DNS query to obtain an FQDN; sending, by the first communication device, first information to a second communication device, where the first information includes the FQDN or N server IP addresses corresponding to the FQDN, and N is a positive integer; obtaining, by the first communication device, server experience information corresponding to the N server IP addresses from the second communication device, where the server experience information is used to indicate service experience of a server corresponding to each of the server IP addresses; and sending, by the first communication device, a DNS response to a terminal based on the server experience information.