Microsoft IPAM & DNS Module

Using the OneFuse IPAM and/or DNS module for Microsoft, it’s easy to create API-based, Microsoft-powered IPAM and DNS services to drive solutions from upstream automation tools or scripts.

OneFuse provides the control and standardization for requesting, validating and registering records with the unique ability to abstract and dynamically drive network selection and many other Microsoft features.

OneFuse eliminates the security risk of requiring direct access to a Microsoft, enabling least-privilege access for specific use cases via policy-based services, versus custom scripting. Each policy defines the automation use case, subnets, DNS record settings and more – with the added flexibility of having the requester influence all use cases dynamically via templated fields defined in OneFuse policies.

Reserved DNS Records in OneFuse

OneFuse Microsoft DNS in vRA Cloud Assembly

OneFuse Microsoft DNS in Terraform

OneFuse Makes vRA Better

Learn More

Highlights

IP and DNS Record Management

Obtain and reserve unique IP address(es) and/or drive DNS record creation and automatically release during the appropriate lifecycle

Flexibility & Scale

Separate dynamic Microsoft Endpoints and Policies for IPAM and DNS configurations (as well as Active Directory configurations) that allow for ultimate flexibility and scale
Ability to mix and match and migrate between other OneFuse IPAM and DNS modules interchangeably

Centralized Visibility

View the active deployment inventory representing the outputs and relevant log data of each IPAM and DNS policy execution

Features and Capabilities

IPAM

Create flexible IPAM Policies that include a Microsoft Endpoint
Reserve unique IP address(es) and assign to the NIC(s) based on IPAM Policy
Perform pre and post validation for IP and DNS assignment
Ability to single-thread operations to reduce load on downstream Microsoft endpoints
Provides control and standardization for resources on both public and private cloud (on-prem) environments.
OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without exposing the full Microsoft IPAM services or over-allocating permissions to users or upstream automation tools.
Ability to support sub-interfaces, e.g. multiple IP assignments per NIC in vRealize Automation
IPAM Policies include basic IP information such as subnets and DNS and WINS configurations
IPAM Policies can be pinned to specific NIC numbers
IPAM Policies can span multiple networks, each consisting of a network name, subnet, CIDR block, gateway address and network mask
Added flexibility of having the requester influence all use cases dynamically via templated fields
Multiple IPAM Policies (each specifying a Microsoft Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption
Microsoft Endpoints can also be used with the OneFuse IPAM, DNS or Active Directory modules
Centralized visibility into inventory of IP assignments, log data
Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API

DNS

Drive from any tool, e.g. vRealize Automation, Terraform, Ansible, ServiceNow, CloudBolt CMP or directly via the API
Create flexible DNS Policies that include a Microsoft Endpoint
Reserve unique DNS Record(s) and based on DNS Policy
Provides control and standardization for resources on both public and private cloud (on-prem) environments
OneFuse enables least-privilege access wherein each policy serves as an API-based service, restricted to the specific use cases defined in the policy, without the need for custom scripting
Drives advanced Microsoft features such as share path via the OneFuse Template Engine
Employs several methods to improve DNS data integrity and mitigate issues from stale, duplicate or orphaned DNS records, such as retry logic, record availability and DNS propagation/post validation checks
Allows for independent configurations for forward and forward/reverse record scenarios, if desired
Added flexibility of having the requester influence all use cases dynamically via templated fields
Multiple DNS Policies (each specifying a Microsoft Endpoint) can safely co-exist, allowing for isolated testing and promotion without disruption
Microsoft Endpoints can also be used with the OneFuse Microsoft Active Directory module
Centralized visibility into inventory of DNS registrations, log data