25.1.0 - Release Notes - Micetro

New Features

• ALIAS resource records: Micetro now supports ALIAS resource records, which are read-only. For information, refer to AWS and Azure ALIAS records in Micetro
• Anycast: Anycast network configuration is now supported through two routing protocols on MDDS. For more information, refer to Configuring Anycast on Appliances
• Cisco Meraki IPAM: Micetro now supports the synchronization of non-DHCP Meraki subnets and subnets that have a DHCP relay configured, in addition to those with DHCP enabled. Refer to Cisco Meraki
• Dedicated management interface for MDDS: Micetro now allows you to enable a dedicated management interface on an MDDS appliance. Refer to Integrating and Managing Appliances. When setting Micetro mode on MDDS, make sure to open the firewall on correct network interface (KI-026258)
• DNS cache management: Micetro now provides the ability to view and clear the DNS server cache in the Web Application. Refer to Managing the DNS cache
• Export feature: You can now copy and export up to 500 rows from most of the data grids in the Web Application. Export is available in .csv, .tsv, and .xslx formats (KI-026187 and KI-025581)
• Migrate DHCP Scopes: The Web Application now enables you to migrate DHCP scopes between servers. For more information, refer to Migrating Scopes
• Private zones: Micetro now provides read and write support for private zones on AWS and Azure services. For more information, refer to Zone Types (KI-025776)

Improvements

• Added ability for DHCP administrators to assign client classes to DHCP superscopes on Kea servers
• Added ability to associate a DHCP reservation to a class upon creation and then edit it (KI-025841)
• Added ability to filter for exclusively dynamic or static IP addresses within a DHCP scope using the sidebar filter (KI-025768)
• Added a new synchronization mechanism for Kea DHCP servers to improve syncing performance
• Added support for Uniform Resource Identifier (URI) resource records on BIND (KI-025623)
• Added a system setting that requires user administrator access to be able to retrieve a list of users, groups, and/or roles. Defaults to true on new installations, but false for existing users (KI-026053)
• Added a tooltip with instructions for enabling the Configure button if it’s in a disabled state
• By default, new password fields will not autofill with your Micetro password
• Implemented separate calls to fetch DHCPv4 and DHCPv6 leases to remove the risk of error in retrieving both at the same time
• Improved logging of object history for appliances that have been moved between address spaces
• Improved the method by which Micetro fetches DNS server IP addresses to use in root records for primary zones and when connecting secondary zones to the DNS server
• Improved PXE support for Kea servers and added DHCP configuration options, like client classes, to those that can be edited in the Web Application (KI-025642)
• Increased the limit of subranges you can allocate from a range at a given time to 512 (KI-025504)
• Micetro will refuse to initialize a new database if the selected encoding is case-insensitive
• Micetro uses a parser to handle BIND configuration as of version 11.0. More information is available in the BIND DNS File Structure reference article (KI-026056)
• Minimum password strength constraint added as a system setting, for which the default is 12 characters (KI-026043 and KI-025508)
• Read-only DNS records are visually indicated in the Micetro UI with a read-only icon
• Significantly increased performance when sorting IP address ranges by their custom properties in large environments
• The Add Service dialog was improved for consistency in the Web Application
• The item selected in the left sidebar is now used as the default when creating zones, DHCP scopes, or DNS records
• Users assigned the administrator role can add or remove address spaces (KI-025782)
• When creating a network, the folder in which the network will be created is always displayed
• You can now add VendorClasses to Kea DHCP when defining new Custom Options in the Web Application
• You can now edit subnet ranges in the Web Application (KI-025520)

Bug Fixes

• Active nodes in High-Availability mode now actively check whether the standby nodes have failed and, if so, the standby nodes are set to an Offline state (KI-025777)
• Failover relationships created on Kea servers do not support multi-threaded (MT) communication between peers in Kea. Users must edit the config directly to create failover relationships with MT enabled
• Fixed an issue affecting database performance for customers with MS SQL server
• Fixed an issue in which a user with only the built-in administrator role could not see the System Settings when only one of the core license keys (DNS or IPAM) was present (KI-026062)
• Fixed an issue in which having multiple IP address spaces configured resulted in duplicate result rows in IP address reports
• Fixed an issue during the creation of a new zone, in which a custom property with a dot in its name resulted in an error (KI-025859)
• Fixed an issue during the creation of a secondary zone on a BIND server in the Web Application that prevented creation of the zone file (KI-026175)
• Fixed an issue during the creation of a report, in which filtering by a custom property with a space in its name resulted in a report with no data entries
• Fixed an issue in which the Remove from AD Site task was missing a “danger” property, so it didn’t display properly as a destructive action
• Fixed an issue preventing users from editing SNMP profiles by moving the fetch call for tasks available to each SNMP profile to prevent potential re-render loops (KI-025983)
• Fixed an issue that caused Micetro Central to potentially crash when working with IP addresses (KI-025997)
• Fixed an issue that didn’t remove the timestamp value from the Web Application when the “aging” parameter is removed while editing TTL for dynamic records (KI-025957)
• Fixed an issue that returned duplicate records when DNS cache nodes had same records cached
• Fixed an issue that returned IP addresses that had already been assigned when using the NextFreeAddress API call (KI-026010)
• Fixed an issue that reverted changes Smart Folder filter to its original value (KI-026044)
• Fixed an issue with fetching reservation options on ISC DHCP
• Fixed connectivity issue with Cisco IOS servers connecting to Micetro (KI-025719)
• Fixed a problem with the DNS cache for BIND when no cache-file was defined (KI-026188)
• IP address license usage is correctly calculated for overlapping Meraki scopes, so that IP addresses across all instances are counted
• IPv6 networks are now excluded from subnet monitoring. Micetro will only monitor IPv4 networks (KI-025635)
• Micetro can now sync a lease history from Microsoft when the hostname field contains a quotation mark (”) (KI-026093)
• Removing an appliance from Micetro does not remove or shut down the DNS and DHCP servers hosted on that appliance
• Size of the viewname database column in mm_views has been increased to 128 characters (KI-026094)
• There is no limit to the number of services displayed on Services grid. All services are displayed
• TSIG logic that was previously used during zone transfer has been removed and a message is considered the last message only if the last read record is an SOA record with a serial number equal to that of the first read SOA record (KI-025874)
• When a DNS server is detached and reattached, make sure it is synced
• You can now import MS DHCP reservations using the data in the Description column of the Import function (KI-025758)

Deprecation Announcements

• The Men&Mice Management Console has been deprecated in version 25.1.0. This is the final version in which the Management Console is guaranteed to function with Micetro. This version will be supported for two years and, during this time, we will integrate the final features in upcoming releases. If you have any questions about features from the Management Console that are critical to your operation which you don’t currently see replicated in the Micetro Web Application, please contact BlueCat Support at support@bluecatnetworks.com.

• The following software components have been deprecated:

  • mmcmd — Instead, the BackupDatabase API has been added in version 25.1 which provides the ability to back up an SQLite database.
  • mmedit
  • mmlock

• Following version 11.1, new database setups should use the UTF-8 encoding. Older setups using SQL Server or PostgreSQL with Latin1 encoding will continue to work, but users can only enter values with Latin1 characters. Setups using the embedded data storage (SQLite) can use all characters.
• Support for PostgreSQL 12 has been deprecated, as this database is not supported by the vendor as of November 21, 2024.

• Support for the following drivers is deprecated for SQL Server on Windows:

  • Native Client 10 OLE (sqlncli10.dll)
  • Native Client (sqlncli.dll)
  • ODBC SQL Server Driver (sqlsrv32.dll) bundled with Windows

  An error is logged upon startup if no other driver is found. We recommend that all users with SQL Server on Windows and Linux use the Microsoft OBDC driver, either version 18 or 17. This is required when using UTF-8 encoded collations. Otherwise, Micetro will connect to a database using older drivers, which could result in issues such as degraded performance.

• Support for Debian 6 and 7 has been deprecated, as these operating systems are not supported by the vendor. Micetro supports Debian 8 as the minimum version.
• Support for Suse Enterprise Linux 12 has been deprecated in Micetro as this operating system is not supported by the vendor as of October 31, 2024. More information is available here.

• Support for Python 3.8 has been deprecated, as it reached its end of life on October 7, 2024.

Breaking Changes

Failover relationships on Kea created through the Micetro Web Application now explicitly disable multi-threaded communication between the peers. With Kea v2.6, the default value for enable-multi-threading in High Availability configurations has been changed to true. This is a potentially breaking change that could affect existing failover relationships in which both the DHCPv4 and DHCPv6 services are enabled and configured to use the same port number. With multi-threading enabled, the services will both try to bind the same port. The latter service will fail and, therefore, not be started. This will not occur if enable-multi-threading is explicitly set to false. If multi-threaded communication between the peers is required, manually configure the Kea Control Agent, the DHCPv4 service, and the DHCPv6 service to use different port numbers, e.g., 8000, 8001, and 8002, respectively.