DNS Request Routing With Shared Authentication and DoS Isolation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Large enterprises face challenges in managing complex DNS records due to cumbersome authentication processes, risks of Denial of Service (DoS) attacks, and inadvertent creation of DNS zones from user errors, particularly when handling large quantities of DNS records.

Innovation Solution

Implementing a DNS Ownership Intermediary API that uses shared authentication credentials and load balancing to manage DNS requests, authenticating users through a separate framework, and validating requests to prevent errors, thereby offloading authentication complexity and protecting DNS servers from attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication processes are used for DNS record management, then security is maintained, but authentication complexity and burden on DNS servers increase

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary authentication service that sits between users and DNS servers. This service handles authentication requests, validates credentials, and manages authorization, thereby reducing the authentication burden on DNS servers while maintaining security. The intermediary acts as a mediator that simplifies the authentication process for end users without compromising security requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication system is segmented into separate components: user authentication, credential validation, and DNS record management. By dividing the authentication process into distinct stages handled by different system components, the patent reduces the complexity any single component must handle while maintaining overall security. DNS servers focus only on record management, while authentication is handled by specialized services.

Inventive Principle:
Principle #1Segmentation

2Reliability

If DNS servers handle all authentication requests directly, then authentication control is maintained, but DNS servers become vulnerable to DoS attacks and overloading

Engineering Contradiction:
Improveauthentication controlVSAvoidDoS attack vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

An intermediary service is positioned between external users and DNS servers to handle all authentication requests. This intermediary absorbs malicious traffic and authentication attempts, protecting DNS servers from DoS attacks. The intermediary validates credentials and manages authentication state, allowing DNS servers to focus on their primary function of resolving domain names without being overwhelmed by authentication overhead or attack traffic.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The authentication handling function is extracted from DNS servers and placed in a separate dedicated service. By removing the authentication burden from DNS servers, the patent makes DNS servers more resilient to DoS attacks and overloading. The extracted authentication service can be independently scaled, monitored, and protected, while DNS servers maintain their core functionality with reduced attack surface.

Inventive Principle:
Principle #2Taking out (Extraction)

3Ease of operation

If users can directly modify DNS records, then management flexibility is improved, but user errors can inadvertently create DNS zones causing system fragmentation

Engineering Contradiction:
Improverecord management flexibilityVSAvoidDNS zone integrity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system performs preliminary validation of user requests before allowing DNS record modifications. Before applying changes, the system checks whether the requested operation would inadvertently create new DNS zones or violate zone integrity constraints. This preliminary action prevents user errors from causing system fragmentation while still allowing flexible record management within authorized boundaries.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms that provide users with information about the consequences of their DNS modification requests. Before finalizing a change, the system analyzes the request and provides feedback to the user about potential impacts, such as whether the change would create unexpected zones or violate policies. This feedback loop allows users to correct errors before they cause system fragmentation, maintaining both flexibility and integrity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260025376A1Shared Authentication Via DNS Request Routing
Publication Date: 2026.01.22 CAPITAL ONE SERVICES LLC
  • US20260025376A1 patent drawing
  • US20260025376A1 patent drawing
  • US20260025376A1 patent drawing

AI summary

Methods, systems, and apparatuses are described herein for management of a Domain Name System (DNS) system. The system comprises numerous improvements, many related to CNAME records of the DNS. A computing device may manage authentication for a DNS using shared authentication credentials of a first authentication framework. In this manner, a wide variety of users might authenticate themselves using a first framework and use authentication credentials for a second framework to access a DNS. The computing device may further protect DNS servers from Denial of Service (DoS) attacks by bifurcating read and write requests to a DNS to different servers, such that attacks on read requests do not affect all of the DNS. The computing device may further validate DNS requests using, for example, natural language processing to avoid typographical errors inadvertently creating DNS zones.