本文介绍了webapp的内部解析无法正常工作;但使用8.8.8.8(google DNS)的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

你好;主题说了这一切:-)

Hi there ; subject says it all :-)

有人知道为什么会这样吗?

Anybody knows why this is happening? 

我们可以解决指定WEBSITE_DNS_SERVER的问题;但想知道为什么内部DNS可以正常运行,但只能部分运行.

We can work around specifying WEBSITE_DNS_SERVER ; but wondering why internal DNS is working, but partially.

例如www.google.com的解析工作...

www.google.com resolving works for instance...

谢谢!

蒂姆

nameresolver token.dpwqa.dieteren.be 8.8.8.8
D:\home\site\wwwroot
Server: 8.8.8.8

Non-authoritative answer:
Name: token.dpwqa.dieteren.be
Addresses: 
	193.53.xxx.xxx
> nameresolver token.dpwqa.dieteren.be 
D:\home\site\wwwroot
Server: Default

*** Can't find token.dpwqa.dieteren.be: Non-existent domain

推荐答案

1.您的应用程序是否启用了VNET集成?如果是这样,它应该从VNET集成中提取DNS.如果您在完成集成后添加了DNS,则可能需要重新启动应用或重新同步网络 通过应用服务计划->联网刀片. ***这将暂时降低该应用程序服务计划中使用VNET集成的任何应用程序的连通性***.

1. Do you have VNET integration enabled with your app? If so it should pickup your DNS from the VNET integration. If you added the DNS after completing the integration you may need to restart your app or resync the network via the App Service Plan -> Networking blade. ***This will temporarily bring down the connectivity of any app in that app service plan that is using the VNET integration***. 

2.如果在App Service环境中,它还应该自动从VNET中拾取DNS服务器.与上面类似,如果在创建ASE之后添加了DNS服务器,则需要重新启动ASE.这可能需要45分钟 完成.

2. If this in side of an App Service Environment it should also automatically pick up the DNS servers from the VNET as well. Similar to above, if you added the DNS servers after creating the ASE you need to restart the ASE. This may take up to 45 minutes to complete.


这篇关于webapp的内部解析无法正常工作;但使用8.8.8.8(google DNS)的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

10-28 00:04