Document Details
Dns Get Started Template
This page contains Windows bias
About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
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 examples use Azure PowerShell, with no Azure CLI (bash) or Linux shell equivalents provided. Instructions for validating DNS resolution use Windows Command Prompt syntax (cmd), and there is no mention of Linux or macOS alternatives. The workflow and screenshots are tailored to Windows users, and Linux users are not directly addressed.
Recommendations
- Provide equivalent Azure CLI (az) commands alongside PowerShell examples, preferably with a tabbed interface for PowerShell, Azure CLI, and REST API.
- Include Linux/macOS shell instructions for DNS validation (e.g., using 'dig' or 'nslookup' in bash/zsh), and clarify that the commands work cross-platform.
- Mention that Azure Cloud Shell supports both Bash and PowerShell, and show how to select the preferred shell.
- Ensure that screenshots and instructions are not Windows-specific, or provide Linux/macOS alternatives where appropriate.
- Explicitly state that all steps can be performed from Linux, macOS, or Windows, and link to platform-agnostic documentation where possible.
Create Pull Request
Scan History
| Date | Scan | Status | Result |
|---|---|---|---|
| 2025-07-12 23:44 | #41 | cancelled |
Biased
|
| 2025-07-12 00:58 | #8 | cancelled |
 Clean
|
| 2025-07-10 05:06 | #7 | processing |
Clean
|
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: