2012年4月8日 上午 07:12
We need our Azure role machines to have access to the entries in the DNS server running on the on premises AD machine. Considering that they're connected using Azure Connect, can I manually set the DNS server in the IPv6 properties window? Are there any negative consequences? If so, is there a way to add this on-premises DNS as a static default DNS some other way?
Thanks in advance,
2012年4月9日 上午 06:02
I don't think there are any negative consequences for setting IPv6 in DNS server. If there would have been any negative points why Azure connect would have been using IPv6. So setting IPv6 should not be a problem.
Hope it helps.
Mark As Answer if it helps you | My Blog
2012年4月9日 下午 05:30I've actually followed that tutorial but it doesn't say anything about using the domain DNS server. I've also tried changing the DNS server in the IPv6 configuration but there's something running on the Azure machine which reset the configuration back to automatic.
2012年4月11日 上午 08:40版主
I haven't tried this scenario before. But one potential issue of this approach is the Windows Azure instance may be unable to communicate with the Windows Azure infrastructure, as your on-premises DNS server is unlikely to know any servers inside the Windows Azure data center. This may in turn cause issues to your hosted services. You can give it a try, but it is not recommended. The Azure DNS server must be able to find any machine on the internet, if you need to access your intranet machine, I would like to suggest you to add that machine to Connect.
- 已標示為解答 Arwind - MSFTModerator 2012年4月16日 上午 08:35