You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/dns/dns-faq-private.md
+21-23Lines changed: 21 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,14 +12,10 @@ ms.author: victorh
12
12
13
13
## Does Azure DNS support private domains?
14
14
15
-
Support for private domains is implemented by using the Private Zones feature. This feature is currently available in public preview. Private zones are managed by using the same tools as internet-facing Azure DNS zones. They're resolvable only from within your specified virtual networks. For more information, see the [overview](private-dns-overview.md).
15
+
Support for private domains is supported using Azure Private DNS Zones feature. Private DNS zones are managed using the same tools as internet-facing Azure DNS zones. They're resolvable only from within your specified virtual networks. For more information, see the [overview](private-dns-overview.md).
16
16
17
17
For information on other internal DNS options in Azure, see [Name resolution for VMs and role instances](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md).
18
18
19
-
## What's the difference between Registration virtual network and Resolution virtual network in the context of private zones?
20
-
21
-
You can link virtual networks to a DNS private zone as a Registration virtual network or as a Resolution virtual network. In either case, virtual machines in the virtual network successfully resolve against records in the private zone. With a Registration virtual network, DNS records are automatically registered into the zone for the virtual machines in the virtual network. When a virtual machine in a Registration virtual network is deleted, the corresponding DNS record from the linked private zone is automatically removed.
22
-
23
19
## Will Azure DNS Private Zones work across Azure regions?
24
20
25
21
Yes. Private Zones is supported for DNS resolution between virtual networks across Azure regions. Private Zones works even without explicitly peering the virtual networks. All the virtual networks must be specified as Resolution virtual networks for the private zone. Customers might need the virtual networks to be peered for TCP/HTTP traffic to flow from one region to another.
@@ -32,29 +28,29 @@ No. Private zones work along with virtual networks. Customers use them to manage
32
28
33
29
Yes. You can associate up to 1000 virtual networks with a single private zone.
34
30
35
-
## Can a virtual network that belongs to a different subscription be added as a Resolution virtual network to a private zone?
31
+
## Can a virtual network that belongs to a different subscription be added as a linked virtual network to a private zone?
36
32
37
33
Yes. You must have write operation permission on the virtual networks and the private DNS zone. The write permission can be granted to several RBAC roles. For example, the Classic Network Contributor RBAC role has write permissions to virtual networks. For more information on RBAC roles, see [Role-based access control](../role-based-access-control/overview.md).
38
34
39
35
## Will the automatically registered virtual machine DNS records in a private zone be automatically deleted when you delete the virtual machine?
40
36
41
-
Yes. If you delete a virtual machine within a Registration virtual network, the registered records are automatically deleted.
37
+
Yes. If you delete a virtual machine within a linked virtual network with autoregistration enabled, the registered records are automatically deleted.
42
38
43
-
## Can an automatically registered virtual machine record in a private zone from a Registration virtual network be deleted manually?
39
+
## Can an automatically registered virtual machine record in a private zone from a linked virtual network be deleted manually?
44
40
45
41
Yes. You can overwrite the automatically registered DNS records with a manually created DNS record in the zone. The following question and answer address this topic.
46
42
47
-
## What happens when I try to manually create a new DNS record into a private zone that has the same hostname as an automatically registered existing virtual machine in a Registration virtual network?
43
+
## What happens when I try to manually create a new DNS record into a private zone that has the same hostname as an automatically registered existing virtual machine in a linked virtual network?
48
44
49
-
You try to manually create a new DNS record into a private zone that has the same hostname as an existing, automatically registered virtual machine in a Registration virtual network. When you do, the new DNS record overwrites the automatically registered virtual machine record. If you try to delete this manually created DNS record from the zone again, the delete succeeds. The automatic registration happens again as long as the virtual machine still exists and has a private IP attached to it. The DNS record is re-created automatically in the zone.
45
+
You try to manually create a new DNS record into a private zone that has the same hostname as an existing, automatically registered virtual machine in a linked virtual network. When you do, the new DNS record overwrites the automatically registered virtual machine record. If you try to delete this manually created DNS record from the zone again, the delete succeeds. The automatic registration happens again as long as the virtual machine still exists and has a private IP attached to it. The DNS record is re-created automatically in the zone.
50
46
51
-
## What happens when we unlink a Registration virtual network from a private zone? Will the automatically registered virtual machine records from the virtual network be removed from the zone too?
47
+
## What happens when we unlink a linked virtual network from a private zone? Will the automatically registered virtual machine records from the virtual network be removed from the zone too?
52
48
53
-
Yes. To unlink a Registration virtual network from a private zone, you update the DNS zone to remove the associated virtual network link. In this process, virtual machine records that were automatically registered are removed from the zone.
49
+
Yes. To unlink a linked virtual network from a private zone, you update the DNS zone to remove the associated virtual network link. In this process, virtual machine records that were automatically registered are removed from the zone.
54
50
55
-
## What happens when we delete a Registration or Resolution virtual network that's linked to a private zone? Do we have to manually update the private zone to unlink the virtual network as a Registration or Resolution virtual network from the zone?
51
+
## What happens when we delete a linked virtual network that's linked to a private zone? Do we have to manually update the private zone to unlink the virtual network as a linked virtual network from the zone?
56
52
57
-
Yes. When you delete a Registration or Resolution virtual network without unlinking it from a private zone first, your deletion operation succeeds. But the virtual network isn't automatically unlinked from your private zone, if any. You must manually unlink the virtual network from the private zone. For this reason, unlink your virtual network from your private zone before you delete it.
53
+
Yes. When you delete a linked virtual network without unlinking it from a private zone first, your deletion operation succeeds. But the virtual network isn't automatically unlinked from your private zone, if any. You must manually unlink the virtual network from the private zone. For this reason, unlink your virtual network from your private zone before you delete it.
58
54
59
55
## Will DNS resolution by using the default FQDN (internal.cloudapp.net) still work even when a private zone (for example, private.contoso.com) is linked to a virtual network?
60
56
@@ -64,17 +60,19 @@ Yes. Private Zones doesn't replace the default DNS resolutions by using the Azur
64
60
65
61
No. The DNS suffix on the virtual machines in your linked virtual network stays as the default Azure-provided suffix ("*.internal.cloudapp.net"). You can manually change this DNS suffix on your virtual machines to that of the private zone.
66
62
67
-
## Are there any limitations for private zones?
68
-
69
-
Yes. During the public preview, the following limitations exist:
70
-
71
-
* Reverse DNS works only for private IP space in the Registration virtual network.
72
-
* Reverse DNS for a private IP that's not registered in the private zone returns "internal.cloudapp.net" as the DNS suffix. This suffix can't be resolved. An example is a private IP for a virtual machine in a virtual network that's linked as a Resolution virtual network to a private zone.
73
-
* Conditional forwarding isn't supported, for example, to enable resolution between Azure and on-premises networks. Learn how customers can realize this scenario via other mechanisms. See [Name resolution for VMs and role instances](../virtual-network/virtual-networks-name-resolution-for-vms-and-role-instances.md)
63
+
## What are the usage limits for Azure Private DNS?
74
64
75
-
## Are there any quotas or limits on zones or records for private zones?
65
+
The following default limits apply when you use Azure Private DNS.
76
66
77
-
See the [Azure subscription and service limits](../azure-subscription-service-limits.md#azure-dns-limits) article.
67
+
| Resource | Default limit |
68
+
| --- | --- |
69
+
|Private DNS zones per subscription|1000|
70
+
|Record sets per Private DNS zone|25,000|
71
+
|Records per record set|20|
72
+
|Virtual Network Links per private DNS zone|1000|
73
+
|Virtual Networks Links per private DNS zones with auto-registration enabled|100|
74
+
|Number of private DNS zones a virtual network can get linked to with auto-registration enabled|1|
75
+
|Number of private DNS zones a virtual network can get linked|1000|
0 commit comments