DNS LINK Record Subtree Redirection for Scalable Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing DNS systems face scalability and provisioning challenges when managing vanity domains and their subordinate records, particularly in high-availability web services like video conferencing, due to the limitations of standard DNS record types such as DNAME and CNAME records, which are resource-intensive and difficult to scale.

Innovation Solution

The implementation of a unique LINK record type that is hidden from DNS clients and redirects both the record owner and its subordinates within the DNS server, allowing for subtree redirection and resolution, thereby reducing the need for duplicate records and enhancing scalability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standard DNS record types (DNAME, CNAME) are used for subtree redirection, then DNS queries can be resolved, but the system becomes resource-intensive and difficult to scale

Engineering Contradiction:
ImproveDNS query resolutionVSAvoidsystem resource consumption
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the subtree redirection functionality from the traditional DNAME and CNAME record mechanisms by introducing a new DNS record type that specifically handles subtree owner redirection. This new record type isolates the redirection logic to only what is necessary, removing the resource-intensive aspects of the existing mechanisms while preserving the core functionality of resolving DNS queries for subtrees.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If multiple vanity domains are managed with individual records, then each domain can be resolved independently, but the provisioning becomes difficult to scale and manage

Engineering Contradiction:
Improvedomain resolution independenceVSAvoidprovisioning speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent merges the management of multiple vanity domains by introducing a subtree owner DNS record type that can redirect entire subtrees of domains to a common target. This allows multiple vanity domains to share the same redirection logic and resource records, combining what would otherwise require individual management into a single unified mechanism that maintains domain resolution independence while dramatically improving provisioning scalability.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If duplicate resource records are created for each customer, then each customer has dedicated records, but memory consumption increases significantly

Engineering Contradiction:
Improvecustomer record dedicationVSAvoidmemory consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent uses a selective copying approach where the subtree owner DNS record type enables customers to share common resource records while maintaining the ability to have customer-specific records when needed. Instead of creating duplicate records for every customer, the system copies only the necessary redirection logic at the subtree owner level, allowing multiple customers to reference the same underlying resource records, thereby significantly reducing memory consumption while preserving customer dedication where required.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10791086B2Transparent DNS subtree redirection inclusive of subtree owner
Publication Date: 2020.09.29 CISCO TECHNOLOGY INC
  • US10791086B2 patent drawing
  • US10791086B2 patent drawing
  • US10791086B2 patent drawing

AI summary

A methodology for operating an authoritative DNS server includes receiving a DNS query from a DNS client, in response to the DNS query, traversing a label tree stored in the authoritative DNS server to find a resource record that matches the DNS query, while traversing the label tree, encountering a LINK record in the label tree that is configured to redirect the traversing to a different branch of the label tree, and in response to the LINK record, redirecting the traversing to the different branch of the label tree, wherein the LINK record is a resource record type that is hidden from DNS clients and is configured to redirect for an owner of the record type and subordinates thereof.