Partitioned Recursive Name Servers for Per-Device DNS Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional DNS systems lack effective per-user and per-device filtering capabilities, leading to inadequate protection against malware and phishing sites, as global blacklisting and whitelisting apply uniformly across households, failing to provide customized filtering for individual devices and users.
Innovation Solution
Implementing a method that partitions name servers to enable per-device and per-user DNS filtering by associating specific DNS settings with unique name servers, allowing for customized blacklisting and whitelisting based on device and user profiles, using a public IP address to determine filtering policies and routing DNS requests to appropriate name servers for tailored responses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If global blacklisting and whitelisting are applied uniformly across households, then internet security protection is provided, but per-user and per-device filtering capabilities are lost
Solution Approach 1:
The patent segments the DNS resolution process by introducing multiple recursive name servers (first recursive name server and second recursive name server) that can be selectively assigned to different devices. Each name server can be configured with different filtering policies, allowing per-device customization while maintaining centralized management. This resolves the contradiction by dividing the uniform filtering system into device-specific filtering units.
Solution Approach 2:
The system dynamically assigns devices to different recursive name servers based on device identifiers or user profiles. The DNS settings are configurable and can be changed per device, enabling the system to adapt filtering behavior to individual device needs. This dynamic configuration capability provides both security protection and customized filtering capabilities simultaneously.
2Adaptability or versatility
If per-device DNS filtering is implemented, then customized filtering for individual devices is achieved, but system complexity increases
Solution Approach 1:
The patent introduces an intermediary component (the resolver or DNS management system) that handles the complexity of managing multiple recursive name servers and their associated filtering policies. This intermediary translates high-level device identifiers into appropriate name server assignments, shielding users from the underlying system complexity while enabling per-device customization. The intermediary absorbs the management complexity rather than requiring users to directly configure complex DNS settings.
3Adaptability or versatility
If multiple recursive name servers are used for different devices, then per-device filtering policies are enabled, but DNS resolution time may increase
Solution Approach 1:
The system performs preliminary configuration by pre-assigning devices to specific recursive name servers based on device identifiers or user profiles. This assignment is established in advance through configurable DNS settings, so that when DNS queries are made, devices can directly contact their designated name server without real-time decision-making delays. The preliminary assignment minimizes resolution time while maintaining per-device filtering capabilities.
Data Source
AI summary
A method of applying device preferences to network traffic includes establishing first DNS settings of a first device and establishing second DNS settings of a second device. The first DNS settings are associated with one or more first name servers. The second DNS settings are associated with one or more second name servers. The method also includes transmitting, from the first device, at least a portion of a first DNS query and a public IP address to the first name server. The method further includes transmitting, from the second device, at least a portion of a second DNS query and the public IP address to the second name server.