DNS Forwarder Hostname Traffic Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current DNS traffic management systems fail to effectively manage traffic when multiple hostnames resolve to the same IP address, as they rely on IP addresses to apply policies, leading to increased processing power consumption and latency due to packet inspection, and are limited by the format recognition of packets.

Innovation Solution

A DNS forwarder intercepts hostname requests, generates private IP addresses for each hostname, and returns them to manage network traffic and apply policies, allowing differentiation between hostnames that share the same IP address without packet inspection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DNS traffic management systems use IP addresses to apply policies, then traffic management is simplified, but multiple hostnames resolving to the same IP address cannot be differentiated and managed separately

Engineering Contradiction:

Improveability to manage multiple hostnamesVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a DNS forwarder as an intermediary component between the client and the authoritative DNS server. This forwarder intercepts DNS queries, assigns unique private IP addresses to each hostname, and manages the mapping between hostnames and private IP addresses. This intermediary layer enables differentiated traffic management for multiple hostnames without requiring complex modifications to the existing DNS infrastructure, resolving the contradiction between adaptability and device complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Measurement precision

If packet inspection is used to identify hostnames, then traffic management precision is improved, but processing power consumption increases

Engineering Contradiction:

Improvetraffic management precisionVSAvoidprocessing power consumption

Core Design Contradiction:

Measurement precisionVSUse of energy by moving object

Solution Approach 1:

The patent implements preliminary action by assigning unique private IP addresses to each hostname in advance, before actual traffic flow occurs. The DNS forwarder pre-establishes the mapping between hostnames and private IP addresses during the DNS resolution phase. This preliminary assignment eliminates the need for complex packet inspection during traffic flow, as routing decisions can be made simply based on the private IP address, significantly reducing processing power consumption while maintaining precise traffic management.

Inventive Principle:

Principle #10Preliminary action

3Manufacturing precision

If packet inspection is performed to manage traffic by hostname, then policy application accuracy is improved, but latency increases

Engineering Contradiction:

Improvepolicy application accuracyVSAvoidrequest latency

Core Design Contradiction:

Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent replaces the mechanical packet inspection process with a simpler IP address-based routing mechanism. Instead of inspecting packet contents to identify hostnames, the system uses the pre-assigned private IP addresses to directly determine routing and policy application. This substitution of the identification mechanism eliminates the time-consuming packet inspection step while maintaining accurate policy application, thereby reducing latency without sacrificing precision.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

4Device complexity

If DNS traffic management relies on IP addresses, then system simplicity is maintained, but the system is limited by packet format recognition

Engineering Contradiction:

Improvesystem simplicityVSAvoidpacket format flexibility

Core Design Contradiction:

Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent adds another dimension to the traffic management system by introducing a new addressing layer (private IP addresses assigned by the DNS forwarder) on top of the existing public IP address system. This dimensional addition allows the system to differentiate between multiple hostnames that share the same public IP address without complicating the underlying IP routing infrastructure. The private IP addresses serve as an additional identifier dimension, enabling versatile traffic management while maintaining system simplicity through IP-based routing.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10404651B2Domain name system network traffic management

Publication Date: 2019.09.03 RED HAT INC

AI summary

A mechanism for replacing a first internet protocol (IP) address with a second IP address in a response to a request to a server from an application is disclosed. A processing device may receive a request from an application. The processing device may receive a response from the server, where the response includes a first IP address. The processing device may replace the first IP address with a second IP address that is different than the first IP address. The processing device sends the response to the application and assigns a management policy to the second IP address. The management policy is different than a second management policy assigned to a third IP address associated with a second hostname assigned to the server.