Skip to content

Commit 1d57946

Browse files
committed
minor edit
1 parent cc09c71 commit 1d57946

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

articles/dns/private-reverse-dns.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ In this article, you learn how to create a private reverse lookup DNS zone and a
1414

1515
## What is reverse DNS?
1616

17-
Reverse DNS (as the name indicates) is the opposite process to forward DNS. Reverse enables you to resolve an IP address to a name, whereas forward DNS resolves a name to an IP address. Azure Private DNS supports both IPv6 and IPv4 reverse DNS.
17+
Reverse DNS (as the name indicates) is the opposite process to forward DNS. Reverse enables you to resolve an IP address to a name (for example: 10.1.2.5 --> myvm.contoso.com), whereas forward DNS resolves a name to an IP address. Azure Private DNS supports both IPv6 and IPv4 reverse DNS.
1818

1919
### IPv6 reverse DNS
2020

@@ -28,6 +28,8 @@ IPv4 reverse DNS zones contain pointer (PTR) records and use the reserved domain
2828
- **1.10.in-addr.arpa** contains all PTR records for IPv4 addresses in the 10.1.0.0/16 address space.
2929
- **2.1.10.in-addr.arpa** contains only PTR records for IPv4 addresses in the 10.1.2.0/24 address space.
3030

31+
Private IPv4 reverse DNS zones are intended for use with private IP address space as defined in [RFC 1918](https://www.rfc-editor.org/info/rfc1918).
32+
3133
### IPv4 reverse DNS records
3234

3335
To create an IPv4 reverse DNS record in your zone, add the remaining IP address octets in reverse order into the appropriate in-addr.arpa zone and provide a fully qualified domain name value (also called a **ptrdname**). The number of remaining IP address octets depend on the scope of the reverse DNS zone. For example:
@@ -42,9 +44,9 @@ To create an IPv4 reverse DNS record in your zone, add the remaining IP address
4244
## Requirements and restrictions
4345

4446
- [Autoregistration](private-dns-autoregistration.md) isn't supported for reverse DNS.
45-
- A [virtual network link](private-dns-virtual-network-links.md) from the reverse zone is required to enable DNS resolution of PTR records.
47+
- A [virtual network link](private-dns-virtual-network-links.md) from the reverse zone is required to enable DNS resolution of PTR records. The process of [adding a virtual network link](#add-a-virtual-network-link) is demonstrated in this article. This is different from reverse DNS for public IP addresses, which don't require a virtual network link.
4648
- You can also forward DNS queries to a DNS resolver if the resolver's VNet is linked to the reverse zone.
47-
- Reverse zones must follow the naming guidelines described in this article and in [RFC 3172](https://www.rfc-editor.org/rfc/rfc3172.html).
49+
- Reverse zones must follow the naming guidelines described in this article and in [RFC 3172](https://www.rfc-editor.org/info/rfc3172).
4850

4951
## Create a reverse lookup DNS zone
5052

@@ -56,7 +58,7 @@ To create an IPv4 reverse DNS record in your zone, add the remaining IP address
5658
| --- | --- |
5759
| **Subscription** | Select your subscription.|
5860
| **Resource group** | Select or create a new resource group. |
59-
| **Name** | Enter a name for the DNS zone. In this example, the class C reverse DNS zone name 2.1.10.in-addr.arpa is used. |
61+
| **Name** | Enter a name for the DNS zone. In this example, the class C reverse DNS zone name **2.1.10.in-addr.arpa** is used. |
6062
| **Location** | Select the location for the resource group. The location is already be selected if you're using a previously created resource group. |
6163

6264
See the following example:

0 commit comments

Comments
 (0)