Hybrid DNS Resolver with Anycast Routing for Location Accuracy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DNS systems often assume that a client's local DNS server is in close network proximity to the user, which is not always accurate, leading to inefficient content delivery and ad targeting, as 5-10% of Internet users are not located near their DNS server.
Innovation Solution
Implementing a hybrid DNS system that uses direct DNS addresses and IP anycast techniques to route DNS requests to the closest content delivery network (CDN) point of presence, allowing for more accurate location determination and improved quality of service by directing users to nearby content stores.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If DNS requests are routed through client local DNS servers, then DNS resolution can be performed, but user location accuracy deteriorates because 5-10% of users are not located near their DNS server
Solution Approach 1:
The patent introduces an intermediary mechanism (anycast routing infrastructure) between the user and the DNS resolution process. Multiple DNS servers are configured with the same IP address, creating an intermediary layer that automatically routes requests to the geographically closest server, thereby improving location accuracy without adding noticeable delay to the resolution process.
Solution Approach 2:
The patent segments the DNS server infrastructure into multiple geographically distributed instances, each handling requests from nearby users. This segmentation allows the system to maintain high location accuracy by assigning users to their nearest DNS server segment, while the overall system maintains efficiency through the distributed architecture.
2Productivity
If DNS servers are distributed geographically, then content delivery efficiency improves, but system complexity increases
Solution Approach 1:
The patent applies universality by making multiple DNS servers share the same IP address and functional interface. This multi-functionality allows a single DNS service to operate across multiple geographic locations simultaneously, improving content delivery efficiency while presenting a unified, simple interface to clients, thereby masking the underlying system complexity.
Solution Approach 2:
The patent creates copies of the DNS server infrastructure across different geographic locations. Each copy maintains the same functionality and interface, enabling efficient local content delivery. The copying approach distributes the system's computational load while maintaining a consistent user experience, effectively managing complexity through replication rather than differentiation.
3Speed
If DNS resolution uses recursive process through client local DNS server, then domain names can be resolved, but latency increases when user is not near the DNS server
Solution Approach 1:
The patent implements preliminary action by pre-configuring multiple DNS servers with identical IP addresses across different geographic locations. This preparation ensures that when a DNS request arrives, it is automatically and immediately routed to the nearest server without requiring real-time location calculation or dynamic routing decisions, thereby reducing latency while maintaining high resolution speed.
Data Source
AI summary
A domain name service (DNS) resolver returns Internet protocol (IP) addresses. A connection with an Internet application or device receives domain name resolution requests that originate outside of the Internet. A direct DNS resolver identifies IP addresses without referring to the Internet or using other DNS resolvers. An address store includes a predetermined list of domain names and corresponding IP addresses specified from a point remote to the DNS resolver. The DNS resolver processes the domain name resolutions for the predetermined list of domain names differently than domain name resolutions for other domain names not on the predetermined list of domain names. At least part of the predetermined list is pushed to a destination upon receiving a resolution request for a domain name in the predetermined list of domain names, the request being of a type other than an authoritative resolution request to be performed by the direct DNS resolver.