IPAM API – How to Integrate Multiple DNS Zones Within a Single Subnet

akshayshirke633

Hello Everyone,

We have a requirement where a single subnet contains Servers, Devices, and VIPs across multiple DNS domains/zones.

SolarWinds IPAM does not currently provide a built-in option to associate multiple DNS zones/domains with a single subnet. We have been advised to consider using the IPAM API/automation approach to handle this requirement.

We would like to understand how others have implemented this through the SolarWinds API.

Our requirement is:

• One subnet may contain IP addresses belonging to multiple DNS zones/domains.
• We need to integrate/query the appropriate DNS zones and update the corresponding IPAM information through the API.
• The solution should be automated so that IPAM can be kept in sync with the DNS information.

Could anyone please provide guidance on:

1. How can we associate or manage multiple DNS zones within a single subnet through the API?
2. Is there a recommended API workflow for querying DNS records from multiple zones and updating IPAM?
3. Are there any existing SolarWinds API examples, scripts, or PowerShell implementations for this type of integration?
4. Are there any limitations or considerations we should be aware of when implementing this through API/automation?

If anyone has implemented a similar solution, an example workflow or sample PowerShell/API code would be very helpful.

Thanks in advance for your guidance.

Regards,
Akshay S

giovana.prado

One option is to use the SolarWinds IPAM API/SWIS in conjunction with PowerShell automation, treating subnets and DNS zones as independent objects and correlating the data based on IP address.

The suggested workflow is as follows:

1.Query the SolarWinds IPAM API for the subnets and IP addresses that need to be synchronized;
2.Query the various DNS zones/domains using PowerShell or mechanisms available within the DNS environment;
3.Correlate DNS records with their respective IP addresses;
4.Identify the hostname/FQDN and the associated DNS zone for each address;
5.Use the API/SWIS to update the IPAM attributes designated for storing this information;
6.Run this process on a recurring basis—for example, via Windows Task Scheduler—to keep IPAM synchronized with DNS.