DNS Device Name Duplication Prevention via Two-Stage Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing Domain Name System (DNS) technologies, including Multicast DNS (mDNS) and DNS-SD, fail to prevent duplicate device name registrations across local and wide area networks, leading to user confusion during device searches.
Innovation Solution
An information processing device equipped with a first confirmation unit to check for duplicate device names within the local area network, a second confirmation unit to verify uniqueness across the DNS server, and a registration unit to register a unique device name, ensuring no duplication occurs within or outside the local area network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If mDNS is used for device name resolution within local area network, then device search capability within LAN is improved, but duplicate device names can still be registered in DNS server beyond local area network
Solution Approach 1:
The device name verification process is segmented into two distinct stages: first checking for duplicates within the local area network using mDNS, then checking against the DNS server for broader network uniqueness. This segmentation allows each verification stage to operate independently and effectively within its scope.
Solution Approach 2:
The system performs preliminary verification of device name uniqueness within the local area network using mDNS before attempting registration in the DNS server. This preliminary action prevents potential duplicates from reaching the DNS server, ensuring cleaner data at the broader network level.
2Ease of manufacture
If device name registration is allowed without duplication guard in DNS server, then registration process is simplified, but duplicate device names are registered causing user confusion
Solution Approach 1:
The system implements self-service verification where the device itself performs the duplication check against the DNS server before registration. This eliminates the need for complex server-side duplication guard mechanisms while maintaining data integrity through client-side responsibility.
Solution Approach 2:
The device performs a preliminary query to the DNS server to check if its chosen device name already exists in the broader network before completing registration. This preliminary action prevents duplicate registrations without requiring complex server-side validation logic.
3Adaptability or versatility
If duplicate device names are registered in DNS server, then device search beyond local area network becomes possible, but user clarity is reduced due to displayed duplicates
Solution Approach 1:
The system implements feedback mechanisms where the device queries the DNS server to verify name uniqueness before registration. This feedback loop ensures that only unique device names are registered, maintaining clear and distinct device identification across the entire network while preserving broad search capability.
Data Source
AI summary
An information processing device that is connected to a DNS server via a network in which the information processing device and the DNS server can communicate with each other comprising: a first confirmation unit that confirms if there is a duplication of a device name of the information processing device within the same local area network; a second confirmation unit that confirms if the device name of the information processing device is a duplicate of a device name registered in the DNS server if it is confirmed there is no duplication of the device name of the information processing device within the same local area network; and a registration unit that registers the device name of the information processing device in the DNS server if it is confirmed that the device name of the information processing device is not a duplicate of the device name registered in the DNS server.