DNS Query Correlation via Unique Address Pooling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional network routing methodologies make it difficult for service providers to correlate DNS queries with subsequent communications, limiting their ability to assess performance and optimize service delivery based on unique network addresses.

Innovation Solution

A DNS service provides a pool of unique network addresses that can be selected for each DNS query, allowing service providers to correlate DNS queries with subsequent communications and analyze performance metrics such as latency, reliability, and efficiency by linking log entries based on these unique addresses.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional network routing methodologies are used, then network communication can be established, but service providers cannot correlate DNS queries with subsequent communications

Engineering Contradiction:
Improvecorrelation informationVSAvoidnetwork routing complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent introduces a correlation identifier as an intermediary element that bridges DNS queries and subsequent communications. This identifier is inserted into DNS responses and used to match subsequent HTTP requests with their originating DNS queries, enabling service providers to track and analyze the full request lifecycle without fundamentally changing network routing infrastructure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the correlation process into distinct components: DNS query identification, correlation identifier generation, identifier insertion into DNS responses, and subsequent request matching. This segmentation allows each component to be implemented and managed independently, reducing overall system complexity while enabling comprehensive correlation capability.

Inventive Principle:
Principle #1Segmentation

2Loss of information

If unique network addresses are assigned to each DNS query, then correlation between DNS queries and communications is enabled, but network address resources are consumed faster

Engineering Contradiction:
Improvecorrelation capabilityVSAvoidnetwork address pool
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

Instead of assigning unique network addresses to each DNS query, the patent creates a correlation identifier that copies or references the query information in a lightweight format. This identifier can be reused and does not consume network address resources, yet maintains the ability to correlate DNS queries with subsequent communications through matching mechanisms.

Inventive Principle:
Principle #26Copying

3Measurement precision

If service providers want to assess performance metrics like latency, then detailed tracking of DNS queries and communications is needed, but this increases system complexity

Engineering Contradiction:
Improveperformance measurement accuracyVSAvoidperformance tracking complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent implements a feedback mechanism where correlation identifiers enable service providers to track the complete journey of a request from DNS query through subsequent communications. This feedback loop provides precise performance metrics (latency, reliability) by matching timing information across different stages of the request lifecycle, while the automated matching process reduces manual tracking complexity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11461402B2Routing based request correlation
Publication Date: 2022.10.04 AMAZON TECH INC
  • US11461402B2 patent drawing
  • US11461402B2 patent drawing
  • US11461402B2 patent drawing

AI summary

Aspects of the disclosure will be described with regard to the processing of DNS queries by a DNS service based on multiple network addresses associated with a single network entity (e.g., a service provider). The DNS service may respond to each DNS query for identifying network addresses associated with the service provider with a respective unique network address from a pool of network addresses. Based on the uniqueness of network addresses, DNS queries and subsequent communications between respective client computing devices and the service can be correlated.