Searching for 64.116.200.207.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 90 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 134 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 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 ns5.yahoo.com. [202.165.97.53] ...took 273 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 90 ms
Searching for x.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for x.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 99 msSearching for x.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for ns1.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 6 ms
Searching for ns1.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 12 msSearching for ns1.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns1.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 134 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 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 ns5.yahoo.com. [202.165.97.53] ...took 273 ms
REFUSED
Searching for 64.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 9 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,609 ms