Configuring a Custom DNS for Azure SQL Database Managed Instance

An Azure SQL Database Managed Instance must be deployed within an Azure virtual network (VNet). There are a few scenarios (for example, db mail, linked servers to other SQL instances in your cloud or hybrid environment) that require private host names to be resolved from the Managed Instance. In this case, you need to configure a custom DNS inside Azure.

Since Managed Instance uses the same DNS for its inner workings, you need to configure the custom DNS server so that it can resolve public domain names.


Always use fully-qualified domain names (FQDN) for the mail servers, SQL Servers, and other services even if they are within your private DNS zone. For example use for mail server because simple smtp will not be properly resolved.


Updating virtual network DNS servers would not affect Managed Instance immediately. Managed Instance DNS configuration will be updated after DHCP lease expires or after the platform upgarade, whatever comes first. Users are advised to set their virtual network DNS configuration before creating their first Managed Instance.

Next steps