Searching for 239.116.200.207.in-addr.arpa. PTR record at B.ROOT-SERVERS.NET. [192.228.79.201]
...took 22 ms
Searching for 239.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 215 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at a.in-addr-servers.arpa. [199.180.182.53] ...took 93 ms
Searching for arin.authdns.ripe.net. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 7 ms
Searching for arin.authdns.ripe.net. A record at l.gtld-servers.net. [192.41.162.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 16 ms
Searching for 239.116.200.207.in-addr.arpa. PTR record at arin.authdns.ripe.net. [193.0.9.10]
...took 11 msSearching for arin.authdns.ripe.net. A record at l.gtld-servers.net. [192.41.162.30] ...took 13 ms
Searching for arin.authdns.ripe.net. A record at ns4.apnic.net. [202.12.31.53] ...took 16 ms
Searching for ns4.yahoo.com. A record at E.ROOT-SERVERS.NET. [192.203.230.10]
...took 6 ms
Searching for ns4.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 183 ms
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157]
...took 126 msSearching for ns4.yahoo.com. A record at j.gtld-servers.net. [192.48.79.30] ...took 11 ms
Searching for ns4.yahoo.com. A record at ns5.yahoo.com. [202.165.97.53] ...took 183 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 6 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 215 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns1.yahoo.com. [68.180.131.16] ...took 12 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns4.yahoo.com. [98.138.11.157] ...took 126 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns3.yahoo.com. [27.123.42.42] ...took 155 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns5.yahoo.com. [202.165.97.53] ...took 187 ms
REFUSED
Searching for 239.116.200.207.in-addr.arpa. PTR record at ns2.yahoo.com. [68.142.255.16] ...took 14 ms
REFUSED
None of the nameservers responded correctly.
Total elapsed query time: 1,370 ms