BlueCat Edge v25.1.0 release notes - Release Notes - BlueCat Edge

BlueCat Edge release notes
ft:locale
en-US
Product name
BlueCat Edge

Announcement date: January 27, 2025

 

What's new

Ability to delete disconnected Cloud Resolver instances

BlueCat Edge v25.1 introduces the ability to delete disconnected Cloud Resolver instances.

What's new

Simplified namespaces for hybrid cloud DNS

The DNS resolver service has been updated to be aware of on-premise and cloud DNS zones. With this capability, users can now reach the applications or resources with reduced latency and administrators no longer need to maintain this forwarding complexity elsewhere in their DNS service infrastructure. This provides the following benefit:

  • Seamless cloud integration: Built for hybrid environments, allowing users to create a single namespace that efficiently resolves for on-premise DNS hosted on Address Manager with DNS environments in AWS, Azure, and GCP.

  • Direct resolution path: By knowing exactly where each DNS record resides, DNS resolver service skips unnecessary recursive steps, reducing DNS resolution times significantly.

  • Adaptive cache: For cloud users, clients receive cloud-optimized DNS answers based on their source IP. If the requested resource is not within the cloud-discovered zones, they are automatically redirected to the DNS answer discovered within Address Manager.

Improved DNS resolution stability

When DNS resolver service is deployed to a service point, the service is automatically scales to make use of the additional CPU and memory available on the service point.
Note: The CPU and memory allocated to the DNS resolver service is set at the time of deployment. If you modify the resources available on the service point after DNS resolver service has been deployed, the CPU and memory allocation will not scale with the resource changes. To ensure that the CPU and memory allocation of DRS makes use of the resource changes, you must redeploy DNS resolver service to the service point.

Support for namespace failover with NOERROR/NODATA response

DNS resolver service now introduces support for namespace failover when a namespace returns a NODATA and NOERROR response. When you have multiple namespaces configured, you can configure the first namespace so that in the event that a query returns NOERROR/NODATA, the next namespace can be used to assess the query.

To configure the namespace failover scenario, specify NODATA in the Response Code field in the first namespace configuration. When a query is encountered where the response is NOERROR/NODATA and the answer does not include a record that matches the query type, the next namespace within a site will attempt to resolve the DNS query.

 

Resolved issues

DNS ID collisions under high QPS

Previously, in environments where there are high QPS loads, the DNS resolver service might incorrectly wrap the incorrect DNS ID around responses if a client is running a slow DNS query. This issue has now been resolved.

SERVFAIL responses may not be removed from the cache

Previously, SERVFAIL response keys may collide in the cache due to no records that differentiate their response cache key. When the DNS resolver service receives a new SERVFAIL, the TTL time was reset due to a new cache entry being added into the same key. This issue has now been resolved.

SERVFAIL cache time can cause issues with successful forwarder responses

Previously, the cache TTL for SERVFAILS was set to 60 seconds, causing issues where a subset of forwarders returned SERVFAILS while other forwarders would return successful responses. This issue has been resolved and the SERVFAIL TTL has been reduced to 5 seconds.

What's new

Discover DNS infrastructure in AWS, Azure, and GCP environments

Discovery instance has been updated to support DNS data discovery cloud environments. Starting in Discovery Instance v1.1.0, you can create Discovery Configurations to retrieve data from AWS, Azure, or GCP environments. You can apply the configurations to Discovery Instances to allow you to manage DNS records across multiple platforms effortlessly using a single namespace. The discovery service introduces the following features:

  • Multi-environment discovery: Continuously discover DNS zones across on-premises, cloud, and third-party services. You can run multi-environment discoveries from a single service point, streamlining Edge deployment architecture.

  • Continuous polling: With continuous polling, the Edge Resolver service keeps up to new DNS infrastructure being created, updated, or removed, ensuring that the DNS resolver services stay up-to-date.

Support for credential recovery from HashiCorp Vault

Discovery Instance v1.1.0 introduces support for retrieving credentials from HashiCorp Vault. If you store your Address Manager, AWS, Azure, or GCP credentials in HashiCorp Vault, you must first store HashiCorp Vault authentication credentials in Secrets Manager.

Changes to service point diagnostics response

As part of the changes introduced in DNS resolver service for the improved DNS resolution performance, the GET http://<spv4_ip_address>:2021/v2/diagnostics API response has been updated to include additional information about memory allocation based on container services.