CNAME Flattening for Root Domain DNS Resolution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing DNS system limits flexibility and performance by requiring IP addresses for root domains, making it difficult to manage traffic and isolate issues between domains sharing the same IP address, as CNAME records are not allowed at the root domain level, violating DNS specifications.

Innovation Solution

Implementing CNAME flattening, where the authoritative DNS infrastructure performs a recursive lookup to follow CNAME chains and return an Address record, effectively supporting CNAME records at the root domain while complying with DNS specifications, allowing for better traffic management and isolation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If CNAME records are implemented at the root domain level, then flexibility and traffic management capability are improved, but DNS specification compliance deteriorates

Engineering Contradiction:
ImproveflexibilityVSAvoidDNS specification compliance
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism where the root domain does not directly store CNAME records but instead uses a special handling approach: when a CNAME record is needed at the root level, the system creates a subdomain (e.g., 'www' or other placeholder) that holds the CNAME record, while the root domain itself maintains an A record that points to the same IP address. This intermediary subdomain acts as a bridge that allows CNAME functionality at the root level without actually placing CNAME records at the root, thus maintaining DNS specification compliance while achieving the desired flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple domains share the same IP address through virtual hosting, then resource utilization is improved, but traffic isolation and performance stability deteriorate

Engineering Contradiction:
Improveresource utilizationVSAvoidperformance stability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent applies segmentation by allowing each domain to have its own CNAME record that points to a unique alias or service endpoint, even when multiple domains resolve to the same underlying IP address. This segmentation of domain identities through CNAME records enables better traffic management and isolation, so that issues affecting one domain (such as DNS-level attacks or misconfigurations) do not directly impact other domains sharing the same IP infrastructure.

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If IP addresses are assigned to each customer for custom domains, then service flexibility is improved, but IP address management complexity and cost deteriorate

Engineering Contradiction:
Improveservice flexibilityVSAvoidIP address management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements universality by using a shared pool of IP addresses that can serve multiple customers through virtual hosting and CNAME record mechanisms. Instead of requiring dedicated IP addresses for each customer, the system allows a single IP address to handle traffic for multiple domains simultaneously. This multi-functional approach to IP address usage reduces the total number of IP addresses needed while maintaining the ability to provide customized domain services to each customer.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11159479B2Domain name system CNAME record management
Publication Date: 2021.10.26 CLOUDFLARE INC
  • US11159479B2 patent drawing
  • US11159479B2 patent drawing
  • US11159479B2 patent drawing

AI summary

A DNS name server manages CNAME records. The server receives a query for a first Address record for a fully qualified domain name from a requester. The server determines that the fully qualified domain name has a CNAME record, where the fully qualified domain name is a root domain. The server traverses a chain according to the CNAME record to locate a second Address record that includes an IP address. The server generates a response to the query that includes a third Address record for the fully qualified domain name that includes at least the IP address of the located second Address record. The server transmits the generated response to the requester.