DNS Server Address Update via Notification List
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing DNS systems face connection failures due to outdated IP addresses when server address information changes before the TTL period expires, leading to increased load and inefficiency in updating server address information.
Innovation Solution
A system and method where a second DNS updates server address information in real-time by maintaining a notification list of network addresses, allowing immediate transmission of changed information to all DNS systems that have obtained server address information, thereby avoiding the need for a TTL-based update process and ensuring correct address information is provided.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a DNS stores server address information with a TTL value, then the DNS can reduce update frequency and lower system load, but the server address information becomes outdated when the IP address changes before the TTL period expires
Solution Approach 1:
The patent implements a feedback mechanism where the second DNS monitors whether stored server address information has been requested by client servers. When the information is accessed, the second DNS receives feedback and proactively transmits updated IP address information to the first DNS, ensuring the stored information remains accurate without relying solely on TTL expiration.
Solution Approach 2:
The second DNS performs preliminary actions by monitoring and detecting changes in server address information before client servers attempt to use outdated addresses. When an IP address change is detected, the update is transmitted proactively to participating DNS systems before any connection failure can occur, preventing the reliability issue rather than correcting it afterward.
2Reliability
If a DNS repeatedly executes query operations to update IP addresses, then the DNS can ensure current address information, but the system load and time consumption increase significantly
Solution Approach 1:
Instead of continuous or repeated query operations, the patent implements periodic action where the second DNS transmits updated IP address information at specific intervals triggered by actual changes in server address information. This change-driven periodic update mechanism ensures current information is provided without the time consumption of frequent unnecessary queries.
Solution Approach 2:
The second DNS performs self-service by autonomously monitoring its own server address information changes and initiating updates to participating DNS systems without requiring external requests. This eliminates the need for other DNS systems to repeatedly query for updates, reducing overall system time consumption while maintaining information currentness.
3Reliability
If the DNS uses a notification list to track participating DNS systems, then real-time updates can be transmitted to all DNS, but the device complexity and storage requirements increase
Solution Approach 1:
The notification list serves multiple functions: it stores participating DNS system addresses, tracks which DNS systems have received updates, and manages update distribution. This multi-functionality reduces the need for separate mechanisms for each task, managing the complexity through consolidation rather than multiplication of components.
Data Source
AI summary
A method of a first DNS which can update server information in real time without necessarily using a TTL (Time To Live) by recording a network address of the first DNS, which has previously obtained server address information from a second DNS, in a notification list, by the second DNS, and transmitting the changed information from the second DNS to the first DNS recorded in the notification list when the previously obtained/requested server address changes, and updating the server address by the first DNS as provided by the second DNS. A DNS updating server address method may further include providing a first DNS with server address information corresponding to a domain, recording a network address of the first DNS in a notification list, corresponding to the domain and/or the server address information, and transmitting a changed server address information to the first DNS based on the notification list.