Searching for 119.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 119.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 251 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 216 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 211 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 251 ms
Searching for r.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for r.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 23 ms
Searching for r.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 119.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 92 msSearching for r.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 23 ms
Searching for r.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns1.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns1.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 11 msSearching for ns1.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 216 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 120 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 211 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 119.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,595 ms