DNS
144
Total Pages
96
Linux-Friendly Pages
48
Pages with Bias
33.3%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
124 issues found
Showing 101-124 of 124 flagged pages
DNS
Quickstart: Create an Azure DNS Private Resolver - Azure Resource Manager template (ARM template)
...icles/dns/dns-private-resolver-get-started-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell (a Windows-centric tool) is given its own tab and is presented immediately after the CLI example. There are no Linux/macOS-specific instructions or mentions of platform differences. The validation and next steps are portal-based and platform-neutral, but the deployment section shows a slight Windows bias by including PowerShell and not, for example, Bash or shell script alternatives.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Consider listing Azure CLI instructions first, as it is platform-neutral.
- Add a note that PowerShell Core is available on Linux/macOS, or clarify if the example is for Windows PowerShell only.
- Include explicit Bash/shell script examples for Linux/macOS users if relevant.
- Add a brief section on platform compatibility for the deployment tools.
Create Pull Request
DNS
Tutorial: Create Custom Azure DNS Records For a Web App
.../blob/main/articles/dns/dns-web-sites-custom-domain.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation demonstrates a mild Windows bias. PowerShell examples and references are prominent throughout, and Windows-centric tools (like nslookup in a PowerShell prompt) are used for validation. In most sections, PowerShell is presented before Azure CLI, and the CLI examples use generic shell syntax but do not explicitly mention Linux/macOS environments or alternatives to Windows tools. The validation step uses a Windows-style nslookup session, which may not match the experience of Linux/macOS users.
Recommendations
- Explicitly mention that Azure CLI commands work cross-platform (Windows, Linux, macOS) and provide shell-specific notes if needed.
- Include Linux/macOS-specific validation examples, such as showing nslookup or dig usage in a bash/zsh shell.
- When demonstrating command-line tools, avoid showing only Windows-style prompts (e.g., 'PS C:\>') and include equivalent Linux/macOS terminal prompts.
- Present CLI examples before or alongside PowerShell to signal platform neutrality.
- Add notes or links for installing and using Azure CLI and PowerShell on Linux/macOS.
DNS
How to sign your Azure Public DNS zone with DNSSEC
...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Windows Tools
Summary
The documentation provides step-by-step instructions for signing an Azure DNS zone with DNSSEC using the Azure portal, Azure CLI, and PowerShell. The CLI and PowerShell examples are platform-agnostic, but the documentation shows a slight Windows bias: PowerShell is featured as a primary automation method, and the use of 'dig.exe' (Windows-specific nomenclature) is mentioned before the generic 'dig' command. There are no explicit Linux/macOS examples or screenshots, and the ordering of tabs places PowerShell after CLI but still gives it prominence. The CLI examples use 'jq', which is cross-platform, but the explicit reference to 'dig.exe' and the lack of Linux/macOS-specific guidance or troubleshooting tips indicate a mild Windows-centric approach.
Recommendations
- Replace references to 'dig.exe' with 'dig', and clarify that 'dig' is available on Linux/macOS by default and can be installed on Windows.
- Add explicit Linux/macOS examples or troubleshooting notes, such as installation instructions for 'jq' and 'dig' on those platforms.
- Include screenshots or terminal output from Linux/macOS environments to demonstrate parity.
- Mention that Azure CLI and PowerShell are available cross-platform, and provide links to installation guides for Linux/macOS.
- Consider reordering or balancing the examples so that Linux/macOS tools and workflows are equally represented.
DNS
Import and export a private DNS zone file - Azure portal
.../main/articles/dns/private-dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows DNS as a source for zone files before mentioning BIND (the most common Linux DNS server). It provides the Windows DNS zone file path and GUI instructions, while the BIND section is brief and lacks equivalent detail. No Linux-specific tools or file locations are described, and screenshots and examples are generic, not platform-specific. There are no PowerShell examples, but Windows is referenced first and more thoroughly.
Recommendations
- List BIND (Linux) before Windows DNS when describing how to obtain zone files.
- Provide example BIND zone file paths (e.g., /etc/bind/zones/) and instructions for locating them.
- Include a brief example of extracting a zone file from BIND using common Linux commands (e.g., cat, cp).
- Clarify that the Azure portal workflow is OS-agnostic and can be performed from any platform.
- Add a note or section for macOS users if relevant.
DNS
Tutorial: Create an alias record to refer to a resource record in a zone
...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides command-line testing instructions using nslookup from 'a command prompt', which implicitly refers to Windows. There are no explicit Linux/macOS instructions or examples, and the use of 'command prompt' and nslookup is presented without mentioning Linux alternatives or shell environments.
Recommendations
- Explicitly mention that nslookup is available on Linux/macOS and show example commands in a Bash shell.
- Include Linux/macOS terminology (e.g., 'open a terminal') alongside 'command prompt'.
- Optionally provide examples using dig, which is common on Linux systems.
- Clarify that the Azure portal steps are OS-agnostic, but command-line verification can be performed on any platform.
DNS
Import and export a domain zone file for Azure private DNS - Azure CLI
...cs/blob/main/articles/dns/private-dns-import-export.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Windows DNS and its default zone file location before describing BIND (Linux) equivalents. It provides specific Windows folder paths and GUI instructions, while the BIND section is more generic. No Linux/macOS-specific CLI examples or file paths are given, and verification instructions use 'nslookup', which is available cross-platform but often associated with Windows. However, the core Azure CLI instructions are cross-platform and do not show a strong bias in command usage.
Recommendations
- List BIND (Linux) zone file locations and extraction instructions before or alongside Windows DNS.
- Provide explicit Linux/macOS file path examples and commands (e.g., showing typical BIND zone file paths like '/etc/bind/zones').
- Include Linux/macOS-specific verification commands (e.g., 'dig' alongside 'nslookup').
- Clarify that Azure CLI commands are identical across platforms and provide sample shell commands for Linux/macOS (e.g., bash).
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page mentions Azure PowerShell before Azure CLI when describing how to create a private DNS zone, subtly prioritizing the Windows-preferred tool. No explicit Windows-only examples or tools are present, and Linux parity is generally maintained.
Recommendations
- List Azure CLI before Azure PowerShell when presenting cross-platform instructions, as CLI is natively supported on Linux/macOS.
- Explicitly state that both Azure PowerShell and Azure CLI are available on Windows, Linux, and macOS, and link to platform-specific installation guides.
- Where possible, provide examples for both Azure PowerShell and Azure CLI side-by-side, or clarify which is recommended for cross-platform use.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by referencing the PowerShell-based 'get started' guide for creating a Private DNS zone as the primary next step, without mentioning Azure CLI, Bash, or Linux/macOS-specific instructions. No explicit Linux examples or cross-platform tooling are referenced, and the only actionable link for setup is PowerShell-centric.
Recommendations
- Include links to Azure CLI and ARM template guides for creating Private DNS zones alongside the PowerShell guide.
- Explicitly mention that Azure DNS management can be performed from Linux/macOS using Azure CLI or REST API.
- Add example commands for both PowerShell and Azure CLI in relevant scenarios.
- Ensure that introductory and 'next steps' sections do not prioritize Windows tools unless parity is provided.
DNS
Azure Private DNS: Secure DNS for Virtual Networks
...re-docs/blob/main/articles/dns/private-dns-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page demonstrates mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary tool. While Azure CLI is mentioned, there are no explicit Linux/macOS-specific examples or guidance, and the documentation does not mention Linux tools or shell patterns. The overall content is platform-neutral, but the ordering and emphasis slightly favor Windows users.
Recommendations
- Present Azure CLI examples before or alongside PowerShell examples to reflect cross-platform parity.
- Explicitly mention that Azure CLI is available on Linux/macOS and provide links or notes for installation/use on those platforms.
- Include example commands for both PowerShell and Bash (Azure CLI) in relevant sections.
- Avoid listing Windows tools first unless there is a technical reason.
- Add a note clarifying that all features are available regardless of OS, and link to cross-platform documentation.
DNS
Import and export a domain zone file for Azure private DNS - Azure CLI
...cs/blob/main/articles/dns/private-dns-import-export.md
Low Priority
View Details →
Detected Bias Types
Windows Tools
Windows First
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (Linux), and provides specific details for Windows tools (DNS console, %systemroot% path). No Linux-specific commands or examples are given for obtaining zone files, and Windows DNS is described first in the relevant section.
Recommendations
- Provide explicit Linux/BIND examples for obtaining zone files, such as showing typical BIND zone file paths (e.g., /etc/bind/zones) and commands to locate them.
- Mention Linux tools (e.g., cat, grep) for viewing or copying zone files, alongside Windows instructions.
- Present Windows and Linux/BIND instructions in parallel or alternate their order to avoid Windows-first bias.
- Clarify that Azure CLI commands are identical across platforms, and highlight any platform-specific considerations (such as file path formats).
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias, primarily in the 'Next steps' section, where instructions for creating an Azure DNS Private Resolver reference Azure PowerShell and the Azure portal, but do not mention CLI or Linux-native tools. PowerShell is a Windows-centric tool, and its mention before any cross-platform alternatives may create friction for Linux/macOS users. The main architecture guidance itself is platform-neutral, but the example and guidance for getting started are Windows-first.
Recommendations
- Add explicit instructions and links for using Azure CLI (az) to create and manage Azure DNS Private Resolvers, ensuring parity with PowerShell examples.
- Where PowerShell is mentioned, clarify that Azure CLI is available and provide links/examples for both.
- Consider listing cross-platform tools (Azure CLI, REST API) before or alongside PowerShell in 'Next steps' and other instructional sections.
- Review other related documentation to ensure Linux/macOS users are not directed only to Windows/PowerShell-based workflows.
DNS
Quickstart: Create an Azure DNS zone and record - Bicep
...e-docs/blob/main/articles/dns/dns-get-started-bicep.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deployment, validation, and cleanup. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented as a primary option throughout. There is no explicit Linux/macOS bias, but the repeated inclusion of PowerShell may suggest a slight Windows orientation, especially since PowerShell is less commonly used on Linux/macOS platforms compared to Azure CLI.
Recommendations
- Clarify that Azure CLI is cross-platform and generally preferred for Linux/macOS users.
- Consider listing Azure CLI examples first in each section to reflect its broader platform compatibility.
- Add a note explaining PowerShell availability on Linux/macOS, or link to installation instructions for non-Windows users.
- Optionally, include Bash script examples for Linux users where relevant.
DNS
Import and export a domain zone file - Azure portal
...ocs/blob/main/articles/dns/dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows DNS and its zone file location before mentioning BIND (the most common Linux DNS server) and its configuration. The Windows path is given explicitly, while the BIND location is described less directly. No Linux/macOS-specific examples or screenshots are provided, and the only concrete file path given is for Windows. There are no PowerShell examples, but Windows DNS is referenced first and more concretely than Linux equivalents.
Recommendations
- List BIND (Linux) before or alongside Windows DNS when describing how to obtain zone files.
- Provide explicit example file paths for BIND (e.g., /etc/bind/zones/) and other common Linux DNS setups.
- Include screenshots or step-by-step instructions for obtaining zone files from Linux/BIND environments.
- Clarify that the Azure portal and CLI are cross-platform, and mention that no OS-specific tools are required for import/export.
- If possible, add a table comparing how to obtain zone files from Windows DNS, BIND, and other common DNS servers.
DNS
Import and export a domain zone file - Azure CLI
...azure-docs/blob/main/articles/dns/dns-import-export.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Missing Linux Example
Summary
The documentation page demonstrates mild Windows bias. While the Azure CLI is correctly described as cross-platform and most examples are OS-neutral, the section on obtaining the DNS zone file lists Windows DNS first and provides a Windows-specific path, while the Linux/BIND equivalent is mentioned second. The only explicit example of verifying DNS records uses Windows Command Prompt syntax for nslookup, with no Linux/macOS alternative (e.g., shell prompt, dig command, or Linux nslookup usage). There are no PowerShell-specific examples, but Windows tools and patterns are prioritized.
Recommendations
- Provide Linux/macOS equivalents for all Windows-specific instructions, such as showing the default BIND zone file location before or alongside Windows DNS.
- Include Linux/macOS command-line examples for verifying DNS records, such as using 'dig' or 'nslookup' from a bash shell.
- When referencing file paths or commands, use OS-neutral phrasing or show both Windows and Linux/macOS formats.
- Explicitly state that all Azure CLI commands work identically on Linux/macOS, and show sample commands in a Linux shell prompt as well.
DNS
Quickstart: Create an Azure DNS Private Resolver - Azure Resource Manager template (ARM template)
...icles/dns/dns-private-resolver-get-started-template.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but the PowerShell example is given equal prominence and is presented immediately after the CLI example. There are no Linux/macOS-specific instructions or references to Bash, and PowerShell is a Windows-centric tool (though it is cross-platform now, many users still associate it with Windows). No explicit Linux tools or workflows are mentioned, and the validation steps focus on the Azure Portal, which is platform-neutral.
Recommendations
- Explicitly mention that Azure CLI works on Linux/macOS and Windows.
- Add Bash-specific examples or clarify that the CLI example is suitable for Bash on Linux/macOS.
- Consider moving the PowerShell example to a separate tab or section labeled 'Windows/PowerShell', and the CLI example to 'Linux/macOS/CLI'.
- Add a note about installing Azure CLI on Linux/macOS if not already present.
- If PowerShell is recommended for cross-platform use, clarify that PowerShell Core is available on Linux/macOS.
DNS
Quickstart: Create an Azure DNS Private Resolver using Terraform
...cles/dns/dns-private-resolver-get-started-terraform.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for verifying results, but the PowerShell examples are given equal prominence and detail. There is a subtle 'windows_first' bias as PowerShell is included as a primary tab, which may imply parity, but PowerShell is a Windows-centric tool. No Linux/macOS-specific shell examples (e.g., Bash) or explicit Linux guidance are provided, though Azure CLI is cross-platform.
Recommendations
- Clarify that Azure CLI commands are cross-platform and preferred for Linux/macOS users.
- Add explicit Bash shell examples for Linux/macOS users (e.g., using export instead of set for environment variables).
- Note that PowerShell examples are primarily for Windows users, and provide equivalent Bash commands where appropriate.
- Consider listing Azure CLI (cross-platform) examples before PowerShell to reinforce Linux parity.
DNS
How to unsign your Azure Public DNS zone
...ocs/azure-docs/blob/main/articles/dns/dnssec-unsign.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation provides three main methods for unsigning an Azure Public DNS zone: Azure Portal, Azure CLI, and PowerShell. While the Azure CLI is cross-platform, the PowerShell example is Windows-centric and is presented as a full tab, with no mention of Linux/macOS alternatives (such as Bash or shell scripting). The CLI example uses the 'azurepowershell-interactive' code block type, which may confuse Linux users, and PowerShell is shown as a first-class method alongside CLI, reinforcing a Windows bias.
Recommendations
- Clarify that Azure CLI commands work on Linux, macOS, and Windows, and use the 'bash' or 'shell' code block type for CLI examples to avoid confusion.
- Add explicit Bash or shell scripting examples for Linux/macOS users where appropriate.
- Note that PowerShell Core is available cross-platform, but provide guidance for Linux/macOS users on installation and usage if PowerShell is required.
- Consider listing CLI examples before PowerShell, or at least clarify platform compatibility for each method.
DNS
Azure Private DNS: Secure DNS for Virtual Networks
...re-docs/blob/main/articles/dns/private-dns-overview.md
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation page shows mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, and by emphasizing PowerShell as a primary tool for getting started. While Azure CLI is mentioned, there are no explicit Linux/macOS examples or references to platform-specific usage, and PowerShell (traditionally Windows-centric) is given precedence.
Recommendations
- Present Azure CLI examples before or alongside PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI and Azure portal are fully supported on Linux/macOS, and provide links or notes for platform-specific guidance.
- Include example workflows or screenshots for Linux/macOS environments where relevant.
- Avoid implying PowerShell is the default or primary tool, especially in introductory or 'getting started' sections.
DNS
Fallback to internet for Azure Private DNS zones
...re-docs/blob/main/articles/dns/private-dns-fallback.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation page demonstrates a mild Windows bias by consistently showing command-line examples using Windows command prompt syntax (e.g., 'C:\>') and referencing Windows tools (nslookup, dig) with Windows-style output. The examples and screenshots use Windows conventions, and instructions for running DNS queries assume a Windows environment. There are no explicit Linux/macOS examples or references, though the tools used (dig, nslookup) are cross-platform.
Recommendations
- Include Linux/macOS command-line examples alongside Windows ones, using typical shell prompts (e.g., '$ dig ...').
- Clarify that 'dig' and 'nslookup' are available on Linux/macOS and provide installation instructions if needed.
- Add screenshots or output examples from Linux/macOS terminals.
- Avoid using only Windows-style prompts (C:\>) in code blocks; alternate or use generic prompts.
- Explicitly state that the procedure applies to both Windows and Linux/macOS VMs.
DNS
Import and export a private DNS zone file - Azure portal
.../main/articles/dns/private-dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Windows Tools
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (the most common DNS server on Linux/Unix). The Windows path is given explicitly, while the BIND example is less detailed. No Linux-specific tools or file paths are described, and screenshots and instructions are platform-neutral (web portal). There are no PowerShell examples, and the CLI is referenced but not shown. The bias is minor and limited to the order and detail of DNS server examples.
Recommendations
- Present BIND (Linux/Unix) and Windows DNS examples with equal detail and in parallel, rather than listing Windows first.
- Provide explicit example paths for BIND zone files (e.g., /etc/bind/zones/db.example.com) as is done for Windows.
- Include a brief note on how to obtain zone files from common Linux DNS servers (e.g., BIND, Unbound), not just mention the config file.
- Ensure that any references to file locations or DNS server types are balanced between Windows and Linux/Unix.
- If CLI instructions are referenced, provide example commands for both Windows and Linux shells.
Low Priority
View Details →
Detected Bias Types
Windows First
Powershell Heavy
Summary
The documentation references Azure PowerShell before Azure CLI when describing how to create a private DNS zone, suggesting a Windows-first approach. While both PowerShell and CLI links are provided, PowerShell is mentioned first, which may subtly prioritize Windows tooling. No explicit Linux/macOS examples or tools are highlighted, and no Linux-specific guidance is given.
Recommendations
- Alternate the order of PowerShell and CLI references, or mention CLI first to balance platform representation.
- Explicitly state that Azure CLI is cross-platform and works on Linux/macOS, while PowerShell is available on Windows and other platforms.
- Add examples or notes for Linux/macOS users, such as how to install and use Azure CLI or PowerShell on those platforms.
- Include links to platform-specific setup guides for both CLI and PowerShell.
DNS
What is a virtual network link subresource of Azure DNS private zones
...main/articles/dns/private-dns-virtual-network-links.md
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation references Azure PowerShell before Azure CLI in the 'Next steps' section, suggesting a Windows-first approach. While both Windows (PowerShell) and cross-platform (CLI) tools are mentioned, PowerShell is listed first, which may subtly prioritize Windows users. No explicit Windows-only tools or examples are present, and Linux/macOS users are not blocked from completing the tasks.
Recommendations
- List Azure CLI before Azure PowerShell to emphasize cross-platform support.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links to installation guides for those platforms.
- Ensure all examples and walkthroughs have CLI equivalents and are clearly marked as cross-platform.
- Consider adding a note about parity between PowerShell and CLI for Azure DNS tasks.
DNS
Tutorial: Create an alias record to refer to a resource record in a zone
...azure-docs/blob/main/articles/dns/tutorial-alias-rr.md
Low Priority
View Details →
Detected Bias Types
Windows First
Missing Linux Example
Summary
The documentation provides instructions and examples primarily using the Azure portal UI and the nslookup command, referencing 'command prompt' without specifying platform. The only command-line example is nslookup, which is available on both Windows and Linux, but the instructions refer to 'command prompt' (a Windows term) and do not mention Linux/macOS equivalents (e.g., terminal, dig command). No Linux/macOS-specific instructions or screenshots are provided.
Recommendations
- Explicitly mention that nslookup is available on Linux/macOS and provide equivalent instructions for running the command in a Linux/macOS terminal.
- Include alternative Linux/macOS DNS query tools such as dig, with example commands and expected output.
- Use platform-neutral terminology (e.g., 'open a terminal or command prompt') when referring to command-line operations.
- If screenshots of command-line output are included, provide examples from both Windows and Linux/macOS environments.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific troubleshooting examples or commands. However, when discussing DNS resolution, it references using web-based tools (digwebinterface) and does not mention command-line tools like 'dig' or 'nslookup' for either Windows or Linux. There is no explicit Windows bias, but the lack of Linux-specific examples or mention of Linux tools (such as the 'dig' command) means Linux parity is not fully achieved.
Recommendations
- Add troubleshooting examples using common Linux command-line tools such as 'dig' and 'nslookup'.
- Include both Windows and Linux command-line examples for DNS queries and validation steps.
- Explicitly mention platform-agnostic methods and clarify when steps apply to all operating systems.
- Provide links to documentation for using DNS tools on both Windows and Linux.