DNS Reverse Zone File Compilation for Subnetted Class C IP Addresses
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mechanisms for subnetted class C internet protocol address DNS reverse lookups involve multiple zone files and queries, leading to overhead on DNS servers and potential customer confusion, as well as the risk of affecting other customers when changes are made to subnetted class C IP address zones.
Innovation Solution
A server that compiles separate subnetted class C IP address DNS reverse zone files into a single zone file for the entire class C or B internet protocol address block, transmitting this to an authoritative DNS server, allowing for one-step reverse DNS lookups without generating DNS canonical names, thereby reducing query time and minimizing errors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple subnetted class C IP address DNS reverse zone files are used for reverse lookups, then the DNS service can support subnetted class C internet protocol addresses, but the query time and response time increase due to multiple queries
Solution Approach 1:
The patent combines multiple subnetted class C IP address DNS reverse zone files into a single consolidated zone file that covers the entire class C or class B internet protocol address block. This merging eliminates the need for multiple separate queries, reducing both query time and response time while maintaining support for subnetted class C addresses.
2Adaptability or versatility
If multiple zone files are used for subnetted class C IP addresses, then reverse lookup functionality is provided, but overhead on DNS servers increases
Solution Approach 1:
The patent consolidates multiple separate zone files into a single zone file that handles the entire class C or class B internet protocol address block. This reduces DNS server overhead by eliminating the need to manage, load, and query multiple separate zone files, while maintaining full reverse lookup functionality.
3Ease of manufacture
If separate zone files are used for each subnetted class C IP address zone, then specific zone management is enabled, but changes to one zone may affect other customers
Solution Approach 1:
The patent uses DNS canonical names (CNAME) within the consolidated zone file to segment and isolate different customer zones. Each customer's internet protocol address range is associated with a unique CNAME, ensuring that changes to one customer's zone data do not affect other customers while maintaining a single unified zone file structure.
4Adaptability or versatility
If DNS canonical names are generated for subnetted class C IP addresses, then reverse lookup mapping is achieved, but customer confusion occurs
Solution Approach 1:
The patent uses DNS canonical names as intermediary references within the zone file structure, but the actual reverse lookup process resolves these to direct domain names without exposing the CNAME mechanism to customers. This allows the system to maintain efficient mapping while presenting simple, confusion-free domain names to end users.
Data Source
AI summary
A subnetted class C internet protocol (IP) address domain name system (DNS) reverse zone file compiling server. The server comprises a memory, a processor, and an application stored in the memory that, when executed by the processor, generates a class C IP address DNS reverse zone file associated with the starting class C internet protocol address based on the parsing of the plurality of subnetted class C IP address DNS reverse zone files, wherein the class C IP address DNS reverse zone file comprises an entry for each of assigned internet protocol addresses, wherein each entry for each of the assigned internet protocol addresses directly maps a domain name to an internet protocol address and does not indicate a DNS canonical name type.