Skip to content

Commit 6f01abf

Browse files
authored
Merge pull request #49982 from srdan-bozovic-msft/sql-mi-dns-configuration
sql mi dns configuration update
2 parents a13db1b + 11526da commit 6f01abf

File tree

1 file changed

+6
-45
lines changed

1 file changed

+6
-45
lines changed

articles/sql-database/sql-database-managed-instance-custom-dns.md

Lines changed: 6 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -14,58 +14,19 @@ ms.reviewer: bonova, carlrab
1414

1515
# Configuring a Custom DNS for Azure SQL Database Managed Instance
1616

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.
1818

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**.
29-
30-
![DNS](./media/sql-database-managed-instance-custom-dns/dns.png)
31-
32-
2. Double-click **Forwarders**.
33-
34-
![Forwarders](./media/sql-database-managed-instance-custom-dns/forwarders.png)
35-
36-
3. Click **Edit**.
37-
38-
![Forwarders-list](./media/sql-database-managed-instance-custom-dns/forwarders-list.png)
39-
40-
4. Enter Azure's recursive resolvers IP address, such as 168.63.129.16.
41-
42-
![Recursive resolvers ip address](./media/sql-database-managed-instance-custom-dns/recursive-resolvers-ip-address.png)
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
4322

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.
49-
50-
![network-interface](./media/sql-database-managed-instance-custom-dns/network-interface.png)
51-
52-
2. In IP Configurations section. select IP configuration
53-
54-
![ip configuration](./media/sql-database-managed-instance-custom-dns/ip-configuration.png)
55-
56-
57-
3. Set private IP address as Static. Write down the IP address (10.0.1.5 on this screenshot)
58-
59-
![static](./media/sql-database-managed-instance-custom-dns/static.png)
60-
61-
62-
## Register Custom DNS as primary and Azure DNS as secondary
23+
## Setting up custom DNS servers configuration
6324

6425
1. In the Azure portal, find custom DNS option for your VNet.
6526

6627
![custom dns option](./media/sql-database-managed-instance-custom-dns/custom-dns-option.png)
6728

68-
2. Switch to Custom and enter your custom DNS server IP address as well as Azure's recursive resolvers IP address, such as 168.63.129.16.
29+
2. Switch to Custom and enter your custom DNS server IP address as well as Azure's recursive resolvers IP address 168.63.129.16.
6930

7031
![custom dns option](./media/sql-database-managed-instance-custom-dns/custom-dns-server-ip-address.png)
7132

0 commit comments

Comments
 (0)