DNS
73
Total Pages
24
Linux-Friendly Pages
49
Pages with Bias
67.1%
Bias Rate
Bias Trend Over Time
Pages with Bias Issues
323 issues found
Showing 301-323 of 323 flagged pages
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 Windows command prompt examples (e.g., 'C:\>nslookup', 'C:\>dig') and referencing Windows-style command lines first. Screenshots and instructions refer to the Azure portal, which is cross-platform, but the DNS resolution demonstration and troubleshooting sections use Windows-centric notation and tools. There are no explicit Linux/macOS examples or terminal screenshots, though the use of 'dig' is cross-platform.
Recommendations
- Include Linux/macOS terminal examples alongside Windows command prompt examples (e.g., show '$ dig ...' in addition to 'C:\>dig ...').
- Clarify that 'dig' is available on Linux/macOS by showing sample outputs from those platforms.
- Avoid using Windows-specific prompt notation ('C:\>') when the command is not Windows-exclusive.
- Add a note or section for Linux/macOS users, mentioning any platform-specific considerations for DNS resolution or Azure CLI usage.
Create Pull Request
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 a mild Windows bias. In the 'Next steps' section, Azure PowerShell (a Windows-centric tool) is listed before Azure CLI, suggesting a Windows-first approach. The benefits section also lists Azure PowerShell among the 'familiar tools' without mentioning Linux-specific alternatives or parity. No Linux/macOS-specific examples, tools, or considerations are provided, and the documentation does not reference shell environments or package managers common to Linux/macOS users.
Recommendations
- Alternate the order of PowerShell and CLI examples, or list CLI first to signal cross-platform parity.
- Explicitly mention that Azure CLI is fully supported on Linux/macOS and provide links to installation guides for those platforms.
- Include examples or references to Linux/macOS environments where relevant, such as using Bash or zsh with Azure CLI.
- Add a note clarifying that all Azure DNS features are accessible from Linux/macOS via Azure CLI and REST API.
- Consider including troubleshooting or operational notes for Linux/macOS users if there are platform-specific nuances.
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Azure PowerShell before Azure CLI when describing how to create a private DNS zone, which subtly prioritizes Windows tooling. However, both Windows (PowerShell) and cross-platform (CLI) options are referenced, and no examples or instructions are given in this overview page itself.
Recommendations
- List Azure CLI before Azure PowerShell when referencing cross-platform instructions.
- Explicitly state that Azure CLI is available on Windows, Linux, and macOS to encourage parity.
- Ensure that linked pages (PowerShell and CLI guides) provide equivalent, complete instructions for both platforms.
- Consider including a direct Linux/macOS example or note in the overview for common tasks.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias in its 'Next steps' section, where it lists Azure PowerShell (a Windows-centric tool) before the Azure portal for creating a DNS Private Resolver. There are no Linux/macOS CLI examples or references to cross-platform tools like Azure CLI. The main architectural guidance is platform-neutral, but the guidance for getting started leans toward Windows tools.
Recommendations
- Add instructions or links for creating an Azure DNS Private Resolver using Azure CLI, which is cross-platform.
- List cross-platform options (Azure CLI, REST API) before or alongside PowerShell in 'Next steps'.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify platform support.
- Provide example commands for both Azure PowerShell and Azure CLI in setup and configuration guides.
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
Windows First
Summary
The documentation references both Azure PowerShell and Azure CLI for creating a private DNS zone, but lists Azure PowerShell (typically associated with Windows environments) before Azure CLI (which is cross-platform and more common on Linux/macOS). No explicit Windows-only tools or examples are given, and Linux/macOS users are not blocked from completing any tasks.
Recommendations
- List Azure CLI before Azure PowerShell in 'Next steps', as CLI is cross-platform and more widely used on Linux/macOS.
- Explicitly mention that both Azure PowerShell and Azure CLI are available on all major platforms, or provide links to installation guides for each platform.
- Consider adding a note clarifying that all tasks can be performed on Linux, macOS, and Windows.
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 all deployment, validation, and cleanup steps. However, PowerShell (a Windows-centric tool) is given equal prominence to Azure CLI, and is presented in every section. There is no explicit mention of Linux/macOS-specific considerations, nor are there any examples using Bash or shell scripting, which are common on non-Windows platforms. The ordering of examples sometimes places PowerShell after CLI, but the parity is close. No Windows-only tools or patterns are used, but the repeated inclusion of PowerShell may suggest a slight Windows bias.
Recommendations
- Clarify that Azure CLI works cross-platform (Windows, Linux, macOS) and is recommended for non-Windows users.
- Add a note for Linux/macOS users that PowerShell Core is available cross-platform, but Azure CLI is typically pre-installed or easier to use.
- Consider providing Bash script examples for automation on Linux/macOS.
- Explicitly mention platform compatibility in the prerequisites section.
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
Summary
The documentation mentions Windows DNS as the first example when describing where to obtain a zone file, providing the default Windows folder path and referencing the DNS console. The Linux/BIND equivalent is mentioned second, with less detail. No PowerShell examples or Windows-only tools are used, and the main workflow is platform-agnostic via the Azure portal. However, the ordering and detail of examples subtly prioritize Windows.
Recommendations
- Present Linux/BIND and Windows DNS examples with equal detail and prominence.
- List both Windows and Linux/BIND zone file locations together, or alternate which is mentioned first.
- Provide explicit instructions for obtaining zone files from BIND (e.g., example paths, commands to copy the file).
- Consider adding macOS notes if relevant (e.g., for BIND or other 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 Azure CLI is correctly described as cross-platform and most examples use CLI commands applicable to all OSes, there are notable instances where Windows-specific tools, paths, and instructions are mentioned first or exclusively. For example, the location of zone files for Windows DNS is described in detail, while BIND (Linux/Unix) is mentioned only briefly. The verification section provides a Windows Command Prompt nslookup example, with no equivalent Linux/macOS shell example. There are no PowerShell-specific commands, but the overall pattern favors Windows context and tools.
Recommendations
- Provide explicit Linux/macOS shell examples alongside Windows Command Prompt examples, especially for verification steps (e.g., show nslookup usage in bash/zsh).
- Describe the location of BIND zone files in more detail, similar to the Windows DNS section.
- When referencing file paths, include both Windows and Linux/macOS formats.
- Avoid phrases like 'Use Windows Command Prompt' unless alternatives for other platforms are also given.
- Consider listing Linux/BIND instructions before or alongside Windows DNS instructions to balance presentation.
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
Missing Linux Example
Summary
The documentation provides both Azure CLI and Azure PowerShell instructions for verifying results, but the PowerShell examples are included as a separate tab, and there is no explicit mention of Linux/macOS shell environments or commands (e.g., bash, zsh). The Azure CLI examples are cross-platform, but the PowerShell tab and variable assignment syntax ($resource_group_name=$(terraform output -raw resource_group_name)) may confuse Linux users, as PowerShell is primarily Windows-centric and not the default on Linux/macOS. There are no Linux-specific troubleshooting steps, nor is there mention of shell-specific differences or requirements.
Recommendations
- Clarify that Azure CLI commands work on Linux/macOS and Windows, and provide explicit bash/zsh syntax for variable assignment (e.g., resource_group_name=$(terraform output -raw resource_group_name)).
- Add a note or tab for Linux/macOS users, highlighting any differences in command usage or environment setup.
- Ensure troubleshooting and cleanup instructions mention cross-platform compatibility and provide examples for both bash and PowerShell where relevant.
- Consider listing Azure CLI (cross-platform) instructions before PowerShell, or clarify their parity.
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 presenting command prompt (cmd.exe) and nslookup examples first, and referencing Windows-specific tools (cmd.exe) for DNS resolution steps. However, it also uses 'dig', which is available on Linux/macOS, and does not rely on PowerShell or other Windows-only utilities. No Linux/macOS-specific instructions or screenshots are provided, but the core steps are platform-agnostic.
Recommendations
- Include explicit Linux/macOS terminal examples (e.g., using bash, zsh) for DNS queries.
- Clarify that 'dig' is available on Linux/macOS and provide installation instructions if needed.
- Add screenshots or instructions for running DNS queries from Linux/macOS VMs in Azure.
- Avoid using Windows command prompt syntax (C:\>) as the default prompt; use generic or OS-specific prompts as appropriate.
- Mention that the Azure portal steps are identical across platforms.
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 the equivalent for BIND (Linux). Windows-specific paths and tools are referenced, and Windows DNS is listed before BIND in the section on obtaining zone files. However, all CLI examples use Azure CLI, which is cross-platform, and there are no PowerShell-only or Windows-only command examples.
Recommendations
- List BIND (Linux) before Windows DNS when describing how to obtain zone files, as BIND is more commonly used in cross-platform and cloud environments.
- Provide explicit examples for both Linux and Windows paths and commands where relevant, ensuring parity.
- Add notes or examples for macOS users if there are any platform-specific considerations.
- Avoid referencing Windows tools or paths first unless there is a clear reason for prioritizing Windows.
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 location is described less directly. No Linux/macOS-specific tools or file paths are shown, and screenshots and examples are platform-neutral (portal-based), but the initial orientation favors Windows. There are no PowerShell examples, but Windows DNS is referenced first and more concretely.
Recommendations
- List BIND (Linux/Unix) before or alongside Windows DNS when discussing zone file locations.
- Provide explicit example paths for BIND zone files (e.g., /etc/bind/zones/).
- Clarify how to obtain zone files from Linux/macOS systems, including common commands (e.g., cp, scp) and file locations.
- Add a note that the Azure portal workflow is platform-agnostic and does not require Windows.
- If mentioning Windows-specific details, ensure Linux/macOS equivalents are provided with equal prominence.
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 exhibits mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section and referencing PowerShell as a primary tool for getting started. While Azure CLI is mentioned, there are no explicit Linux/macOS-specific examples or guidance, and no mention of Linux-native DNS tools or workflows. The documentation assumes familiarity with Windows-centric tooling and does not provide parity for Linux/macOS users in terms of examples or tool recommendations.
Recommendations
- Present Azure CLI examples before or alongside Azure PowerShell, as CLI is cross-platform and preferred by many Linux/macOS users.
- Explicitly mention that Azure CLI works on Linux/macOS and provide links or instructions for installation on those platforms.
- Include references to Linux-native DNS tools (e.g., dig, nslookup) for troubleshooting or validation steps.
- Add a section or note highlighting cross-platform compatibility and best practices for Linux/macOS administrators.
- Ensure that all critical workflows have both PowerShell and CLI examples, with equal prominence.
Low Priority
View Details →
Detected Bias Types
Powershell Heavy
Windows First
Summary
The documentation page exhibits mild Windows bias in its 'Next steps' section, where it suggests learning how to create an Azure DNS Private Resolver using Azure PowerShell or the Azure portal, but does not mention Azure CLI or provide Linux/macOS-specific guidance. PowerShell is a Windows-centric tool, and its mention before any cross-platform alternatives may create friction for Linux/macOS users.
Recommendations
- Add instructions and links for creating an Azure DNS Private Resolver using Azure CLI, which is cross-platform and widely used on Linux/macOS.
- Explicitly mention that Azure PowerShell is available on Linux/macOS, or clarify platform requirements for each tool.
- Ensure example commands and walkthroughs are provided for both PowerShell and Azure CLI, with parity in detail and order.
- Consider listing Azure CLI before PowerShell, or presenting both together to avoid implicit prioritization.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting examples, commands, or tools. However, where DNS resolution is discussed, it refers to 'your local PC' and 'corporate networks' without specifying operating systems, and does not provide any command-line examples (such as dig, nslookup, or PowerShell equivalents) for either Windows or Linux. No Windows-specific tools or patterns are mentioned, but the lack of Linux-specific examples or explicit parity is a subtle bias.
Recommendations
- Add troubleshooting examples using common DNS tools for both Windows (e.g., nslookup, PowerShell Resolve-DnsName) and Linux (e.g., dig, host, nslookup).
- Explicitly mention how to perform DNS queries and troubleshooting steps on both Windows and Linux systems.
- Include command-line snippets for both platforms when discussing DNS resolution and record verification.
- Reference platform-specific documentation or guides for DNS troubleshooting where appropriate.
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any platform-specific troubleshooting commands or examples (such as PowerShell, Windows command line, or Linux shell tools). However, when suggesting how to check DNS resolution, it recommends using web-based tools (e.g., digwebinterface) and does not mention native command-line tools like 'dig' or 'nslookup' for either Windows or Linux. This omission may disadvantage Linux users, as it does not acknowledge or instruct on using common Linux DNS troubleshooting tools.
Recommendations
- Add examples using native command-line tools for both Windows (e.g., 'nslookup') and Linux (e.g., 'dig', 'host').
- Explicitly mention how to run DNS queries from Linux and Windows terminals, including sample commands.
- Where troubleshooting steps involve checking DNS resolution, provide parity by listing both web-based and OS-native methods.
- Consider including a table or section comparing DNS troubleshooting commands across platforms.
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
Summary
The documentation mentions Windows DNS before BIND when describing how to obtain an existing DNS zone file, and provides explicit details for Windows (default folder, DNS console) before briefly mentioning BIND (Linux/Unix) and its configuration file. No PowerShell examples or Windows-only tools are used, and the main workflow is platform-neutral via the Azure portal. However, the ordering and detail level show mild Windows-first bias.
Recommendations
- Present instructions for obtaining zone files from BIND (Linux/Unix) before or alongside Windows DNS, with equal detail (e.g., typical BIND zone file locations such as /etc/bind/).
- Include example commands for copying or viewing zone files on Linux (e.g., using cat, cp, or ls).
- Clarify that the Azure portal workflow is OS-agnostic and accessible from any platform.
- If mentioning Windows-specific paths or tools, provide equivalent Linux/Unix paths and commands for parity.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-troubleshoot.md
.../azure-docs/blob/main/articles/dns/dns-troubleshoot.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation does not provide any OS-specific troubleshooting commands or examples, but it does mention using the Azure portal and web-based tools for DNS troubleshooting. There is no explicit Windows bias (no PowerShell, Windows tools, or Windows-first patterns), but there is a lack of parity in that no Linux command-line examples (e.g., dig, nslookup) are given for DNS troubleshooting, nor is there mention of using Linux tools for DNS validation.
Recommendations
- Add troubleshooting examples using common Linux command-line tools such as dig and nslookup, showing how to query Azure DNS records from Linux systems.
- Include instructions or examples for validating DNS delegation and record resolution using Linux shell commands.
- Explicitly mention that the troubleshooting steps apply equally to both Windows and Linux environments, and provide parity in tool recommendations.
- If referencing the Azure portal, clarify that it is cross-platform and accessible from any OS.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export-portal.md
.../main/articles/dns/private-dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows DNS as a source for zone files before mentioning BIND (the most common DNS server on Linux/Unix). The Windows DNS file path is described in detail, while the BIND example is more generic. No PowerShell or Windows-specific command-line tools are used, and the main workflow is through the Azure portal, which is cross-platform. However, the ordering and detail given to Windows DNS is evidence of a subtle 'windows_first' bias.
Recommendations
- List BIND (Linux/Unix) as a source for zone files before or alongside Windows DNS, and provide an example BIND zone file path (e.g., '/etc/bind/zones/db.example.com').
- Offer more detail for BIND users, such as how to locate the zone file using 'named.conf' or typical Linux file locations.
- Ensure that all references to obtaining zone files are platform-neutral, or provide equal detail for both Windows and Linux/Unix environments.
- Consider including a note or link for MacOS users, if relevant.
- Review future documentation for ordering and depth of platform-specific instructions to ensure parity.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/dns-import-export-portal.md
...ocs/blob/main/articles/dns/dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows DNS as a source for zone files before BIND (the most common Linux DNS server), and provides the Windows DNS file path explicitly, while only referencing BIND's configuration file generically. There are no command-line or tool-specific examples for either platform, but the ordering and detail favor Windows.
Recommendations
- List BIND (Linux/Unix) as a source for zone files before or alongside Windows DNS, reflecting its prevalence in non-Windows environments.
- Provide the typical BIND zone file path (e.g., /etc/bind/zones/) as an example, similar to the explicit Windows path.
- Add a brief note or example for exporting a zone file from BIND (e.g., using 'cp' or 'cat' to copy the file), to match the specificity given for Windows.
- Ensure parity in detail and ordering when describing both Windows and Linux/Unix DNS systems.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-privatednszone.md
...s/blob/main/articles/dns/private-dns-privatednszone.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation page exhibits a mild 'windows_first' bias in the 'Next steps' section, where Azure PowerShell (primarily associated with Windows environments) is mentioned before Azure CLI (which is cross-platform and widely used on Linux). There are no explicit examples or instructions that are Windows- or PowerShell-specific in the main content, and Linux tools or patterns are not omitted, but the ordering subtly prioritizes Windows tooling.
Recommendations
- List Azure CLI before Azure PowerShell in the 'Next steps' section, as CLI is cross-platform and more familiar to Linux users.
- Wherever possible, provide parallel examples or links for both PowerShell and CLI, and clarify the cross-platform nature of Azure CLI.
- Review other related documentation to ensure Linux and macOS users are equally supported and addressed, especially in introductory or 'getting started' materials.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/private-dns-import-export-portal.md
.../main/articles/dns/private-dns-import-export-portal.md
Low Priority
View Details →
Detected Bias Types
Windows First
Summary
The documentation mentions Windows DNS and its default zone file location before mentioning BIND (the most common DNS server on Linux/Unix). No Linux-specific tools or commands are provided, but both Windows and Linux are referenced in the context of obtaining zone files. No PowerShell or Windows-only command-line examples are present, and the main workflow is via the Azure portal (cross-platform). However, the order of presentation gives Windows DNS precedence.
Recommendations
- List BIND (Linux/Unix) before Windows DNS when discussing sources of zone files, or present both in parallel to avoid perceived prioritization.
- Provide explicit examples or references for obtaining zone files from both Windows DNS and BIND (e.g., sample commands or file paths for both platforms).
- If mentioning default file paths, clarify that %systemroot% is Windows-specific and provide the typical BIND zone file path (e.g., /etc/bind/ or /var/named/).
- Consider including a table or section summarizing how to obtain zone files from common DNS servers on both Windows and Linux.
DNS
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/dns/tutorial-public-dns-zones-child.md
...b/main/articles/dns/tutorial-public-dns-zones-child.md
Low Priority
View Details →
Detected Bias Types
Missing Linux Example
Summary
The documentation exclusively uses the Azure Portal (web UI) for all instructions and does not provide any command-line examples for either Windows (PowerShell/Command Prompt) or Linux (Bash/CLI). However, there is an implicit bias in that no CLI-based (cross-platform) instructions are given, which are often preferred by Linux users and automation scenarios. There are no references to Windows-specific tools, but the lack of Azure CLI or Bash examples means Linux users do not see parity with their typical workflows.
Recommendations
- Add Azure CLI examples for all major steps (creating child DNS zones, verifying NS records, deleting resources), as Azure CLI is cross-platform and widely used on Linux.
- If possible, provide both Azure CLI and PowerShell examples, but ensure CLI examples are presented first or equally to avoid Windows-first bias.
- Include a note or section on how to perform these tasks via command line for automation and scripting scenarios, which are common in Linux environments.
- Reference relevant documentation for Azure CLI DNS zone management.