DNS Client Raw Query Handling for Unrecognized Records

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

DNS clients often fail to decode or recognize newly created DNS records due to infrequent updates, limiting applications from utilizing the latest functionalities and increasing resource and energy consumption.

Innovation Solution

A DNS client with an API that allows applications to send and receive raw DNS queries, passing through host system policies and settings, and generates a subset of DNS records based on priority information, reducing the need for frequent updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If DNS client frequently updates to recognize new DNS records, then system adaptability improves, but resource consumption and update overhead increase

Engineering Contradiction:

ImproveDNS record recognition capabilityVSAvoidenergy consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent introduces an intermediary application layer between the DNS client and DNS server that handles raw DNS queries and responses. This intermediary can process and interpret new DNS record formats without requiring the DNS client itself to be updated, thereby maintaining adaptability while keeping the DNS client resource-efficient and stable.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If DNS client frequently updates to recognize new DNS records, then system adaptability improves, but configuration overhead increases

Engineering Contradiction:

ImproveDNS record recognition capabilityVSAvoidconfiguration overhead

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The application acts as an intermediary that absorbs the complexity of handling new DNS record formats. The DNS client maintains its simple, stable configuration while the application layer handles the adaptability requirements, effectively isolating configuration overhead from the DNS client.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Reliability

If DNS client processes all DNS records, then system robustness improves, but network congestion increases

Engineering Contradiction:

Improvesystem robustnessVSAvoidnetwork congestion

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The patent extracts the processing of specific DNS records from the DNS client to the application layer. The DNS client focuses on essential DNS functionality while the application handles specialized DNS record processing, reducing the DNS client's workload and associated network traffic while maintaining system robustness.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system is segmented into two functional parts: the DNS client that handles basic DNS operations, and the application that handles advanced DNS record processing. This segmentation allows each component to operate efficiently with appropriate workload distribution, reducing overall network congestion.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentUS12407643B2Handling raw DNS queries in DNS client

Publication Date: 2025.09.02 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

Methods and apparatuses for handling raw DNS queries or DNS queries that generate responsive DNS records from a DNS server that are not recognized or decodable by a DNS client are described. The DNS client may receive a DNS query from an application and provide a numerical IP address and one or more DNS records for a given domain name to the application. In some cases, a DNS client provides an interface that enables the application to send and receive DNS queries and responses to DNS queries that use DNS functionalities and customizations that are not recognized by the DNS client. This capability allows the application to craft its own DNS queries to send and receive resulting response bytes or packets through the DNS client, while allowing the DNS queries to pass through the DNS client to make use of host system cache, policies, and settings.