Dynamic DNS Collision Avoidance via Location-Based Attribution

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Dynamic DNS collisions occur when multiple client devices with the same dynamic DNS agent provide the same IP address, leading to uncertainty in attributing content filtering policies, potentially disrupting the enforcement of intended policies on private networks.

Innovation Solution

A method that determines the most likely owner of a network by comparing locations associated with client devices using trace routes, triangulation, or geolocation, allowing the backend server to attribute the IP address and apply the appropriate content filtering policy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If dynamic DNS services are provided to multiple client devices, then domain name resolution and content filtering services are made more accessible, but DNS collisions occur when multiple devices provide the same IP address

Engineering Contradiction:
Improveaccess to domain name resolution servicesVSAvoidDNS collision occurrence
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces location information as an intermediary attribute to distinguish between multiple client devices that share the same IP address. The backend server uses location data (derived from trace routes, triangulation, or geolocation) as a mediating factor to resolve DNS collisions by identifying which client device is the most likely owner of the private network based on spatial proximity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If location determination methods (trace routes, triangulation, geolocation) are used to resolve DNS collisions, then IP address attribution accuracy is improved, but system complexity increases

Engineering Contradiction:
ImproveIP address attribution accuracyVSAvoidsystem complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent applies partial action by implementing location determination methods selectively rather than universally. The system uses trace routes, triangulation, or geolocation only when DNS collisions are detected and location data is needed to resolve the conflict, rather than continuously collecting and processing location information for all client devices, thereby reducing overall system complexity.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If the backend server determines the most likely owner based on location data, then content filtering policy enforcement is improved, but processing time increases

Engineering Contradiction:
Improvecontent filtering policy enforcementVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary action by pre-determining and storing location data for client devices before DNS collision resolution is needed. Location information is collected and stored in advance, allowing the backend server to quickly compare pre-computed location data when a DNS collision occurs, rather than performing complex location determination in real-time during the collision resolution process.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9130994B1Techniques for avoiding dynamic domain name system (DNS) collisions
Publication Date: 2015.09.08 GEN DIGITAL INC
  • US9130994B1 patent drawing
  • US9130994B1 patent drawing
  • US9130994B1 patent drawing

AI summary

Techniques for avoiding dynamic domain name system (DNS) collisions are disclosed. In one particular exemplary embodiment, the techniques may be realized as a method for avoiding dynamic domain name system (DNS) collisions comprising: storing a first location associated with a first client device, a second location associated with a second client device, and a third location associated with a network, receiving, from the first client device, a first notification indicating an Internet Protocol (IP) address via the network, receiving, from the second client device, a second notification indicating the IP address via the network, determining a most likely owner of the network between the first client device and the second client device based on the first location, the second location, and the third location, and applying a content filtering policy associated with the first client device when the first client device is determined to be the most likely owner.