Searching for 0.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 166 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 184 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 166 ms
Searching for y.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 39 ms
Searching for y.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for y.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 7 msSearching for y.arin.net. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for y.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 143 ms
Searching for ns1.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 40 ms
Searching for ns1.yahoo.com. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns1.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 195 ms
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 13 msSearching for ns1.yahoo.com. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns1.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 195 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 184 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 0.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 186 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,677 ms