The following section outlines changes that have been made between discovery instance service versions:
1.2.0
- Support for new AWS record types
Discovery instance has been updated to support new resource record types introduced by AWS. Discovery instance v1.2.0 now supports SSHFP, CAA, HTTPS, TLSA, SVCB, HINFO, and URI record types.
- Resolves an issue where previously, if the Discovery Instance is performing discovery in an Azure tenant with multiple subscriptions and one subscription has a State that is not Enabled or Past Due, the Discovery Instance would abandon discovery for all subscriptions in that tenant.
- Resolves an issue where previously, when the Discovery Instance performed discovery in large environments, the Discovery Instance would hit the memory limit and abandon discovery. This issue has now been resolved and the Discovery Instance scales resource allocations based on the resources of the host machine.
- Resolves an issue where previously, when the Discovery Instance created entries in a snapshot for each VPC that records were discovered in, the discovered zone count that appeared in the UI would contain multiple times more entries than what was discovered.
- Resolves an issue where previously, the Discovery Instance could not update the discovered domain list in BlueCat Edge due to special characters, resulting in additional issues where discovered namespaces took longer to receive the updated discovered zones.
1.1.0
- Discover DNS infrastructure in AWS, Azure, and GCP environments
Discovery instance has been updated to support DNS data discovery cloud environments. 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.
- Support for credential recovery from HashiCorp Vault
This release 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.
1.0.1
- Resolves an issue where the Discovery Instance would retrieve information from Address Manager and when it encountered a DNS server configured with the type "Other DNS Server", the Discovery Instance would not retrieve any information, as the service IP address fields are empty.
1.0.0
- Initial introduction of Discovery Instance services.