Merge pull request #287047 from greg-lindsay/dns-freshness

add note about pricing

Author: denrea

articles/dns/media/tutorial-alias-tm/add-endpoint-tm-expanded.png

@@ -6,7 +6,7 @@ services: dns
 author: greg-lindsay
 ms.service: azure-dns
 ms.topic: tutorial
-ms.date: 03/08/2024
+ms.date: 09/19/2024
 ms.author: greglin
 ms.custom: template-tutorial #Required; leave this attribute/value as-is.
 #Customer intent: As an experienced network administrator, I want to configure Azure DNS alias records to use my apex domain name with Traffic Manager.
@@ -55,8 +55,8 @@ For more information, see [Resolve errors for resource provider registration](/a
 Create a virtual network and a subnet to place your web servers in.
 
 1. In the Azure portal, enter *virtual network* in the search box at the top of the portal, and then select **Virtual networks** from the search results.
-1. In **Virtual networks**, select **+ Create**.
-1. In **Create virtual network**, enter or select the following information in the **Basics** tab:
+2. In **Virtual networks**, select **+ Create**.
+3. In **Create virtual network**, enter or select the following information in the **Basics** tab:
 
     | Setting | Value |
     |---------|-------|
@@ -67,23 +67,23 @@ Create a virtual network and a subnet to place your web servers in.
     | Name   | Enter *myTMVNet*.    |
     | Region    | Select your region. |
 
-1. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
-1. In the **IP Addresses** tab, enter the following information:
+4. Select the **IP Addresses** tab or select the **Next: IP Addresses** button at the bottom of the page.
+5. In the **IP Addresses** tab, enter the following information:
 
     | Setting | Value |
     |---------|-------|
     | IPv4 address space | Enter *10.10.0.0/16*.  |
 
-1. Select **+ Add subnet**, and enter this information in the **Add subnet**:
+6. Select **+ Add subnet**, and enter this information in the **Add subnet**:
 
     | Setting | Value |
     |---------|-------|
     | Subnet name | Enter *WebSubnet*. |
     | Subnet address range | Enter *10.10.0.0/24*. |
 
-1. Select **Add**.
-1. Select the **Review + create** tab or select the **Review + create** button.
-1. Select **Create**.
+7. Select **Add**.
+8. Select the **Review + create** tab or select the **Review + create** button.
+9. Select **Create**.
 
 ## Create web server virtual machines
 
@@ -94,8 +94,8 @@ Create two Windows Server virtual machines, and install IIS web server on them,
 Create two Windows Server 2019 virtual machines.
 
 1. In the Azure portal, enter *virtual machine* in the search box at the top of the portal, and then select **Virtual machines** from the search results.
-1. In **Virtual machines**, select **+ Create** and then select **Azure virtual machine**.
-1. In **Create a virtual machine**, enter or select the following information in the **Basics** tab:
+2. In **Virtual machines**, select **+ Create** and then select **Azure virtual machine**.
+3. In **Create a virtual machine**, enter or select the following information in the **Basics** tab:
 
     | Setting | Value |
     |---------|-------|
@@ -117,9 +117,8 @@ Create two Windows Server 2019 virtual machines.
     | Public inbound ports | Select **None**. |
 
 
-1. Select the **Networking** tab, or select **Next: Disks**, then **Next: Networking**.
-
-1. In the **Networking** tab, enter or select the following information:
+4. Select the **Networking** tab, or select **Next: Disks**, then **Next: Networking**.
+5. In the **Networking** tab, enter or select the following information:
 
     | Setting | Value |
     |---------|-------|
@@ -131,9 +130,9 @@ Create two Windows Server 2019 virtual machines.
     | Public inbound ports  | Select **Allow selected ports**. |
     | Select inbound ports  | Select **HTTP (80)**, **HTTPS (443)** and **RDP (3389)**. |
 
-1. Select **Review + create**.
-1. Review the settings, and then select **Create**.
-1. Repeat previous steps to create the second virtual machine. Enter *Web-02* in the **Virtual machine name** and *Web-02-ip* in the **Name** of **Public IP**. For the other settings, use the same information from the previous steps used with first virtual machine.
+6. Select **Review + create**.
+7. Review the settings, and then select **Create**.
+8. Repeat previous steps to create the second virtual machine. Enter *Web-02* in the **Virtual machine name** and *Web-02-ip* in the **Name** of **Public IP**. For the other settings, use the same information from the previous steps used with first virtual machine.
 
 Each virtual machine deployment may take a few minutes to complete.
 
@@ -142,44 +141,44 @@ Each virtual machine deployment may take a few minutes to complete.
 Install IIS on both **Web-01** and **Web-02** virtual machines.
 
 1. In the **Connect** page of **Web-01** virtual machine, select **RDP** and then **Download RDP File**.
-1. Open *Web-01.rdp* file, and select **Connect**.
-1. Enter the username and password entered during virtual machine creation.
-1. On the **Server Manager** dashboard, select **Manage** then **Add Roles and Features**.
-1. Select **Server Roles** or select **Next** three times. On the **Server Roles** screen, select **Web Server (IIS)**.
-1. Select **Add Features**, and then select **Next**.
+2. Open *Web-01.rdp* file, and select **Connect**.
+3. Enter the username and password entered during virtual machine creation.
+4. On the **Server Manager** dashboard, select **Manage** then **Add Roles and Features**.
+5. Select **Server Roles** or select **Next** three times. On the **Server Roles** screen, select **Web Server (IIS)**.
+6. Select **Add Features**, and then select **Next**.
 
     :::image type="content" source="./media/tutorial-alias-tm/iis-web-server-installation.png" alt-text="Screenshot of Add Roles and Features Wizard in Windows Server 2019 showing how to install the I I S Web Server by adding the Web Server role.":::
 
-1. Select **Confirmation** or select **Next** three times, and then select **Install**. The installation process takes a few minutes to finish.
-1. After the installation finishes, select **Close**.
-1. Go to *C:\inetpub\wwwroot* and open *iisstart.htm* with Notepad or any editor of your choice to edit the default IIS web page.
-1. Replace all the text in the file with `Hello World from Web-01` and save the changes to *iisstart.htm*. 
-1. Open a web browser. Browse to **localhost** to verify that the default IIS web page appears.
+7. Select **Confirmation** or select **Next** three times, and then select **Install**. The installation process takes a few minutes to finish.
+8. After the installation finishes, select **Close**.
+9. Go to *C:\inetpub\wwwroot* and open *iisstart.htm* with Notepad or any editor of your choice to edit the default IIS web page.
+10. Replace all the text in the file with `Hello World from Web-01` and save the changes to *iisstart.htm*. 
+11. Open a web browser. Browse to **localhost** to verify that the default IIS web page appears.
 
     :::image type="content" source="./media/tutorial-alias-tm/iis-on-web-01-vm-in-web-browser.png" alt-text="Screenshot of Internet Explorer showing the I I S Web Server default page of first virtual machine.":::
 
-1. Repeat previous steps to install IIS web server on **Web-02** virtual machine. Use `Hello World from Web-02` to replace all the text in *iisstart.htm*.
+12. Repeat previous steps to install IIS web server on **Web-02** virtual machine. Use `Hello World from Web-02` to replace all the text in *iisstart.htm*.
 
 ### Add a DNS label
 
 Public IP addresses need DNS labels to work with Traffic Manager.
 
 1. In the Azure portal, enter *TMResourceGroup* in the search box at the top of the portal, and then select **TMResourceGroup** from the search results.
-1. In the **TMResourceGroup** resource group, select the **Web-01-ip** public IP address.
-1. Under **Settings**, select **Configuration**.
-1. Enter *web01pip* in the **DNS name label**.
-1. Select **Save**.
+2. In the **TMResourceGroup** resource group, select the **Web-01-ip** public IP address.
+3. Under **Settings**, select **Configuration**.
+4. Enter *web01pip* in the **DNS name label**.
+5. Select **Save**.
 
     :::image type="content" source="./media/tutorial-alias-tm/ip-dns-name-label-inline.png" alt-text="Screenshot of the Configuration page of Azure Public IP Address showing D N S name label." lightbox="./media/tutorial-alias-tm/ip-dns-name-label-expanded.png":::
 
-1. Repeat the previous steps for the **Web-02-ip** public IP address and enter *web02pip* in the **DNS name label**.
+6. Repeat the previous steps for the **Web-02-ip** public IP address and enter *web02pip* in the **DNS name label**.
 
 ## Create a Traffic Manager profile
 
 1. In the **Overview** page of **Web-01-ip** public IP address, note the IP address for later use. Repeat this step for the **Web-02-ip** public IP address.
-1. In the Azure portal, enter *Traffic Manager profile* in the search box at the top of the portal, and then select **Traffic Manager profiles**.
-1. Select **+ Create**.
-1. In the **Create Traffic Manager profile** page, enter or select the following information:
+2. In the Azure portal, enter *Traffic Manager profile* in the search box at the top of the portal, and then select **Traffic Manager profiles**.
+3. Select **+ Create**.
+4. In the **Create Traffic Manager profile** page, enter or select the following information:
 
     | Setting | Value |
     |---------|-------|
@@ -190,10 +189,9 @@ Public IP addresses need DNS labels to work with Traffic Manager.
 
     :::image type="content" source="./media/tutorial-alias-tm/create-traffic-manager-profile.png" alt-text="Screenshot of the Create Traffic Manager profile page showing the selected settings.":::
 
-1. Select **Create**.
-
-1. After **TM-alias-test** deployment finishes, select **Go to resource**.
-1. In the **Endpoints** page of **TM-alias-test** Traffic Manager profile, select **+ Add** and enter or select the following information:
+5. Select **Create**.
+6. After **TM-alias-test** deployment finishes, select **Go to resource**.
+7. In the **Endpoints** page of **TM-alias-test** Traffic Manager profile, select **+ Add** and enter or select the following information:
 
     | Setting | Value |
     |---------|-------|
@@ -204,9 +202,8 @@ Public IP addresses need DNS labels to work with Traffic Manager.
 
     :::image type="content" source="./media/tutorial-alias-tm/add-endpoint-tm-inline.png" alt-text="Screenshot of the Endpoints page in Traffic Manager profile showing selected settings for adding an endpoint." lightbox="./media/tutorial-alias-tm/add-endpoint-tm-expanded.png":::
 
-1. Select **Add**.
-
-1. Repeat the last two steps to create the second endpoint. Enter or select the following information:
+8. Select **Add**.
+9. Repeat the last two steps to create the second endpoint. Enter or select the following information:
 
     | Setting | Value |
     |---------|-------|
@@ -220,33 +217,36 @@ Public IP addresses need DNS labels to work with Traffic Manager.
 Create an alias record that points to the Traffic Manager profile.
 
 1. In the Azure portal, enter *contoso.com* in the search box at the top of the portal, and then select **contoso.com** DNS zone from the search results.
-1. In the **Overview** page of **contoso.com** DNS zone, select the **+ Record set** button.
-1. In the **Add record set**, leave the **Name** box empty to represent the apex domain name. An example is `contoso.com`.
-1. Select **A** for the **Type**.
-1. Select **Yes** for the **Alias record set**, and then select the **Azure Resource** for the **Alias type**.
-1. Select the **TM-alias-test** Traffic Manager profile for the **Azure resource**.
-1. Select **OK**.
+2. On the **Overview** page of **contoso.com** DNS zone, select the **+ Record set** button.
+3. In **Add record set**, leave the **Name** box empty to represent the apex domain name. An example is `contoso.com`.
+4. Select **A** for the **Type**.
+5. Select **Yes** for the **Alias record set**, and then select the **Azure Resource** for the **Alias type**.
+6. Select the **TM-alias-test** Traffic Manager profile for the **Azure resource**.
+7. Select **OK**.
 
     :::image type="content" source="./media/tutorial-alias-tm/add-record-set-tm-inline.png" alt-text="Screenshot of adding an alias record to refer to the Traffic Manager profile." lightbox="./media/tutorial-alias-tm/add-record-set-tm-expanded.png":::
 
+> [!NOTE]
+> DNS Queries to your newly aliased Traffic Manager recordset are displayed in your Traffic Manager profile billing. For more information on Traffic Manager billing, see [Traffic Manager pricing](https://azure.microsoft.com/pricing/details/traffic-manager).
+
 ## Test the alias record
 
 1. From a web browser, browse to `contoso.com` or your apex domain name. You see the IIS default page with `Hello World from Web-01`. The Traffic Manager directed traffic to **Web-01** IIS web server because it has the highest priority. Close the web browser and shut down **Web-01** virtual machine. Wait a few minutes for the virtual machine to completely shut down.
-1. Open a new web browser, and browse again to `contoso.com` or your apex domain name.
-1. You should see the IIS default page with `Hello World from Web-02`. The Traffic Manager handled the situation and directed traffic to the second IIS server after shutting down the first server that has the highest priority.
+2. Open a new web browser, and browse again to `contoso.com` or your apex domain name.
+3. You should see the IIS default page with `Hello World from Web-02`. The Traffic Manager handled the situation and directed traffic to the second IIS server after shutting down the first server that has the highest priority.
 
 ## Clean up resources
 
 When no longer needed, you can delete all resources created in this tutorial by following these steps:
 
 1. On the Azure portal menu, select **Resource groups**.
-1. Select the **TMResourceGroup** resource group.
-1. On the **Overview** page, select **Delete resource group**.
-1. Enter *TMResourceGroup* and select **Delete**.
-1. On the Azure portal menu, select **All resources**.
-1. Select **contoso.com** DNS zone.
-1. On the **Overview** page, select the **@** record created in this tutorial.
-1. Select **Delete** and then **Yes**.
+2. Select the **TMResourceGroup** resource group.
+3. On the **Overview** page, select **Delete resource group**.
+4. Enter *TMResourceGroup* and select **Delete**.
+5. On the Azure portal menu, select **All resources**.
+6. Select **contoso.com** DNS zone.
+7. On the **Overview** page, select the **@** record created in this tutorial.
+8. Select **Delete** and then **Yes**.
 
 ## Next steps