From 821620167b9c58f2a1c1ee9a65305afca322d4e5 Mon Sep 17 00:00:00 2001 From: caowei Date: Tue, 14 Nov 2017 10:42:59 +0800 Subject: [PATCH] Update PTR Record example * 192.0.2.12 --> example.org. * example.org. --> 192.0.2.12 * RPC 12.2.0.192.in-addr.arpa. Change-Id: I609983a5f66614aeba36da63ac9a8446c70b4e18 --- doc/source/user/manage-ptr-records.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/user/manage-ptr-records.rst b/doc/source/user/manage-ptr-records.rst index 5e43601c5..b395ade2f 100644 --- a/doc/source/user/manage-ptr-records.rst +++ b/doc/source/user/manage-ptr-records.rst @@ -27,7 +27,7 @@ addresses to a domain. For example, .. code-block:: bash - $ dig -x 192.0.2.5 +short + $ dig -x 192.0.2.12 +short example.org. The way this works in the DNS system is through the `in-addr.arpa.` @@ -47,10 +47,10 @@ zone. For example ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: - ;12.55.168.192.in-addr.arpa. IN PTR example.org. + ;12.2.0.192.in-addr.arpa. IN PTR example.org. ;; AUTHORITY SECTION: - 12.55.168.192.in-addr.arpa. 3600 IN NS ns1.example.org. + 12.2.0.192.in-addr.arpa. 3600 IN NS ns1.example.org. ;; Query time: 40 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) @@ -58,7 +58,7 @@ zone. For example ;; MSG SIZE rcvd: 119 In the question section we see the address being requested from the -DNS system as `12.55.168.192.in-addr.arpa.`. As you can see, the IP +DNS system as `12.2.0.192.in-addr.arpa.`. As you can see, the IP address has been reversed in order to function similarly to a domain name where the more specific elements come first. The reversed IP address is then added to the `in-addr.arpa.` domain, at which point