Searching for 170.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 170.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 215 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
Searching for 170.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 H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for r.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for r.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for 170.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 93 msSearching for r.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for r.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for ns2.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 5 ms
Searching for ns2.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16]
...took 5 msSearching for ns2.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 215 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 170.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 186 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,433 ms