Searching for 231.116.200.207.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for 231.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 196 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for y.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for y.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for y.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for 231.116.200.207.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 5 msSearching for y.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 23 ms
Searching for y.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for ns5.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns5.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 184 msSearching for ns5.yahoo.com. A record at h.gtld-servers.net. [192.54.112.30] ...took 6 ms
Searching for ns5.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 196 ms
REFUSED
Searching for 231.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,353 ms