DNS-Based Routing Lookup Without Direct Router Queries
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional command-line interface (CLI) approaches for obtaining network routing information impose a processing burden on network devices, require authentication and authorization, lack standardization, and cause performance lag, making it difficult to access network routing information efficiently.
Innovation Solution
Utilizing a Domain Name System (DNS) server to receive and process network routing information from network devices, such as Border Gateway Protocol (BGP) configured routers, without direct queries, enabling standardized access and reducing the processing load on these devices.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional CLI approaches are used to obtain network routing information, then network devices can provide routing data, but the processing burden on network devices increases and authentication/authorization is required
Solution Approach 1:
The patent introduces a DNS server as an intermediary between clients and network devices. The DNS server receives routing information from network devices and serves it to clients through standardized DNS queries. This mediator approach eliminates the need for clients to directly query network devices via CLI, thereby reducing the processing burden on network devices while maintaining reliable access to routing information.
Solution Approach 2:
The patent replaces the mechanical CLI query system with a DNS-based information retrieval system. Instead of using traditional network management protocols that require authentication and complex processing, the system uses standardized DNS queries to access routing information, simplifying the interaction mechanism and reducing processing requirements on network devices.
2Reliability
If conventional CLI approaches are used, then network routing information can be obtained, but authentication and authorization are required and standardization is lacking
Solution Approach 1:
The patent makes the DNS server universal by enabling it to handle both traditional DNS queries and routing information retrieval through the same interface. This multi-functionality allows any client to access routing information from any network device through standardized DNS protocols, eliminating the need for separate authentication mechanisms and providing universal access without requiring user-specific credentials.
Solution Approach 2:
The DNS server acts as an intermediary that handles authentication and authorization centrally. Instead of requiring individual clients to authenticate with each network device, the DNS server manages access control and serves routing information to authenticated clients through standardized queries, thereby simplifying the operational process and eliminating repeated authentication requirements.
3Productivity
If direct queries to network devices are made, then routing information can be retrieved, but performance lag occurs
Solution Approach 1:
The patent implements preliminary action by having the DNS server proactively retrieve and cache routing information from network devices before clients need it. The DNS server can periodically update its routing information cache or retrieve information in advance of client requests, thereby reducing the time required for client queries and eliminating performance lag associated with real-time direct queries to network devices.
Data Source
AI summary
Methods may comprise receiving, at a Domain Name System (DNS) server, a domain name, determining, based at least on the domain name, a network identifier, causing retrieval, via the DNS server and based on at least a portion of the network identifier, of network routing information associated with a network device, and transmitting, from the DNS server, at least a portion of the network routing information to one or more computing devices.