Searching for 42.168.146.124.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for ns1.apnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns1.apnic.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 21 ms
Searching for ns1.apnic.net. A record at ns2.apnic.net. [203.119.95.53] ...took 230 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at ns1.apnic.net. [203.119.42.53]
...took 166 msSearching for ns1.apnic.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 21 ms
Searching for ns1.apnic.net. A record at ns2.apnic.net. [203.119.95.53] ...took 230 ms
Searching for ns3.sphere.ad.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns3.sphere.ad.jp. A record at d.dns.jp. [210.138.175.244] ...took 24 ms
Searching for ns3.sphere.ad.jp. A record at ns1.sphere.ad.jp. [202.239.113.19] ...took 282 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at ns3.sphere.ad.jp. [202.239.113.22]
...took 270 msSearching for ns3.sphere.ad.jp. A record at d.dns.jp. [210.138.175.244] ...took 24 ms
Searching for ns3.sphere.ad.jp. A record at ns1.sphere.ad.jp. [202.239.113.19] ...took 282 ms
Nameserver ns3.sphere.ad.jp. reports: No such host 42.168.146.124.in-addr.arpa.
Total elapsed query time: 1,331 ms