Azure Public DNS text file import

Hi Andy,

It handles that automatically. When it creates new zone it will create the SOA with Azure DNS servers instead of SOA in the import file. If it is existing zone and you import it will give you an error saying it partially failed because it cannot modify the existing SOA record or similar.

Below is excerpt from documentation:

The following notes provide more details about the zone import process.

• The $TTL directive is optional, and is supported. When no $TTL directive is given, records without an explicit TTL are imported set to a default TTL of 3600 seconds. When two records in the same record set specify different TTLs, the lower value is used.
• The $ORIGIN directive is optional, and is supported. When no $ORIGIN is set, the default value used is the zone name as specified on the command line, including the ending dot (.).
• The $INCLUDE and $GENERATE directives aren't supported.
• The following record types are supported: A, AAAA, CAA, CNAME, MX, NS, SOA, SRV, and TXT.
• The SOA record is created automatically by Azure DNS when a zone is created. When you import a zone file, all SOA parameters are taken from the zone file except the host parameter. This parameter uses the value provided by Azure DNS because it needs to refer to the primary name server provided by Azure DNS.
• The name server record set at the zone apex is also created automatically by Azure DNS when the zone is created. Only the TTL of this record set is imported. These records contain the name server names provided by Azure DNS. The record data isn't overwritten by the values contained in the imported zone file.
• Azure DNS supports only single-string TXT records. Multistring TXT records are to be concatenated and truncated to 255 characters.
• The zone file to be imported must contain 10k or fewer lines with no more than 3k record sets.

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP