Searching for 166.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for 166.116.200.207.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 251 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 196 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 135 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 200 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
Searching for 166.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 40 ms
Searching for r.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for r.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for 166.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 97 msSearching for r.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for r.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for ns2.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for ns2.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns2.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 198 ms
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16]
...took 14 msSearching for ns2.yahoo.com. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for ns2.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 198 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 196 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 135 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 200 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 166.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,906 ms