Searching for 138.100.163.152.in-addr.arpa. PTR record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 250 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 171 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 180 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at e.in-addr-servers.arpa. [203.119.86.101] ...took 250 ms
Searching for z.arin.net. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for z.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 7 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 91 msSearching for z.arin.net. A record at i.gtld-servers.net. [192.43.172.30] ...took 6 ms
Searching for z.arin.net. A record at u.arin.net. [204.61.216.50] ...took 7 ms
Searching for ns1.yahoo.com. A record at M.ROOT-SERVERS.NET. [202.12.27.33]
...took 14 ms
Searching for ns1.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16]
...took 20 msSearching for ns1.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns1.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 171 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 123 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 150 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 13 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 180 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,524 ms