|
| 1 | +--- |
| 2 | +title: Quickstart - Create an Azure DNS private zone using the Azure portal |
| 3 | +description: In this quickstart, you create and test a private DNS zone and record in Azure DNS. This is a step-by-step guide to create and manage your first private DNS zone and record using the Azure portal. |
| 4 | +services: dns |
| 5 | +author: vhorne |
| 6 | +ms.service: dns |
| 7 | +ms.topic: quickstart |
| 8 | +ms.date: 09/20/2019 |
| 9 | +ms.author: victorh |
| 10 | +#Customer intent: As an experienced network administrator I want to create an Azure DNS private zone, so I can resolve host names on my private virtual networks. |
| 11 | +--- |
| 12 | + |
| 13 | +# Quickstart: Create an Azure DNS private zone using the Azure portal |
| 14 | + |
| 15 | +This quickstart walks you through the steps to create your first private DNS zone and record using the Azure portal. |
| 16 | + |
| 17 | +[!INCLUDE [private-dns-public-preview-notice](../../includes/private-dns-public-preview-notice.md)] |
| 18 | + |
| 19 | +A DNS zone is used to host the DNS records for a particular domain. To start hosting your domain in Azure DNS, you need to create a DNS zone for that domain name. Each DNS record for your domain is then created inside this DNS zone. To publish a private DNS zone to your virtual network, you specify the list of virtual networks that are allowed to resolve records within the zone. These are called *linked* virtual networks. When autoregistration is enabled, Azure DNS also updates the zone records whenever a virtual machine is created, changes its' IP address, or is deleted. |
| 20 | + |
| 21 | +In this quickstart, you learn how to: |
| 22 | + |
| 23 | +> [!div class="checklist"] |
| 24 | +> * Create a DNS private zone |
| 25 | +> * Create a virtual network |
| 26 | +> * Link the virtual network |
| 27 | +> * Create test virtual machines |
| 28 | +> * Create an additional DNS record |
| 29 | +> * Test the private zone |
| 30 | +
|
| 31 | +If you don’t have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin. |
| 32 | + |
| 33 | +If you prefer, you can complete this quickstart using [Azure PowerShell](private-dns-getstarted-powershell.md) or [Azure CLI](private-dns-getstarted-cli.md). |
| 34 | + |
| 35 | +## Create a DNS private zone |
| 36 | + |
| 37 | +The following example creates a DNS zone called **private.contoso.com** in a resource group called **MyAzureResourceGroup**. |
| 38 | + |
| 39 | +A DNS zone contains the DNS entries for a domain. To start hosting your domain in Azure DNS, you create a DNS zone for that domain name. |
| 40 | + |
| 41 | + |
| 42 | + |
| 43 | +1. On the portal search bar, type **private dns zones** in the search text box and press **Enter**. |
| 44 | +1. Select **Private DNS zone**. |
| 45 | +2. Select **Create private dns zone**. |
| 46 | + |
| 47 | +1. On the **Create Private DNS zone** page, type or select the following values: |
| 48 | + |
| 49 | + - **Resource group**: Select **Create new**, enter *MyAzureResourceGroup*, and select **OK**. The resource group name must be unique within the Azure subscription. |
| 50 | + - **Name**: Type *private.contoso.com* for this example. |
| 51 | +1. For **Resource group location**, select **West Central US**. |
| 52 | + |
| 53 | +1. Select **Review + Create**. |
| 54 | + |
| 55 | +1. Select **Create**. |
| 56 | + |
| 57 | +It may take a few minutes to create the zone. |
| 58 | + |
| 59 | +## Create a virtual network |
| 60 | + |
| 61 | +1. On the portal page upper left, select **Create a resource**, then **Networking**, then select **Virtual network**. |
| 62 | +2. For **Name**, type **myAzureVNet**. |
| 63 | +3. For **Resource group**, select **MyAzureResourceGroup**. |
| 64 | +4. For **Location**, select **West Central US**. |
| 65 | +5. Accept the other default values and select **Create**. |
| 66 | + |
| 67 | +## Link the virtual network |
| 68 | + |
| 69 | +To link the private DNS zone to a virtual network, you create a virtual network link. |
| 70 | + |
| 71 | + |
| 72 | + |
| 73 | +1. Open the **MyAzureResourceGroup** resource group and select the **private.contoso.com** private zone. |
| 74 | +2. On the left pane, select **Virtual network links**. |
| 75 | +3. Select **Add**. |
| 76 | +4. Type **myLink** for the **Link name**. |
| 77 | +5. For **Virtual network**, select **myAzureVNet**. |
| 78 | +6. Select the **Enable auto registration** check box. |
| 79 | +7. Select **OK**. |
| 80 | + |
| 81 | +## Create the test virtual machines |
| 82 | + |
| 83 | +Now, create two virtual machines so you can test your private DNS zone: |
| 84 | + |
| 85 | +1. On the portal page upper left, select **Create a resource**, and then select **Windows Server 2016 Datacenter**. |
| 86 | +1. Select **MyAzureResourceGroup** for the resource group. |
| 87 | +1. Type **myVM01** - for the name of the virtual machine. |
| 88 | +1. Select **West Central US** for the **Region**. |
| 89 | +1. Type **azureadmin** for the administrator user name. |
| 90 | +2. Type **Azure12345678** for the password and confirm the password. |
| 91 | + |
| 92 | +5. For **Public inbound ports**, select **Allow selected ports**, and then select **RDP (3389)** for **Select inbound ports**. |
| 93 | +10. Accept the other defaults for the page and then click **Next: Disks >**. |
| 94 | +11. Accept the defaults on the **Disks** page, then click **Next: Networking >**. |
| 95 | +1. Make sure that **myAzureVNet** is selected for the virtual network. |
| 96 | +1. Accept the other defaults for the page, and then click **Next: Management >**. |
| 97 | +2. For **Boot diagnostics**, select **Off**, accept the other defaults, and then select **Review + create**. |
| 98 | +1. Review the settings and then click **Create**. |
| 99 | + |
| 100 | +Repeat these steps and create another virtual machine named **myVM02**. |
| 101 | + |
| 102 | +It will take a few minutes for both virtual machines to complete. |
| 103 | + |
| 104 | +## Create an additional DNS record |
| 105 | + |
| 106 | + The following example creates a record with the relative name **db** in the DNS Zone **private.contoso.com**, in resource group **MyAzureResourceGroup**. The fully qualified name of the record set is **db.private.contoso.com**. The record type is "A", with the IP address of **myVM01**. |
| 107 | + |
| 108 | +1. Open the **MyAzureResourceGroup** resource group and select the **private.contoso.com** private zone. |
| 109 | +2. Select **+ Record set**. |
| 110 | +3. For **Name**, type **db**. |
| 111 | +4. For **IP Address**, type the IP address you see for **myVM01**. This should be auto registered when the virtual machine started. |
| 112 | +5. Select **OK**. |
| 113 | + |
| 114 | +## Test the private zone |
| 115 | + |
| 116 | +Now you can test the name resolution for your **private.contoso.com** private zone. |
| 117 | + |
| 118 | +### Configure VMs to allow inbound ICMP |
| 119 | + |
| 120 | +You can use the ping command to test name resolution. So, configure the firewall on both virtual machines to allow inbound ICMP packets. |
| 121 | + |
| 122 | +1. Connect to myVM01, and open a Windows PowerShell window with administrator privileges. |
| 123 | +2. Run the following command: |
| 124 | + |
| 125 | + ```powershell |
| 126 | + New-NetFirewallRule –DisplayName “Allow ICMPv4-In” –Protocol ICMPv4 |
| 127 | + ``` |
| 128 | + |
| 129 | +Repeat for myVM02. |
| 130 | + |
| 131 | +### Ping the VMs by name |
| 132 | + |
| 133 | +1. From the myVM02 Windows PowerShell command prompt, ping myVM01 using the automatically registered host name: |
| 134 | + ``` |
| 135 | + ping myVM01.private.contoso.com |
| 136 | + ``` |
| 137 | + You should see output that looks similar to this: |
| 138 | + ``` |
| 139 | + PS C:\> ping myvm01.private.contoso.com |
| 140 | +
|
| 141 | + Pinging myvm01.private.contoso.com [10.2.0.4] with 32 bytes of data: |
| 142 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 143 | + Reply from 10.2.0.4: bytes=32 time=1ms TTL=128 |
| 144 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 145 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 146 | +
|
| 147 | + Ping statistics for 10.2.0.4: |
| 148 | + Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), |
| 149 | + Approximate round trip times in milli-seconds: |
| 150 | + Minimum = 0ms, Maximum = 1ms, Average = 0ms |
| 151 | + PS C:\> |
| 152 | + ``` |
| 153 | +2. Now ping the **db** name you created previously: |
| 154 | + ``` |
| 155 | + ping db.private.contoso.com |
| 156 | + ``` |
| 157 | + You should see output that looks similar to this: |
| 158 | + ``` |
| 159 | + PS C:\> ping db.private.contoso.com |
| 160 | +
|
| 161 | + Pinging db.private.contoso.com [10.2.0.4] with 32 bytes of data: |
| 162 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 163 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 164 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 165 | + Reply from 10.2.0.4: bytes=32 time<1ms TTL=128 |
| 166 | +
|
| 167 | + Ping statistics for 10.2.0.4: |
| 168 | + Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), |
| 169 | + Approximate round trip times in milli-seconds: |
| 170 | + Minimum = 0ms, Maximum = 0ms, Average = 0ms |
| 171 | + PS C:\> |
| 172 | + ``` |
| 173 | + |
| 174 | +## Delete all resources |
| 175 | + |
| 176 | +When no longer needed, delete the **MyAzureResourceGroup** resource group to delete the resources created in this quickstart. |
| 177 | + |
| 178 | + |
| 179 | +## Next steps |
| 180 | + |
| 181 | +> [!div class="nextstepaction"] |
| 182 | +> [Using Azure DNS for private domains](private-dns-overview.md) |
0 commit comments