DNS Server Load Distribution via Non-Overlapping Address Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional network routing methodologies limit service providers to using the same DNS server components for all DNS requests associated with the same domain, leading to strain on resources and inefficiencies in managing high volumes of content requests from multiple client devices.
Innovation Solution
Implementing a system where a service provider assigns multiple sets of DNS server components with non-overlapping network addresses to handle DNS queries for a content provider domain, allowing different sets of clients to transmit queries to different DNS server components, thereby distributing the load and reducing resource strain.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If traditional network routing methodologies are used to route all DNS requests for the same domain to the same DNS server components, then the routing process is simple, but the resource strain on DNS server components increases and efficiency decreases
Solution Approach 1:
The patent segments the DNS server components into multiple sets with non-overlapping network addresses, allowing different client devices to be routed to different DNS server components based on their network addresses. This segmentation distributes the load across multiple servers rather than concentrating all requests on a single server, thereby improving processing efficiency while maintaining manageable routing complexity through automated selection mechanisms.
2Productivity
If multiple sets of DNS server components with non-overlapping network addresses are assigned to handle DNS queries, then the load is distributed and resource strain is reduced, but the system complexity increases
Solution Approach 1:
The patent applies local quality by assigning specific DNS server components to specific client devices based on their network addresses. Each client device is configured to use a particular DNS server component, creating a localized mapping relationship. This approach improves efficiency by matching clients to optimal servers while managing complexity through deterministic, address-based selection rules that are easy to implement and maintain.
3Device complexity
If the same DNS server components are used for all DNS requests, then the system is simple to manage, but latency in content delivery increases
Solution Approach 1:
The patent introduces dynamics by enabling the DNS routing to adapt based on the network address of the client device. Instead of a static one-to-one mapping, the system dynamically selects which DNS server component should handle a particular DNS request based on the client's network address. This dynamic routing reduces latency by optimizing the server-client connection while maintaining management simplicity through automated selection based on network address information.
Data Source
AI summary
Generally described, the present disclosure is directed to managing request routing functionality corresponding to resource requests for one or more resources associated with a content provider. A service provider can assign a set of DNS servers corresponding to a distributed set of network addresses, or portions of network addresses, for one or more identifiable domains. If the service provider receives requests to assign a DNS server to conflicting domains, the set of DNS servers for each identifiable domain are assigned such that there are no matching network addresses between the sets of domains associated with the conflicting domains. Thereafter, DNS resolver components can be configured such that DNS queries may be resolved in accordance with a determination of an authoritative DNS server based on the identified destination address associated with the DNS queries.