Searching for 38.143.173.220.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 25 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 170 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at I.ROOT-SERVERS.NET. [192.36.148.17] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53] ...took 5 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 167 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53] ...took 156 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 243 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 14 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 14 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 243 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 155 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 244 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 170 ms
Searching for apnic.authdns.ripe.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for apnic.authdns.ripe.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for apnic.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9]
...took 11 msSearching for apnic.authdns.ripe.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 11 ms
Searching for apnic.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for ns.gxnnptt.net.cn. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns.gxnnptt.net.cn. A record at e.dns.cn. [203.119.29.1] ...took 22 ms
Searching for ns.gxnnptt.net.cn. A record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 240 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69]
...took 246 msSearching for ns.gxnnptt.net.cn. A record at e.dns.cn. [203.119.29.1] ...took 22 ms
Searching for ns.gxnnptt.net.cn. A record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 240 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at I.ROOT-SERVERS.NET. [192.36.148.17] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for ns.lzptt.gx.cn. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 25 ms
Searching for ns.lzptt.gx.cn. A record at b.dns.cn. [203.119.26.1] ...took 19 ms
Searching for ns.lzptt.gx.cn. A record at ns.lzptt.gx.cn. [202.103.225.70] ...took 248 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.lzptt.gx.cn. [202.103.225.70]
...took 238 msSearching for ns.lzptt.gx.cn. A record at b.dns.cn. [203.119.26.1] ...took 19 ms
Searching for ns.lzptt.gx.cn. A record at ns.lzptt.gx.cn. [202.103.225.70] ...took 248 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53] ...took 5 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 167 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at rirns.arin.net. [199.253.249.53] ...took 156 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 243 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33] ...took 14 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 14 ms
Searching for ns2.apnic.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for ns2.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 6 ms
Searching for ns2.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 191 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns2.apnic.net. [203.119.95.53]
...took 5 msSearching for ns2.apnic.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 6 ms
Searching for ns2.apnic.net. A record at ns1.apnic.net. [203.119.42.53] ...took 191 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 243 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13] ...took 11 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 155 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at apnic.authdns.ripe.net. [193.0.9.9] ...took 12 ms
Searching for 38.143.173.220.in-addr.arpa. PTR record at ns.gxnnptt.net.cn. [202.103.224.69] ...took 244 ms
Too many delegations to other servers. Probably a loop.
Total elapsed query time: 2,808 ms