DNS Server Caching for Endpoint Security Classification Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional endpoint security systems experience latency and resource consumption when classifying Internet resources, as they often require outbound requests to third-party providers for classification, leading to inefficiencies in network bandwidth and productivity.

Innovation Solution

Enhancing domain-name-server responses by receiving a DNS request, identifying the domain, retrieving classification information from a third-party system, and including it in the response, which can be cached to reduce latency and offload network traffic.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If traditional endpoint security systems make outbound requests to third-party providers for classification, then classification information can be obtained, but network bandwidth and latency increase

Engineering Contradiction:
Improveclassification informationVSAvoidlatency
Core Design Contradiction:
Loss of informationVSLoss of time

Solution Approach 1:

The DNS server performs preliminary action by proactively retrieving classification information for domains before the endpoint security system needs it. The DNS server caches this classification information and includes it in DNS responses, so when the endpoint security system later queries for classification data, the information is already available locally, eliminating the need for additional outbound requests and reducing latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The DNS server acts as an intermediary between the endpoint security system and third-party classification providers. Instead of the endpoint security system directly querying third-party providers (causing latency and bandwidth consumption), the DNS server retrieves classification information from third-party providers once and caches it, then serves this pre-fetched information to endpoint security systems through DNS responses, thereby mediating the interaction and reducing direct network traffic.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If traditional endpoint security systems query third-party providers separately, then classification can be performed, but network resources are consumed

Engineering Contradiction:
Improveclassification informationVSAvoidnetwork bandwidth
Core Design Contradiction:
Loss of informationVSQuantity of substance

Solution Approach 1:

The invention merges the DNS response function with the classification information delivery function. The DNS server combines domain name resolution with classification information retrieval by including classification data directly in DNS responses. This merging eliminates separate outbound requests from endpoint security systems to third-party providers, consolidating network traffic into single DNS requests that carry both resolution and classification information, thereby conserving network bandwidth.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The DNS server serves as an intermediary that consolidates network traffic. Instead of endpoint security systems making separate outbound requests to third-party classification providers, the DNS server retrieves classification information once from third-party providers and serves it to multiple endpoint security systems through DNS responses, acting as a traffic consolidator that reduces overall network bandwidth consumption.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Measurement precision

If endpoint security systems make separate queries for classification, then accurate classification is achieved, but productivity decreases

Engineering Contradiction:
Improveclassification accuracyVSAvoidaccess speed
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The DNS server performs preliminary action by pre-retrieving and caching classification information before endpoint security systems need it. When an endpoint security system makes a DNS request, the classification information is already cached and included in the response, eliminating the need for separate subsequent queries. This preliminary action maintains classification accuracy while significantly improving access speed and productivity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by having the DNS server learn from and cache classification information retrieved from third-party providers. This feedback mechanism allows the DNS server to serve endpoint security systems with pre-fetched classification data, improving access speed without sacrificing accuracy, as the same third-party classification providers are consulted to ensure accurate and up-to-date classification information.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8694659B1Systems and methods for enhancing domain-name-server responses
Publication Date: 2014.04.08 GEN DIGITAL INC
  • US8694659B1 patent drawing
  • US8694659B1 patent drawing
  • US8694659B1 patent drawing

AI summary

A computer-implemented method for enhancing domain-name-server responses may include: 1) receiving a domain-name-system request, 2) identifying a domain of the domain-name-system request, 3) retrieving classification information relating to the domain from a third-party system, and 4) including the classification information in a response to the domain-name-system request. Various other methods, systems, and computer-readable media are also disclosed.