Searching for 38.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for 38.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 134 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
Searching for z.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for z.arin.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 154 ms
Searching for 38.116.200.207.in-addr.arpa. PTR record at z.arin.net. [199.180.180.63]
...took 93 msSearching for z.arin.net. A record at k.gtld-servers.net. [192.52.178.30] ...took 12 ms
Searching for z.arin.net. A record at ns2.arin.net. [199.71.0.108] ...took 154 ms
Searching for ns3.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns3.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42]
...took 155 msSearching for ns3.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 12 ms
Searching for ns3.yahoo.com. A record at ns4.yahoo.com. [98.138.11.157] ...took 127 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 268 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 125 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 274 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 134 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 11 ms
REFUSED
Searching for 38.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,664 ms