Searching for 2.116.200.207.in-addr.arpa. PTR record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 6 ms
Searching for 2.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 129 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 27 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 266 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 129 ms
Searching for u.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for u.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 2.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 a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for u.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for ns3.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for ns3.yahoo.com. A record at i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
Searching for 2.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 i.gtld-servers.net. [192.43.172.30] ...took 7 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 27 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 265 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 266 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 2.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 117 ms
REFUSED
Searching for 2.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,484 ms