Announcing Preview Refresh for Azure DNS Private Zones
Published date: June 26, 2019
We are delighted to announce Refresh release for Azure DNS private zones (preview). Azure DNS private zones (preview) provides secure and reliable name resolution for your virtual networks in Azure. The Preview Refresh introduces new functionality and lifts several restrictions that public preview had.
What’s New in Preview Refresh?
New Resource Model and API
Preview Refresh introduces a new resource model (REST API) for Azure DNS private zones. The resource model introduces the following changes:
- Azure DNS private zones will now be an independent top-level ARM resource called privateDnsZones instead of being a "type" of existing public dnszones resource.
- The privateDnsZones resource will not have registrationVirtualNetwork and resolutionVirtualNetwork virtual network properties. Virtual networks will be linked to a privateDnsZones by creating a virtualNetworkLinks sub-resource under the privateDnsZones resource.
- To enable auto registration of DNS records for virtual machines simply set the registrationEnabled flag on the properties of virtualNetworkLinks resource as true.
- We have also shipped new CLI/PS and SDKs for privateDnsZones.
Click here for updated guidance on how to use new CLI and PowerShell to create private DNS zones and link these to your virtual networks.
New Portal Experience
A new portal experience for Azure DNS private zones will enable you to manage the private DNS zones and their linked virtual networks from the Azure Portal. You'll also be able to view the auto-registered resource records for the virtual machines under the private DNS zone. Click here to get started with creating private DNS zones through Azure portal.
Note that your existing private DNS zones will not show in this experience unless they are migrated to the new resource model (See below). You can, however, create new private DNS zones and link these to virtual networks.
Public Preview had several limitations including limits on the number of virtual networks that can be linked to a DNS zone. These limits have been substantially enhanced. Click here to see new limits.
Following Restrictions have been Removed
- You will be able to link existing non-empty virtual networks to your private DNS zones. The restriction for the vnet to be empty will no longer apply.
- You will be able to link more than one virtual network as registration virtual networks to a private DNS zone.
- You will be able to create subdomains and link these to the same virtual networks. For example, If you have created a private DNS zone called contoso.com and linked it to a virtual network, you will be able to create subdomain.contoso.com and link it to the same virtual network.
Migrating existing zones to new resource model
Private DNS zones that you have already created will continue to work. However, you will not get the benefits of enhanced limits or new functionality with these zones. These zones will continue to be listed along with public DNS zones in the Azure portal and will not show up under the new private DNS zones experience. We strongly recommend that you migrate your existing private DNS zones to new resource model as soon as possible.