Searching for 218.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 218.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 174 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 183 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 174 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 k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for u.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 152 ms
Searching for 218.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 k.gtld-servers.net. [192.52.178.30] ...took 11 ms
Searching for u.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 k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16]
...took 9 msSearching for ns2.yahoo.com. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for ns2.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 183 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 188 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 218.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,361 ms