Dns Get Started Template - Document Details

About This Page

This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.

View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Detected Bias Types

powershell_heavy

windows_first

missing_linux_example

windows_tools

Summary

The documentation page demonstrates a strong Windows bias. All command-line deployment instructions are provided exclusively using Azure PowerShell, with no Azure CLI (bash) or Linux shell examples. The validation step uses Windows command prompt syntax (cmd) for nslookup, and there are no Linux or macOS equivalents. The instructions and screenshots reference Windows tools and workflows first or exclusively, making it less accessible for Linux or cross-platform users.

Recommendations

Add Azure CLI (az) examples alongside or before the Azure PowerShell examples for deploying ARM templates.
Provide Linux/macOS shell equivalents for validation steps (e.g., using nslookup or dig in bash/zsh).
Include screenshots or terminal output from Linux/macOS environments where appropriate.
Explicitly mention that Azure Cloud Shell supports both Bash and PowerShell, and provide instructions for both.
Avoid using only Windows command prompt syntax; show cross-platform alternatives.
Ensure all steps and code blocks have parity between Windows and Linux/macOS environments.

Create Pull Request

Scan History

Date	Scan	Status	Result
2026-01-14 00:00	#250	in_progress	Biased
2026-01-13 00:00	#246	completed	Biased
2026-01-11 00:00	#240	completed	Biased
2026-01-10 00:00	#237	completed	Biased
2026-01-09 00:34	#234	completed	Biased
2026-01-08 00:53	#231	completed	Biased
2026-01-06 18:15	#225	cancelled	Clean
2025-08-17 00:01	#83	cancelled	Clean
2025-07-13 21:37	#48	completed	Biased
2025-07-09 13:09	#3	cancelled	Clean
2025-07-08 04:23	#2	cancelled	Biased

Flagged Code Snippets

Wait until you see the prompt from the console.

1. Select **Copy** from the previous code block to copy the PowerShell script.

1. Right-click the shell console pane and then select **Paste**.

1. Enter the values.

The template deployment creates a zone with one `A` record pointing to two IP addresses. The resource group name is the project name with `rg` appended.

It takes a couple seconds to deploy the template. When completed, the output is similar to:

:::image type="content" source="./media/dns-getstarted-template/create-dns-zone-powershell-output.png" alt-text="Azure DNS zone Resource Manager template PowerShell deployment output":::

Azure PowerShell is used to deploy the template. In addition to Azure PowerShell, you can also use the Azure portal, Azure CLI, and REST API. To learn other deployment methods, see [Deploy templates](../azure-resource-manager/templates/deploy-portal.md).

## Validate the deployment

1. Sign in to the [Azure portal](https://portal.azure.com).

1. Select **Resource groups** from the left pane.

1. Select the resource group that you created in the previous section. The default resource group name is the project name with `rg` appended.

1. The resource group should contain the following resources seen here:

:::image type="content" source="./media/dns-getstarted-template/resource-group-dns-zone.png" alt-text="DNS zone deployment resource group":::

1. Select the DNS zone with the suffix of `azurequickstart.org` to verify that the zone is created properly with an `A` record referencing the value of `203.0.113.1` and `203.0.113.2`.

:::image type="content" source="./media/dns-getstarted-template/dns-zone-overview.png" alt-text="DNS zone deployment":::

1. Copy one of the name server names from the previous step.

1. Open a command prompt, and run the following command:

   You should see something like the following screenshot:

    :::image type="content" source="./media/dns-getstarted-template/dns-zone-validation.png" alt-text="DNS zone nslookup":::

The host name `www.2lwynbseszpam.azurequickstart.org` resolves to `203.0.113.1` and `203.0.113.2`, just as you configured it. This result verifies that name resolution is working correctly.

## Clean up resources

When you no longer need the resources that you created with the DNS zone, delete the resource group. This action removes the DNS zone and all the related resources.

To delete the resource group, call the `Remove-AzResourceGroup` cmdlet: