Client-Side DNS Prioritization Using Time Zone Offset
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing DNS solutions fail to optimize resource access based on geographic location, leading to increased latency and congestion when users travel, as they often connect to distant DNS servers despite their new location, resulting in suboptimal performance.
Innovation Solution
Implementing client-side DNS prioritization that determines the current time zone of a user equipment (UE) device and selects a regional DNS server from a configured list, allowing the device to receive tailored responses prioritizing resource addresses based on geographic proximity, thereby ensuring connection to locally optimal resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If users connect to distant DNS servers when traveling, then global generic responses can be provided, but latency increases and performance deteriorates
Solution Approach 1:
The patent segments the DNS server infrastructure into multiple geographically distributed regional DNS servers instead of using a single centralized DNS server. Each regional DNS server serves a specific geographic region, allowing users to connect to the nearest server and reducing latency while maintaining global coverage through the segmented architecture.
Solution Approach 2:
The patent introduces a time zone detection mechanism as an intermediary that mediates between the user device and the DNS server selection process. The intermediary detects the user's current time zone and uses this information to select the appropriate regional DNS server, enabling automatic adaptation without requiring users to manually configure server addresses.
2Loss of time
If regional DNS servers are implemented, then latency is reduced and performance improves, but device complexity increases due to time zone detection and server selection logic
Solution Approach 1:
The patent implements self-service by enabling user devices to automatically detect their own time zone information and select appropriate regional DNS servers without requiring manual configuration or complex user intervention. The device performs self-diagnosis of its geographic location and self-configures the optimal DNS server selection, simplifying the user experience while reducing latency.
3Adaptability or versatility
If multiple DNS server configurations are maintained, then regional optimization is achieved, but the number of fully qualified domain names required increases
Solution Approach 1:
The patent changes the selection parameter from static FQDN-based DNS server identification to dynamic time zone-based selection. Instead of maintaining separate FQDN configurations for different regions, the system uses time zone offset as a dynamic parameter to select from a configured list of DNS servers, reducing the number of FQDNs required while maintaining regional optimization capability.
Data Source
AI summary
Systems and network devices configured for client-side domain name system (DNS) prioritization using time zone offset to select from configured list of DNS servers. A UE device (DNS client) may determine its current time zone, and query a locally stored domain name system (DNS) server list to select a regional DNS server based on its current time zone. The UE device may send DNS requests for resource addresses to the selected regional DNS server. In response, the UE device may receive DNS response messages that priorities resource addresses based on their geographic proximity to the current time zone of the UE device.