Searching for 6.116.200.207.in-addr.arpa. PTR record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for 6.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 89 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 276 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 89 ms
Searching for arin.authdns.ripe.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for arin.authdns.ripe.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns3.afrinic.net. [204.61.216.100] ...took 6 ms
Searching for 6.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 j.gtld-servers.net. [192.48.79.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns3.afrinic.net. [204.61.216.100] ...took 6 ms
Searching for ns1.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 31 ms
Searching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 20 msSearching for ns1.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 276 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 6.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,392 ms