Searching for 232.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for 232.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 90 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 166 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 196 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 176 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 90 ms
Searching for z.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for z.arin.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 13 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for 232.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 k.gtld-servers.net. [192.52.178.30] ...took 13 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for ns3.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for ns3.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 183 ms
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 184 msSearching for ns3.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 23 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 183 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 166 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 196 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 176 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 232.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,679 ms