Try Azure: Not on a fast sports car, not across cloud Service

From Aliyun's pit master to Azure's smear guru, we seem to be typical of the negative users of cloud computing, but we can't help but want to express our true sense of use. If there is a wrong place, you are welcome to criticize!

After building the virtual network (vitual network) on Azure (see Cloud Computing Road-Try Azure: How to build intranet connection between virtual machines), the virtual machine (fictitious Machine) needs to communicate with intranet. The use of computer names in communication is more user-friendly, more convenient and more responsive to change than using intranet IP directly.

When using Aliyun, we can only add the mapping between the compute name and IP in the hosts of each virtual machine, but if the IP of a certain virtual machine changes, it is necessary to modify the Hosts file in all the virtual machines with which it communicates.

If you've been a network administrator and you've built a LAN with Windows, you know that Microsoft already has a solution to this problem--when DHCP, dynamically add the computer name and IP address mappings to the DNS server.

In Azure, we are pleasantly surprised to find that the virtual network also has this function, for example, the blogserver1 of this virtual machine in the following image of the network interface information.

Both the IP address and the DNS server are assigned by DHCP.

Then we look at the network interface information of another virtual machine blogserver2 in the same cloud service.

As you can see, you are using the same DNS server. Then we ping the blogserver2 directly in the Blogserver1:

See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/Servers/cloud-computing/