The 4.0 comes with following list of new features and improvements:
- Support for BIND DNS management and monitoring
- Create, edit, delete DNS zones and DNS records for BIND DNS v8.x and v9.x (A, AAAA, MX, PTR, CNAME)
- Monitor BIND DNS service status
- Monitor BIND DNS zone status
- Active IP Address conflict detection in both static and DHCP environments.
- Integration of IPAM with our UDT product via subviews
- See Port and User information on the same page as IP address Host or DNS assignment history
- Shutdown port remotely in case of IP address conflict (UDT functionality)
- New Icon pack for IP addresses, DNS zones and DHCP scopes.
Some of you may read IPAM 4.0 RC blog post that presents BIND DNS management and monitoring and IP Address conflict detection. For thos who didn't, here is a short summary:
BIND DNS Monitoring and Management
BIND DNS is de-facto DNS standard and it's frequently used among IT guys. Those who need to configure BIND DNS via CLI know that there is a lot of space of human mistake during adding new DNS zones or updating DNS records. I can also imagine that admins are not comfortable with giving CLI credentials for read/write/create/modify BIND config files to people that just need to maintain DNS records. And that's why we added support for BIND management into IPAM - no more errors during config and no more sharing of CLI credentials.
Adding and configuring BIND DNS servers is a matter of few minutes. As a user, you need to do three steps:
- Add device that hosts BIND DNS as a node into IPAM (that will also allow you to monitor device performance)
- Let IPAM to scan BIND configuration (enable scanning)
- Allow/Deny other users to change BIND configuration (Power User role and above can do that).
Active IP address conflict & User Device Tracker integration
IPAM 4.0 can detect IP Address conflicts (both IP static and DHCP environments) and help you to troubleshoot the problem. It would allow you to switch down the port remotely if you have UDT installed along with IPAM. Let's take an example of IP conflict and how IPAM may help you:
IPAM 4.0 offers following IP Address Conflict detection and historical data in order to help you identify devices in conflict.
- IP Address conflict is triggered
- IPAM contains information about the IP Address history assignment from where may user see MAC addresses that are using IP in conflict
- If UDT is installed, UDT view provides information about Device, Port and Active Directory information.
- UDT can remotely shut down switch port and unblock IP in conflict.
For more details about IPAM 4.0 release visit SolarWinds IP Address Manager Release Notes