Searching for 213.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 213.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at b.in-addr-servers.arpa. [199.253.183.183] ...took 6 ms
Searching for r.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 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 u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 213.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 90 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 u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns4.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for ns4.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 126 msSearching for ns4.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 184 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 213.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,336 ms