Skip to content

Commit 05b0cd8

Browse files
authored
Update application-gateway-dns-resolution.md
1 parent df62f65 commit 05b0cd8

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

articles/application-gateway/application-gateway-dns-resolution.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ Application Gateway performs DNS resolution for the Fully Qualified Domain Names
2424
2) **Management FQDNs** that are utilized for various Azure infrastructure endpoints (control plane). These are the building blocks that form a complete Application Gateway resource. For example, communication with monitoring endpoints enable flow of Logs and Metrics. Thus, it is important for application gateways to internally communicate with other Azure services' endpoints having suffixes like `.windows.net`, `.azure.net`, etc.
2525

2626
> [!IMPORTANT]
27-
> The management endpoint domain names that an Application Gateway resource interacts with are listed here. Depending on the type of application gateway deployment (detailed in this article), any name resolution issue for FQDNs with domain names may lead to either partial or complete loss of resource functionality.
27+
> The management endpoint domain names that an Application Gateway resource interacts with are listed here. Depending on the type of application gateway deployment (detailed in this article), any name resolution issue for these Azure domain names may lead to either partial or complete loss of resource functionality.
2828
>
2929
> * .windows.net
3030
> * .chinacloudapi.cn
@@ -47,23 +47,24 @@ The Azure-provided DNS comes as a default setting with all virtual networks in A
4747

4848
:::image source="media/application-gateway-dns-resolution/default-dns.png" alt-text="A diagram showing DNS resolution for Azure-provided DNS.":::
4949

50-
**Flow**
51-
52-
In this diagram, we can see,
53-
* The Application Gateway instance talks to Azure-provided DNS (168.63.129.16) for name resolution of the backend servers FQDN "server1.contoso.com" and "server2.contoso.com", as shown with blue line.
50+
Flows:
51+
* In this diagram, we can see the Application Gateway instance talks to Azure-provided DNS (168.63.129.16) for name resolution of the backend servers FQDN "server1.contoso.com" and "server2.contoso.com", as shown with blue line.
5452
* Similarly, the instance reaches out 168.63.129.16 for the name resolution of private link-enabled Key Vault resource, as shown in orange line. To allow an application gateway to DNS resolve the key vault endpoint to its private IP, it is important to link the Private DNS zone to that application gateway’s virtual network.
5553
* After performing successful DNS resolutions for these FQDNs, the instance can communicate with the Key Vault and backend server endpoints.
5654

57-
**Considerations**
58-
55+
Considerations:
5956
* Do not create and link private DNS zones for top-level Azure domain names. You must create DNS zone for a subdomain as specific as possible. For example, having a private DNS zone for `privatelink.vaultcore.azure.net` for a key vault’s private endpoint works in all cases than having a zone for `vaultcore.azure.net` or `azure.net`.
6057
* For communication with backend servers or any service using a Private Endpoint, ensure the private link DNS zone is linked to your application gateway’s virtual network.
6158

59+
#### Using custom DNS servers
6260

61+
In your virtual network, it is possible to designate custom DNS servers. This configuration may be required for managing zones independently for specific domain names. Such an arrangement directs the application gateway instances within the virtual network also to utilize the specified custom DNS servers for resolving non-Azure domain names.
6362

63+
:::image source="media/application-gateway-dns-resolution/custom-dns.png" alt-text="A diagram showing DNS resolution with custom DNS servers.":::
6464

65-
66-
65+
Flows:
66+
* The diagram shows that the Application Gateway instance uses Azure-provided DNS (168.63.129.16) for name resolution of the private link Key Vault endpoint "contoso.privatelink.vaultcore.azure.net". The DNS queries for Azure domain names, which includes `azure.net`, are redirected to Azure-provided DNS. Shown in orange line.
67+
* For DNS resolution of "server1.contoso.com", the instance honors the custom DNS setup, as shown in blue line.
6768

6869

6970

0 commit comments

Comments
 (0)