Searching for 254.230.222.122.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 254.230.222.122.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 116 ms
Searching for 254.230.222.122.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 116 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 j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for rirns.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 93 ms
Searching for 254.230.222.122.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53]
...took 96 msSearching for rirns.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for rirns.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 93 ms
Searching for ns1.vectant.ne.jp. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1.vectant.ne.jp. A record at h.dns.jp. [161.232.72.25] ...took 11 ms
Searching for ns1.vectant.ne.jp. A record at ns1.vectant.ne.jp. [163.139.230.164] ...took 245 ms
Searching for 254.230.222.122.in-addr.arpa. PTR record at ns1.vectant.ne.jp. [163.139.230.164]
...took 246 msSearching for ns1.vectant.ne.jp. A record at h.dns.jp. [161.232.72.25] ...took 11 ms
Searching for ns1.vectant.ne.jp. A record at ns1.vectant.ne.jp. [163.139.230.164] ...took 245 ms
| Domain | Type | TTL | Answer |
|---|---|---|---|
| 254.230.222.122.in-addr.arpa. | PTR | 3600 | 122-222-230-254.tokyo.otk.vectant.ne.jp. |
Total elapsed query time: 861 ms