Searching for 0.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 0.100.163.152.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 248 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 182 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 248 ms
Searching for arin.authdns.ripe.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 15 ms
Searching for arin.authdns.ripe.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 90 ms
Searching for 0.100.163.152.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 12 msSearching for arin.authdns.ripe.net. A record at d.gtld-servers.net. [192.31.80.30] ...took 24 ms
Searching for arin.authdns.ripe.net. A record at rirns.arin.net. [199.253.249.53] ...took 90 ms
Searching for ns4.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns4.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 122 msSearching for ns4.yahoo.com. A record at m.gtld-servers.net. [192.55.83.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 122 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 182 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 148 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 170 ms
REFUSED
Searching for 0.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,489 ms