Searching for 234.39.43.218.in-addr.arpa. PTR record at A.ROOT-SERVERS.NET. [198.41.0.4]
...took 7 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 256 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 256 ms
Searching for ns2.apnic.net. A record at A.ROOT-SERVERS.NET. [198.41.0.4]
...took 7 ms
Searching for ns2.apnic.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns2.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 17 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at ns2.apnic.net. [203.119.95.53]
...took 6 msSearching for ns2.apnic.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for ns2.apnic.net. A record at apnic.authdns.ripe.net. [193.0.9.9] ...took 17 ms
Searching for e.dns.jp. A record at J.ROOT-SERVERS.NET. [192.58.128.30]
...took 30 ms
Searching for e.dns.jp. A record at f.dns.jp. [150.100.6.8] ...took 263 ms
Searching for e.dns.jp. A record at nsg.dns.jp. [203.119.40.4] ...took 245 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at e.dns.jp. [192.50.43.53]
...took 17 msSearching for e.dns.jp. A record at f.dns.jp. [150.100.6.8] ...took 263 ms
Searching for e.dns.jp. A record at nsg.dns.jp. [203.119.40.4] ...took 245 ms
Searching for ns-kn001.ocn.ad.jp. A record at A.ROOT-SERVERS.NET. [198.41.0.4]
...took 6 ms
Searching for ns-kn001.ocn.ad.jp. A record at h.dns.jp. [161.232.72.25] ...took 12 ms
Searching for ns-kn001.ocn.ad.jp. A record at ns1.ocn.ad.jp. [202.234.232.202] ...took 260 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at ns-kn001.ocn.ad.jp. [211.129.12.50]
...took 257 msSearching for ns-kn001.ocn.ad.jp. A record at h.dns.jp. [161.232.72.25] ...took 12 ms
Searching for ns-kn001.ocn.ad.jp. A record at ns1.ocn.ad.jp. [202.234.232.202] ...took 260 ms
Nameserver ns-kn001.ocn.ad.jp. reports: No such host 234.39.43.218.in-addr.arpa.
Total elapsed query time: 1,407 ms