Searching for 8.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 187 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
Searching for r.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for r.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 38 ms
Searching for r.arin.net. A record at u.arin.net. [204.61.216.50] ...took 19 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 93 msSearching for r.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 38 ms
Searching for r.arin.net. A record at u.arin.net. [204.61.216.50] ...took 19 ms
Searching for ns3.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 37 ms
Searching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 21 ms
Searching for ns3.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 185 msSearching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 21 ms
Searching for ns3.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 8.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 187 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,332 ms