Searching for 243.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 243.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 174 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 174 ms
Searching for y.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for y.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 25 ms
Searching for y.arin.net. A record at u.arin.net. [204.61.216.50] ...took 6 ms
Searching for 243.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 e.gtld-servers.net. [192.12.94.30] ...took 25 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 M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for ns2.yahoo.com. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
Searching for 243.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 a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 172 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 173 ms
REFUSED
Searching for 243.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,237 ms