Microsoft Azure Virtual Networks | Part 3


Name Resolution DNSdns
Domain Name System which allows you to communicate with your VMs using the Host Name NOT the IP address.

Azure by default has his own dns if your network is running on it with no integration with the on-premises, it’s gonna work GREAT, but what about the network integration?
this is the most scenario case in business environment, VMs in azure and other VMs in the local servers…. in this case you have to let Azure access your on-premises DNS, so let’s configure this…

Bring your Own DNS
From NEW > NETWORKS > VIRTUAL NETWORK > REGISTER DNS SERVER > Provide NAME and real IP ADDRESS.

DNS


Traffic Manager
If you have multi cloud services in the same virtual network, how can you control the performance and user traffic of each one?VNet
So traffic manager is the process of control the distribution of user traffic to your cloud services
The cloud services is the container of the virtual machines
Load Balancing on the cloud services
There are multi balancing methods ” Algorithms

  1. Failover: work as ON/OFF key if one cloud services failed to run or start the load goes on the other one and so..
  2. Performance: choose the nearest cloud services region for your tasks and run them on it.
  3. Round Robin: Running the work load on cloud service 1 >> cloud services 2 >> cloud services 3… cloud services 1 …etc.Traffic-Manager
Advertisements

One thought on “Microsoft Azure Virtual Networks | Part 3

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s