Searching for 30.116.200.207.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for 30.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at f.in-addr-servers.arpa. [193.0.9.1] ...took 11 ms
Searching for r.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for r.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for r.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for 30.116.200.207.in-addr.arpa. PTR record at r.arin.net. [199.180.180.63]
...took 93 msSearching for r.arin.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for r.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 156 ms
Searching for ns3.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns3.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 150 msSearching for ns3.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 136 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 177 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 129 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 149 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 30.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 174 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,479 ms