Searching for 64.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 175 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 177 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
Searching for r.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for r.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for r.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 160 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 91 msSearching for r.arin.net. A record at f.gtld-servers.net. [192.35.51.30] ...took 7 ms
Searching for r.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 160 ms
Searching for ns5.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns5.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 29 ms
Searching for ns5.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 179 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53]
...took 174 msSearching for ns5.yahoo.com. A record at d.gtld-servers.net. [192.31.80.30] ...took 29 ms
Searching for ns5.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 179 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 175 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 177 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 10 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,619 ms