Azure DNS IP 168.63.129.16向下？ [英] Azure DNS IP 168.63.129.16 Down?

问题描述

您好。我们的DNS服务器无法再解析Azure DNS IP 168.63.129.16（我们已将其添加为主条件转发器）。

我们已经使用Ingress在Kubernetes中设置了几个应用程序，并创建了附加到这些应用程序的Azure公共IP地址。我创建了指向这些公共IP的DNS A记录。在网络上，一切正常。但是没有外部
可以通过子域名访问我们的应用程序。

我无法从外部ping我们的子域名，所以它让我觉得这是一个DNS问题。我发现条件转发器（168.63.129.16）无法解析，所以我想我会在这里查看这是否是潜在的问题。

解决方案

您好，

这看起来更像是您的内部DNS无法在外部工作。当您获得一个Azure Pulic IP并直接在浏览器上输入而没有dns别名时，您是否能够访问该应用程序？

您是否能够验证子域是否可公开路由？

如果你去这个dns检查站点，输入你的子域名，它是否正在解析以及是什么IP

https：//www.whatsmydns达网络/

Hi. Our DNS Server can no longer resolve the Azure DNS IP 168.63.129.16 (We've added it as the primary conditional forwarder).

We've setup several apps in Kubernetes with Ingress and have created Azure public IP addresses that are attached to these apps. I have created DNS A Records pointing to these public IPs. Interally on the network, everything works fine. But nobody external can get to our apps via the subdomain.

I can't ping our subdomain from outside, so it makes me think it's a DNS issue. I found that the conditional forwarder (168.63.129.16) was unable to be resolved so I thought I'd check here to see if this is the underlying problem or not.

解决方案

Hello,

This seems more like your internal DNS not working externally. When you get one these Azure Pulic IP and enter it on a browser directly with no dns alias, are you able to access the application?

Are you able to validate that the subdomain is publicly routable?

If you go to this dns checker site, enter your subdomain, is it resolving and to what IP

https://www.whatsmydns.net/

这篇关于Azure DNS IP 168.63.129.16向下？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！