Searching for 42.168.146.124.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for ns1.apnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1.apnic.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns1.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at ns1.apnic.net. [203.119.42.53]
...took 239 msSearching for ns1.apnic.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns1.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for ns4.sphere.ad.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns4.sphere.ad.jp. A record at g.dns.jp. [203.119.40.1] ...took 264 ms
Searching for ns4.sphere.ad.jp. A record at penguin.kddnet.ad.jp. [210.132.91.129] ...took 259 ms
Searching for 42.168.146.124.in-addr.arpa. PTR record at ns4.sphere.ad.jp. [202.239.113.30]
...took 258 msSearching for ns4.sphere.ad.jp. A record at g.dns.jp. [203.119.40.1] ...took 264 ms
Searching for ns4.sphere.ad.jp. A record at penguin.kddnet.ad.jp. [210.132.91.129] ...took 259 ms
Nameserver ns4.sphere.ad.jp. reports: No such host 42.168.146.124.in-addr.arpa.
Total elapsed query time: 1,098 ms