Microsoft Azure has Public DNS in beta at this time, and this service will facilitate the IT Pro a lot where besides of the regular infrastructure (IaaS, SaaS) the administrator can use the same authentication method to manage Public DNS which nowadays is done through a third partner, or in some cases with servers in the on-premises DMZ.
Microsoft Azure DNS at this time is managed through PowerShell, the first step is to create a Resource Group and that can be done using either PowerShell or Azure Portal. For this Tutorial we are going to create a new Resource Group to host all DNS zones and it is going to be called RG-DNS and this was the cmdlet used to create it.
New-AzureRMResourceGroup –Name RG-DNS –Location “East US”
The second step is to create the DNS Zone, and the process is straight forward, here are the cmdlets used to create the zone Infralab.org
$NewZone = New-AzureRMDNSZone –Name Infralab.org –ResourceGroupName RG-DNS
Get-AzureRMDNSZone –ResourceGroupName RG-DNS | fl
Until this point the zone was created in Microsoft Azure however the Internet is not aware of its existence. The next step is take a note of the Name Servers in Microsoft Azure that are responsible for this new zone, and we can do that using the following cmdlet:
Get-AzureRMDNSRecordSet –ZoneName infralab.org –ResourceGroupName RG-DNS –RecordType NS
The final piece of the puzzle is to change the current Name Servers of the zone to the ones that we took a note in the previous step. After doing that and the DNS replication takes place, all new DNS queries will be going to Microsoft Azure.
These are the basic steps to create a zone and transfer it over to Azure DNS, keep in mind that before performing the transition, the recommendation for production zoens is to make sure that all entries are already there prior to the transition.