DNS Overriding via Routing Table for Edge Server Proximity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing DNS systems using an anycast addressing and routing methodology do not provide optimal means for accelerating content delivery, as they route requests to a data center with both DNS and edge servers, rather than a geographically closer edge server without a DNS server, which can offer better proximity and thus faster delivery.

Innovation Solution

Configuring a CDN to override the DNS system by generating and transmitting a routing table that maps edge server IP addresses to geographic regions, allowing DNS servers to route requests to the nearest geographically-proximal edge server, thereby optimizing content delivery.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If the DNS system uses anycast addressing and routing methodology, then requests are routed to a data center with both DNS and edge servers, but this results in suboptimal content delivery speed because the data center may not be geographically closer to the client

Engineering Contradiction:
Improvecontent delivery speedVSAvoidDNS routing complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent introduces a routing table as an intermediary component that mediates between the DNS system and edge servers. The routing table contains geographic region mappings to edge server IP addresses and is transmitted to DNS servers, allowing them to override default anycast routing and directly route requests to geographically-proximal edge servers without modifying the core DNS infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the routing function by separating the routing table (containing geographic mappings) from the DNS query resolution process. The routing table is independently generated, stored, and transmitted to DNS servers, allowing geographic-based routing decisions to be made separately from traditional DNS lookup operations

Inventive Principle:
Principle #1Segmentation

2Loss of time

If requests are routed to geographically-proximal edge servers, then content delivery latency is reduced, but this requires overriding the traditional DNS system which increases system complexity

Engineering Contradiction:
Improvecontent delivery latencyVSAvoidDNS override system complexity
Core Design Contradiction:
Loss of timeVSDevice complexity

Solution Approach 1:

The patent performs preliminary action by pre-generating and pre-transmitting the routing table to DNS servers before actual content delivery requests occur. The routing table contains all necessary geographic region to edge server IP address mappings in advance, allowing DNS servers to immediately route requests to optimal edge servers without real-time computation or complex decision-making

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The routing table acts as an intermediary that simplifies the override process. Instead of implementing complex geographic routing logic within the DNS servers themselves, the patent provides a pre-computed routing table that mediates between the DNS system and edge servers, reducing the complexity burden on the DNS infrastructure

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9961164B2DNS overriding-based methods of accelerating content delivery
Publication Date: 2018.05.01 GO DADDY OPERATING CO LLC
  • US9961164B2 patent drawing
  • US9961164B2 patent drawing
  • US9961164B2 patent drawing

AI summary

An exemplary method accelerating content delivery via DNS overriding may comprise the steps of generating a routing table for a content delivery network (CDN), the routing table map one or more edge server IP addresses to each of one or more geographic regions, transmitting the routing table to one or more DNS server computers, receiving a request from a registrant of a domain name to subscribe the domain name to the CDN, and designating said domain name as subscribed to the CDN in a DNS zone for the domain name.