Import BIND zones to Azure DNS

One of my customers was using BIND to handle their public facing DNS. In a effort to remove technical debt, minimize their infrastructure footprint, and to make it easier for staff, I was tasked to look for a cloud alternative to BIND

Introducing Azure DNS #

Azure has a DNS hosting solution that has recently been slapped with a 100% SLA. Given this SLA and the fact that it’s dirt cheap, there’s no reason why you shouldn’t be using Azure DNS!

Importing the BIND Zones #

Now on to the task at hand, getting the zones imported into Azure DNS. Using Azure CLI, we can very easily import the zone files directly to Azure!

 az network dns zone import --resource-group ResourceGroupName --name NameOfZone.com --file-name C:\Path\to\your\db.domain.com

Once you kick that off, you should start seeing it importing each record:
BindImport.png

Shout out to Microsoft for making it straight forward. The only quirk I’ve ran across was on one of the zones I was importing, the last character on each record got cut off? For example, an A record of example.domain.com imported as example.domain.co

wut

 
0
Kudos
 
0
Kudos

Now read this

Search Exchange Online for a missing calendar

“Someone deleted our shared calendar!” # Welp, here I go.. Once in a blue moon, we would get a panicked email about an important shared calendar mysteriously going MIA. What would end up happening is during some cleanup, an end user... Continue →