Searching for 174.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 174.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 168 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 168 ms
Searching for u.arin.net. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 18 ms
Searching for u.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 96 ms
Searching for 174.116.200.207.in-addr.arpa. PTR record at u.arin.net. [204.61.216.50]
...took 6 msSearching for u.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for u.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 96 ms
Searching for ns3.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 155 msSearching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 185 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 174.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 203 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,342 ms