2.4.2

Enterprise DDI 2.4.2 contains new geo-steering granularity, several fixes and enhancements.

• New Features
  • DNS: Additional ISO-3166-2 country subdivisions are available for geotarget country and geofence country filters; import premium versions of Maxmind’s GeoIP databases to take full advantage of additional geo-steering granularity; all subdivisions can be referenced in the new endpoint v1/metatypes/geo
• Feature Enhancements
  • Portal: Records now show the number of answers they have
  • IPAM: Search now works across all networks
• What’s fixed?
  • DNS: Creating a record with no answers will no longer cause the zones api and portal page to fail
  • DNS: Fixed an issue which prevented configuring DNS forwarding via supd UI and CLI
  • DNS: Fixed a regression where the number of zones in an organization were limited to five thousand
  • DNS: Fixed a regression where the number of records in an organization were limited to one million
  • Portal: Fixed numerous UI issues related to Record Level permissions
  • API: Spaces will now be stripped from the address range when creating an IP range
  • API: Fixed POST requests to /v1/account/apikeys/ resulting in 500: Internal Server Error responses
• Known issues
  • DHCP: Creating or modifying scope groups without DHCPv4 or DHCPv6 enabled yet passing in parameters for DNS synthesis will result in DHCPv4 being enabled and the .com TLD chosen as the zone for synthesis; enable DHCPv4 or DHCPv6 to avoid this misconfiguration
  • DNS: Specific countries in the country list without subdivision data return 500: Internal server errors when configured on answers (e.g. Chad, Bermuda, etc.); upcoming fix will respond with 400 response codes instead in these cases