I am trying to setup an Azure VM with proper DNS to allow multiple cloud services to communicate across cloud service boundaries.
As I understand it, I need to provide my own DNS server. I do not have any on-premise infrastructure, so I am trying to configure an Azure VM to act as my DNS.
This SO question - Azure: How to connect one cloud service with other in one virtual network - is very similar to my setup.
The Name Resolution (DNS) from MSDN describes my particular case:
Name resolution between virtual machines and role instances located in the same virtual network, but different cloud services
Here is what I have done:
- Created Azure Virtual Network and declared subnets for each of my cloud services.
- Created an Azure VM (Windows 2012 R2) with DNS enabled
- RDP to the VM and enabled the DNS role and installed features
- Added the appropriate NetworkConfiguration xml section to each of my cloud services .csfg files
- Re-deployed my cloud services
I have verified that I setup the virtual network and networkconfiguration properly because my cloud service hosts are able to communicate with each other if I use the internal ips. However, name resolution doesn't appear to be working, and it doesn't appear that my cloud service roles can communicate with my DNS server.
How do I configure my VM so that my different cloud services roles register themselves with my DNS server?
I think I am 1 step closer to getting this to work. The cloud services that I was using are in an old affinity group which is not supported by VMs, so I was unable to add my VM into my virtual network. I created a new VNET in a new affinity group with my VM added into it. However, I still don't know how to configure the Azure VM's DNS server so that the cloud services register themselves for name resolution. Also, an added bonus guaranteed to get a +1 would be to explain if it is possible to register a DNS entry for the VIP for an internal endpoint of my cloud services so we can get load balancing.