Is there any documentation referencing what exactly is expected by azure DNS zone import ?

Lucas Bouvy 0

I'm trying to import a DNS zone into azure and it just keeps failing.

It doesn't want trailing dots in the zone file, it doesn't want the domain to reference itself, it splits one big txt record in several and then errors because you can't have multiple txt record for the same hostname.

I'm exporting from Google Domains, not a small provider, how comes the BIND format is not accepted by azure dns ?

I'm just looking for resources to solve that, in the meanwhile I just did the import job myself starting with an empty zone since editing in the portal is horrendous.

ChaitanyaNaykodi-MSFT 26,216 Reputation points Microsoft Employee

2024-06-03T16:48:46.3433333+00:00
@Lucas Bouvy Thank you for reaching out.

I understand you are facing issue while importing the DNS zone file on Azure DNS.

The consideration required to import a DNS zone file in Azure are currently documented here

and I think you might have faced the issue above because of the limitation mentioned below

Azure DNS supports only single-string TXT records. Multistring TXT records are to be concatenated and truncated to 255 characters.

If the above considerations mentioned in the document above does not reflect your observation, then can you please share an example? as it will help us further troubleshoot the issue.

If it helps you can try the Az CLI method to import a DNS zone file as the command reports the progress in the console window along with any errors or warnings. You can use Azure Cloud Shell to run the commands.

Thank you!
Lucas Bouvy 0 Reputation points

2024-06-04T10:00:49.56+00:00
Thanks for your reply, unfortunately this doc doesn't indicate the expected format.

After playing around with the import here's what I had to change :

remove all trailing dots from the A records

replace all self references with @

merge TXT records with same host into a single multiline record

For me the easiest way to achieve my zone creation was to only import A records (after removing trailing dots) with the zone import, then create the rest of records through CLI instead of trying to play with the zone file to import them

I'm still surprised that importing a BIND file form a provider like Google fails 100% on azure dns
ChaitanyaNaykodi-MSFT 26,216 Reputation points Microsoft Employee

2024-06-13T23:02:20.0133333+00:00

@Lucas Bouvy

Thank you for getting back and apologies for the delay.

I am sharing your observation above with the team and will request them to update the documentation if required. Thank you!

Share via

Is there any documentation referencing what exactly is expected by azure DNS zone import ?

Your answer