Searching for 2.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for 2.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 184 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
Searching for x.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for x.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for 2.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 91 msSearching for x.arin.net. A record at c.gtld-servers.net. [192.26.92.30] ...took 24 ms
Searching for x.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 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 g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
Searching for 2.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 g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 189 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 184 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,529 ms