Searching for 201.116.200.207.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 6 ms
Searching for 201.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for z.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for z.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for 201.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 90 msSearching for z.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for ns1.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for ns1.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns1.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 19 msSearching for ns1.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 31 ms
Searching for ns1.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 201.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 201.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,373 ms