Resolver Server DNS Record Proactive Push

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The current DNS system is inefficient due to frequent DNS queries from user machines to resolver servers, especially for domain names with short TTLs, leading to increased internet traffic and resolver server costs, despite the use of cache servers which do not reduce query frequency.

Innovation Solution

A method where the resolver server sends the association between a domain name and its address, along with its TTL, to an application server, which then forwards it to the user machine, reducing the need for user machines to send DNS requests directly to the resolver server, and adjusts TTL based on the stability of the association and receives updates from authoritative servers to manage record freshness.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If DNS queries are sent frequently to ensure up-to-date resolutions, then resolution accuracy is improved, but internet traffic and resolver server load increase

Engineering Contradiction:

Improveresolution accuracyVSAvoidinternet traffic

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The application server proactively requests DNS records from the resolver server before user machines need them. The resolver server sends records with extended TTLs in advance, allowing application servers to cache and forward them to user machines, eliminating the need for frequent DNS queries and reducing overall traffic.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The application server acts as an intermediary between user machines and the resolver server. Instead of user machines directly querying the resolver server frequently, they query the application server, which maintains a cached copy of DNS records obtained proactively from the resolver server.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If DNS queries are sent frequently to ensure up-to-date resolutions, then resolution accuracy is improved, but resolver server load increases

Engineering Contradiction:

Improveresolution accuracyVSAvoidresolver server load

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If TTL is set short to ensure accuracy, then resolution accuracy is improved, but query frequency increases

Engineering Contradiction:

Improveresolution accuracyVSAvoidquery frequency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

4Speed

If cache servers are used to replicate DNS records, then access speed is improved, but query frequency is not reduced

Engineering Contradiction:

Improveaccess speedVSAvoidquery frequency

Core Design Contradiction:

SpeedVSProductivity

Solution Approach 1:

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentEP3632089B1Optimisation de la fréquence de rafraichissement d'un enregistrement DNS

Publication Date: 2023.07.26 ORANGE SA

Figure 1~2

AI summary

The invention relates to a method for optimizing the refresh rate of at least one part of a registration comprising an association between a first identifier of a resource on a network and at least one second identifier of the resource, and a time-to-live for said association, the method being implemented by a resolver server (Sres) having obtained said registration from a server, called authoritative server (Saut), the method being characterised in that it comprises: transmitting (E06) a message comprising at least said association to an application server (Sapp) referencing the first identifier.