Searching for 122.199.47.199.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 122.199.47.199.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 203 ms
Searching for 122.199.47.199.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 203 ms
Searching for r.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for r.arin.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 94 ms
Searching for 122.199.47.199.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 159 msSearching for r.arin.net. A record at g.gtld-servers.net. [192.42.93.30] ...took 6 ms
Searching for r.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 94 ms
Searching for ns4.wansecurity.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns4.wansecurity.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 6 ms
Searching for ns4.wansecurity.com. A record at ns5.wansecurity.com. [199.47.193.253] ...took 169 ms
Searching for 122.199.47.199.in-addr.arpa. PTR record at ns4.wansecurity.com. [199.47.197.253]
...took 260 msSearching for ns4.wansecurity.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 6 ms
Searching for ns4.wansecurity.com. A record at ns5.wansecurity.com. [199.47.193.253] ...took 169 ms
Nameserver ns4.wansecurity.com. reports: No such host 122.199.47.199.in-addr.arpa.
Total elapsed query time: 941 ms