如何在应用程序网关上使用内部linux fqdn? [英] How to use an internal linux fqdn on an Application Gateway?

查看:96
本文介绍了如何在应用程序网关上使用内部linux fqdn?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在同一Vnet上创建了应用程序网关(AG)和linux VM(没有自定义DNS服务器).

nslookup .

如何在应用程序网关上使用内部linux fqdn?如果可能的话...

解决方案

我不认为这是直接可能的.您可以将FQDN用作后端池,但必须可以从公共Internet上解析它. 

如果内部Linux应用程序在多台服务器上运行,则可以将它们放在内部负载均衡器的后面,并将该负载均衡器的内部IP地址设置为后端池. 


Hello,

I have created an application gateway (AG) and a linux VM on the same Vnet (without custom DNS server).

I try now to configure the AG with a backend pool that targets the VM using the FQDN of this VM (and not the IP nor the NIC). I get the FQDN using the command nslookup "$(hostname)".

The AG does not manage to resolve the VM FQDN. The Connection troubleshoot of the AG failed at the DNS resolution. Every VMs in the same Vnet succeed in resolving this FQDN but not the AG...

How to use an internal linux fqdn on an Application Gateway? If it is possible...

Thank you.

解决方案

I do not believe that this is directly possible. you can use a FQDN for a backend pool, but it must be resolvable from the public internet. 

If your internal Linux application is run on multiple servers, you can put them behind an Internal Load Balancer, and set the Internal IP Address of that load balancer as your backend pool. 


这篇关于如何在应用程序网关上使用内部linux fqdn?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆