You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/sql-database/sql-database-managed-instance-custom-dns.md
+6-45Lines changed: 6 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,58 +14,19 @@ ms.reviewer: bonova, carlrab
14
14
15
15
# Configuring a Custom DNS for Azure SQL Database Managed Instance
16
16
17
-
An Azure SQL Database Managed Instance (preview) must be deployed within an Azure [virtual network (VNet)](../virtual-network/virtual-networks-overview.md). There are a few scenarios, 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, the virtual network DNS configuration needs to be compatible with Managed Instance.
17
+
An Azure SQL Database Managed Instance (preview) must be deployed within an Azure [virtual network (VNet)](../virtual-network/virtual-networks-overview.md). There are a few scenarios (i.e. 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, the virtual network DNS configuration needs to be compatible with Managed Instance.
18
18
19
-
To make a custom DNS configuration compatible with Managed Instance, you need to complete the following steps:
20
-
- Configure Custom DNS to forward requests to Azure DNS
21
-
- Set up the Custom DNS as primary and Azure DNS as secondary for the VNet
22
-
- Register the Custom DNS as primary and Azure DNS as secondary
23
-
24
-
## Configure Custom DNS to forward requests to Azure DNS
25
-
26
-
To configure DNS forwarding on Windows Server 2016, use these steps:
27
-
28
-
1. In **Server Manager**, click **Tools**, and then click **DNS**.
4. Enter Azure's recursive resolvers IP address, such as 168.63.129.16.
41
-
42
-

19
+
To make a custom DNS configuration is compatible with the Managed Instance, you need to:
20
+
- Configure custom DNS server so it is able to resolve public domain names
21
+
- Put Azure Recursive Resolver DNS IP address 168.63.129.16 at the end of the virtual network DNS list
43
22
44
-
## Set up Custom DNS as primary and Azure DNS as secondary
45
-
46
-
DNS configuration on an Azure VNet requires that you enter IP addresses, so configure the Azure VM that hosts the DNS server with a static IP address using the following next steps:
47
-
48
-
1. In the Azure portal, open the custom DNS VM network interface.
0 commit comments