Selective DNS Record Synchronization via Tagged Difference Propagation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current DNS synchronization methods mirror all DNS records across multiple data centers, failing to efficiently manage situations where certain records should not be mirrored or where only subset changes are made, leading to inefficiencies and potential network outages.
Innovation Solution
Implementing selective synchronization logic that initializes a synchronization data store with DNS records, identifies differences, and propagates changes based on tags, attributes, and characteristics, ensuring only authorized and necessary changes are synced between data centers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If all DNS records are mirrored across multiple data centers, then DNS service availability is improved, but synchronization efficiency deteriorates due to unnecessary propagation of records that should not be mirrored
Solution Approach 1:
The patent segments DNS records into different categories based on their synchronization requirements. Records are tagged with attributes indicating whether they should be propagated to other data centers. This segmentation allows the system to selectively synchronize only the necessary records, improving efficiency while maintaining availability for records that require replication.
Solution Approach 2:
The patent applies local quality by allowing different DNS records to have different propagation characteristics. Some records are marked for synchronization across data centers while others are kept local. This enables each data center to maintain appropriate copies of records based on their specific needs, balancing availability with synchronization efficiency.
2Stability of the object's composition
If complete DNS record sets are synchronized between data centers, then consistency is improved, but network overhead increases due to propagating unnecessary changes
Solution Approach 1:
The patent extracts only the necessary DNS records for synchronization by evaluating their tags and attributes. Instead of propagating complete record sets, the system identifies and extracts only those records that require synchronization, thereby maintaining consistency while significantly reducing network overhead and energy consumption.
Solution Approach 2:
The patent applies partial action by synchronizing only the subset of DNS records that are marked for propagation rather than complete record sets. This partial synchronization approach maintains adequate consistency for records that need it while avoiding the network overhead of syncing unnecessary records.
3Loss of time
If DNS synchronization occurs at frequent intervals, then record freshness is improved, but system resource consumption increases
Solution Approach 1:
The patent implements periodic synchronization intervals rather than continuous syncing. By configuring appropriate time intervals between synchronization cycles, the system maintains reasonably fresh DNS records while avoiding excessive resource consumption that would result from continuous or overly frequent synchronization attempts.
Data Source
AI summary
Systems and methods described herein provide selective synchronization of DNS records. A synchronization data store is synchronized by: obtaining a complete set of domain name system (DNS) records for a first data center; and copying the complete set of DNS records to the synchronization data store. After the synchronization data store is initialized, at a particular time interval, a snapshot of the complete set of DNS records is repeatedly collected. Differences between the copied complete set of DNS records of the synchronization data store and the snapshot of the complete set of DNS records are identified. The synchronization data store is updated with the differences and a determination is made as to whether the differences should be implemented at a second data center. When the differences should be implemented at the second data center, the differences are propagated to the second data center, otherwise they are not.