OracleDB for Azure Autonomous Database with Private Endpoint FQDN Doesn't Resolve When Networking Configuration Doesn't Use Azure DNS

Learn how the DNS configuration of an Azure VNET or subnet affects the ability of an Autonomous Database FQDN to resolve.

If the Azure Account used for Oracle Database Service for Azure uses non-Azure DNS in the peered VNET or the subnet of an Autonomous Database with a private endpoint connection, the Autonomous Database fully qualified domain name (FQDN) might not successfully resolve. We recommend using Azure DNS in the peered VNET or the subnet used by Autonomous Database private endpoints to ensure that the FQDN resolves and the network traffic remains within the private interconnect that links the Oracle and Azure cloud data centers.