Skip to content

2.5.3
Compare
Choose a tag to compare
@saxmfone1 saxmfone1 released this 19 Jun 13:53
· 119 commits to master since this release
2.5.3
64085d1
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Enterprise DDI 2.5.3 brings a large number of UI and API bug fixes.

  • Feature Enhancements
    • API: The records API now requires record type along with the record name when requesting a paginated set of records
    • API: The GET /ipam/address/:id/adjacent route now distinguishes between a bad prefix and no adjacent addresses upon error
    • DHCP: Reduced the amount of spurious logs generated by the DHCP container
    • Monitoring: Logging is more consistent with the rest of the applications
    • Monitoring: It is now possible to disable TLS verification on HTTP jobs
    • System: Updated to the latest GEO country codes across the product
  • What’s fixed?
    • API: It is now possible to change a Service Definition’s name without supplying its properties
    • API: The GET /zones/:zone/dnssec route now returns the correct data
    • API: Multiple fixes regarding the /dhcp/scopegroup endpoint
    • API: Reverted to previous default values for rate limits
    • API: IPAM search now properly filters based on the tag provided
    • DHCP: Fixed an issue where restarting the DHCP container may cause it to stop handing out leases
    • DDNS: Creating duplicate DDNS zones in a single scope group is now prevented
    • DNSSEC: Performing a KSK rollover now works as expected
    • Portal: It is now possible to untoggle DHCPv6 in a scope group
    • Portal: Fixed an issue when editing a remote server's KDC FQDN causes the remote DNS to reset to 127.0.0.1
    • Portal: Fixed an issue when creating a remote zone using the same FQDN but different scope groups causes duplicate entries
    • Portal: The DDNS reverse zone page now displays correctly for /16 or larger scopes
  • Known issues
    • Monitoring: API validation prevents creation of jobs to monitor private IP addresses (RFC 1918, RFC 4193, etc.)
    • Monitoring: monitoring_edge containers cannot deploy downstream of distribution (dist) containers; workaround is to configure monitoring_edge containers connecting directly to core containers
    • Portal: No objects appear if a user only has the View IPAM/DHCP permission without Manage IPAM/DHCP
    • Portal: Activity log incorrectly shows a successful login even if it was not successful when using 2 Factor Authentication
Assets 2
Loading