Searching for 204.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 204.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 12 ms
Searching for x.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for x.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for 204.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 94 msSearching for x.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 92 ms
Searching for ns3.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 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 ns1.yahoo.com. [68.180.131.16] ...took 12 ms
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 144 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 ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 178 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 191 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 7 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 204.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 130 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,238 ms