You will get a validation warning that your server should have a static IP address, but recall that our DHCP lease is effectively the same thing, so we can disregard. In the left pane of the Server Manger, select the DNS section.If it doesn't show up, click in the pane and hit F5 to refresh.In the case of Azure, the servers must use DHCP, but the lease they receive lasts for the life of the machine, as long as you don't shut down the machine through the management console, which will deallocate the VM.Shutting down the machine through Windows itself, however, will preserve the lease.Set the DNS server by typing "server 127.0.0.1", which tells the session to use the local server (same machine that we're on). Confirm that the IP address returned matches what you entered for the DNS record.This would also be a good time to test a public address such as to ensure that addresses that the DNS server cannot resolve are passed to the upstream DNS server (this should work by default).Many of these scenarios require a more flexible local DNS server than what is provided by default in Azure.For example, programmatically building a dynamic cluster of VM's.
A forward lookup zone.aspx) is a map of names and IP addresses, and is used to look up the IP address for one of those particular names.
Think of it as a simple associative array that maps names to IP's.
Right-click and choose you can use your DNS server to resolve *net addresses.
With the recent GA release and rapidly growing usage of virtual machines within Windows Azure, many are trying to set up an independent/non-VPN network.
The great part of Azure virtual machines is that it can be as flexible as a set of PCs or VMs hosted within your own datacenter.