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 --file-name C:\Path\to\your\

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

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 imported as



Now read this

BECS - An Office 365 Incident Response Tool

Gosh golly, another blog post?! # I seem to have found myself doing a lot of incident response (IR) engagements here lately. I mean, I’m not complaining; it’s bittersweet in that I have a lot of fun during these engagements, but also sad... Continue →