Local DNS Record Buffering and Threshold-Based Deletion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In current Internet Protocol networks, terminals frequently query DNS servers for IP addresses corresponding to domain names, leading to unnecessary network traffic due to the possibility of receiving inappropriate IP addresses when multiple IP addresses are associated with a single domain name, causing repeated queries and increased traffic.

Innovation Solution

A method and device for storing DNS records that locally store and manage DNS records, deleting excess records if the storage threshold is exceeded, and a domain name parsing method that selects appropriate network addresses based on service IDs and user information to reduce unnecessary queries and traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the terminal frequently queries the DNS server for IP addresses, then the terminal can obtain domain name resolution, but the network traffic increases and the query efficiency decreases

Engineering Contradiction:
Improvedomain name resolutionVSAvoidnetwork traffic
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The terminal pre-queries the DNS server to obtain multiple IP addresses corresponding to a domain name before actual access is needed. These IP addresses are stored locally in a buffer, so when the terminal needs to access the domain name, it can directly use the pre-obtained IP address without sending another query request, thereby reducing network traffic and improving query efficiency

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The terminal creates a local copy of the DNS resolution results (IP addresses) by storing them in a buffer. Instead of repeatedly querying the DNS server, the terminal uses the copied IP address data from the buffer, which reduces the number of network requests while maintaining the ability to resolve domain names

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If the DNS server returns multiple IP addresses, then the terminal has more options for access, but the terminal may receive inappropriate IP addresses and send queries again, increasing network traffic

Engineering Contradiction:
ImproveIP address selectionVSAvoidnetwork traffic
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The terminal monitors whether the accessed IP address is appropriate (e.g., whether the access succeeds or fails). If the access using a returned IP address is unsuccessful, the terminal feeds back this information and tries the next IP address from the buffer. This feedback mechanism ensures that the terminal can adapt to the actual network conditions while avoiding unnecessary repeated queries to the DNS server, as the IP addresses are already cached locally

Inventive Principle:
Principle #23Feedback

3Productivity

If the terminal stores DNS records locally, then the query efficiency improves, but the storage capacity of the terminal is consumed

Engineering Contradiction:
Improvequery efficiencyVSAvoidstorage capacity
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The terminal extracts only the necessary IP address data from the complete DNS records and stores only this extracted information in the buffer. By taking out only the essential elements (IP addresses) rather than storing entire DNS records, the terminal improves query efficiency by having local cache while minimizing the consumption of storage capacity

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8874718B2Method and device for storing domain name system records, method and device for parsing domain name
Publication Date: 2014.10.28 HUAWEI TECH CO LTD
  • US8874718B2 patent drawing
  • US8874718B2 patent drawing
  • US8874718B2 patent drawing

AI summary

A method for storing domain name system (DNS) records includes locally storing received DNS records needed to be stored. If the size of all the stored DNS records does not satisfy a preset storing threshold, a part of the stored DNS records are deleted to make the size of the remaining DNS records after deletion satisfy the storing threshold. A domain name parsing method, device, and server are also provided.