Searching for 137.100.163.152.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 89 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 281 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 272 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 89 ms
Searching for y.arin.net. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 30 ms
Searching for y.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 151 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at y.arin.net. [192.82.134.30]
...took 7 msSearching for y.arin.net. A record at a.gtld-servers.net. [192.5.6.30] ...took 24 ms
Searching for y.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 151 ms
Searching for ns3.yahoo.com. A record at K.ROOT-SERVERS.NET. [193.0.14.129]
...took 32 ms
Searching for ns3.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 290 ms
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 154 msSearching for ns3.yahoo.com. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for ns3.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 290 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 281 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 19 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 124 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 272 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 121 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 137.100.163.152.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,809 ms