Searching for 138.100.163.152.in-addr.arpa. PTR record at I.ROOT-SERVERS.NET. [192.36.148.17]
...took 12 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 170 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 118 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at c.in-addr-servers.arpa. [196.216.169.10] ...took 170 ms
Searching for z.arin.net. A record at D.ROOT-SERVERS.NET. [199.7.91.13]
...took 11 ms
Searching for z.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 10 ms
Searching for z.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 88 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 155 msSearching for z.arin.net. A record at j.gtld-servers.net. [192.48.79.30] ...took 10 ms
Searching for z.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 88 ms
Searching for ns3.yahoo.com. A record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 19 ms
Searching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 5 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 143 msSearching for ns3.yahoo.com. A record at g.gtld-servers.net. [192.42.93.30] ...took 5 ms
Searching for ns3.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 118 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 142 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 138.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 5 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,715 ms