Document Details

Dns Reverse Dns Hosting
Home / Scan 41 / Dns Reverse Dns Hosting
❌
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.
GitHub View on GitHub 📚 View on Microsoft Learn

Bias Analysis

Bias Types:
⚠️ powershell_heavy
⚠️ windows_first
⚠️ windows_tools
Summary:
The documentation consistently presents Azure PowerShell (a Windows-centric tool) examples before Azure CLI, and includes PowerShell-specific instructions and screenshots. There is a strong emphasis on PowerShell usage throughout, which may suggest a Windows-first approach. While Azure CLI is cross-platform and included, there are no Linux shell-specific examples or references, and no mention of Linux-native tools or workflows. The documentation does not provide parity in terms of Linux command-line usage or guidance for Linux administrators.
Recommendations:
  • Provide Linux shell (bash) command examples where appropriate, especially for DNS-related tasks that could be performed outside Azure CLI.
  • Include explicit notes that Azure CLI commands work identically on Linux, macOS, and Windows, and consider demonstrating usage in a Linux terminal.
  • Balance the order of examples by sometimes presenting Azure CLI before PowerShell, or grouping them together without a clear preference.
  • Reference Linux-native DNS tools (such as dig, nslookup, or host) for verification steps, and provide example commands for checking DNS records from a Linux environment.
  • Add screenshots or terminal outputs from Linux environments to illustrate cross-platform compatibility.
  • Clarify that Azure PowerShell is available on non-Windows platforms, but that Azure CLI is often preferred for Linux users.
GitHub Create pull request

Scan History

Date Scan ID Status Bias Status
2025-07-12 23:44 #41 in_progress ❌ Biased
2025-07-12 00:58 #8 cancelled ✅ Clean
2025-07-10 05:06 #7 processing ✅ Clean

Flagged Code Snippets

### IPv6 The following example explains the process of creating new PTR record for IPv6. To learn more about record types or how to modify existing records, see [Manage DNS records and record sets](dns-operations-recordsets-portal.md). 1. At the top of the reverse DNS zone **Overview** page, select **Record sets** and then select **+Add**. ![A screenshot of how to add an IPv6 reverse DNS record to a DNS zone.](./media/dns-reverse-dns-hosting/create-record-set-ipv6.png) 1. The name of the record set for a PTR record is the rest of the IPv6 address in reverse order. It must not include any zero compression. In this example, the first 64 bits of the IPv6 gets populated as part of the zone name (0.0.0.0.c.d.b.a.8.b.d.0.1.0.0.2.ip6.arpa). That's why only the last 64 bits are supplied in the **Name** box. The last 64 bits of the IP address gets entered in reverse order, with a period as the delimiter between each hexadecimal number. Name your record set **e.5.0.4.9.f.a.1.c.b.0.1.4.2.5.f** if you have a resource whose IP address is 2001:0db8:abdc:0000:f524:10bc:1af9:405e. :::image type="content" source="./media/dns-reverse-dns-hosting/create-ipv6-ptr.png" alt-text="Screenshot of create IPv6 pointer record."::: 1. For *Type*, select **PTR**. 1. For *DOMAIN NAME*, enter the FQDN of the resource that uses the IP. 1. Select **OK** to create the DNS record. The following examples show how to complete this task by using PowerShell or Azure CLI. #### PowerShell
## View records To view the records that you created, browse to your DNS zone in the Azure portal. In the lower part of the **DNS zone** pane, you can see the records for the DNS zone. You should see the default NS and SOA records, plus any new records that you've created. The NS and SOA records are created in every zone. ### IPv4 The **DNS zone** page shows the IPv4 PTR record: :::image type="content" source="./media/dns-reverse-dns-hosting/view-ipv4-ptr-record.png" alt-text="Screenshot of IPv4 pointer record on overview page." lightbox="./media/dns-reverse-dns-hosting/view-ipv4-ptr-record.png"::: The following examples show how to view the PTR records by using Azure PowerShell and Azure CLI. #### PowerShell
### IPv6 The **DNS zone** page shows the IPv6 PTR record: :::image type="content" source="./media/dns-reverse-dns-hosting/view-ipv6-ptr-record.png" alt-text="Screenshot of IPv6 pointer record on overview page." lightbox="./media/dns-reverse-dns-hosting/view-ipv6-ptr-record.png"::: The following examples show how to view the records by using PowerShell or Azure CLI. #### PowerShell
### IPv6 The name of an IPv6 reverse lookup zone should be in the following form: `<IPv6 network prefix in reverse order>.ip6.arpa`. For examples, see [Overview of reverse DNS](dns-reverse-dns-overview.md#ipv6) for IPv6. The following example shows how to create an IPv6 reverse DNS lookup zone named `0.0.0.0.d.c.b.a.8.b.d.0.1.0.0.2.ip6.arpa` in Azure DNS via the Azure portal: :::image type="content" source="./media/dns-reverse-dns-hosting/ipv6-arpa-zone.png" alt-text="Screenshot of create IPv6 arpa DNS zone."::: The following examples show how to complete this task using Azure PowerShell and Azure CLI. #### PowerShell
## Delegate a reverse DNS lookup zone Once the reverse DNS lookup zone gets created, you then need to make sure the zone gets delegated from the parent zone. DNS delegation enables the DNS name resolution process to find the name servers that host your reverse DNS lookup zone. Those name servers can then answer DNS reverse queries for the IP addresses in your address range. For forward lookup zones, the process of delegating a DNS zone is described in [Delegate your domain to Azure DNS](dns-delegate-domain-azure-dns.md). Delegation for reverse lookup zones works the same way. The only difference is that you need to configure the name servers with the ISP. The ISP manages your IP range, that's why they need to update the name servers instead of domain name registrar. ## Create a DNS PTR record ### IPv4 The following example explains the process of creating a PTR record for a reverse DNS zone in Azure DNS. To learn more about record types or how to modify existing records, see [Manage DNS records and record sets](dns-operations-recordsets-portal.md). 1. At the top of the reverse DNS zone **Overview** page, select **Record sets** and then select **+Add**. ![A screenshot of how to add an IPv4 reverse DNS record to a DNS zone.](./media/dns-reverse-dns-hosting/create-record-set-ipv4.png) 2. The name of the record set for a PTR record is the rest of the IPv4 address in reverse order. In this example, the first three octets are already populated as part of the zone name `.2.0.192`. That's why only the last octet is needed in the **Name** box. For example, give your record set the name of **15** for a resource whose IP address is `192.0.2.15`. :::image type="content" source="./media/dns-reverse-dns-hosting/create-ipv4-ptr.png" alt-text="Screenshot of create IPv4 pointer record."::: 3. For *Type*, select **PTR**. 4. For *DOMAIN NAME*, enter the fully qualified domain name (FQDN) of the resource that uses the IP. 5. Select **Add** to create the reverse DNS record. The following examples show how to complete this task by using Azure PowerShell and Azure CLI. #### PowerShell