Searching for 7.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 7.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 133 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for arin.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for 7.116.200.207.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 11 msSearching for arin.authdns.ripe.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 17 ms
Searching for ns5.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns5.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 179 msSearching for ns5.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns5.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 133 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 7.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,052 ms