DNS Manager Automates Virtual Network Rule Updates

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In virtual network environments, DNS servers require frequent manual reconfiguration due to dynamic changes in virtual machines and IP addresses, posing a challenge in maintaining up-to-date DNS rules, especially in complex networks with frequent changes.

Innovation Solution

A DNS manager maps VM inventory objects to IP addresses and DNS names, dynamically configuring the DNS server by replacing VM inventory objects with IP addresses from IPAM or NAT tables and modifying DNS names using zone and view tables, reducing the need for manual updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If DNS rules are manually configured and updated, then DNS server can be configured, but administrative burden increases and updates are delayed

Engineering Contradiction:
ImproveDNS rule configuration automationVSAvoidAdministrative burden
Core Design Contradiction:
Extent of automationVSEase of operation

Solution Approach 1:

The system enables self-service by automatically detecting VM lifecycle events and IP address changes, then autonomously updating DNS rules without requiring administrator intervention. The DNS manager monitors inventory objects, IPAM tables, and NAT tables to detect changes and dynamically configures DNS server records, allowing the system to maintain itself without human operation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring VM inventory objects, IP address assignments, and network changes. When changes are detected in the inventory or IPAM/NAT tables, the system receives feedback about these changes and automatically adjusts DNS rules accordingly, creating a closed-loop system that responds to real-time network conditions.

Inventive Principle:
Principle #23Feedback

2Reliability

If DNS rules are frequently updated to track network changes, then DNS accuracy is maintained, but system complexity increases

Engineering Contradiction:
ImproveDNS rule accuracyVSAvoidNetwork configuration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system introduces a DNS manager as an intermediary component that sits between the network infrastructure (VM inventory, IPAM, NAT tables) and the DNS server. This mediator automatically translates network changes into corresponding DNS rule updates, shielding the DNS server from direct complexity of network change management while maintaining accurate and up-to-date DNS records.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system performs preliminary actions by proactively monitoring and detecting network changes before they affect DNS operations. By continuously watching VM lifecycle events and IP address assignments in advance, the system can prepare and apply DNS rule updates before clients experience any issues, maintaining reliability without reacting to problems after they occur.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If manual DNS reconfiguration is performed, then DNS rules can be updated, but time consumption increases

Engineering Contradiction:
ImproveDNS configuration speedVSAvoidTime for manual updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system ensures continuity of useful action by maintaining continuous monitoring of VM inventory objects and network configurations. Rather than periodic manual checks, the system operates continuously to detect and respond to changes instantly, eliminating downtime and delays associated with manual update cycles. DNS rules are always current because the system is continuously synchronized with network changes.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The system performs preliminary detection and preparation of DNS updates before they are needed. By monitoring network changes in advance and pre-processing DNS rule modifications, the system eliminates the time-consuming manual update process entirely, achieving near-instantaneous DNS configuration changes as VMs are added, removed, or reconfigured.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9419937B2System and method for dynamically configuring a DNS server in a virtual network environment
Publication Date: 2016.08.16 VMWARE INC
  • US9419937B2 patent drawing
  • US9419937B2 patent drawing
  • US9419937B2 patent drawing

AI summary

Techniques for dynamic configuration of a domain name system (DNS) server in a virtual network environment are described. In one example embodiment, DNS rules are configured using virtual machine (VM) inventory objects and associated DNS names. Further, the configured DNS rules are transformed by replacing the VM inventory objects in the configured DNS rules with associated Internet protocol (IP) addresses using an IP address management (IPAM) table or a network address translation (NAT) table and the DNS names in the configured DNS rules with modified DNS names using a zone table and a view table. Furthermore, the transformed DNS rules are sent to the DNS server for performing domain name resolutions associated with multiple VMs running on a plurality of host computing systems in a computing network.