Searching for 2.241.240.134.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 34 ms
Searching for 2.241.240.134.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 300 ms
Searching for 2.241.240.134.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 300 ms
Searching for r.arin.net. A record at F.ROOT-SERVERS.NET. [192.5.5.241]
...took 6 ms
Searching for r.arin.net. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for 2.241.240.134.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 90 msSearching for r.arin.net. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for ns02.army.mil. A record at J.ROOT-SERVERS.NET. [192.58.128.30]
...took 34 ms
Searching for ns02.army.mil. A record at con1.nipr.mil. [199.252.157.234] ...took 132 ms
Searching for ns02.army.mil. A record at NS01.ARMY.MIL. [140.153.43.44] ...took 131 ms
Searching for 2.241.240.134.in-addr.arpa. PTR record at ns02.army.mil. [192.82.113.7]
...took 136 msSearching for ns02.army.mil. A record at con1.nipr.mil. [199.252.157.234] ...took 132 ms
Searching for ns02.army.mil. A record at NS01.ARMY.MIL. [140.153.43.44] ...took 131 ms
Nameserver ns02.army.mil. reports: No such host 2.241.240.134.in-addr.arpa.
Total elapsed query time: 967 ms