Prerequisites
In order to use a Cloudera-managed private DNS, you should meet the following prerequisites.
Review DNS zones existing in your resource group
If you would like Cloudera to create and manage the Private DNS Zone, review the DNS
zones that exist in the resource group that you are planning to use for Cloudera and make sure
that one of the following is true:
- No Private DNS Zone named
privatelink.postgres.database.azure.comorflexible.postgres.database.azure.com(for Flexible Server with Private Link or Flexible Server with delegated subnet respectively) is connected to the VNnet. - If there is a Private DNS Zone named
privatelink.postgres.database.azure.comorflexible.postgres.database.azure.com(for Flexible Server with Private Link or Flexible Server with delegated subnet respectively) connected to the VNet, verify that the zone is located in the existing resource group that you are planning to use for Cloudera. If the Private DNS Zone is already used for one environment, Cloudera can reuse it for another environment.
Ensure that Cloudera has adequate permissions
Ensure that the role that you are using for the Azure credential has the permissions mentioned in Role definition 2: Allows Cloudera to use only a single existing resource group create private endpoints.
