Updating reverse lookup zones

You may have noticed that it is also possible to define DNS servers from the standard New/Create feature in Azure.

The DNS server will work fine across any subnets within your network.

Typically, a DNS server should be configured with a static IP address.

Access the Advanced TCP/IP Settings (Network and Sharing Center-DNS Tab) and set your DNS suffix as shown in the screenshot below. It also ensures that if one machine becomes deallocated, your servers will failover and give you time to update the DNS settings for the newly assigned IP address of the re-built replacement server.

You should always configure at least 2 DNS servers and configure Azure to use both. In a typical on-premise DNS installation, the records are kept up-to-date by the DHCP server.

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.I have not found any particular reason to create entries this way.If you want to use short DNS names (eg: "test") instead of fully qualified names (eg: "net"), you'll need to update the DNS suffix of your virtual machine.:-) Create your virtual machine to host the DNS just like you would create any server.I highly recommend choosing Windows Server 2012 or above. When you first remote into the server, you'll be presented with the .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.

Tags: , ,