Searching for 238.116.200.207.in-addr.arpa. PTR record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for 238.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 206 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at d.in-addr-servers.arpa. [200.10.60.53] ...took 117 ms
Searching for x.arin.net. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 7 ms
Searching for x.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 93 ms
Searching for 238.116.200.207.in-addr.arpa. PTR record at x.arin.net. [199.180.180.63]
...took 89 msSearching for x.arin.net. A record at b.gtld-servers.net. [192.33.14.30] ...took 30 ms
Searching for x.arin.net. A record at ns1.arin.net. [199.212.0.108] ...took 93 ms
Searching for ns4.yahoo.com. A record at H.ROOT-SERVERS.NET. [198.97.190.53]
...took 6 ms
Searching for ns4.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 121 msSearching for ns4.yahoo.com. A record at l.gtld-servers.net. [192.41.162.30] ...took 12 ms
Searching for ns4.yahoo.com. A record at ns3.yahoo.com. [27.123.42.42] ...took 154 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 20 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 190 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 206 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 238.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,520 ms