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 201-225 of 323 flagged pages
DNS Overview of DNS security policy ...ure-docs/blob/main/articles/dns/dns-security-policy.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation mentions Azure PowerShell as a configuration method for DNS security policy but does not mention or provide examples for cross-platform tools like Azure CLI, Bash, or Linux-native workflows. No Linux/macOS-specific instructions or parity are provided, and the only automation tool referenced is PowerShell, which is primarily associated with Windows environments.
Recommendations
  • Add instructions and examples for configuring DNS security policy using Azure CLI, which is cross-platform and widely used on Linux/macOS.
  • Explicitly state that the Azure portal and Azure CLI are supported on all platforms, including Linux and macOS.
  • Provide sample commands for both PowerShell and Azure CLI side-by-side in relevant sections.
  • Include a note clarifying that PowerShell Core is available on Linux/macOS, if PowerShell is required, and link to installation instructions.
GitHub Create Pull Request
DNS Secure and view DNS traffic - Azure DNS ...-docs/blob/main/articles/dns/dns-traffic-log-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Windows First Missing Linux Example
Summary
The documentation page exhibits a notable Windows bias. PowerShell is the only CLI method described in detail, with extensive Windows-centric instructions (e.g., using C:\ paths, Register-PSRepository, and Windows environment variables). There are no equivalent Linux/macOS CLI examples (such as Azure CLI, Bash, or cross-platform scripting). Windows tools and patterns (PowerShell, Windows paths, Windows environment variables) are mentioned exclusively and before any Linux alternatives. The lack of Linux/macOS instructions may hinder non-Windows users from following the guide without significant adaptation.
Recommendations
  • Add Azure CLI and Bash examples for all PowerShell instructions, ensuring parity for Linux/macOS users.
  • Provide guidance for installing and using Az.DnsResolver via Azure CLI or REST API, which are cross-platform.
  • Replace or supplement Windows-specific paths (e.g., C:\bin\PSRepo) with Linux/macOS equivalents (e.g., ~/bin/PSRepo).
  • Clarify environment variable usage for Linux/macOS shells (e.g., $USER instead of $env:USER).
  • Include instructions for running DNS queries and tests from Linux/macOS (e.g., using dig, nslookup, or host commands).
  • Explicitly state cross-platform compatibility and provide troubleshooting tips for non-Windows environments.
GitHub Create Pull Request
DNS Tutorial: Create Custom Azure DNS Records For a Web App .../blob/main/articles/dns/dns-web-sites-custom-domain.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation shows a moderate Windows bias. While it provides Azure Portal, PowerShell, and Azure CLI instructions for all major steps, Windows/PowerShell examples and terminology are consistently presented before Linux-friendly alternatives. The only explicit example of DNS record testing uses Windows-style nslookup output and command prompt, with no mention of Linux/macOS equivalents. PowerShell is highlighted as a primary automation method, and Windows-centric tools (like PowerShell and nslookup with Windows prompt) are referenced without Linux parity notes.
Recommendations
  • Include Linux/macOS-specific instructions and examples for DNS record testing (e.g., show dig and nslookup output from a Linux shell).
  • Present CLI examples before or alongside PowerShell to avoid Windows-first ordering.
  • Add notes clarifying that Azure CLI works cross-platform and provide installation/usage tips for Linux/macOS users.
  • Explicitly mention Linux/macOS compatibility in prerequisites and tool selection sections.
  • Where PowerShell is referenced, add Bash or shell script equivalents for automation.
GitHub Create Pull Request
DNS Quickstart - Create an Azure private DNS zone using the Azure CLI ...s/blob/main/articles/dns/private-dns-getstarted-cli.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias, especially in the testing section. All VM creation examples use Windows images, and all instructions for configuring firewalls and testing DNS resolution are given exclusively for Windows (PowerShell commands, Windows firewall, and Windows command prompt outputs). There are no Linux VM creation examples, nor any Linux-specific instructions for configuring ICMP or testing DNS resolution. Windows tools and patterns are mentioned exclusively and before any Linux equivalents (which are absent).
Recommendations
  • Include Linux VM creation examples (e.g., using --image UbuntuLTS) alongside or instead of Windows examples.
  • Provide Linux instructions for configuring the firewall to allow ICMP (e.g., using ufw or firewalld).
  • Show how to test DNS resolution on Linux VMs (e.g., using ping, dig, or nslookup from a bash shell).
  • Present both Windows and Linux examples in parallel, or alternate which OS is shown first.
  • Clarify that the steps apply to both Windows and Linux, and note any OS-specific differences.
GitHub Create Pull Request
DNS How to sign your Azure Public DNS zone with DNSSEC ...ocs/azure-docs/blob/main/articles/dns/dnssec-how-to.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation provides three main tabs for signing a DNS zone: Azure Portal, Azure CLI, and PowerShell. The PowerShell tab is Windows-centric, and PowerShell examples are given in detail. The CLI tab uses Azure CLI, which is cross-platform, but references 'dig.exe' (a Windows-specific executable name) for DNS queries, rather than the generic 'dig' command. The ordering of tabs places PowerShell as a first-class citizen, and there is no mention of Linux/macOS-specific shell usage or examples (e.g., Bash, zsh). There are no explicit Linux/macOS examples or screenshots, and the only command-line tool mentioned outside Azure CLI is 'dig.exe', which may confuse non-Windows users.
Recommendations
  • Replace references to 'dig.exe' with 'dig', and clarify that 'dig' is available on Linux/macOS and can be installed on Windows.
  • Add explicit Bash/zsh examples for querying DS records, e.g., using 'dig' and 'jq' on Linux/macOS.
  • Clarify that Azure CLI commands work on all platforms and provide example shell environments for Linux/macOS.
  • Add screenshots or instructions for Linux/macOS environments where relevant.
  • Consider reordering tabs or examples so that cross-platform tools (Azure CLI) are presented before Windows-specific tools (PowerShell).
GitHub Create Pull Request
DNS Overview of DNSSEC - Azure Public DNS ...rosoftDocs/azure-docs/blob/main/articles/dns/dnssec.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy 🔧 Windows Tools
Summary
The documentation page demonstrates a moderate Windows bias. Windows tools and patterns (e.g., PowerShell's Resolve-DnsName) are presented first and in greater detail, with multiple PowerShell examples and references to Windows-specific features like Group Policy and NRPT. While dig is mentioned and shown, it is presented as 'dig.exe' and in a Windows command prompt context, rather than as the standard Linux/macOS tool. There are no explicit Linux/macOS examples or mentions of Linux-native DNS tools (e.g., host, drill), nor are Linux command-line environments referenced.
Recommendations
  • Add Linux/macOS-specific examples using dig in a native shell (e.g., $ dig contoso.com +dnssec), not just Windows cmd.exe.
  • Include references to other common DNS tools available on Linux/macOS, such as host or drill, and provide example usage.
  • Present examples for both Windows and Linux/macOS side-by-side, or alternate which platform is shown first.
  • Clarify that dig is a cross-platform tool and provide installation instructions for Linux/macOS if needed.
  • Mention how DNSSEC validation can be enforced or configured on Linux/macOS clients and servers (e.g., Unbound, BIND).
  • Avoid referring to dig as 'dig.exe', which is a Windows-specific notation.
GitHub Create Pull Request
DNS Quickstart - Create an Azure private DNS zone using the Azure portal ...lob/main/articles/dns/private-dns-getstarted-portal.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools Powershell Heavy
Summary
The documentation demonstrates a notable Windows bias by exclusively using Windows Server as the test VM, referencing RDP for access, and providing only PowerShell-based examples for command execution (e.g., RunPowerShellScript). There are no Linux VM creation or SSH access examples, nor are Linux command-line tools (like bash or dig) mentioned for DNS testing. The documentation assumes a Windows environment throughout the quickstart steps.
Recommendations
  • Include parallel instructions for creating a Linux VM (e.g., Ubuntu) and accessing it via SSH.
  • Provide Linux shell command examples (e.g., using bash and dig/nslookup) for DNS resolution testing.
  • Show how to use the Azure portal's Run Command feature with Linux VMs (e.g., RunShellScript).
  • Mention Linux/macOS equivalents for VM access (SSH instead of RDP) and command execution.
  • Ensure screenshots and walkthroughs include both Windows and Linux scenarios where applicable.
GitHub Create Pull Request
DNS Resolve Azure and on-premises domains. .../blob/main/articles/dns/private-resolver-hybrid-dns.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example 🔧 Windows Tools
Summary
The documentation page demonstrates a notable Windows bias. Examples and procedures for configuring on-premises DNS are exclusively shown using Windows DNS Server, with no mention of Linux-based DNS solutions (e.g., BIND). Quickstarts and next steps prioritize PowerShell and Windows-centric workflows, with CLI options mentioned but not emphasized. There are no Linux/macOS-specific instructions or screenshots, and the conditional forwarder configuration is only illustrated for Windows DNS.
Recommendations
  • Add explicit instructions and screenshots for configuring conditional forwarders on popular Linux DNS servers (e.g., BIND, Unbound).
  • Include Linux/macOS CLI examples for DNS queries (e.g., using dig or nslookup).
  • Present CLI and PowerShell examples side-by-side, or provide parity in walkthroughs for both platforms.
  • Mention Linux DNS server alternatives in the 'Configure on-premises DNS conditional forwarders' section.
  • Ensure that Linux/macOS users are guided on how to complete all critical steps, not just Windows users.
GitHub Create Pull Request
DNS Tutorial: Create an Azure DNS alias record to refer to an Azure public IP address ...zure-docs/blob/main/articles/dns/tutorial-alias-pip.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Missing Linux Example 🔧 Windows Tools
Summary
The tutorial exclusively uses Windows Server for the virtual machine example, including instructions for installing IIS via Windows Server Manager and connecting via RDP. There are no Linux-based VM examples, nor instructions for deploying a Linux web server (e.g., Apache or Nginx) or connecting via SSH. All screenshots and step-by-step guidance are tailored to Windows environments, which may exclude or confuse Linux/macOS users.
Recommendations
  • Add parallel instructions for creating a Linux VM (e.g., Ubuntu) and installing a web server (Apache/Nginx) using SSH.
  • Provide Linux command-line examples for web server installation and verification.
  • Include screenshots or terminal output relevant to Linux environments.
  • Clarify that the alias record steps are OS-agnostic and can be used with any VM type.
  • Consider presenting both Windows and Linux options side-by-side, or allow users to choose their preferred platform at the start of the tutorial.
GitHub Create Pull Request
DNS Create and manage reverse DNS zones in Azure Private DNS ...ure-docs/blob/main/articles/dns/private-reverse-dns.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 3 bias types
Detected Bias Types
Windows First Powershell Heavy Missing Linux Example
Summary
The documentation provides only a Windows/Powershell example for testing DNS resolution (nslookup), with the command prompt shown as 'C:\>' and PowerShell syntax. There are no Linux/macOS equivalents (e.g., Bash shell, dig command) shown, and the example is presented as the sole method for verification, which may create friction for non-Windows users.
Recommendations
  • Include Linux/macOS examples for DNS resolution, such as using 'nslookup' or 'dig' from a Bash shell.
  • Show command output from a Linux terminal (e.g., '$ nslookup 10.1.2.5' or '$ dig -x 10.1.2.5') alongside the Windows example.
  • Clarify that the steps are platform-agnostic and that any OS with DNS utilities can be used.
  • Avoid showing only Windows command prompts; provide parity in screenshots and instructions.
GitHub Create Pull Request
DNS Tutorial - Set up DNS failover using private resolvers ...articles/dns/tutorial-dns-private-resolver-failover.md
Medium Priority View Details →
Scanned: 2026-01-13 00:00
Reviewed by: LLM Analysis
Issues: 4 bias types
Detected Bias Types
Powershell Heavy 🔧 Windows Tools Missing Linux Example Windows First
Summary
The documentation demonstrates a notable Windows bias, especially in the section on configuring on-premises DNS forwarding. Only Windows Server and PowerShell instructions are provided, with no equivalent guidance for Linux-based DNS servers (e.g., BIND). The use of Windows-specific tools and terminology (PowerShell, DNS console) is exclusive, and Linux alternatives are not mentioned or linked. Windows command-line examples (nslookup) are shown, but these are generally cross-platform. The overall flow assumes a Windows environment for on-premises DNS management.
Recommendations
  • Add step-by-step instructions for configuring conditional forwarders on common Linux DNS servers, such as BIND/named.
  • Include Linux command-line examples for DNS queries (e.g., dig, host) alongside nslookup.
  • Explicitly mention that the procedure applies to both Windows and Linux DNS servers, and provide links to relevant Linux documentation.
  • Present Windows and Linux examples in parallel or clearly label them, rather than only showing Windows.
  • Consider adding a table comparing steps for Windows and Linux environments.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver - Azure Resource Manager template (ARM template) ...icles/dns/dns-private-resolver-get-started-template.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and PowerShell examples for deploying the ARM template, but PowerShell is given equal prominence as CLI, despite PowerShell being primarily a Windows tool. There are no Linux shell-specific examples (e.g., Bash), nor is there mention of Linux-native tooling or workflows. The order of presentation does not prioritize Linux, and PowerShell is included as a main tab, which may signal a Windows-centric approach.
Recommendations
  • Add explicit Bash examples for Linux users, especially for common deployment scenarios.
  • Clarify that Azure CLI commands work cross-platform and can be run on Linux, macOS, and Windows.
  • Consider listing CLI/Bash examples before PowerShell to signal Linux parity.
  • Mention installation or usage notes for CLI on Linux systems.
  • If PowerShell is included, note that PowerShell Core is available cross-platform, but most Linux users will prefer Bash/CLI.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Azure CLI ...zure-docs/blob/main/articles/dns/dns-getstarted-cli.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a mild Windows bias in the 'Test the name resolution' section, where the instructions reference opening a 'command prompt' and show a screenshot of the Windows command prompt. The use of 'nslookup' is platform-neutral, but the visual and textual cues favor Windows. There are no Linux-specific instructions, examples, or screenshots for this step, and the documentation does not mention Linux terminal usage or alternative tools (e.g., dig).
Recommendations
  • Include instructions and screenshots for testing DNS resolution using a Linux or macOS terminal, not just Windows command prompt.
  • Mention that 'nslookup' is available on Linux and macOS, and provide equivalent commands for those platforms.
  • Consider referencing alternative DNS query tools such as 'dig', which are commonly used on Linux.
  • Use platform-neutral language such as 'open a terminal' instead of 'open a command prompt'.
  • If screenshots are provided, offer both Windows and Linux/macOS examples or use generic terminal screenshots.
GitHub Create Pull Request
DNS Quickstart: Use Terraform to configure private DNS zones in Azure ...s/blob/main/articles/dns/dns-private-zone-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a Windows bias by exclusively creating Windows virtual machines in the Terraform example, with no mention of Linux VM creation or Linux-specific configuration. The customer intent and checklist reinforce this focus on Windows. While Azure CLI and PowerShell verification steps are provided, there are no Linux shell or SSH examples for interacting with the created resources.
Recommendations
  • Include examples for creating Linux virtual machines alongside Windows VMs in the Terraform code and checklist.
  • Add verification steps using Linux shell commands (e.g., SSH into a Linux VM, use dig/nslookup for DNS verification) in addition to Azure CLI and PowerShell.
  • Update the customer intent and description to mention both Windows and Linux VM scenarios.
  • Provide parity in troubleshooting and cleanup instructions for both Windows and Linux environments.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS Private Resolver using Terraform ...cles/dns/dns-private-resolver-get-started-terraform.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 as the CLI examples. PowerShell is primarily a Windows tool, and its inclusion alongside CLI may suggest a slight Windows bias, especially since no explicit Linux shell examples (e.g., bash, sh) are provided. The variable assignment syntax in the PowerShell tab uses `$resource_group_name=$(terraform output -raw resource_group_name)`, which is not standard PowerShell and may confuse Linux users. There are no Linux-specific instructions or troubleshooting tips, and no mention of platform differences in running Terraform or Azure CLI/PowerShell.
Recommendations
  • Add explicit bash/Linux shell examples for all CLI commands, especially for variable assignment and command usage.
  • Clarify any platform-specific differences in running Terraform, Azure CLI, and PowerShell (e.g., installation, environment setup).
  • If PowerShell is included, note that it is available cross-platform, but provide guidance for Linux/macOS users on using bash/zsh.
  • Ensure troubleshooting and cleanup sections mention both Windows and Linux environments where relevant.
  • Consider listing Azure CLI (which is cross-platform) before PowerShell, or provide a clear note about platform compatibility.
GitHub Create Pull Request
DNS Delegate a subdomain - Azure DNS ...zure-docs/blob/main/articles/dns/delegate-subdomain.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line testing instructions using 'nslookup' and refers to 'command prompt' without specifying platform, which implicitly favors Windows. There are no examples or instructions for Linux or macOS users (e.g., using 'dig' or Linux terminal). All screenshots and UI references are platform-neutral (Azure portal), but command-line instructions lack Linux parity.
Recommendations
  • Include Linux/macOS equivalents for command-line instructions (e.g., show how to use 'dig' or 'nslookup' in a Linux terminal).
  • Clarify that 'nslookup' is available on multiple platforms and provide platform-specific instructions where necessary.
  • Add notes or examples for Linux users, such as opening a terminal and running 'dig www.engineering.adatum.com' or 'nslookup www.engineering.adatum.com'.
  • When referencing command-line tools, avoid assuming the user is on Windows; use neutral language like 'open a terminal or command prompt'.
GitHub Create Pull Request
DNS Tutorial: Host your domain in Azure DNS ...lob/main/articles/dns/dns-delegate-domain-azure-dns.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation provides command-line verification instructions using 'nslookup' from a 'command prompt', which implicitly suggests a Windows environment. No Linux-specific instructions or examples (such as using 'dig' or referencing Linux terminals) are provided. The only tool mentioned for DNS verification is 'nslookup', which is available on both platforms but is more commonly associated with Windows. There are no explicit PowerShell examples or Windows-only tools, but the phrasing and lack of Linux parity indicate a subtle Windows-first bias.
Recommendations
  • Include Linux-specific instructions and examples, such as using 'dig' for DNS verification.
  • Clarify that 'nslookup' is available on both Windows and Linux, and provide sample commands for both environments.
  • Mention how to open a terminal or shell on Linux, not just 'command prompt'.
  • Add a note or section for users on macOS/Linux, ensuring parity in tooling and instructions.
GitHub Create Pull Request
DNS Quickstart: Create an Azure DNS zone and record - Bicep ...e-docs/blob/main/articles/dns/dns-get-started-bicep.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for all steps, but PowerShell is featured equally alongside CLI, which can indicate a Windows bias since PowerShell is primarily a Windows tool (though it is available cross-platform). The use of PowerShell tabs and examples throughout may signal to Linux users that Windows tooling is expected or preferred. No Linux-specific shell examples (e.g., Bash) or explicit mention of Linux environments is present.
Recommendations
  • Clarify that Azure CLI commands work natively on Linux, macOS, and Windows, and consider mentioning Bash or shell environments explicitly.
  • Add notes or examples for running Azure CLI in Bash or other Linux shells to reinforce cross-platform support.
  • If PowerShell is included, specify that PowerShell Core is available cross-platform, or provide links to installation instructions for Linux/macOS.
  • Consider listing Azure CLI examples first, as CLI is more universally available across platforms than PowerShell.
  • Explicitly state that no Windows-only tools are required and that all steps can be performed on Linux, macOS, or Windows.
GitHub Create Pull Request
DNS Quickstart - Create an Azure DNS Private Resolver using the Azure portal ...rticles/dns/dns-private-resolver-get-started-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Missing Linux Example
Summary
The documentation page demonstrates a bias toward Windows by exclusively using the Azure portal for all instructions and only mentioning Azure PowerShell as an alternative. There are no references to Linux tools, CLI commands, or cross-platform automation methods (such as Azure CLI or Bash). The mention of PowerShell as the only alternative further reinforces a Windows-centric approach, and there are no examples or guidance for Linux users.
Recommendations
  • Add instructions and examples using Azure CLI (az), which is cross-platform and commonly used on Linux and macOS.
  • Explicitly mention that the Azure portal and Azure CLI are both supported, and provide links to Linux-friendly quickstarts.
  • Include sample Bash scripts or command-line steps for key actions (resource group creation, VNet setup, DNS resolver deployment) alongside portal and PowerShell instructions.
  • Ensure parity in troubleshooting and testing steps by including Linux-native DNS query tools (e.g., dig, nslookup) for verifying resolver functionality.
  • Review related documentation to ensure Linux and macOS users are equally supported in all quickstart and how-to guides.
GitHub Create Pull Request
DNS Azure Private DNS Zone Overview ...s/blob/main/articles/dns/private-dns-privatednszone.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates a mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which can imply a preference for Windows tooling. There are no explicit Linux examples or mentions of Linux-specific tools or patterns, and the page does not provide parity in example ordering or highlight cross-platform usage.
Recommendations
  • List Azure CLI before Azure PowerShell in example links or alternate their order to avoid perceived preference.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
  • Include example commands for both CLI and PowerShell in the main body, not just in linked articles.
  • Add a note or section on managing DNS with Linux-native tools (e.g., dig, resolvectl) where appropriate.
  • Ensure future documentation includes equal coverage and visibility for Linux and cross-platform workflows.
GitHub Create Pull Request
DNS Fallback to internet for Azure Private DNS zones ...re-docs/blob/main/articles/dns/private-dns-fallback.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation page demonstrates a Windows bias by consistently presenting command-line examples using Windows tools (cmd.exe, nslookup, dig) with Windows-style prompts (C:\>), and referencing command prompt usage on Azure virtual machines without mentioning Linux equivalents or shell environments. The examples and screenshots are Windows-centric, and there is no explicit guidance for Linux users or parity in example commands for bash or Linux shells.
Recommendations
  • Provide parallel Linux examples for DNS queries, using bash shell prompts (e.g., $ dig ...) and Linux tools (e.g., dig, host, nslookup) with appropriate output.
  • Explicitly mention that the steps can be performed on both Windows and Linux VMs, and clarify any differences in command syntax or expected output.
  • Include screenshots or terminal output from Linux environments alongside Windows examples.
  • Avoid using only Windows-style prompts (C:\>) in command examples; use generic or dual prompts (C:\> and $) where appropriate.
  • Add a note or section addressing Linux users, ensuring they are supported throughout the guide.
GitHub Create Pull Request
DNS Import and export a private DNS zone file - Azure portal .../main/articles/dns/private-dns-import-export-portal.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
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 Linux DNS server). It provides explicit details for Windows DNS (folder path, console tab) while only briefly referencing BIND's configuration. No Linux-specific tools or commands are discussed, and Windows is presented first in the section on obtaining zone files.
Recommendations
  • Present Linux/BIND instructions before or alongside Windows instructions when discussing zone file locations.
  • Provide explicit examples for BIND, such as typical zone file paths (e.g., /etc/bind/zones/) and how to locate them in named.conf.
  • Mention other common Linux DNS servers (e.g., Unbound, PowerDNS) and how to obtain zone files from them.
  • Include references to Linux command-line tools (e.g., cat, cp, scp) for handling zone files.
  • Ensure parity in detail and clarity between Windows and Linux instructions throughout the documentation.
GitHub Create Pull Request
DNS What is a virtual network link subresource of Azure DNS private zones ...main/articles/dns/private-dns-virtual-network-links.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Powershell Heavy Windows First
Summary
The documentation page shows mild Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which may suggest a preference for Windows-centric tooling. There is no explicit Linux example or mention of Linux-specific patterns, and PowerShell (traditionally Windows-focused) is highlighted as a primary automation method.
Recommendations
  • List Azure CLI before Azure PowerShell in examples and 'Next steps' to reflect cross-platform parity, as CLI is natively supported on Linux and macOS.
  • Explicitly mention that both Azure CLI and PowerShell are cross-platform, and provide guidance for Linux/macOS users where relevant.
  • Include example links or instructions for using Bash or other Linux-native tools where appropriate.
  • Avoid implying PowerShell is the default or preferred method for automation unless justified by feature differences.
GitHub Create Pull Request
DNS Import and export a domain zone file for Azure private DNS - Azure CLI ...cs/blob/main/articles/dns/private-dns-import-export.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First 🔧 Windows Tools
Summary
The documentation mentions Windows DNS and its default zone file location before describing BIND (Linux) equivalents. It provides explicit details for locating zone files on Windows, including folder paths and GUI references, while the Linux/BIND section is less detailed. The verification section references 'nslookup', a tool available on both platforms, but does not show platform-specific usage or alternatives. No PowerShell examples are present, and all CLI examples use Azure CLI, which is cross-platform.
Recommendations
  • Present BIND (Linux) instructions before Windows DNS instructions, or provide them in parallel for equal prominence.
  • Expand the BIND section to include example paths (e.g., /etc/bind/zones) and commands for locating zone files, similar to the Windows details.
  • Include Linux-specific verification examples, such as using 'dig' in addition to 'nslookup', and clarify usage on both platforms.
  • Add notes or links for Linux users on installing and using Azure CLI, and mention any platform-specific considerations for file paths or permissions.
GitHub Create Pull Request
DNS What is autoregistration feature in Azure DNS private zones? ...blob/main/articles/dns/private-dns-autoregistration.md
Medium Priority View Details →
Scanned: 2026-01-11 00:00
Reviewed by: LLM Analysis
Issues: 2 bias types
Detected Bias Types
Windows First Powershell Heavy
Summary
The documentation page demonstrates Windows bias by listing Azure PowerShell before Azure CLI in the 'Next steps' section, which subtly prioritizes Windows tooling. The primary example for enabling autoregistration is via the Azure portal UI, which is platform-neutral, but the order of command-line tool references favors Windows users. No Linux-specific tools or examples are provided, and there is no mention of Bash, Linux shell, or cross-platform scripting.
Recommendations
  • List Azure CLI before Azure PowerShell when presenting command-line options, as CLI is cross-platform and more commonly used on Linux.
  • Explicitly mention that both Azure CLI and PowerShell are available on Windows, Linux, and macOS to avoid platform assumptions.
  • Provide example commands for both Azure CLI and PowerShell when describing how to enable autoregistration, ensuring parity.
  • Include a note or section highlighting Linux usage scenarios or considerations, if any exist.
  • Avoid language or ordering that implies Windows is the default or preferred platform.
GitHub Create Pull Request
← Previous Page 9 of 13 Next →