Reputation: 35873
I am a bit confused about the Azure Cloud Service, and what's its use. I mean what is the concept, at least in the use case if one would like to run only VMs and not interested in "Web Sites" (newly: "Wep Apps")
First I thought it is for reserving IP and domain name (I mean myservice.cloudapp.net). (Then I discovered it is not even capable to reserve a static fixed public IP between VM shutdowns/starts, unless you do PowerShell homework)
But the most confusing thing for me: it seems that is possible to deploy multiple Azure VMs to one single Cloud Service. However the Cloud Servie is what have public IP and domain name, then how it is possible to have multiple VMs on the same IP?
Upvotes: 0
Views: 54
Reputation: 947
Virtual machines deployed into the same cloud service will have name resolution by default. This is possible because Azure provides a multi-tenant DNS server for your virtual machines. The Azure DNS server does not support the advanced records needed for workloads like Active Directory. In those workloads, deploying your own DNS server is a requirement.
To access virtual machines inside of the cloud service externally, you create an endpoint. An endpoint can refer to a single virtual machine, or it can be configured as part of a load balanced set. To access an individual virtual machine, you create an endpoint with an unused public port that forwards traffic to the private port on the virtual machine itself.
Virtual machines are exposing port 3389 (Remote Desktop) to the outside world through separate endpoints. To access the virtual machines individually through the single IP address of the cloud service (the VIP), an unused public port must be used for each virtual machine endpoint (6510 and 6511 in this case) that is configured to forward to the internal port 3389 on each virtual machine.
Upvotes: 1