Searching for 130.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 130.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 92 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 16 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 16 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 92 ms
Searching for z.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for z.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 146 ms
Searching for 130.100.163.152.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 93 msSearching for z.arin.net. A record at e.gtld-servers.net. [192.12.94.30] ...took 24 ms
Searching for z.arin.net. A record at ns3.arin.net. [199.5.26.108] ...took 146 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 m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 145 msSearching for ns3.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 13 ms
Searching for ns3.yahoo.com. A record at ns1.yahoo.com. [68.180.131.16] ...took 13 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 16 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 16 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 144 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 119 ms
REFUSED
Searching for 130.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 194 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,386 ms