Searching for 42.168.146.124.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 13 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
Searching for rirns.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for rirns.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 32 ms
Searching for rirns.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53]
...took 100 msSearching for rirns.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 32 ms
Searching for rirns.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 153 ms
Searching for ns4.sphere.ad.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 13 ms
Searching for ns4.sphere.ad.jp. A record at e.dns.jp. [192.50.43.53] ...took 18 ms
Searching for ns4.sphere.ad.jp. A record at ns1.sphere.ad.jp. [202.239.113.19] ...took 268 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at ns4.sphere.ad.jp. [202.239.113.30]
...took 268 msSearching for ns4.sphere.ad.jp. A record at e.dns.jp. [192.50.43.53] ...took 18 ms
Searching for ns4.sphere.ad.jp. A record at ns1.sphere.ad.jp. [202.239.113.19] ...took 268 ms
Nameserver ns4.sphere.ad.jp. reports: No such host 42.168.146.124.in-addr.arpa.
Total elapsed query time: 996 ms