Searching for 202.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 202.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 118 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 294 ms
Searching for u.arin.net. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 20 ms
Searching for u.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for 202.116.200.207.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 18 msSearching for u.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 90 ms
Searching for ns4.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 21 ms
Searching for ns4.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 121 msSearching for ns4.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns4.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 145 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 118 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 202.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,426 ms