Skip to content

Commit 26ab8ba

Browse files
authored
Update application-gateway-faq.yml
1 parent 839f797 commit 26ab8ba

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/application-gateway/application-gateway-faq.yml

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -186,7 +186,10 @@ sections:
186186
- question: Can Application Gateway communicate with instances outside of its virtual network or outside of its subscription?
187187
answer: |
188188
As long as you have IP connectivity, Application Gateway can communicate with instances outside of the virtual network that it's in. Application Gateway can also communicate with instances outside of the subscription it's in. If you plan to use internal IPs as backend pool members, use [virtual network peering](../virtual-network/virtual-network-peering-overview.md) or [Azure VPN Gateway](../vpn-gateway/vpn-gateway-about-vpngateways.md).
189-
189+
190+
- question: Why am I seeing 502 errors or unhealthy backend servers after I changed the DNS servers for the virtual network?
191+
answer: The instances of your application gateway use the virtual network's DNS configuration for name resolution. After changing any DNS server configuration, you need to restart (Stop and Start) the application gateway for the new DNS servers to get assigned. Until then, FQDN-based name resolutions for outbound connectivity could fail.
192+
190193
- question: Can I deploy anything else in the application gateway subnet?
191194
answer: No. But you can deploy other application gateways in the subnet.
192195

0 commit comments

Comments
 (0)