Working with Azure DNS

And, Azure now has a DNS service. Why would anyone use a new service where there are so many already? DNS providers are abundant, some good, some very bad.

It makes sense, when a company provisions its resources in Azure and specially if they’re using automation in its multiple forms, JSON, powershell, Azure CLI (On the Mac) to create, if required the DNS entries and update automatically.

For the time being, Azure DNS is an internet facing DNS hosting service only. I confirmed this with the product team, reference here.

What this means is, when you need a DNS for resources that are in a Virtual Network with no internet access whatsoever, this will not be useful, in that case a VM with a DNS will do the work.

So, I went and I in order to test the service, I set it up, using Powershell, you obviously have to log-in and select the right subscription.

  1. Create the Resource Group for the DNS service:



2.  Register the Network provider, this is a one time only operation


3. Create your actual DNS Zone, Domain Name for this exercise is (Think Cocodrilo goes to the Moon)

Command is:  New-AzureRmDnsZone -Name -ResourceGroupName DNSAuEaResourceGroup -Tag @( @{ Name=”project”; Value=”blogpost” }, @{ Name=”env”; Value=”test” } ) 

This commands adds the tags for the sake of easy management, they’re not mandatory but useful:



4. Verify your zone was correctly created


5. Add your new nameservers to your name registrar, GoDaddy is mine for this domain. I only added two, you can add more depending on your provider.



6. Verify the update is successful using a service like MXToolbox:


Now, all requests that come for this domain will be solved by the Azure DNS. BTW, SOA means Start of Authority 

Once done it will look like this:


Here you can add records and manage the DNS graphically, all convenient.

See you next post