Browser Add-on Passive DNS Data Collection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Building a passive DNS database requires network infrastructure to intercept DNS messages, which can be difficult to set up and obtain permissions for, and existing methods lack efficient data collection without specialized infrastructure.
Innovation Solution
A browser-based passive DNS system that uses a browser add-on to log and transmit mapping data from user devices to a passive DNS system, allowing for the compilation of domain name to IP address mappings without needing extensive infrastructure, by monitoring DNS look-ups and batching data for transmission based on user-defined criteria.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If network infrastructure is used to intercept DNS messages, then DNS database can be built, but device complexity and difficulty of obtaining permissions increase
Solution Approach 1:
The system allows user devices to automatically collect and transmit DNS mapping data without requiring centralized infrastructure. Each device independently performs DNS lookup monitoring and contributes data to the passive DNS database, eliminating the need for complex interception infrastructure.
Solution Approach 2:
A passive DNS system server acts as an intermediary that receives mapping data from multiple user devices and compiles the DNS database. This mediator approach allows distributed data collection while centralizing database management, avoiding the need for complex network interception infrastructure.
2Reliability
If DNS mapping data is transmitted continuously, then database is updated in real-time, but network overhead and latency increase
Solution Approach 1:
The system implements periodic batch transmission where mapping data is collected over time and transmitted in batches based on thresholds (data volume, time intervals, or queue size). This periodic approach reduces network overhead compared to continuous transmission while maintaining reasonable database update timeliness.
Solution Approach 2:
The system performs preliminary data collection and buffering at user devices before transmission. Mapping data is accumulated in local queues and pre-processed, then transmitted in batches when thresholds are met, reducing the frequency and volume of network transmissions.
3Loss of information
If more mapping data is collected, then DNS database completeness improves, but data transmission frequency increases
Solution Approach 1:
The system transmits data in batches based on configurable thresholds rather than transmitting all collected data continuously. This partial transmission approach balances database completeness with transmission efficiency, sending sufficient data to maintain database quality without excessive transmission frequency.
Solution Approach 2:
The system dynamically adjusts transmission behavior based on multiple factors including data volume thresholds, time intervals, and queue sizes. This dynamic approach allows the system to optimize between data completeness and transmission efficiency based on current conditions.
Data Source
AI summary
In some implementations, a method includes logging, by a user device, mapping data that maps domain names of Internet resources presented on the user device to Internet Protocol (IP) addresses of the Internet resources, determining, by the user device, that one or more criteria are satisfied for transmitting the mapping data to a passive Domain Name Service (DNS) system, and in response to determining that the one or more criteria are satisfied, transmitting, by the user device, the mapping data to the passive DNS system.