Searching for 234.39.43.218.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 277 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 277 ms
Searching for ns2.apnic.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns2.apnic.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns2.apnic.net. A record at ns2.apnic.net. [203.119.95.53] ...took 7 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 k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns2.apnic.net. A record at ns2.apnic.net. [203.119.95.53] ...took 7 ms
Searching for f.dns.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for f.dns.jp. A record at b.dns.jp. [202.12.30.131] ...took 238 ms
Searching for f.dns.jp. A record at nsd.dns.jp. [210.138.175.245] ...took 25 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at f.dns.jp. [150.100.6.8]
...took 254 msSearching for f.dns.jp. A record at b.dns.jp. [202.12.30.131] ...took 238 ms
Searching for f.dns.jp. A record at nsd.dns.jp. [210.138.175.245] ...took 25 ms
Searching for ns-kn001.ocn.ad.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns-kn001.ocn.ad.jp. A record at d.dns.jp. [210.138.175.244] ...took 20 ms
Searching for ns-kn001.ocn.ad.jp. A record at ns1.ocn.ad.jp. [202.234.232.202] ...took 253 ms
Searching for 234.39.43.218.in-addr.arpa. PTR record at ns-kn001.ocn.ad.jp. [211.129.12.50]
...took 255 msSearching for ns-kn001.ocn.ad.jp. A record at d.dns.jp. [210.138.175.244] ...took 20 ms
Searching for ns-kn001.ocn.ad.jp. A record at ns1.ocn.ad.jp. [202.234.232.202] ...took 253 ms
Nameserver ns-kn001.ocn.ad.jp. reports: No such host 234.39.43.218.in-addr.arpa.
Total elapsed query time: 1,404 ms