Searching for 176.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 176.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 169 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 206 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 169 ms
Searching for y.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for y.arin.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for y.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 176.116.200.207.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 7 msSearching for y.arin.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for y.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns2.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for ns2.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 13 ms
Searching for ns2.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16]
...took 6 msSearching for ns2.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 13 ms
Searching for ns2.yahoo.com. A record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 131 ms
REFUSED
Searching for 176.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 206 ms
REFUSED
Searching for 176.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,242 ms